AI Governance
Set the rules for the ReturnGuide pilot
Give an AI pilot accountable owners, boundaries, evidence requirements, and a way to stop.
- Each attempt samples six questions from a bank of eight. The pass mark is 80%, so you need at least five correct answers out of six.
- Feedback points you to the relevant chapter sections. You can review the chapter and retake the assessment.
- Each chapter’s pass status depends on its assessment result. Course completion requires all twelve chapter assessment passes and instructor approval of your final ReturnGuide project.
- Use the project workspace to build one pilot-decision pack through the chapters. Save each checkpoint, then send the final pack for review. The separate practice exercises and self-checks can help you prepare it.
- No class attendance or panel is required. The instructor reviews your final project online. If changes are requested, revise your work and send a new version.
- Assessments do not inspect practical work or notes, verify legal compliance, or certify professional competence. The completion record does not certify an organisation’s compliance or replace a recognised professional credential.
| Words you need | What it means here |
|---|---|
| Governance | Who can make decisions about a system, what evidence they need, and who answers for the result. |
| Pilot and synthetic examples | A pilot is a limited trial before wider use. Synthetic examples are made-up questions or records used for testing. |
| Scope | The boundaries of a use: which people, data, tasks, and actions are included or excluded. |
| Control | A rule, design feature, or working step intended to reduce a risk, such as blocking access to another account. |
| Residual risk | The risk left after controls are in place. Judging it requires evidence that those controls work. |
| Assurance | Checking whether evidence supports a claim, such as a claim that private records stay private. |
By the end of this chapter
- Distinguish a governance decision from a policy statement.
- Assign responsibility and approval authority for a bounded pilot.
- Distinguish law, voluntary risk frameworks, and management-system standards.
- Write a usable governance charter with evidence and escalation.
Define the proposed ReturnGuide pilot
The service head asks, “Who can tell me we are ready?” An enthusiastic demo cannot answer that question. Someone must define the approved purpose and the evidence needed. Name who can accept the remaining risk. State what happens if the conditions are not met. These arrangements are the beginning of governance.
Give people authority to approve or stop use
An AI policy might say that systems must be fair, secure, and transparent. Governance turns that direction into decisions. Name who assesses a proposal and who can approve a defined use. State what evidence the approver must inspect, what they can refuse, and who can pause use later. A committee needs a decision to make. It also needs the information and authority to make it.
These activities overlap, but each has a different job:
- Risk management analyses possible harm and chooses how to respond.
- Governance establishes how those choices become authorised decisions and remain accountable.
- Delivery puts the controls into practice.
- Assurance challenges whether the claims and evidence are adequate.
Keep the responsibilities clear. A control owner should not simply approve their own unsupported claim.
Permission to run a staff-only test with synthetic data covers that test. It does not authorise real customer records, sending messages, or expansion to a new market. Record the approval conditions so a later reader can tell exactly what was allowed.
Propose, assess, decide, and operate
- 1Propose
State purpose, users, scope, and alternatives.
- 2Assess
Collect evidence and examine harms and constraints.
- 3Decide
Approve, restrict, hold, or reject within named authority.
- 4Operate
Monitor conditions and escalate changes or failures.
Name the people responsible for each decision
| Role in the case | Responsibility | Decision boundary |
|---|---|---|
| Dana, service head | Own the business purpose and resource the service. | Accept only the residual exposure within delegated organisational authority. |
| Maya, product owner | Keep scope, inventory, controls, and decision records current. | Cannot waive privacy, security, or other mandatory requirements. |
| Imani and Leon, privacy and security leads | Challenge data use and technical protections. | Escalate unmet requirements; specialist advice must reach the approver. |
| Noor, evaluation lead; Ellis, operations lead | Produce testing evidence and maintain operating readiness. | Can recommend a hold; Ellis can invoke the agreed containment plan. |
| Priya, independent reviewer | Challenge the evidence without owning the implementation. | Documents findings and verifies important corrective actions. |
The responsibility table must name who can stop an unsafe use. It must also explain what happens if the sponsor disagrees with a specialist. Give unresolved concerns an escalation route to someone with enough authority. Record the disagreement and how it was handled. Attending a meeting does not imply approval.
Compare three tools: NIST, ISO, and law
NIST AI RMF 1.0 is a voluntary risk-management framework: a structure for organising this work. Its four functions are Govern, Map, Measure, and Manage. The Playbook offers suggestions to tailor to the context. It is not a checklist that must be completed in full. These references help organise the work; they do not establish that a product complies with every applicable law.
ISO/IEC 42001 concerns an organisational AI management system. These are the arrangements an organisation uses to direct and manage its AI activities. The public overview describes establishing and improving that system. It is different from a product quality score or a course certificate. This course discusses its purpose, not the text of its paid requirements. Laws and contracts create separate obligations. Check their applicability: whether they cover the actual organisation and use.
Write a one-page pilot charter
- Purpose: support agents locating current return policy; no automatic commitments.
- Scope: named staff, synthetic data, approved policy collection, named environment, and pilot period.
- Authority: approver, specialist reviewers, control owners, escalation contact, and pause operator.
- Evidence: inventory, data-flow map, risk record, evaluation, supplier review, and containment test.
- Gate: unresolved critical issues block the proposed exposure; exceptions need authority and a record.
- Change triggers: new data, users, geography, model, permissions, or actions require reassessment.
- Record: decision, conditions, dissent, evidence versions, expiry or review date, and owner.
Optional independent practice
Self-guided practice: write the pilot charter
Optional solo practice: use ReturnGuide or a non-sensitive fictional use case. Write a decision that could be approved or refused, then inspect every proposed action for a named decision owner and explicit boundary. Compare your draft with the model reasoning and self-check below; keep any revision in your own notes.
- One-page charter with the actual approval scope.
- Responsibility and escalation table.
- Decision record containing at least one condition and one reassessment trigger.
| Self-check | What your notes should show |
|---|---|
| Scope | Name the users, data, environment, source collection, permitted actions, and exclusions. |
| Authority | Identify who approves, who operates each control, and who can pause or escalate. |
| Evidence | Connect at least one approval condition to a record or test that could be inspected. |
| Change | State one material change that would require a new decision. |
Review the chapter and take the assessment
- Can someone tell which pilot actions remain prohibited?
- Does each important control and decision have a named owner?
- Can a specialist concern reach somebody able to pause or refuse exposure?
- Are framework alignment and legal compliance described as different claims?
Sources and further reading
- NIST AI Risk Management Framework 1.0
January 2023 edition, especially the Core and lifecycle context. NIST states that this edition is being revised; check the official resource centre for updates. References checked 16 November 2026.
- NIST AI RMF Playbook: Govern
See GOVERN 1 and 2 for policy, accountability, and documented responsibilities. Voluntary suggested practices, not a universal legal checklist. Checked 16 November 2026.
- ISO/IEC 42001:2023: public scope overview
Public overview only. This course does not reproduce the paid standard, interpret each clause, or confer conformity or certification. Checked 16 November 2026: the older /standard/81230.html address redirects to this canonical page.
Required project checkpoint
Write the ReturnGuide pilot charter
Turn the pilot idea into a decision with clear boundaries and owners.
Start with
Read the Northstar case and role table in Chapter 1. Start a single ReturnGuide project document. You need no external workbook or live organisation.
State the permitted use
Write that ReturnGuide retrieves approved return-policy passages and drafts a reply for staff review. Specify the synthetic-question learning boundary and small named staff group. Keep live customer records, external sending, refunds, and worker scoring in an explicit excluded section.
Expected result. A scope statement that a later reviewer can distinguish from general permission to use AI.
Assign the decisions
Use the existing role table. Put Dana against the permitted service decision, Maya against scope and records, and Ellis against the agreed containment route. Show where Imani, Leon, and Noor provide evidence or challenge. Do not let a role waive mandatory requirements.
Expected result. An owner and escalation record that identifies who can act, not just who attends a meeting.
Name evidence before approval
Choose an approval condition concerning source support or account access. Name the evaluation or control record needed to inspect it. At this stage label the check proposed, not passed.
Expected result. A condition linked to a specific missing evidence item.
Write the decision boundary
Draft conditional permission for the specified synthetic test or a hold while evidence is collected. State what would stop it and what change, such as live data or an action tool, needs a new decision.
Expected result. A bounded recommendation with a pause condition and reassessment trigger.
Review and save
Read the charter as service head and operations lead. Ask whether each could tell what is permitted and what to do if a condition fails. Revise one ambiguous phrase and keep the prior wording.
Expected result. The first project record, ready to constrain the inventory in Chapter 2.
Save these outputs
- Pilot charter containing scope, exclusions, authority, proposed evidence, conditions, pause route, and revision.
If you get stuck
- My decision says “approved to use AI.”
- Replace it with the actual users, data, source collection, actions, and conditions.
- I have no evidence yet.
- Say so. A proposed check or a hold is legitimate; an invented test pass is not.
Your checkpoint template
Record: Pilot charter Permitted users and purpose: Permitted data, sources, and actions: Excluded uses: Decision owner and authority: Control/evidence owners: Required evidence and current status: Conditional permission or hold: Pause owner and trigger: Reassessment trigger: Revision after self-review:
In the student classroom, save this checkpoint in the project workspace. After the final chapter, send the complete project for instructor review. This owner review shows the instructions; it does not save or send learner work.