Sheet 07
Artifact library
A program is only as durable as its records. These are the fifteen artifacts this operating model runs on — each with its purpose, its owner, its retention, every required field with the guidance that makes the field answerable, and a worked example filled in with the sample record set.
About these templates
These are demonstration templates written for a fictional organization. They are a starting structure, not a compliance product — a real implementation would be adapted with the functional owners who have to live with each one.
What downloads, and what it contains
4 generated from live records
The use-case register, tool inventory, decision log, and exception log export as CSV built from this site’s sample records at the moment you click — the same rows the page is showing, not a stored file. Each also offers the same columns with no rows, as a blank starting point.
11 documents, worksheets, and forms
These carry a written worked example on the page and download as a blank template with every field and its guidance — a standalone HTML file you can fill in or print. Each detail page also prints clean, without navigation or download controls, so “Save as PDF” produces a usable document.
Every button on this site produces a real file. There are no placeholder downloads.
The library
Fifteen artifacts across five formats. Select one for its fields, its guidance, its worked example, and its downloads.
Showing 15 of 15 artifacts — no filters applied
- ART-01RegisterGenerated from live records
AI use-case register
The single list of every AI use case anyone has proposed, in progress, or running. If it is not here, the program cannot support it and leadership cannot see it.
9 fields · owned by AI Program Manager
- ART-02RegisterGenerated from live records
AI tool and vendor inventory
What is approved, for whom, for what data, with what conditions, and when it was last reviewed. The answer to 'can I use this?' lives here.
8 fields · owned by AI Program Manager with IT & Security
- ART-03LogGenerated from live records
Decision log
What was decided, by whom, why, and what was considered and rejected. This is what makes the program defensible a year later when the people involved have moved on.
8 fields · owned by AI Program Manager maintains it; the decision owner approves the entry.
- ART-04LogGenerated from live records
Exception log
Every deviation from published guidance, with compensating controls and an expiry date. Exceptions are normal; undocumented and permanent ones are not.
6 fields · owned by AI Program Manager maintains it; the approving function owns the exception.
- ART-05Document
Pilot charter
One page that fixes scope, participants, guardrails, measures, and a decision date before anyone starts. The decision date is the field that matters most.
7 fields · owned by Business owner, drafted with the AI Program Manager
- ART-06Worksheet
Responsible-use review checklist
The questions a reviewer works through, with the answers recorded. It exists so reviews are consistent between reviewers and legible to the requester afterward.
8 fields · owned by AI Program Manager coordinates; each function answers its own section.
- ART-07Worksheet
Vendor evaluation worksheet
Structured, comparable criteria for evaluating a tool or vendor, so decisions rest on the same questions each time and the gaps are visible.
8 fields · owned by AI Program Manager coordinates; Security, Risk, and Finance own their sections.
- ART-08Document
Human-oversight plan
Turns 'a human reviews it' into a named role performing a specific check at a defined frequency with the authority to override. Without those four elements, oversight is a claim rather than a control.
7 fields · owned by Business owner
- ART-09Worksheet
Pilot measurement plan
Defines what will be measured, against what baseline, by whom, and how good the evidence will be — agreed before the pilot starts so the result cannot be reverse-engineered afterward.
7 fields · owned by Business owner with the AI Program Manager
- ART-10Document
Governance meeting agenda
A standing agenda built around decisions rather than status, so the committee's hour is spent on things only the committee can do.
6 fields · owned by AI Program Manager prepares; Director of Technology chairs.
- ART-11Document
Leadership status report
What leadership needs to decide, what the program learned, and what is not yet known — in two pages, with evidence labels on every number.
6 fields · owned by AI Program Manager
- ART-12Form
Training feedback form
Short enough that people finish it, and pointed enough to change the next session. Feedback that only produces a satisfaction score changes nothing.
6 fields · owned by AI Program Manager
- ART-13Document
AI champion role description
Defines what a champion is, what they are not, and what they get for the two hours a month. Written so a manager can approve the time.
6 fields · owned by AI Program Manager
- ART-14Register
Prompt and agent record
A record for any prompt, agent, or automation that colleagues will rely on — what it does, what it assumes, how it was tested, and who maintains it. Reusable resources are only reusable if someone can find and trust them.
8 fields · owned by The author, with the AI Program Manager maintaining the register
- ART-15Worksheet
AI system retirement checklist
Retirement is a lifecycle stage, not an accident. This covers what happens to the data, the records, the people using it, and the work it was producing.
8 fields · owned by AI Program Manager coordinates; the tool or business owner executes.