Stage 4 of 8 · Set up and assess

Design controls and document

Choose and document the right safeguards.

For reference purposes only. Not legal advice.

SimplifiedGeneral guidance in plain language. Region callouts are short summaries; read the region pages and sources.Source: NIST AI Risk Management Framework · Checked 3 Oct 2026

What this stage is for

Pick controls that match the tier, document what each system is for and where it falls short, and do due diligence on vendors before signing. Documentation is also how you will later prove what you did.

Who is involved

Product owner, Engineering and data science, Procurement, Privacy, Security.

Key outputs: Control plan, model or system card, data documentation, vendor file.

Step-by-step tasks

Tick each task as you complete it. Your ticks stay in this browser tab unless you export your workspace.

Region callouts

Shown for the regions in My regions (header). The region pages are never hidden.

EU

For possible high-risk systems, start preparing technical documentation, logging and oversight design well ahead of the 2027 and 2028 dates. European Union page

US

If you sell to US federal agencies, OMB memoranda on agency AI use and procurement may affect what you must provide. United States page

UK

Sector regulators apply the five UK principles. Document how each is met in your sector. United Kingdom page

IN

Regulated financial entities should review RBI's FREE-AI expectations when designing controls. India page

Tools and templates

Tools

Templates

Common mistakes

  • Accepting a vendor's compliance claim without evidence.
  • Documentation written once and never versioned.
  • Controls chosen by habit, not by risk tier.

You're done when…

  • Each system has a control plan with owners.
  • Each material system has a card and data record.
  • Each AI vendor has a due diligence file and contract terms.

Reviewed 3 Oct 2026.

← Stage 3: Assess risk and impact · Stage 5: Test and validate →

Was this page useful? Tell us what is missing or wrong ↗ · Report a correction