Exception log: end repeat bypasses
In the previous lesson we built an escalation ladder: a written deadline for every step and three levels the case rises through when a deadline passes. After a month of running it, many owners notice something irritating: the same step escalates every week, the same employee asks to bypass the same approval, and the same answer comes back — this case is an exception.
An exception that repeats is no longer an exception: it is an unwritten procedure that depends on one person deciding in the moment. This lesson is about the exception log — how to capture every bypass and turn it, after a month, into a permanent fix in the procedure.
Why allowing the exception is not enough
- It passes verbally: approval arrives by phone call or private message, leaving no trace to review later.
- No recorded cause: you know the step was bypassed, but not whether the cause was an impatient customer, a missing document, or an unrealistic deadline.
- It becomes the rule by habit: after ten times the team treats the bypass as the normal path, and the written procedure becomes a page nobody reads.
- It disappears at handover: the new employee inherits the procedure but not the exceptions, and blocks work that used to flow.
The four steps
1. Make the exception request a declared path, not a favour
A silent exception will happen whether you allow it or not. Open one known door for it: a request the employee writes, routed to whoever holds the authority, recorded like any other transaction. When the request is easy and logged, nobody looks for a side road.
Run from WhatsApp, that looks like a short message from the field rep:
Rep: Exception on order 442, delivery before release approval, customer is waiting at the warehouse.
System: Logged exception request 17 on the release approval step of order 442. Pick the cause: 1 customer present and cannot wait, 2 missing document, 3 approver unavailable, 4 other.
Rep: 3
System: Sent to the warehouse supervisor for approval. The reply comes back here, and the order will not close until the release note is uploaded.
The system neither blocked the work nor left the door open: it allowed the exception and tied it to an approver, a cause, and a document that must follow. More on running operations from chat in WhatsApp ERP.
2. Record the cause as a short list, not free text
Free text makes the log impossible to count: if every employee describes the cause in their own words, you cannot tell which one dominates. Use four to six causes only, with an optional text box for the rare case. The short list turns the log from stories into numbers.
3. Review the log once a month
Set aside twenty minutes at month end for one question: which step was bypassed more than three times? Do not review cases one by one; group them by step and cause. A single case needs a decision, a repeat needs a change in the procedure.
4. Close the loop: fix the procedure or make the exception a rule
Every repeating cause ends in one of three decisions: change the deadline if it was unrealistic, widen the authority if the approver is regularly unavailable, or write the exception in as a rule with clear conditions. The only acceptable fourth option is leaving things unchanged as a conscious decision, not through neglect.
An exception log template
| Step | Repeating cause | Times this month | Decision |
|---|---|---|---|
| Warehouse release approval | Approver unavailable | 9 | Extend authority to the branch supervisor in evening hours |
| Invoice issuing | Missing customer tax details | 6 | Make the field mandatory when the customer record is created |
| Discount approval | Customer present and cannot wait | 4 | Set a discount limit the rep may grant without approval |
| Return receipt | Other | 1 | No change, isolated case |
Checklist before you adopt the log
- Does every exception have a pre-named approver, rather than whoever happens to be around?
- Is the cause picked from a short list?
- Does the request stay open until the missing document is uploaded?
- Does the monthly review have a fixed date and a named owner?
- Is the amended procedure republished to the team instead of sitting in meeting minutes?
One caution: an exception touching a statutory document is not solved by leniency. Delaying or amending an invoice after issue follows defined rules, which belong with invoicing from WhatsApp, not with your internal exception log.
In short: the exception is not the enemy — hiding it is. Open one declared path for it, record its cause from a short list, review the log monthly, then close the loop by fixing the procedure or writing the exception in as a rule. When a case repeats more than three times a month, the problem is in the procedure, not in the employee.