Where this chapter sits
The series argues that the way to adopt AI without losing control is software that can be told what to do, held to what it may do, and made to account for what it did. This chapter is the starting point: the gap every leader already feels between the AI policy the firm wrote and the way AI is actually used. The chapters that follow take the gap apart one question at a time: who may act, what it costs, where the time goes, and how a developer puts a model into an application safely.
The problem, as you would put it
Sometime in the last two years your firm wrote an AI policy. It probably says sensible things. Do not paste client information into public tools. Check what the tool gives you before you rely on it. Use the approved service, not whatever you found last night. Someone in IT or compliance drafted it, the leadership team read it, and it went out to everyone with a request to acknowledge it.
Now ask a harder question. If a client, a regulator or your own board asked tomorrow how AI was used on a particular piece of work last month, could you answer?
In most firms the honest answer is no. Not because people ignored the policy on purpose, but because the work happened somewhere the policy cannot see. Forty people have forty chat windows. Each person has their own way of asking, their own saved prompts, their own sense of what counts as checking the answer. Some use the approved service. Some use a personal account because it was quicker. None of it leaves a record that anyone else can read.
You have a document that describes how AI should be used. You do not have a way of knowing how it is used. That gap is where the questions you dread live: which model produced this, who reviewed it, what client information went into it, and why two people doing the same task got two different results.
This is not a failure of discipline. It is a failure of design. A policy tells people what to do. Nothing in the firm makes it easy, or even possible, to do it the same way every time.
Why the usual fixes do not close the gap
The first fix most firms reach for is a better policy. The document gets longer, more specific and more carefully worded. It does not help, because the problem was never the wording. A clearer rule that still lives in a PDF is still a rule nobody can check.
The second fix is training. Everyone sits through a session on responsible use. People leave better informed and then return to the same private windows with the same habits. Training changes what people know. It does not change where the work happens or whether anyone can see it afterwards.
The third fix is to approve a single tool and block the rest. This is closer, because it at least narrows where the work goes. But an approved chat tool is still a blank box. It records conversations, not work. It cannot tell you that a given output was produced by an agreed method, checked against agreed rules and approved by a named person before it went to a client. Two people using the same approved tool can still do the same task in two different ways.
The fourth fix is to ban AI outright. In a regulated firm this can feel like the safe choice. In practice it moves the use into personal devices and personal accounts, where the firm has even less visibility than before.
Each of these treats AI use as a matter of individual behaviour. The underlying issue is that the firm has no shared place where the work itself is defined.
The idea: a policy is a document, governance is a mechanism
There is a difference between saying how work should be done and having a mechanism that does it that way. A policy is the first. Governance is the second.
Our thesis puts the ownership question plainly: “The organization should decide which information each model receives and what its outputs may influence.” (C2Consultants, Intelligent Software and Autonomous Organizations.) A memo cannot make that decision stick. Only a system can, because only a system sits between the person and the model every time.
That system has three jobs. First, it is where AI work is defined: what the task is, what information it may use, which model it calls and where that model runs. Second, it is where that work is approved: the steps that send, write to a system of record or act in an application stop for a named person before anything goes out. Third, it is where the work is recorded: what was asked, which version of the definition governed it, and what happened when it ran.
When those three jobs live in one place, the policy stops being a request and becomes the default. People do not have to remember the rules, because the rules are built into the only route the work can take. A person who wants a client summary does not open a blank window and improvise. They run the agreed summary, which already knows what it may read, which model it uses and who must approve it.
The thesis describes the result as a change in what a request is: “A request becomes a durable task with a purpose, relevant context, permitted actions and an accountable state.” (C2Consultants, Intelligent Software and Autonomous Organizations.) That sentence is the whole difference between a chat window and governed work. A chat ends when the window closes. A durable task keeps its history, its permissions and its outcome where others can see them.
There is one more benefit, and it is the one leaders tend to undervalue. When the same task runs the same way for everyone, it becomes consistent. The quality of the work no longer depends on which person happened to write the prompt. That is the real meaning of making people follow the policy: not watching them more closely, but giving them one good way to do the work and making it the easiest way.
What it looks like in a firm like yours
Consider a mid-sized firm of around two hundred people in a regulated sector. Its staff use AI informally for three recurring jobs: summarising long incoming documents, drafting first-pass replies to routine client questions, and preparing the paperwork for a government portal filing.
Today each of those happens in someone’s chat window. The summaries vary in length and focus. The draft replies sometimes include details that should not have left the building. The filing preparation depends on one experienced person who knows which fields matter.
Under a governed approach the firm defines each of the three jobs once. The document summary has a stated purpose, a fixed set of sources it may read, and a model the administrator chose. Administrators can choose local models for every use, so a sensitive job can run on the firm’s own hardware. The draft reply runs the same way, but it stops at an approval gate before anything is sent, and a named reviewer sees the draft, approves or rejects it, and that decision is recorded against the run. The filing preparation follows the same steps for every filing, and the trace shows what was entered and who signed off.
Nothing about the policy changed. What changed is that the policy is now the route the work takes. When the board asks how AI was used on last month’s client correspondence, the answer is a record, not a guess.
What to do first, before you buy anything
1. Find out where AI is already being used. Ask each team, without blame, which tasks they use AI for and which tools they use. You will likely find a short list of recurring jobs that account for most of it. That list is your real AI footprint, and it is almost certainly different from the one your policy assumes.
2. Pick one recurring task and write it down as work, not as a rule. Choose a task that happens often and carries some risk. Write what it is for, what information it may use, what a good result looks like, and who must approve it before it leaves the firm. This single page is the start of governance. It will also show you how much of your current policy is guidance nobody can act on.
3. Decide who answers for each step that has consequences. For that one task, name the person who approves the output and the person who owns the definition when it needs to change. If you cannot name them, the policy has no owner in practice, and that is the first thing to fix.
These steps cost nothing but time. They will tell you whether the gap in your firm is small or large, and they give you a concrete starting point whatever you decide next.
How C2Consultants does this
C2Empowered is the operations platform we build for exactly this gap: one place where AI work is defined, approved and recorded, instead of forty people with forty chat windows and no record. Each workflow is a published, versioned definition; the steps that send, write to a system of record or act in an application stop at approval gates set by risk level for a named approver; every run keeps a step-by-step trace tied to the version that governed it; and administrators choose which model each task uses and where it runs, including on the firm’s own hardware. One honest limit: it governs the work that runs through it, so it does not reach a personal chat account someone opens on their own phone, and it works only as well as the definitions your people agree to write. In one line, C2Empowered takes AI and makes it consistent. The way to start is a pilot: discovery of your recurring AI work ($2,000), installation ($1,750), and building and testing your first workflows ($175 per hour), run side by side with how you work today before you decide anything more.
Next chapter: Authority must remain explicit. How AI can act in your operations without acting on its own authority.