Skip to content
Guide

AI governance quick wins: policy intake, risk tiering, and registry.

AI governance programs stall when they try to build the perfect framework before they know what they are governing. The quick wins are simpler: a working intake process so you can see what AI is being used, a risk tiering system so you know where to focus, and a registry that gives the organization a single place to look.

By Average Robot Updated

Why governance stalls when you start with policy.

Your AI governance committee meets on a regular cycle. Your intake form requires sign-off from legal, compliance, and IT security. And adoption has barely moved, because following the rules is slower than ignoring them.

If your governance program started with a policy document, you know how it goes. The steering committee debates principles and definitions, and produces a long framework that nobody reads. Months later, teams are still using AI the company does not know about, and the governance team cannot see what is happening.

The trouble starts when policy comes before ground truth. You cannot govern what you cannot see, and you cannot prioritize risk when you do not know which AI systems are in use or what data they are processing. Governance that works starts with visibility.

The absence shows up as a set of questions nobody can answer. A board member asks how much AI is in use across the company. The CHRO asks which AI systems touch employee data.

The CFO asks which pilots have quietly become production dependencies. The general counsel asks for a list of everything processing customer information.

Each question is reasonable. Each one arrives at a governance team that has a policy and no operating picture, because the answers are scattered across business units or held by people who have since changed roles.

The AI Profit Ready Assessment is eight questions and takes about two minutes. It places the organization at one of three stages, from Foundation to Innovation, and names the first move to make, which gives the three quick wins below a starting point.

The three quick wins that create visibility and control.

Three capabilities deliver immediate value and set up everything else: a policy intake process, a risk tiering system, and a working registry. Together, they let the organization see what AI is in use and assess where the real risk lives, so decisions rest on evidence.

Policy intake is the front door. It is the mechanism that captures every AI system or use case before it goes live. It can be simple: a short form and a clear owner, with a defined route to review. The goal is to make sure no one is flying blind.

Risk tiering is the filter. Not every AI use case carries the same risk. A customer-facing chatbot trained on proprietary data is different from a coding assistant running in a sandboxed environment. Risk tiering gives you a consistent way to classify use cases by impact and exposure, so you can focus governance effort where it matters and let low-risk work move quickly.

The registry is the single source of truth. It is the living document that tracks every AI use case, approved or under review, and every decision the governance team has made. When someone asks what AI the company is using, the registry is the answer. When the board asks about compliance, the registry is the evidence.

How policy intake works in practice.

A working intake process needs no new software: a form and a clear owner are enough, as long as every AI use case runs through it. The form should capture the essentials: what AI product or AI model is being used, what business problem it solves, what data it will process, who owns it, and where it will run.

The intake owner sits in IT, legal, or a dedicated AI governance role. Their job is routing: they send the request to the right reviewers, check the form is complete, and update the registry once a decision is made.

The process works when it is fast and clear. If an answer takes weeks, teams will route around it.

The output of intake is a risk classification and a decision: approved as-is, approved with controls, or requires further review. Every intake should update the registry, even if the answer is no. Denials are data. They tell you where teams are feeling pressure and where policy is out of step with business reality.

Intake works better as two paths than as one queue. Many intake processes are designed for the hardest cases, the ones touching sensitive data or making automated decisions about people, and then get applied to everything that follows. A product manager testing a draft-email assistant waits behind a credit-decisioning system. Neither is served well by that.

The fast lane handles use cases that do not touch customer data, do not make decisions about people, do not integrate into production systems, and do not run without a human in the loop. These need registration and a named owner, with basic guardrails. The form is short and the approval delegated or automated, so the use case moves from request to live work in days.

The deep lane handles everything else: AI systems processing PII, AI models making automated decisions, integrations into regulated workflows. These get the full review across legal, compliance, security, and data privacy, on a timeline that is realistic about what that review involves. Publish the criteria that decide which lane a request enters, so a team can tell which path applies before they file. A route teams cannot predict is a route they will work around.

How to build a risk tiering system that teams will use.

Risk tiering is a scoring system that classifies AI use cases by the severity of potential harm. The simplest versions use two or three dimensions: data sensitivity, user exposure, and decision impact.

Data sensitivity asks what kind of information the AI will process. User exposure asks who will interact with the AI's output. Decision impact asks whether the AI will make decisions on its own or assist a human.

One low-risk use case is an internal summarization assistant that processes public data and produces output a human reviews before it is shared. One high-risk use case is an AI model that scores loan applications using customer financial data and feeds directly into an automated decisioning system. The tiering system should produce a clear label, and three tiers are enough to carry the work: low, medium, and high.

The label determines which intake lane the request enters and what controls are required before it goes live. A low-risk use case routes to the fast lane on delegated approval. A medium-risk one gets a streamlined compliance and security check, with no full committee cycle. A high-risk one goes down the deep lane, with full review and ongoing monitoring.

The tiering system works when it is simple and built into the intake process. Teams should be able to self-assess their use case with a short questionnaire before they submit the intake form. The governance team reviews the self-assessment, confirms or adjusts the tier, and applies the corresponding control requirements.

The tier should set the monitoring cadence as well as the pre-launch scrutiny. A low-risk use case gets an annual review. A medium-risk one gets a quarterly check-in. A high-risk one gets active oversight with a named reviewer.

Tie the cadence to the tier in writing, so review happens because the tier requires it. And treat the tier as a live designation: when an AI system starts touching new data or feeding a new decision, its tier changes and its monitoring changes with it.

What belongs in the registry and how to maintain it.

The registry is a structured list of every AI use case the company knows about. At minimum, it should track the AI product or AI model name, the business owner, the risk tier, the approval status, the date of last review, and any controls or conditions attached to the approval. The registry should also capture denials and pending reviews, so the governance team can see the full pipeline.

The registry lives in a shared location. A spreadsheet works while the list is short. A database or governance platform works once it runs to hundreds of use cases. The important thing is that it is the single source of truth.

If someone wants to know whether an AI system is approved, they look at the registry. If the board asks for a compliance report, the governance team exports the registry.

The registry only works if it is maintained: every intake decision and quarterly review updates it, and decommissioned systems get marked inactive. The registry should be reviewed at least quarterly to catch systems no longer in use and use cases whose risk profile or approval needs another look.

A registry earns its keep when it can answer five operational questions on the day they are asked.

What AI is running in the organization right now? Who is responsible for each AI system, and who answers if something goes wrong? What is the risk profile of each use case, and is it being monitored at the cadence that tier requires? If an AI system had to be switched off tomorrow, what would break and who would need to be told?

And where has the organization become dependent on AI to deliver, as against where it is still experimenting?

Those are operating questions. A registry built for audit answers different ones, and the difference decides how it gets built.

A registry built for audit is a spreadsheet someone refreshes each quarter by asking business units what they are using; the data is months stale on the day it is entered, and nobody consults it to make a decision. A registry built as infrastructure updates when intake approves a system, when a tier changes, when an owner moves roles, and when a system is retired. The test is whether anyone reaches for it during an ordinary working week.

How to choose the right starting point for your organization.

If you have no visibility into AI use, start with intake. Build a simple form, assign an owner, and announce that all new AI use cases must be submitted before they go live. Do not try to inventory every AI system already in use. Let the registry build organically as new requests come in, and run a discovery process in parallel to capture the backlog.

If you already have a list of AI systems but no way to prioritize them, start with risk tiering. Define a simple scoring system, classify the known use cases, and focus governance effort on the high-risk tier. Let low-risk use cases move with lighter oversight, and use the tiering system to guide how much due diligence each new request requires.

If you have intake and tiering but no shared view of what is approved, start with the registry. Consolidate every decision into a single document, make it accessible to the people who need it, and commit to keeping it current. The registry is the artifact that turns governance from a committee into a capability.

Whichever door you come in through, size the first pass so it can be finished. Put a modest set of AI systems in the registry, with metadata their owners have confirmed, and route a batch of intake requests through the fast lane or the deep lane to see whether the routing holds. Apply the tiers consistently enough that different reviewers would land on the same answer. Prove the system on a small set of real cases, then expand.

Why isn't my team using the AI we already paid for?

Because nobody has told them, specifically, what they're allowed to do with it. Faced with ambiguity about red lines and accountability, employees pick the safest option: do nothing, or use AI outside the approved system without mentioning it. Leaders read that as resistance. For the employee, it is a sensible response to unclear rules.

This is the pattern The Elephant in the Algorithm calls out directly: many organizations treat AI as a technology purchase. They choose a platform, run a few pilots and hold a training session, then expect transformation to follow. When the results disappoint, leaders blame enthusiasm or ask for more training. The missing piece is guardrails. People need enough clarity to know where they can experiment freely and who owns the judgment call when something goes wrong.

Without that clarity, even confident employees hold back, because the personal cost of guessing wrong is higher than the personal cost of not trying at all. That calculation is rational. Treating the resulting stall as a training gap just adds another workshop on top of the same unanswered question.

The tell you can check this week

Ask five managers what their team is and is not allowed to do with the AI already deployed. If you get five different answers, or five versions of "I'm not totally sure," you have found the problem: nobody has given them a clear, communicated answer.

What governance looks like when intake, tiering, and registry are working.

When the three capabilities are in place, governance starts to feel like infrastructure. Teams know where to submit new AI use cases, and the executive team has a clear view of AI activity and risk exposure. The registry becomes the artifact that proves the company has control over its AI use.

The change people notice first is speed. Once teams have seen a low-risk request clear in days, the incentive to work around governance disappears, and the committee is no longer buried in requests that never needed it.

Intake, tiering, and registry are the foundation of governance. Once you have visibility and control, you can build out the policy layer and the training and monitoring that make governance sustainable. Without the foundation, none of that other work will stick, so start with the quick wins and build the rest on ground truth.

The AI Profit Partnership starts from the same ground truth for one leader and their team: it researches how the team works today and ends in a plan for the year ahead, with quick wins put in place along the way.

Questions people ask.

How long does it take to set up a working intake process?

A basic intake process is a small build. You need a form and a defined owner, plus a way to route requests to the right reviewers. The hard part is getting organizational agreement on who reviews what and how fast decisions need to be made. Start with a pilot team and run a handful of requests through the process, then adjust based on what breaks.

What if teams are already using AI that was never submitted through intake?

Do not try to inventory everything at once. Announce that the new intake process applies to all new use cases going forward, and run a discovery process in parallel to capture the backlog. Focus discovery on high-risk areas first: customer-facing applications, AI systems processing sensitive data, and anything integrated into production systems. Let the registry build over time.

How detailed should the risk tiering system be?

Simple is better than comprehensive. Start with three tiers and two or three dimensions. You can always add nuance later. The goal is to give teams and reviewers a shared language for talking about risk. If the tiering system takes more than a few minutes to apply, it is too complex.

Who should own the registry?

The registry owner should sit in the function responsible for AI governance, such as IT, legal, or a dedicated governance office. They keep it current, which includes making sure every intake decision updates it, and produce reports when leadership asks. The registry is a living system that reflects the current state of AI use across the company.

What happens when a use case changes after it has been approved?

Any material change should trigger a new intake review. Material means a change in data processed, user exposure, decision-making authority, or the AI model itself. The intake process should include a notification requirement: if the use case changes, the business owner re-submits the form and the governance team re-assesses the risk tier. The registry should track the change history so you can see how a use case evolved.

What's the fastest governance win to restart stalled AI adoption?

The fastest win is publishing the risk tiers and the low-risk yes, this week, before the registry is complete and before the intake process is fully built out. Teams need enough clarity to stop guessing long before every policy is perfected, and a written low-risk tier gives them that immediately.

How do you build a policy intake process without adding bureaucracy?

Intake should be a short form and a same-week answer. A standing committee that meets once a quarter is too slow to keep people asking. The test for whether intake is working: can someone propose a new AI use case on Monday and know by Friday whether it's approved, needs review, or is off the table?

Two ways to start: the free Assessment or a discovery call.

The AI Profit Ready Assessment is free. Eight questions, then your result on screen: where your team stands with AI and which area to look at first.

If you would rather talk it through, the discovery call is 45 minutes. We ask about the work you have in mind and tell you straight whether we are the right fit for it.

Newsletter

With People

The people side of making AI pay.

  • One story from the news about AI at work, read through our book, The Elephant in the Algorithm.
  • A few links worth your time, and sometimes a podcast conversation.
Privacy Policy