An AI governance framework is how your business decides which AI to use, who owns each one, what data it may touch, and who checks its work. For a 10 to 50 person company it fits on one page: an owner per system, a risk level, a sign-off, data rules, a review on a schedule, and a path for problems. NIST's AI Risk Management Framework and the EU AI Act give you the shape. Where it stops: a framework is a plan, and someone still has to keep the list current and check the work each week.
What is an AI governance framework?
An AI governance framework is the way a business decides which AI it uses, who answers for each one, and what happens when one gets something wrong. It is not a policy file that sits in a shared drive. The policy is the rulebook. The framework is how the rules get applied to real choices: which use gets a yes, who signs off, what data the system can reach, and who looks when it acts in a way nobody expected.
Think of how you already handle money. You don't have one document called Money Policy. You have owners, sign-off limits, a second person on big payments, and a record of what was paid. AI governance is the same idea for a newer kind of system. Done well, it lets you say yes faster, because you stop arguing about the same risks each time someone wants to try something.
What should an AI governance framework include?
Seven parts carry the load. Skip one and the others lose their grip.
An owner for each AI system, by name, so someone watches it and answers for it. A risk level for each one, so a tool that drafts internal notes gets a light review and an agent that sends invoices gets a hard one. A sign-off before anything new goes into use, with a record of who said yes. Data rules that say what each system may read and change. Limits on what each system can do, set in the system itself, not just written in a document. A review on a schedule, because AI can drift as the data around it changes. And a path for problems, so an odd case reaches a decision-maker fast instead of being ignored.
In a small company, one person often wears several of these hats. That is fine. What matters is that each part has a name next to it.
NIST AI RMF vs EU AI Act vs a one-page framework
| NIST AI RMF | EU AI Act | One-page framework | |
|---|---|---|---|
| What it is | A US framework for managing AI risk | A European law with rules by risk level | Your own list of AI, owners and rules |
| Do you have to follow it? | No, it is voluntary | Yes, if it covers your AI use in the EU | It is yours to set |
| What it gives you | Four functions: Govern, Map, Measure, Manage | Risk levels and duties for each | Names, dates and limits for your own systems |
| What it leaves to you | Turning suggestions into your own steps | Working out which rules apply to you | Doing the reviews it lists |
How NIST and the EU AI Act fit a small business
You don't have to invent the words. The NIST AI Risk Management Framework, released in January 2023, is voluntary and works for any industry. Its companion Playbook sorts suggested actions under four functions: Govern, Map, Measure and Manage. NIST says plainly that the Playbook is neither a checklist nor a set of steps to follow in full. You take what fits.
The EU AI Act is a law. It sorts AI by risk. Some uses are banned, and those bans took effect in February 2025. Uses that can seriously affect health, safety or people's rights are high-risk, and rules for areas like hiring and education apply from December 2027. Some AI must tell people they are talking to a machine. AI with minimal or no risk gets no new rules. Even if you never sell into Europe, the idea travels well: the more harm a system could do, the more control it gets.
Agents raise the stakes. A tool that writes a draft can only be wrong on the page. An agent that can move money, change records or email customers can be wrong in the world. So set each agent's risk level by what it can do, and put a person's sign-off on its riskiest actions.
What an AI governance framework still leaves to people
A framework is a plan. The work it lists still has to be done each week, and in a 20-person company there is rarely a team to do it. NIST's own Playbook is voluntary suggestions, not steps, so someone has to turn it into a routine and keep it going. The EU AI Act puts the duty to watch a system on the business using it: deployers must make sure there is human oversight and monitoring once an AI system is in use.
The numbers show where the routine slips. IBM's 2025 Cost of a Data Breach report found that 63% of breached companies had no AI governance policy or were still writing one. Of the companies that did have a policy, only 34% checked regularly for AI that nobody approved. And 97% of companies that had an AI system breached had no proper access controls on it.
So the hand work sits in three places. Keeping the list of AI in use current, as staff sign up for new apps. Reading what each agent actually did, not what it was meant to do. And noticing when a rule or a vendor changes. That is checking and chasing, and it is exactly the kind of work that gets skipped in a busy week.
An AI governance framework template you can fill in this week
Start with one system, not a plan for everything. Fill in these lines for it, then repeat for the next one.
- 1
List what is in use
Write down each AI app and agent your team uses, who uses it, and what it touches. Ask people directly. You will find more than you expect.
- 2
Name an owner and a risk level
Put one name next to each system. Mark it low, medium or high by what it can do: draft, change records, or send and pay.
- 3
Write the data rules and limits
Say what each system may read and change, and set those limits in the system's own access settings, not just on paper.
- 4
Set the review and the problem path
Decide how often the owner checks the work, and who gets told when something looks wrong. Use NIST's Playbook for ideas under Govern, Map, Measure and Manage.
- 5
Check whether the EU rules apply
If you sell into Europe, see which risk level your uses fall under and when those rules start.
Where agents fit in AI governance
The parts of a framework that slip are the repeated ones, and those are the parts agents do well. An agent can keep a record of each action it takes and why. Another can read those records each week and post the top problems to the owner in Slack. Another can watch regulator pages overnight and flag a change the same day. The owner still makes the calls. The agents do the checking and chasing that keeps the framework true.
AI agents that keep governance going
Each of these takes a repeated part of the work, so the owner only handles the calls.
Your agents get a weekly review, with the top issues and one fix for each.
- Reads each agent's sessions and logsSunday night
- Flags out-of-date models and aborted runsweekly
- Posts the top issues with one fix eachto Slack
A price cut or a new rule, written up in three lines.
- Checks competitor pages and regulator bulletinsevery night
- Posts a price cut or new rulesame day
- Sends a digest to Slackevery week
Your inbox, calendar and documents, kept up for you.
- Reads and answers your emailall day
- Books and moves your meetingsas they come
- Writes your docs and deckson request
Questions
Is my customers' information safe?
Yes. Agents work in your own accounts and see only what each job needs. Customer details never go into public AI. Agents connect to AI through business-grade connections audited under SOC 2.
Does a small business need an AI governance framework?
Yes, once staff use AI on company data or an agent can change records. For a 10 to 50 person company it can be one page: owners, risk levels, data rules and a review date.
Is an AI governance framework only about the law?
No. Rules like the EU AI Act matter, but the stronger reason is day to day: knowing which AI touches your data, and catching mistakes before a customer does.
How is governance different for AI agents?
Agents act, not just write. Set each agent's risk level by what it can do, limit its access in the system itself, keep a record of its actions, and have a person sign off on its riskiest steps.
What does it cost?
You get the price on the call, along with the hours it saves your team.