06 / 07
RTP Report Tool
A single-purpose utility that computes one recurring metric the same way every cycle, with the method fixed in one readable place.
- TYPE
- Reporting
- USE
- Recurring metric reporting
- ROLE
- Design and build
- STATUS
- In use, ongoing
- BUILT WITH
- Python
- CAPABILITIES
- Reporting, Data processing
BEFORE
One metric recomputed by hand each cycle, with the method drifting quietly.
AFTER
One calculation, one method, and an answer that can be pointed at.
01 / INPUTSource figures
02 / PROCESSOne calculation, one method
03 / DECISIONThe method is explicit, not a special case
04 / OUTPUTThe same number every time
Removed
Recalculation
One metric, done right
Scope
Fixed, auditable
Method
The problem
One metric needed recomputing every cycle, by hand, using the same method every time. Manual recalculation has a specific failure mode that’s easy to miss: the method drifts. Someone rounds at a different step, or includes a category the last person excluded, and two cycles stop being comparable without anyone noticing a mistake was made, because no mistake was made, exactly.
What I built
A small, focused utility that does one calculation and does it identically every time. Not a reporting platform. A tool with one job.
How it works
Source figures go in, the fixed method runs, the number comes out. There is no configuration to get wrong between cycles, because there is nothing to configure.
Technical approach
The narrow scope is intentional. This could have been folded into the general back-office reporting, and it would have been worse: a metric with its own specific method deserves its own explicit implementation, where the method is readable in one place rather than buried as a special case inside something general.
That readability is the actual deliverable. When someone asks “how is this number computed?”, the answer is a file, not a memory of how it was done last time.
Current state
In use each cycle. The recurring recalculation is gone, and the method is fixed and auditable.