Bad reason
Too vague to review
Short, over, forgot, ask GM, maybe deposit, or will check tomorrow all force another follow-up.
Stage 2 - Problem aware
Problem aware guide
Variance Reason Quality Guide for Restaurant Managers
A variance note like short, over, forgot, or ask GM does not help the reviewer. A useful reason explains what likely happened, what proof exists, who owns the next step, and whether the item is still open.
Buyer knows variance notes are vague and wants a better standard.
Good reason
Specific enough to route
The reason names the likely cause, proof state, owner, and whether the reviewer can resolve or needs escalation.
Pilot signal
Reason quality improves
By Day 14, fewer closeouts should need manager memory because the reason already carries useful context.
Reason standard
A reason should help the next reviewer make a decision.
The point is not longer notes. The point is enough context to route, resolve, coach, or escalate without starting from scratch.
- Name the likely cause.
- Tie it to proof or missing proof.
- Name who owns the next action.
- Mark whether the item is open or resolved.
- Avoid blame language and unsupported claims.
Pilot proof standard
The page should move the buyer toward one real closeout.
Feels the pain. Needs checklists, worksheets, and calculators tied to familiar closeout problems.
Likely cause
Proof state
Owner
Status
Next action
Questions
Common Decision Questions
What makes a variance reason useful?
A useful reason names the likely cause, proof state, owner, current status, and next action so the reviewer can route or resolve the exception.
Related in this stage