Governance rules exist. Staff behaviour is somewhere else. I build and deliver role-specific AI operating literacy from your own approved tools, data rules, and governance outputs — not a generic AI course.
Most businesses now have a governance policy and an approved tool list. Most staff are still using AI the way they always have — without clear rules, without role-specific judgment, and without a reliable way to know when their output needs checking.
Generic AI training does not close that gap. A half-day workshop on hallucination or a vendor-run session on prompt writing does not tell your operations team what to do when an AI-generated document looks right but might not be. It does not tell your client delivery staff which data they are allowed to use with which tool.
This program is built entirely from your governance outputs: the approved-tools list, data rules, risk categories, and human review obligations from Service 03. Content is segmented by role, delivered in cohort sessions, and leaves behind artefacts the business keeps and uses. Not a slide deck.
Every session built from your governance. Every cohort trained on what applies to them. Every artefact the business keeps and uses after the program ends.
This layout is for explaining a service as a repeatable operating shape: who it is for, how the work moves, and what the client leaves with.
Governance rules, approved tools, and data-sharing limits are in place. Now the question is whether staff actually understand what those rules mean for their specific work.
The policy exists but staff are still using unapproved tools, pasting sensitive data into consumer tools, or treating AI output as final without review. The gap is operating practice, not more rules.
A one-off workshop fades. Role-specific AI use cards, an internal playbook section, and a staff onboarding brief remain in the business and can be used to train future staff without running the full program again.
Review Service 03 outputs: approved tools, data rules, risk categories, and human review obligations. Define the role cohorts and build the content framework — what each cohort needs to know.
Week 01For each cohort, build role-specific session content and 3–5 practical scenarios drawn from real tasks, actual risk categories, and the client's own governance rules. No generic AI ethics exercises.
Week 02Run facilitated sessions for each role group — 90 to 120 minutes each. Scenario-based, discussion-led, grounded in the client's actual rules and workflows. Distribute AI use cards at close.
Weeks 03–04Finalise the internal playbook section and staff onboarding brief. Brief the named internal owner on maintenance. Deliver the Session Summary and Gaps Report.
Week 04–05One card per cohort. What tools are approved, for what tasks, with what data, and when human review is required. Designed for desk reference, not filing.
Staff have a permanent reference for daily decisions — not a training memory that fades.
Plain-English guidance on what good AI-assisted work looks like in this business: how to verify outputs, how to escalate, and what accountability means in practice.
Keeps operating standards consistent as staff and workflows change.
A structured brief covering approved tools, review obligations, and escalation paths — designed for a manager to use when onboarding new staff.
Makes the program self-sustaining without repeating it.
What the sessions surfaced about actual staff understanding, outstanding governance gaps, and recommended follow-up actions.
Gives leadership an honest view of where operating practice still needs work.