Imagine an AI comparison marked “ready” while the manager supposed to check it has not opened it.
A colleague picks it up for the decision meeting. The manager sees it on the agenda and asks who accepted it.
“I thought you had.”
“I thought it was waiting for me.”
Same file. Same named checker. Two different ideas about what happens next.
If you run operations, you are the person untangling that conversation. The assistant finished the draft. The manager was assigned to review it. Somehow the space between those two things became your job to reconstruct.
Here’s the thing. You have named a checker, but left the work moving on assumption instead of an explicit decision.
A file arriving tells you where the file is. The next person still needs to know what can happen with it.
The name on the job description is the beginning
Keep the hypothetical internal comparison we have been building through the Handbook series.
The assistant compares Option A and Option B from approved source notes. The two requirements are a weekly list export and separate access for people who view the work and people who can change it. Both options support the export in the notes. B’s notes confirm separate access. A’s access remains unanswered.
The assistant recommends B as better supported against those requirements, explains the reason, and points to the supplied evidence. The requesting manager checks the comparison and makes the eventual business decision.
We already defined that role in Write the Job Before You Hire the Tool. The question now is what happens between the assistant finishing its part and the manager accepting it for use.
The manager’s name can be on the page while the comparison sits unnoticed in a folder. Or the document can travel ahead as if the check already happened. The first leaves work waiting. The second lets an assumption do the checker’s job.
Right? Neither problem gets solved by typing the manager’s name a second time.
Give the reviewer the decision they need to make
In the Professional Recipe, Escalation is the hand-back to a person: what triggers it, who receives it, and what travels with the work. For this comparison, the manager’s check is already part of the job. The handoff needs to make that next decision easy to find.
The weak version says:
“Comparison ready. Please take a look.”
Take a look for what? Accuracy? Writing style? A final choice? And does anybody need your answer before the meeting?
The reviewer has to reconstruct the request before reviewing the result. You have handed over a document and left the assignment in your head.
Try a short note that carries both:
For review: A/B comparison against the export and access requirements. B is better supported in the supplied notes; A’s access remains unanswered. Please accept this comparison for the decision meeting, return a specific correction, or hold it while a question is resolved. It is awaiting your decision.
Put the comparison and its source references with that note. Address the requesting manager in the place they normally review this work. Agree when the check needs to happen, before the meeting depends on it.
That is enough for the manager to understand what they owe the work. They can find the result, inspect the support, see the limitation, and make the next decision.
You have literally put the question beside the answer.
Accepted for what?
Suppose the manager reads the comparison, checks the references, and confirms that the unanswered point about A is still visible.
“Accepted as the comparison for our decision meeting.”
Now the colleague preparing the meeting can see what happened. The manager has checked this version for that purpose. The recommendation and its limitation travel together.
The company has not necessarily decided to choose B. The manager might use the comparison to decide that A’s access question needs an answer before anyone buys anything. A useful comparison can be accepted while the wider business decision stays open.
That distinction matters because the word approved can carry more than you meant. Approved as a draft to discuss? Approved as the final choice? Approved to act on?
Name the use in the answer. Then the next person can move the work without inventing the meaning of the approval.
This is a small part of what the Pass does in the Station Plan. It carries work between responsibilities while keeping the next decision attached. In a small team, the person doing that may be the same operations lead already handling the request. The job is making the move clear.
Returned needs a reason someone can act on
Maybe the manager cannot accept the comparison yet because one of its claims is missing a reference to the supplied notes.
“Add the source reference for B’s access settings, then bring this version back for review.”
That is a return somebody can act on. It identifies the missing part and says what happens after the correction. The assistant does not have to guess whether the manager wants more research, different wording, or a different winner.
The revised comparison comes back to the same decision point. Fixing the missing reference does not mean the assistant can announce that the manager has now accepted it.
Yeah. The correction and the acceptance are two different things that need to happen.
Keep the distinction from What Good Looks Like here. A’s unanswered access question is not automatically a reason to return the work. The standard allows the assistant to preserve an unknown. Returning the comparison simply because you dislike uncertainty would quietly change the job.
Return it when it misses the agreed standard, with the specific reason visible. That gives the next version a fair chance of reaching a decision.
Waiting should be something you can see
Back to our opening scene. The requesting manager is occupied and has not checked the comparison.
Its state is pending. The assistant has finished the draft, and the required decision has not happened. Both can be true at the same time.
A hold is more deliberate. The manager has looked at the request and decides something needs resolving before it can move.
“Hold this for now. I need to settle which meeting will use it, and I’ll confirm at our next planning check.”
The exact reason and next check will depend on the work. The useful part is that the pause has a reason, someone responsible for resolving it, and a point when they will look again.
Without that, held can become another word for forgotten. The operations person ends up searching messages to discover whether anyone still owes an answer.
Here’s the thing. Silence has no reliable meaning. It could mean the manager is busy. It could mean they missed the message. It could mean they believe somebody else already dealt with it.
You cannot use silence as evidence that the check passed.
If an already authorized backup can make the decision, the work can go there through the existing arrangement. Otherwise it stays visibly pending until the responsible person can deal with it. Choosing a new approver just because they are available changes the responsibility you had agreed.
Does that make sense? You are making the unfinished part visible so somebody can manage it. You are not asking the assistant to fill the silence with a guess.
Choose the review point before you need the answer
It is tempting to think the fix is a faster reviewer. Actually, first decide when the review needs to happen.
For our comparison, the answer is before the decision meeting relies on it. That gives the manager and the operations person a point to plan around. The manager can say whether they can check it, whether the existing backup should take it, or whether the meeting needs to proceed differently.
“I needed that yesterday” is information delivered too late to help the handoff.
Choose the point while the work is being assigned. A review request that arrives after the decision is already underway creates urgency somebody could have seen coming.
You do not need the reviewer hovering over the assistant. You need the result to arrive with enough context, in the agreed place, before the next step depends on an answer. The same place should show the decision when it comes.
A short note beside the current version is often enough. The next person should not have to remember which conversation contained the yes, whether that yes applied to an earlier draft, or whether the remaining question was ever resolved.
Your Monday Move
Pick one AI-assisted result that already goes to a named checker. Sit with that person and trace one sample from finished draft to the way the team is allowed to use it.
Ask what decision they owe the work. Ask what they need with it, where they expect to find it, and when their answer is needed. Then ask what the sender should do if they are unavailable.
Write a short handoff note for that sample. Include the result, the evidence or references the checker needs, the unanswered point, and the decision you are asking them to make. Show where it waits and what can happen once it is accepted.
Then have each person point to the pending work and name the next action. If one thinks the comparison is waiting and the other thinks it is approved, you have found the part to settle.
The aim is a result that can move without the next person having to reconstruct its history. The assistant’s output can be useful, the reviewer can be busy, and the rest of the team can still know exactly where things stand.
Make the next decision part of the handoff.
Original framework. Distilled from client work.
