A discounted rate gets extended to a long-time client. Months later, a different employee questions why that client is paying less than everyone else, and nobody can say who approved the exception or why. It wasn't a mistake at the time — it just was never written down, and now it looks like one.
Most service businesses make dozens of small, informal decisions like this every month: a pricing exception, a scope change, an exception to a normal policy. Almost none of them get recorded anywhere beyond whoever happened to be in the room.
Why this catches up with growing businesses first
When it's just the owner making every call, memory is usually enough — there's only one decision-maker to ask. That stops working the moment a second manager starts making calls too, because now two people's memories have to agree on decisions that were never written down in the first place.
What belongs in a decision record
Keep a Short, Consistent Log
- What was decided, in a sentence or two
- Who approved it and their role
- The date and the reason behind the decision
- Who it affects — a specific client, a job, or a broader policy
- Whether it's a one-time exception or an ongoing change
Why this isn't about distrust
A decision log isn't about catching anyone doing something wrong — most of these decisions are perfectly reasonable in the moment. It's about being able to answer a question accurately six months later instead of guessing, and about new managers being able to see the reasoning behind past exceptions instead of repeating the same debate from scratch.
The businesses that keep this habit tend to have fewer disputes about "why do we do it this way," because the reasoning is written down somewhere everyone can check instead of living only in whoever happened to make the call.
Get the Decision & Governance System
A simple decision log built to track approvals, exceptions, and the reasoning behind them.