Population Coverage
Demonstrate testing effort is allocated proportionally to risk and value.
- General ledger alone
How the result is read
100% of high-risk value examined in full; a meaningful portion of medium-risk sampled; a small statistical sample from low-risk. The measure has to be defined first, because the obvious one is zero — a signed sum over a balanced population cancels numerator and denominator alike.
The worksheet, on the demo engagement
Population Coverage, as the application draws it for Harrow Precision Engineering Ltd, the fictional demo engagement — one row per risk band.
- High 67-100
- Med 33-66
- Low 0-32
- Not reached
Tested value per band = value × tested %. The pale remainder is the population no procedure reached.
- Tested by value
- 41%
- High-risk $
- 100%
- Untested $
- 59%
Result grid4 rows
| Risk band | Count | % count | Value | % value | Tested |
|---|---|---|---|---|---|
| High 67-100 | 214 | 0.5% | 18,900 | 39% | 100% |
| Med 33-66 | 1,902 | 4.6% | 12,400 | 26% | 22% |
| Low 0-32 | 39,222 | 94.9% | 17,000 | 35% | 1% |
| Total | 41,338 | 100% | 48,300 | 100% | 41% $ · 100% high-risk $ |
In the application
Population Coverage is filed under Completion, index letter L. "Run all analyses" runs it with every other analysis the ledger can answer. The worksheet states the population it tested on its face — or "Not applicable" with the reason when a column it depends on is empty — and the Excel workbook the engagement exports files it under L, beside an index of the source files with their SHA-256 fingerprints.
Read it with
Run your next audit file test without the Excel crash.
One free engagement to evaluate, valid 60 days. The ledger never leaves the machine.
- 20 minutes
- Runs on a fictional engagement
- No client data required