AI Governance Framework Template for IT Teams and MSPs, Mapped to NIST AI RMF and ISO/IEC 42001

Updated: November 2026. NIST, ISO and EU AI Act references checked on 10 November 2026.

An AI policy tells staff what they can paste into a chatbot, but it doesn't tell anyone who checks the agent that resets passwords. That check needs an owner, a date and a record that it happened, written down before an auditor or a client asks. This AI governance framework template gives a small IT team or MSP 16 controls to fill in, each with an owner, evidence and a review date, mapped to NIST AI RMF and ISO/IEC 42001.

TL;DR

• What it is. 16 AI controls, each with an owner, evidence and a review date.
• Start with 10 rows. The core rows cover scope, policy, vendor terms, the register, intake, data exposure, logs, access, risks and incidents.
• Add 6 later. Add them when a client asks for ISO/IEC 42001 or AI starts deciding about people.
• Review on a calendar. Check the registers monthly, access and logs quarterly, and everything yearly.
• Mapped, not certified. Rows map to NIST AI RMF, ISO/IEC 42001 and dated EU AI Act duties.

What Is an AI Governance Framework?

An AI governance framework is the written set of controls that runs AI governance day to day: what gets checked, who owns each check, what evidence proves it ran, and when it's reviewed next. AI governance is the goal; the framework is the checklist that makes it repeatable.

For a team that uses AI rather than builds it, the controls are about bought tools, AI features switched on inside SaaS apps, and agents that act on your systems. Model validation and bias testing belong to teams that train models, and they get one line here.

AI Governance Framework vs AI Policy vs Procedure

The three documents get mixed up because they all mention AI. They answer different questions and go to different readers.

The policy is one row in the framework (GV-2 below), and its text lives in a separate AI acceptable use policy. For how policies and procedures layer in general, see policy vs procedure.

What an AI Governance Framework Includes

Every row in the template has the same six parts:

1. The control. One thing that must be true, written so you can check it.
2. An owner. A named person, not a team. In a 3-person shop, that's usually the IT lead.
3. Evidence. What proves the control ran: a dated register export, a signed review, a log setting screenshot.
4. A cadence. Monthly, quarterly, annual, or tied to an event like a new tool or an incident.
5. A standard mapping. The NIST AI RMF category and ISO/IEC 42001 clause the control supports.
6. A regulatory hook. The EU AI Act duty it covers, only where a deployer duty exists.

Evidence is the column that separates a framework from a wish list. If a control has no evidence, nobody can tell whether it ran.

The AI Governance Framework Template

The 16 controls follow the four NIST AI RMF functions: Govern, Map, Measure and Manage. Rows marked with an asterisk are the 10 core rows a small team runs from day one. The owners assume a small team with one IT lead and an exec who signs off.

Download the .xlsx template for every column, including the MSP split and blank fields for your own owners and review dates.

Prefer Google Sheets? Make your own copy and edit it there.

Govern

Map

MP-3 is the control that stops a new assistant from reading the HR folder someone shared with the whole company years ago. Run an oversharing check on the drives the tool can reach before you switch it on.

Measure

MS-1 only works if the logs land somewhere you'll look. Our log management guide covers where to send them and how long to keep them.

Manage

MG-2 becomes a core row the day an agent can change anything, such as resetting a password or closing a ticket. Prompt injection belongs on the MG-1 register for every tool that reads email, tickets or web pages.

AI Governance Responsibilities

A framework with one owner still needs other people for parts of it. This RACI shows who is Responsible, Accountable, Consulted or Informed for six activities that need more than one person.

In a 3-person team, the framework owner and security are often the same person, and legal means the outside counsel you call twice a year. That's fine. The point is that every row has one name in the A column.

A small IT team asked r/ITManagers how to govern AI without it turning into a full-time job. The top reply says their policy gets ignored because management doesn't hold anyone to it. Another reply lists what to keep for each approved tool: owner, plan tier, allowed data, connected apps and a review date. That's the MP-1 register. A vendor pitched its own product in the thread, so skip that reply.

How Often to Review Each Control

An hour a month keeps the framework alive. The rest runs quarterly, yearly or when something happens.

Put the monthly and quarterly checks on a shared calendar with the owner's name on each. A review that isn't booked doesn't happen.

A Worked Example With One AI Agent

Here's the whole template filled in for one agent: a ticket triage agent connected to the help desk and the RMM. It reads new tickets, sets priority and category, and resets passwords after a technician approves. Our guide to agents for IT operations covers how agents like this are set up.

The 12-month log retention and 20-ticket sample are our example values. Set your own and write them in the evidence column.

Building your own agent instead of buying one? Our guide to building an AI agent covers the parts these rows check.

The same rows apply to any vendor's agent. If you run OpenFrame, open, AI-native infrastructure for IT and security, its agents Fae (which resolves support requests) and Mingo (which runs IT operations) go on the register and through these 16 rows like any other. OpenFrame costs $1 per device per month with a 14-day free trial. Flamingo builds OpenFrame, so read this example with that in mind.

How the Template Maps to NIST AI RMF, ISO/IEC 42001 and the EU AI Act

The template follows the shape of the major AI governance frameworks without copying any of them. Each row points to the NIST AI RMF category and ISO/IEC 42001 clause it supports, and flags an EU AI Act duty only where one applies to a company using AI. This is our mapping at category level. NIST and ISO haven't reviewed or endorsed it. EU dates are as amended by the Digital Omnibus, Regulation (EU) 2026/1744.

NIST AI RMF is voluntary and free. Version 1.0 came out on 26 January 2023, and NIST's page says it's being revised as part of the White House AI Action Plan. No revised version or public draft was out on 10 November 2026, so the category numbers above still match 1.0. Check again before an audit, because the revision could renumber categories.

In this 2023 GovCIO Media interview, Elham Tabassi, then chief of staff of NIST's IT Laboratory, explains how the framework was built. It covers version 1.0, which is still the current one.

ISO/IEC 42001 is the certifiable one. It sets out an AI management system for organizations that develop, provide or use AI, and it's built to sit next to ISO 27001. If a client asks for certification, the template's ISO column shows where your evidence already lines up and where it doesn't. CEN adopted it as EN ISO/IEC 42001:2026 in March 2026, but it isn't a harmonised standard under the EU AI Act, so certification doesn't give you a presumption of conformity. Buy the standard before you rely on our clause numbers; we cite clause titles only.

The EU AI Act applies to companies that use AI in the EU, not only those that build it. For a team that deploys bought tools, two duties apply today. The first is AI literacy for staff, which the Digital Omnibus softened on 27 July 2026 to taking measures that support it. The second is Article 50 transparency from 2 August 2026: chatbot disclosure falls on the provider, while deployers label deepfakes and AI-written public-interest text unless a person reviewed it and took editorial responsibility. The high-risk rules for Annex III uses, including the Article 26 deployer duties on logs, oversight and incidents, apply from 2 December 2027. The side-by-side comparison of all three lives in our AI governance guide.

The OECD AI Principles sit underneath all three as shared values rather than controls, so they don't get a column.

Running One Framework Across MSP Clients

An MSP can run one framework for every client, as long as it's clear which rows the MSP runs and which ones each client signs. The downloadable version has an MSP column for exactly that split.

In r/msp, an MSP whose clients have 20 staff or fewer said they rewrote their service agreement: the client's owner sets the AI-use rules, and the MSP helps but can't monitor everything. Another reply puts the policy decision with HR and management, with IT supplying usage data and the enforcement the client pays for. Vendor staff pitched products in the thread too, so read past those.

Agree the split in the contract, not in a ticket thread.

Fill It In This Week

The 10 core rows take an afternoon if the AI register already exists, and a day if it doesn't. Start with MP-1, because every other row points back to it, then book the monthly and quarterly checks before you close the file.

Next, read our AI governance tools roundup for the software that finds AI in use and enforces these controls.