The Mandate Model: Why Pre-Approval Fails for AI Work
The approval system was built for a calmer world
Your organization is good at one thing: approving things that are fully specified before the money moves. Licenses, headcount, capex. Someone writes a document, someone signs it, the thing arrives roughly as described. The model works because the object of the approval is stable. A server rack does not redefine what a rack is halfway through the purchase.
AI work is not stable. Neither is serious security or infrastructure work. The scope learns things about itself while it is being done. The system under examination answers back. That is not a process failure, it is the nature of the object. And it breaks the approval model underneath almost every initiative that actually matters.
What pre-approval does when the object is unstable
Watch what happens in most organizations when a genuinely uncertain project has to pass through a stable-object approval process. Four failure patterns, on a loop:
The scope is frozen before understanding arrives. The document that gets approved is written by people who are about to learn what they did not know. By week three the world has moved and the paper is fiction. Now every real conversation becomes a change request, and change requests are slow, political, and expensive.
The vendor is paid for presence, not findings. When outcomes cannot be fully specified upfront, procurement defaults to buying bodies and time. Days in the calendar, hourly rates, seats in meetings. The deliverable becomes availability. The evidence of value becomes the timesheet. Nothing in that arrangement rewards finishing.
Nobody owns the verification. A specification can be signed. An outcome has to be tested. Most organizations have elaborate machinery for the first and almost none for the second. The project "completes" because the budget ran out, not because the claim was verified.
The exit never happens. Work that has no defined end quietly becomes a relationship. The pilot becomes production. The consultant becomes institutional. The temporary tool becomes a dependency. Nobody decided any of it. It just accrued.
The mandate: a different shape for unstable work
A mandate is a unit of work shaped for objects that are not fully knowable upfront. Four parts, in this order:
The trigger. Something happened or is about to: a regulator letter, an insurer's renewal questionnaire, an AI budget nobody can govern, an IT head leaving, a migration that cannot fail. The trigger is a fact, not a wish list. It is discovered, not designed.
The scope, agreed before work begins. What is taken, what is refused, and what "done" means, written down while the trigger is still fresh. Where uncertainty is real, the scope says so and prices the discovery itself rather than pretending. A written scope is not a straitjacket. It is the thing both parties can point at when the world surprises them.
The gates. Claims advance through verification, not through meetings. What passes, passes with evidence. What fails, fails early, while failing is still cheap. This is the part borrowed from regulated industries: you do not certify a system by asserting it works, you qualify it by testing installation, operation, and performance under load, in that order, and you keep the records.
The exit. The mandate has an end condition designed in from day one: the client holds the evidence and the capability, and the office leaves. If the work starts feeling permanent, that is a finding, and it gets said out loud. Presence is never the product.
Why this shape survives the AI era specifically
Three properties of the mandate happen to be exactly what AI-era work demands.
It prices uncertainty honestly. Instead of a fixed-price fiction or an open-ended meter, the mandate takes the trigger and its discovery as the unit. When the AI landscape shifts next quarter, the mandate does not need to be renegotiated mid-flight, because the next question simply becomes the next trigger.
It puts verification in the middle, not at the end. The dominant failure mode of AI adoption is not bad models. It is organizations deploying claims they cannot answer: what runs where, who checked it, what happens when it is wrong. A gate-based engagement produces answers to those questions as a byproduct, in writing, with records that outlive the vendor relationship.
It keeps the buyer in charge of approval where approval actually means something. You are not approving an unknowable future. You are approving, in sequence: this trigger, this scope, these gates, this exit. Each approval is small, legible, and real. That is how governance works when the ground moves: not one signature on a two-year plan, but a chain of verified steps.
The uncomfortable sentence
If your current process can only fund what it can fully specify upfront, it cannot fund the work the AI era is asking for. It will produce pilots without production, reports without records, and relationships without results. The fix is not a bigger approval committee. The fix is a shape of work that carries its own verification and its own exit.
That shape is a mandate. My practice consists of five of them. The three-minute fit check on this site tells you which one your trigger matches, or tells you honestly that none do.
Scope and a fixed price are agreed within 48 hours of the first conversation. Describe your situation.
