Copyable cycle worksheet
Time one reporting cycle from request to decision.
Collect
What to record: Sources and people needed
Example evidence: Two exports, one spreadsheet, one delayed reply
Repair
What to record: Cleanup and reconciliation time
Example evidence: Renamed values, missing dates, duplicate accounts
Format
What to record: Active time preparing the output
Example evidence: Arrange the weekly figures and labels
Verify
What to record: Questions needed before sharing
Example evidence: Manager checks a changed pipeline total
Explain
What to record: Follow-up after publication
Example evidence: Why two dashboards disagree or a number moved
Wait separately
What to record: Elapsed delay, cause and decision affected
Example evidence: A two-hour wait for approval is not automatically two labour-hours
Cost model
Measure the whole reporting loop, not only the final build time.
For example, a report might take thirty minutes to assemble after several hours of preparation. Time the preparation too; the assembly step alone does not describe the effort.
Collect
Time spent exporting, requesting, chasing, and gathering data from different places.
Clean
Time spent deduplicating, renaming fields, filling gaps, and correcting obvious errors.
Explain
Time spent defending numbers, answering source-of-truth questions, and clarifying what changed.
The unit that actually matters
The useful unit is a reporting cycle.
Count one weekly, monthly, or campaign reporting cycle from the first data request to the final decision. If the report does not support a decision, that is a separate signal.
Time
Hours per cycle
Add collection, cleanup, checking, formatting, and explanation. Do not only count dashboard assembly.
People
Who touches it
A report that looks cheap for one person may actually pull three people into small recurring interruptions.
Delay
How late decisions become
Record elapsed delay and the decision affected. Only estimate a financial consequence when there is evidence for it; do not add an invented delay cost to labour already counted.
Measurement steps
Use this lightweight measurement before rebuilding reporting.
The point is not to shame manual reporting. Manual reports are often the right first version. The problem starts when the same repair work repeats after the report is already important.
01
List the sources
Write down every tool, export, sheet, message, and person required before the report can be created.
02
Time each segment
Use ranges if exact time is unavailable. A rough but honest estimate is better than pretending the work is free.
03
Mark trust checks
Record active checking time and its purpose. A verification step may be a deliberate control rather than evidence that the report is defective.
04
Tie it to a decision
Record the decision or oversight need the report serves. Some monitoring remains useful even when no intervention is needed during that cycle.
What the number reveals
Include the questions that arrive after the report is sent.
Follow-up may involve checking a changed total or explaining an exclusion. Record how long that takes rather than assuming it is the largest part of the job. Identify which checks should remain even if collection becomes automatic.
Use the guide to turn repeated explanation work into visible source, owner, freshness, and exception rules.
Data Visibility for Commercial Teams ->Fictional worked calculation
Separate labour cost from waiting time.
Suppose a weekly report needs 30 minutes of analyst collection, 45 minutes of repair, 15 minutes of formatting, 15 minutes of manager verification and 15 minutes of manager explanation. These timings and rates are invented, not customer evidence or typical costs.
Analyst effort
Calculation: 90 minutes / 60 × £40 per hour = £60
Interpretation: Collection, repair and formatting; assumed loaded labour rate.
Manager effort
Calculation: 30 minutes / 60 × £60 per hour = £30
Interpretation: Verification and explanation; a separate assumed rate.
Weekly labour
Calculation: £60 + £30 = £90 for 2 person-hours
Interpretation: Two people working for the same 15 minutes contribute 30 person-minutes.
Annual scenario
Calculation: £90 × 48 reporting cycles = £4,320
Interpretation: Assumes 48 equivalent cycles, not every calendar week or an observed annual bill.
Elapsed waiting
Calculation: 2 hours awaiting an input, recorded separately
Interpretation: Do not multiply unattended waiting by a labour rate. Log actual chasing as active work.
Proposed change
Calculation: 45 analyst minutes removed; 15 manager minutes of new checking added
Interpretation: £30 capacity value less £15 new review = £15 per cycle, before tool, build and maintenance costs.
Decision point
A report is expensive when the team has to rebuild trust every time it is opened.
Compare keeping the process, simplifying the report, changing its frequency and automating part of it. Include setup, licences, maintenance and retained checks. Released capacity is not a payroll saving unless spending actually falls. Use a range when timing or future volume is uncertain.
The explanation cost compounds once the numbers themselves lose trust.
Why teams stop trusting dashboards ->