What you can put into practice
- A tailored staff policy, owner procedure and contact card.
- A workflow inventory and scoped approval records.
- Configuration evidence and claim-by-claim output review records.
- Separate records for exceptions, suspected incidents and changes.
- Training observations and periodic reviews with follow-through actions.
Where this guidance helps
- Introduce a first, narrowly defined AI workflow with named owners and a manual fallback.
- Document existing AI use and distinguish approved workflows from unapproved activity.
- Turn broad policy statements into observable input, account, review and reporting rules.
- Train staff through realistic decisions, corrections and recorded observations.
Tools you can adapt
Editable documents Staff policy, owner procedure and contact card. Spreadsheet-ready records Use register, use approval, configuration, output review, exception, incident, training, change and periodic review. CSV files contain no formulas or macros. Markdown files are editable text. Keep blank templates separate from the completed fictional examples.Fictional examples, practical decisions
Case A: a six-person studio. Work through an approval packet, a flawed draft and corrected output, training remediation, a denied exception and three change decisions. Case B: a service business. Follow the discovery of unapproved use, an incident with unresolved assessment, a narrower alternative, corrected complaint output and retraining. Both cases are fictional. Their completed records illustrate the process; they are not evidence about your organization.Inside the handbook
View the handbook contents +
- What this handbook helps you finish
- Establish authority before writing rules
- Find actual use and the unmet business need
- Classify decisions with observable boundaries
- Adoptable model staff policy
- Owner procedure from request to retirement
- Build an approval record that someone else can audit
- Make account and information boundaries observable
- Set up safe practice before live use
- Review outputs as claims and consequences
- Handle exceptions and suspected incidents differently
- Case A: the six-person studio input and decision packet
- Case A: flawed draft, corrected output and review evidence
- Case A: three changes and an evidence-based closeout
- Case B: a service business discovers shadow use
- Case B: redesign, rejection and retraining
- Staff self-paced learning path
- Reviewer and manager learning path
- Administrator learning path and handoff
- Troubleshoot the policy where work actually breaks
- Roll out, maintain and measure without creating busywork
- Use the toolkit and understand the evidence limits