Every decision needs a phone call
List repeat phone calls asking the same rate, discount or dispatch question. Use what you find to change the way this work is handled this week.
This is one cause behind related problems such as Important messages get lost in WhatsApp groups. Nothing is written as a rule, so every case is decided live. The checks below concentrate on this cause rather than repeating the full symptom diagnosis. At the decision log and shared action list, the department manager can usually see the earliest warning. Nothing is written as a rule, so every case is decided live. Check it before staff spend time correcting work that has already moved on.
What it looks like
- The department manager has to search the decision log and shared action list before answering a routine question.
- Nothing is written as a rule, so every case is decided live.
- Staff cannot locate a recorded decision, authority limit and closure evidence for the latest case.
- People spot the gap after the same issue travels through private calls instead of being closed.
- The open case has no documented owner, due date or proof of closure.
Why it happens
The specific failure is left unchecked. Nothing is written as a rule, so every case is decided live. If there is no recorded owner for that condition, the effect travels to the next team.
The work and its evidence move separately. Important decisions are communicated in private calls without a persistent action owner or recorded decision boundary.
A later hand-off exposes the gap. Managers escalate routine cases because approval limits and exception criteria were never agreed in writing.
The less obvious cause: A control may exist on paper but still fail in practice. Test whether someone actually performs this check: check whether those answers exist in any written policy.
Find the first failed hand-off before changing staff targets. A completed register alone cannot prove that physical work happened.
What to check first
- List repeat phone calls asking the same rate, discount or dispatch question. Compare dates, quantities and references. Mark an unconfirmed difference as unverified. Finish the first pass in under 30 minutes and name the missing source if needed.
- Check whether those answers exist in any written policy. Record the affected item or party and the person who can verify the detail. Finish the first pass in under 30 minutes and name the missing source if needed.
- Identify which decisions carry real risk and need manager approval. Mark each exception open, waiting for evidence or resolved, with a named next owner. Finish the first pass in under 30 minutes and name the missing source if needed.
How to fix it
- Start with one live case. List repeat phone calls asking the same rate, discount or dispatch question. Keep the source reference before changing the record.
- Make the control explicit. Write short decision rules with thresholds and examples. Put the rule in the register or sheet that staff already use.
- Set a second guardrail. Escalate only cases outside the rule, with supporting facts. Document who may decide, who must approve and which exceptions require the owner. Protect sensitive customer, payroll and financial information.
- Assign the next decision. The department manager records the action and its due date. A separately authorised person signs off changes affecting money, safety or customer terms.
- Review the open list. Start with items affecting today or tomorrow. Keep third-party commitments separate from completed actions.
- Check whether the rule holds. For four weeks, count routine actions delayed for unclear ownership or approval. Reopen repeat cases and identify where the control failed.
Copy this decision and follow-up register into a register or sheet:
| Reference / item | What went wrong | Evidence checked | Action owner | Promised date | Status / decision |
|---|---|---|---|---|---|
| P134 (example) | every decision needs a call | List repeat phone calls asking the same rate, discount or dispatc | Department manager | Set at review | Open |
Retain the source reference and limit access to authorised staff.
A worked example
Illustrative example only. A buyer phones the owner seven times to approve standard consumables under ₹5,000. Start by locating the source that would verify these amounts or quantities. The department manager records the exact exception, gives it an owner and checks the next relevant event. This example shows how to structure the decision. It does not claim that a business achieved a saving or avoided a loss.
How you know it is fixed
- Completeness: Count routine actions delayed for unclear ownership or approval at the same time every week. Record the count and the oldest item, rather than just saying things are better.
- Timeliness: Check whether the assigned person took the next action before the agreed cut-off. Keep missed dates visible instead of replacing them silently.
- Proof of closure: Sample three closed cases and locate a recorded decision, authority limit and closure evidence. A tick without supporting evidence is still an open control gap.
When it is more serious
A rule is applied to a high-risk exception without proper review. Hold irreversible decisions until the material facts are verified. For contracts, tax, wages or legal rights, retain source documents and consult a qualified adviser. Repeated exceptions after four reviews may require changing the control.
This works if someone does it every day. In most businesses, that someone is you.
Questions people ask
What should we check before taking action?
List repeat phone calls asking the same rate, discount or dispatch question. Keep its date and reference. Then compare it with a recorded decision, authority limit and closure evidence; if they disagree, record the difference before changing either one.
Who should own the next action?
The department manager should own the open item. The person authorised to change money, a technical standard or a customer commitment must still approve that decision.
Can we run this control without new software?
No. Start with a shared sheet or register containing the reference, owner, promised date, status and evidence. Once those fields are reliable, decide whether a system connection is worth setting up.
When is the issue serious enough to escalate?
A rule is applied to a high-risk exception without proper review. Keep supporting records and get specialist help where relevant.