Inspection programme economics
Work out what an inspection programme costs per confirmed case, and what share of inspections must confirm an issue for the programme to cover its cost. Enter your own costs and assumptions. Nothing is pre-filled with a price.
1. THE PROGRAMME
Your costs, in EUR
Planned visits or checks in a year.
Staff time, travel, equipment and admin per visit.
Tools, training, data work, management.
For example meter replacement or a billing correction.
2. YOUR ASSUMPTIONS ABOUT RESULTS
These drive everything below
After human review, and judged to need correction.
Your assumption. Use your own history if you have it. It is not a target.
Value that would be billed or recovered each year once corrected.
After disputes, collection and write-offs.
Your assumption.
How long the correction keeps paying before recurrence.
Your assumption. Starting value is illustrative.
3. RESULT
| Line | Amount |
|---|
4. WHAT IF THE HIT RATE IS DIFFERENT?
Net value over the persistence period, for different hit rates and value per case
Net value over the persistence period = (confirmed cases x annual value per case x share realised x years it persists) minus programme cost. Undiscounted and flat, with no growth. A confirmed case means an issue was found, checked and judged to need correction, after human review. A higher hit rate is not a target and should never be used to set quotas for inspectors.
Costs start at zero so the result uses only the figures you enter. The example is an illustrative placeholder, not a benchmark and not a figure for any organisation. The tool does not detect or confirm loss, fraud or theft, and the hit rate is an assumption, not a target: it should not be used to set quotas for inspectors. Nothing here is advice or a promise of savings. Results are indicators that require verification and human review.