The Approval That Covered Less Than You Did

You ask the owner: "There are about thirty old accounts sitting unpaid — can I close them off?"

They say yes.

You go to do it and find eighty-four.

⚠️ The yes you have covers thirty. It was given against a number you supplied, and the person who gave it was picturing that number when they said it.

The short version

• Permission is granted against the size you described, not the real size
• Finding out it is bigger is new information, which means a new question
• The gap almost always appears after the yes, when you start the work
• Doing the bigger version and reporting after is how trust gets spent
• The fix is one sentence, asked before you continue

Why this happens to conscientious people

What you did	Why it still goes wrong
Asked before acting	You asked about a smaller thing
Described it honestly	Honestly, and incompletely
Got a clear yes	To the description, not the reality

⚠️ Nobody lied and nobody was careless. The number moved between the question and the work, and nothing in the process forced a second look.

One: the shapes it takes

It is rarely a number. It is usually a boundary.

Scale    "about thirty" turns out to be eighty-four
Scope    "the front room" turns out to include the corridor
Time     "an hour on Tuesday" turns out to be three evenings
Money    "a couple of hundred" turns out to be four figures
People   "I'll ask Sam" turns out to need three people's shifts moved

⚠️ All five feel like the same job to the person doing it and like a different job to the person who approved it.

The test

Would they have said yes to the real number
as readily as they said yes to yours?

⇒ If you hesitate, you already know. The hesitation is the signal, and it arrives before the work does.

Two: the moment it is cheap to fix

There is a window, and it is short.

Before  one message: "it's eighty-four, not thirty - still yes?"
During  awkward, but recoverable
After   you are explaining, not asking

⚠️ The cost difference between those three is enormous and the effort difference is one sentence.

What the message looks like

"You said yes to about thirty. It's actually eighty-four,
 same kind of thing, same reason. Confirming that's still fine."

⇒ Short, specific, and it gives them the real number. Most of the time the answer is yes and it takes ten seconds. The value is not in the answer — it is in them having the real number.

Three: why doing it anyway feels reasonable

The reasoning is always sound in the moment.

"It's the same kind of thing"
"They'd obviously say yes"
"It would be silly to ask twice"
"The extra ones are the same situation"

⚠️ Every one of those is true and none of them is the point. The point is that they are now finding out afterwards, and finding out afterwards changes how the next request is received.

What it costs you specifically

Not the work being wrong
The next approval being slower

⇒ Somebody who has been surprised once asks more questions the next time. That is the actual price, and it is paid on every future request, not this one.

Four: the record you leave behind

There is a paperwork version of this problem that outlives the conversation.

The written approval says thirty
The work done was eighty-four
Nothing in between records the difference

⚠️ Months later, only the gap is visible. Anybody reading the record sees a yes for thirty and a job of eighty-four, and the reasonable-at-the-time judgement has left no trace.

The one-line fix

Write the permission at the top of the record,
in their words, before you start.

⇒ Then if the number changes, the change is visible against something. A record with no permission quoted in it cannot be defended, however good the reasoning was.

⇒ On the related problem of records that were correct when written: the note that was true when you wrote it.

Five: the version that goes the other way

It also happens in reverse, and this one is quieter.

You get approval for something
You do a smaller version
Nobody notices, because less was done

⚠️ Under-delivering against an approval is still a gap, and it usually surfaces at the worst moment — when somebody asks whether the thing was handled and the honest answer is "partly."

⇒ Say which part. "Approved for all three rooms, did two, the third needs a part" is a complete answer. "Sorted" is not.

Six: who should be asked again

Not every change needs a second question. The useful filter is small.

Ask again if   the number, cost or risk moved materially
Do not ask if  the method changed but the outcome did not

⚠️ "Materially" is doing the work in that sentence, and the honest test is whether you would want to know if the roles were reversed.

A rough threshold

More than about double     - ask
Crosses a round number     - ask
Touches money or deletion  - always ask
Anything irreversible      - always ask

⇒ The last two are worth holding absolutely. Money and deletion do not have a small version, and an irreversible action taken under an approval for something smaller cannot be walked back.

⇒ On who is actually entitled to halt something: who can say stop.

Seven: giving approvals, from the other side

If you are the one saying yes, you can close the gap from your end.

Weak    "Yes, go ahead."
Better  "Yes - up to fifty. More than that, come back."

⚠️ A ceiling in the approval removes the whole problem, because the person doing the work now has a rule instead of a judgement call.

The three ceilings worth naming

A number   "up to fifty"
A cost     "under two hundred"
A boundary "front room only"

⇒ Any one of these turns an open yes into something checkable. It also protects the person you delegated to, who otherwise has to guess where your line was.

Eight: when you only notice afterwards

Sometimes the gap is visible only in hindsight. The response is the same shape as any other error.

One   Say it plainly, with the real numbers.
Two   Do not bundle it with a justification.
Three Say what you changed so it does not recur.

⚠️ Step two is the hard one. The instinct is to explain why it was reasonable, and the explanation reads as an argument against being told.

What "plainly" sounds like

"The approval was for thirty. I did eighty-four.
 Same category, and I should have come back first."

⇒ That is the whole message. Anything added to it weakens it.

Numbers worth keeping

One   For each standing approval: what it actually covers
Two   Whether it has a ceiling, and what
Three When it was given
Four  Whether the person who gave it still works here

⚠️ Four catches a specific failure: a permission granted by somebody who left, still being relied on by somebody who never met them.

The card for the office

────────────────────────
  Before acting on a yes

  1. Is the real size the size I described?
  2. If not - one message, with the real number.
  3. Money or deletion? Always ask again.
  4. Write their words at the top of the record.

  A yes covers what you said, not what it is.
────────────────────────

Common objections

"They'd have said yes anyway"

⚠️ Almost certainly. The problem is not the answer — it is them learning the real number from you afterwards.

"Asking twice looks indecisive"

⇒ Asking twice with a number in it looks precise. "It's eighty-four, not thirty" is not indecision, it is information.

"There wasn't time"

⚠️ Sometimes true. Then say so at the time, not later: "It turned out to be eighty-four and I couldn't reach you — here is what I did."

"It's the same kind of thing"

⇒ Category is not scale. A yes to thirty small things is not a yes to eighty-four of them, and the person who said it knows the difference.

"We're too small for this"

⇒ Small operations run on exactly this kind of delegated yes, which is why the gap matters more, not less. There is nobody else to catch it.

What to do this week

One   List the standing approvals you rely on.
Two   For each: what did you actually describe when you got it?
Three Add a ceiling to any that has none. Ask for one.
Four  Quote the permission at the top of the next job record.
Five  If you find a gap you already crossed, say so plainly.

Summary

• Approval covers the size you described, not the real size
• The gap appears after the yes, when the work starts
• One message with the real number closes it for ten seconds of effort
• Money and deletion have no small version — always ask again
• If you give approvals, name a ceiling
• When you notice late, say it plainly and without the justification

Nobody objects to being asked a second time. They object to finding out the real number from somebody else, months later, in a record.