Final assignment
- After the case studies
- about 3 hr
Where we are
In this course, you learned to govern AI one piece at a time: owners, an inventory, risk tiers, an impact assessment, policies, controls, evidence, a board and an incident decision. Each piece answered one question for Larkfield. Now you put them together into one governance pack that Larkfield’s board can adopt for its next year.
What you will be able to do
Bring the whole course together in one document: Larkfield’s AI governance pack for its next year. It says what Larkfield runs and who owns each system, how closely each one is checked, the rules for staff and for new AI work, the controls and their proof, and who decides. It ends with the plan for the next 90 days. A governance lead can hand this pack to a board and ask it to adopt it.
Before you startWhat to know and to have ready
What you need to know
- Modules 1 to 6. Each part below names the lessons that it uses.
- The case studies help, and the certificate needs one of them, so you may want to do one first. Learn from a public algorithm failure is an impact assessment from start to end (Part 2). Review a published AI register checks inventory rows and tiers (Part 1). A tribunal case about a chatbot’s answer turns gaps into controls with owners and evidence (Part 4).
What you need
- A browser and a document tool. No account, no installation and no money.
- The pack brief
final-assignment/governance-pack.md, and thetemplates/folder. You used every template in the module practices. - Your own answers to the module practices. They are your first draft: this assignment brings them up to date and makes them fit together.
- As a guide, about ten to fifteen pages. Tables count. A short pack with evidence beats a long pack without it.
The situation
Section titled “The situation”You are Farida, Larkfield’s risk and compliance lead. Nadia, the executive sponsor, asks for one pack that the board can adopt at its next meeting. She wants to know four things: what Larkfield runs, who owns it, what the rules are, and what changes in the next 90 days.
Larkfield, its people, its systems and every vendor answer are constructed for this course. The vendors TicketHarbor, MinuteMoss and LedgerFern are made up for this course. The numbers from earlier courses are recorded: they show what the records look like, not how good a model is today.
You did most of this work once, in the module practices. But later lessons changed some earlier answers. INC-07 showed that an approval step did not work, and that affects the impact assessment for request R-12. The vendor answers affect a request that the board had already approved. Read your module answers again with everything that you know now.
Label every number with the course’s labels: recorded, official source, assumption or constructed. A number that you calculated says what it was calculated from.
This is not legal advice. Your pack may name a law, but it never says what the law means for Larkfield. It says what to ask a lawyer.
The pack at a glance
Section titled “The pack at a glance”The pack has five parts. Each part reads the one before it: you cannot set controls before you know the tiers, and you cannot plan before you know the gaps.
Text description of the diagram
Part 1, inventory, owners and tiers, with a responsibility table: Who is accountable, Meet Larkfield’s AI portfolio, The AI inventory, and Risk tiers and proportionate controls. Part 2, one impact assessment for a high-tier system: Impact assessments, and the case study Learn from a public algorithm failure. Part 3, the acceptable-use policy and the build-and-buy policy, each tested with three “may I…?” questions: Acceptable use for staff, and Building and buying AI. Part 4, a vendor decision and a control map with evidence: Vendor and model checks, From policy to control, Documentation, and Evidence and audits. Part 5, the board’s terms of reference, one incident decision and a 90-day plan with measures: The governance board, Incidents, complaints and redress, and Measure governance. In every part, each legal statement has its official source and the date checked: A map of the landscape, The EU AI Act, and Canada, the US, the UK and others.
Part 1: inventory, owners and tiers
Section titled “Part 1: inventory, owners and tiers”Uses Who is accountable, Meet Larkfield’s AI portfolio, The AI inventory and Risk tiers and proportionate controls.
- Fill the inventory with one row for each of Larkfield’s eight systems: the built ones, the unregistered script and the features inside bought tools.
- Give each system a named person as its accountable owner. A team, a role or “platform” is not an owner.
- Score each system with the risk-tier table. Write the four scores, the sum, the tier and the rule that you used. Ask the two questions before you score.
- Where your tier differs from the registry, write which one is right and why.
- Fill a responsibility table for every medium-tier and high-tier system. Check: one name in every A cell.
- Write what happens now to any system that breaks the policy today, and who decides it.
Part 2: one impact assessment
Section titled “Part 2: one impact assessment”Uses Impact assessments and, as a full example, the case study Learn from a public algorithm failure.
- Choose a system that Part 1 puts in the high tier, or a planned change that moves a system into it. Request R-12 is one such change.
- Fill all seven sections of the impact assessment from the evidence pack. Each harm in section 4 says how likely it is and which record shows it.
- In section 6, give each control an owner and the evidence that it works.
- In section 7, write the decision, its conditions with their owners, and what would change the decision.
- Say who signs it and who reviews it. The person who asked for the change does not sign.
If you wrote R-12’s assessment in Module 3, read it again after INC-07 and the board meeting of Module 6. Some conditions may need to change.
Part 3: two policies, each tested
Section titled “Part 3: two policies, each tested”Uses Acceptable use for staff and Building and buying AI.
- Rewrite the draft acceptable-use policy on one page. It names an owner, who approves it and when it is reviewed. It lists the approved tools and the data classes with examples. It also says what a person checks, what is never allowed, how to ask, and what to do when something goes wrong.
- Make sure that the list of approved tools agrees with your vendor decision in Part 4.
- Fill the build-and-buy policy: the gates by tier, who decides at each gate, and the review of an AI feature in a bought tool.
- Write three “may I…?” questions for each policy, as staff or a team would really ask them. Answer each one from the policy alone. Write the line, or the gate and tier, that answers it.
- If an answer needs “ask someone”, change the policy until it does not.
Part 4: a vendor decision and a control map
Section titled “Part 4: a vendor decision and a control map”Uses Vendor and model checks, From policy to control, Documentation and Evidence and audits.
- Read the vendor answers against the vendor questionnaire. Mark each answer specific, vague, missing, against us or not in the contract.
- Decide on TicketHarbor and MinuteMoss: switch on, on with conditions, or keep off. Give each condition an owner, and close first the gaps that cannot be undone.
- Say what happens to LedgerFern’s feature until its answers arrive, and who decides.
- Write each decision in a decision record. If a decision changes an earlier approval, say which request goes back to the board.
- Fill the control map for each line of your acceptable-use policy. Give each control its kind, its owner, its evidence and how often it is checked.
- Test each piece of evidence with the four tests of the evidence lesson: made by the work, covers what was asked, current, shows the control worked.
Part 5: the board, one incident and the 90-day plan
Section titled “Part 5: the board, one incident and the 90-day plan”Uses The governance board, Incidents, complaints and redress and Measure governance.
- Review the board’s terms of reference after its first quarter. Keep what worked, and change what the scorecard shows was slow or empty. Say who decides each tier’s requests.
- Decide incident INC-07 with the five questions: who decides, what to tell the people affected, how to correct the result, whether anyone outside must be told, and what changes. Write it as a minutes line, with its conditions and what would change it.
- Fill the governance scorecard with today’s values.
- Write the 90-day plan: at most eight actions. Each one has an owner, a measure from the scorecard, today’s value and the value that you expect in 90 days.
- Add what Larkfield will stop doing, as well as what it starts.
Laws and the questions for a lawyer
Section titled “Laws and the questions for a lawyer”Uses A map of the landscape, The EU AI Act and Canada, the US, the UK and others.
Wherever your pack names a law, a bill or a standard, give its official source and the date that you checked it. Copy both from the map of laws and standards, or check the source again yourself. Say what the rule is for, in plain words. Do not say whether Larkfield meets it.
End the pack with questions for a lawyer: one line for each question, with the system and the record that it is about. A good question names the facts, so the lawyer does not have to find them.
Hand in the pack
Section titled “Hand in the pack”Hand in one document, or one folder with a document for each part. Use these headings, so that a reviewer finds each part quickly:
Larkfield AI governance pack: next year1 Inventory, owners and tiers (inventory, tier scores and rules, responsibility tables)2 Impact assessment (one high-tier system or change, seven sections, decision)3 Policies (acceptable use; build and buy; three "may I...?" questions each)4 Vendors and controls (vendor decisions and records; control map with evidence)5 Board, incident and plan (terms of reference; INC-07 minutes line; scorecard; 90-day plan)Questions for a lawyerBefore you hand it in, answer the “Check before you hand in” questions at the end of the pack brief. Each “no” points to the part to fix.
How it is marked
Section titled “How it is marked”A reviewer marks each part demonstrated, partially demonstrated or not yet demonstrated, with a concrete reason. To complete the course, all five parts must be demonstrated. You can improve a part and send it again. If no reviewer is available to you, use the same table on your own pack, or ask a colleague to use it.
| Part | Demonstrated when | Partially demonstrated, for example | Not yet demonstrated, for example |
|---|---|---|---|
| 1. Inventory, owners, tiers and responsibility table | Every system has a named person as owner, and a tier with its scores and rule. A tier that differs from the registry has its reason. Medium and high tiers have a responsibility table. | One system has a team or a role as owner. Or tiers are given without their scores. | A system has no owner or no tier. |
| 2. One impact assessment | A high-tier system or change. Every section is filled from the evidence pack. The decision has conditions with owners, and says what would change it. | The sections are filled with general text, not evidence. Or no condition has an owner. | It is missing, or it is for a low-tier system only. |
| 3. Two policies, each with three “may I…?” questions | Each question is answered by the policy alone, with its line, or its gate and tier. | One answer needs “ask someone”. | The questions are not tested. |
| 4. A vendor decision and a control map | The decision names the gaps and the conditions, each with an owner. Every control has an owner and evidence that the work itself makes. | A control has no evidence. Or the evidence is a document written for the audit. | There is no vendor decision. |
| 5. Board terms, an incident decision and a 90-day plan | The terms say who decides each tier. INC-07 is decided with the five questions. The plan has at most eight actions, each with an owner and a measure, and says what to stop. | The plan has actions but no measures. Or nothing is stopped. | There is no incident decision. |
Not accepted: a pack in which a system has no owner or no tier, or in which a legal statement has no official source and date. Such a pack does not complete the course, however strong the rest is. A legal conclusion about Larkfield (“this is legal”, “we comply”) counts as a statement without a source: write the question for the lawyer instead.
The reviewer also asks you to explain one decision in each part. You must be able to say which record it rests on.
Common mistake
An inventory that copies the registry
Symptom: the inventory has a row for each system, and the tier column says the same as the registry. Half of the systems are missing, and one tier is wrong.
Cause: the learner used one source. The registry only sees the systems that developers registered, and their tiers were never checked against the method.
Fix: go back to The AI inventory and use all three sources. Then score every system yourself, and write the reason wherever you disagree with the registry.
Common mistake
A 90-day plan that only adds work
Symptom: the plan has twelve actions: new forms, new meetings, new training. Nothing stops, and no action has a measure.
Cause: the plan answers “what else could we do?”, not “what does the scorecard show?”.
Fix: start from the scorecard’s warning signs. Give each one action, an owner and the value that you expect. Then find the work that buys no risk reduction and stop it. Measure governance shows one such wait at Larkfield’s board.
Recap
In this course, you learned to govern AI so that teams can still ship:
- Know and own: keep one inventory of every system, built, bought or found, each with one named accountable owner and a responsibility table.
- Check in proportion: score each system for a risk tier, and let the tier set the controls. Autonomy moves the tier, not the topic.
- Assess before you change: write an impact assessment for high-tier work, signed by the owner, with conditions and what would change the decision.
- Write rules people can follow: an acceptable-use policy and a build-and-buy policy, each tested with real “may I…?” questions, and vendor answers read for their gaps.
- Prove it: turn each policy line into a control with an owner and evidence that the work makes.
- Run it: a board with clear terms, fast paths for low risk, incidents decided with five questions, and a scorecard that shows theatre.
- Know the rules, and ask: give every legal statement its source and date, and take the hard questions to a lawyer.
Keep your pack up to date. Review it after each quarter’s scorecard, after each incident and when a rule changes.