Owner dependency and information flow5 min readRecord to report

Reports arrive too late to act on

Compare report delivery timestamps with the point when actions were still possible. Use what you find to change the way this work is handled this week.

A gap in the day-to-day record can be easy to miss. Weekly or monthly numbers come after the chance to fix things has passed. The risk grows when teams use different versions of what was agreed.

What it looks like

  • The department manager has to search the decision log and shared action list before answering a routine question.
  • Weekly or monthly numbers come after the chance to fix things has passed.
  • 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. Weekly or monthly numbers come after the chance to fix things has passed. 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: identify manual copying and reconciliations delaying publication.

Find the first failed hand-off before changing staff targets. A completed register alone cannot prove that physical work happened.

What to check first

  1. Compare report delivery timestamps with the point when actions were still possible. 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.
  2. Identify manual copying and reconciliations delaying publication. 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.
  3. Ask managers which five numbers they need during the shift. 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

  1. Start with one live case. Compare report delivery timestamps with the point when actions were still possible. Keep the source reference before changing the record.
  2. Make the control explicit. Publish a small provisional daily exception snapshot. Put the rule in the register or sheet that staff already use.
  3. Set a second guardrail. Reserve full reconciled reports for the agreed weekly or monthly close. Document who may decide, who must approve and which exceptions require the owner. Protect sensitive customer, payroll and financial information.
  4. 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.
  5. Review the open list. Start with items affecting today or tomorrow. Keep third-party commitments separate from completed actions.
  6. 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 / itemWhat went wrongEvidence checkedAction ownerPromised dateStatus / decision
P136 (example)reports arrive too lateCompare report delivery timestamps with the point when actions weDepartment managerSet at reviewOpen

Retain the source reference and limit access to authorised staff.

A worked example

Illustrative example only. A plant learns on Monday that Friday's ₹1.6 lakh order failed the previous shift. 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

Decisions based on inaccurate preliminary data need explicit caution. 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?

Compare report delivery timestamps with the point when actions were still possible. 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?

Decisions based on inaccurate preliminary data need explicit caution. Keep supporting records and get specialist help where relevant.

Did not find your answer?Message the lamp team on WhatsApp. Ask about setup, your records, or anything we have not covered here.Ask us on WhatsApp →