AI Documentation That Holds Up: Model Cards and Impact Assessments
Regulators, customers and auditors all want AI documentation, each for different reasons. Write model cards and impact assessments once, and keep them true as the system changes.
What you'll be able to do
- Write documentation for each audience without duplicating work
- Produce model, system and data cards that match what's deployed
- Combine privacy, AI and fairness assessments into one decision record
- Keep documents current with clear change triggers and owners
An AI system documentation pack
What's in it. A system card, the model and data documentation it depends on, one combined impact assessment with its decision and approver, instructions for use, a plain explanation for affected people, and a change log with review triggers and owners.
You build it lesson by lesson, using your own organization, and submit it for your certificate. It's yours to keep and adapt.
Who it's for
AI governance, data science and product teams responsible for AI documentation.
What's inside
- 1Where the requirement comes from 18 min
- 2How small teams and enterprises meet it 16 min
- 3Documentation for its audiences 22 min
- 4Model cards, system cards and data documentation 22 min
- 5Impact assessments that combine 24 min
- 6Keeping documents true 20 min
- 7Hands-on lab: small team choose one 22 min
- 8Hands-on lab: enterprise choose one 24 min
- 9Finish and submit your deliverable 20 min
Built for your size
The requirement is the same everywhere. How you meet it depends on who you have. You pick the lab that matches your organization.
How you earn the certificate
Submit your finished deliverable, which is scored against a published rubric, and pass a short scenario quiz. Your certificate goes to your wallet and can be checked by anyone on the public register.