Start with the population subject to the requirement
The report should show the denominator: everyone who had the requirement on the selected date or during the selected period. Otherwise the result may look strong only because unassigned people are absent.
Make filters visible, including unit, role, location, procedure, version and date range. A reader needs to know what was excluded.
Show exceptions and their owners
The most operational part of the report is overdue items, unsuccessful attempts, expiring confirmations and missing assignments. Each exception should lead to an accountable person and next-action date.
Do not hide repeats by replacing the first result with the latest result. History shows whether a problem was detected and closed.
- people subject to the requirement
- completions and results
- overdue items and unsuccessful attempts
- expiry dates
- owners of follow-up actions
Protect the export context
An export should include its generation time, identifier or checksum and selected filters. This distinguishes an authentic snapshot from a file edited after generation.
Limit personal data to what the recipient needs. An auditor report may require different fields from a team manager view.
Questions worth asking
Is an overall percentage enough?
It supports management review, but an audit usually needs drill-down to people, versions, results and exceptions.
How long should reports be retained?
Base retention on legal, contractual and internal requirements. Do not keep a report longer without a defined purpose.