Reported vs evidence
Portfolio of Evidence Completeness
Every reported performance result must be supported by valid, complete evidence - because at audit, an unsupported figure is treated as if it never happened.
Why Portfolio of Evidence Completeness Matters
The portfolio of evidence is the bridge between a reported result and the activity behind it, and completeness is the test of whether that bridge holds. The AGSA assesses whether each result has valid supporting documentation, and gaps translate directly into reliability findings. AuditPro Core checks evidence completeness per indicator so unsupported results are identified and remedied before the audit, not during it.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Indicators reviewed
204
Fully evidenced
61%
▲ 8%
Evidence incomplete
34%
needs remediation
No evidence on file
5%
high risk
Evidence status across reported indicators
Evidence gaps by indicator
| Indicator | Reported | Evidenced | Likely finding |
|---|---|---|---|
| Households with water access | 4200 | 3110 | Usefulness limitation |
| Jobs created via EPWP | 860 | 612 | Reliability limitation |
| RDP houses handed over | 318 | 318 | None |
| km roads resurfaced | 47 | 0 | No supporting evidence |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Validity of evidence
Evidence must genuinely support the specific reported result, not merely relate to the activity. Irrelevant or generic documents leave the figure effectively unsupported.
Completeness per result
Completeness means every reported number has its full evidence set, not most of them. A single unsupported result can still draw a finding.
Documentation standards
Evidence should meet basic standards of authenticity, dating and approval. Documentation that fails these tests is treated as absent for audit purposes.
Unsupported equals unreliable
A result without complete evidence is, from the auditor's perspective, unreliable regardless of whether the underlying performance occurred.
How AuditPro Core Bridges the Gap
- Completeness checks: each reported result is tested for a full, valid evidence set with gaps flagged.
- Exception workflow: unsupported results route to owners for evidence to be supplied before reporting closes.
- Traceability to source: each result links to its supporting documents so completeness is verifiable.
- Audit-ready export: the completeness report exports as assurance over the portfolio of evidence.
Key Takeaways
- Evidence must support the specific result reported, not just the general activity.
- A single unsupported result can still trigger a reliability finding.
- Documents failing authenticity or approval standards count as absent at audit.
- Closing evidence gaps before the audit is far cheaper than restating afterwards.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.
