03 / Decisions & Accountability

What Does "Ready" Authorize?

A status that means "the work is done" to one team and "you may act on it" to the next is one word doing two jobs across an irreversible boundary — and the gap between them is where the expensive mistakes live.

The example below is illustrative.

At a professional-services firm, the technical reviewer marks a client report "ready" once the analysis clears. The account lead reads that as permission to release and emails it to the client, who forwards it to their board. An appendix still contains a second customer's confidential figures the firm had agreed to aggregate before any distribution. By the time the analyst hears about the email, the firm has lost control of where that appendix can travel.

The reviewer had cleared the document to enter the release process. The account lead read the status as permission to leave it. Both worked from the same version and agreed on its contents. The error was never about the analysis. It was about what a person was allowed to do once the status turned green.

Start with the action someone takes

Walk the last report from drafting to delivery and ask each team what it does when the status changes. The reviewer may mean the analysis can be used to prepare a briefing. The release owner needs to know whether a specific file may go to specific recipients under the terms the firm agreed to. "Ready for rehearsal" can license useful internal work long before "authorized to distribute" applies.

Choose where the commitment becomes expensive to reverse. Sending a board pack is not the same as scheduling a tentative discussion. If the firm forces the full release check before allowing a rehearsal, it pays in needless delay on every draft change. If it authorizes external release at mere technical approval, it loses the controls that protect the distribution.

Define evidence, owner, validity, action

ItemReport-release example
EvidenceThe named file version has technical approval, the appendix was checked against the client's terms, recipients match the agreed distribution
OwnerA named engagement lead confirms the evidence and can authorize external distribution
ValidityAuthorization applies to that file and recipient set; a changed appendix, audience, or restriction resets it
Permitted actionThe account lead may send the approved version to the approved recipients through the agreed channel
RevocationAn owner can withdraw the status and alert anyone preparing to distribute

Store the evidence beside the status where the account lead actually works. If the lead signs off in one system while the file keeps changing in another, the status needs a stable identifier or a check at the point of sending. A message saying "looks good" cannot establish which document or audience was approved.

Price the ambiguity, then test both directions

Put a number on the cost of the undefined state. A mis-released appendix like the one above can trigger a confidentiality breach under the second customer's agreement — say a $25,000 contractual remedy — plus the unquantifiable cost of a board seeing figures it should never have had. Against that, the "fix" of freezing all distribution until every detail re-clears can delay routine board packs by a day each, and if the firm ships forty time-sensitive deliverables a quarter, a blanket freeze that adds a day to each is forty delayed client commitments for a risk that lives in maybe two of them. The right control is narrow, not blanket.

Test it both ways. Consider a board packet due at noon; at 10 a.m. the engagement lead learns one figure in the restricted appendix must change. If the file is split, the meeting proceeds and the approved summary still releases on time — only the revised appendix re-enters authorization. That is the useful exception a firm-wide "freeze everything on any change" rule destroys. A state applies to a particular object and action; it can invalidate one permission while another stays usable. Sample ordinary releases, near misses, and delays, and count both the incorrect releases and the valid ones held for no reason.

This is the "ready" problem at the level of a single handoff. Available Is Not Ready is the synthesis that generalizes it across stock, crews, and calendar slots — read it to see why "it exists" and "we can promise it" are different claims everywhere, not just in document release. And Everyone did their job. The truck still shouldn't have left. is the full field case where a status cleared across an irreversible boundary and a crew shipped to a site that was not ready. A separate failure can come from a different mechanism — several defensible numbers behind one promise — which Several Correct Numbers, One Unassigned Decision takes apart.

Take this to your team. When the dashboard turns green, what exactly may the next person commit — and how long does that permission last before it must be rechecked?

← Back to Decisions & Accountability