Manipulated progress reporting and concealment of delays or defects
Performance data and reporting are manipulated to hide delays, defects and cost overruns, weakening oversight and reducing the chance of timely corrective action.
Red Flags & Indicators
- Progress reports show repeatedly high completion that is inconsistent with site observations, material usage, and daily logs.
- Delays are routinely reclassified as excusable, and schedule updates are not supported by contemporaneous evidence.
- Defect records and supervision reports are edited, delayed, and closed without verifiable corrective action.
Stakeholder Guidance
Stakeholder Exposure
Exposure includes hidden delays and defects; elevated risk of payment and liquidated damages disputes; unexpected rework and claims; audit exposure from inaccurate records; and reputational damage when manipulated reports are exposed.
Decision Point
Before submitting progress and defect reports, verify that supporting evidence aligns with reported progress and the updated schedule; pause submission and correct the record through internal review.
Mitigation Actions
• Adopt recognised methods to control project schedules and deadlines (document assumptions, delay evidence, and approved re-baselines; and avoid reclassifying delays without written justification and supporting records)
• Require that progress reports are grounded in verifiable evidence (site diaries, measurements, photos, test results, inspection and certification records)
• Require second-line verification of progress for high-value, high-risk milestones
• Use digital tools that auto timestamp entries to avoid falsification or backdating of progress reports
• Maintain complete and auditable registers of defects and non-conformance reports (owner, due date, closure evidence)
• Adopt a system that do not close defects without verified corrective action
• Require corrective actions and recovery plans to include documented milestones and assigned responsibilities
• Use internal compliance escalation processes and whistleblower channels, where available, to report any pressure to conceal delays, defects, or cost impacts
Mitigation Resources
Control progress reports, schedule records, defect logs, and supporting site evidence through formal evidence requirements, measurement records, defect-closure evidence, and verification before submission or internal sign-off.
Change control, delivery verification, and payment integrity — https://toolbox.infrastructuretransparency.org/resource/change-control-delivery-verification-and-payment-integrity/Failure Cases
Good Practices
Stakeholder Exposure
Exposure includes misleading reporting; late discovery of overruns and defects; higher governance and ESG risk; decrease of project value; and risk of disbursement decisions made on unreliable data.
Decision Point
After receiving progress reports, proceed with independent verification; pause support and require enhanced monitoring where inconsistencies persist.
Mitigation Actions
• Require reconciliation of reported completion with measurable quantities and the schedule baseline
• Treat repeated inconsistencies (high completion vs site evidence, unsupported “excusable” delay reclassifications, closed defects without proof) as suspension triggers
• Include audit/information rights over progress, quality, and defects records
• Require timely disclosure of corrective actions, updated recovery schedules and re-baselines, and verifiable defect closure evidence for material delays and quality issues
• Pause funding and trigger contractual remedies until evidence of completion is presented
Mitigation Resources
Use an independent technical adviser to verify reported progress, measurable quantities, delay status, defect status, and supporting site evidence, and to challenge weak or inconsistent evidence in progress reports, schedule updates, defect logs, or rebaselines before disbursement decisions.
Independent technical due diligence and monitoring — https://toolbox.infrastructuretransparency.org/resource/independent-technical-due-diligence-and-monitoring/Failure Cases
Good Practices
Stakeholder Exposure
Exposure includes cost overruns and poor quality; high risk of delayed interventions and remediation costs; increased audit and legal risks for inaccurate reporting; reduced accountability for delays; and loss of public trust.
Decision Point
Before approving progress report require inspection and records checks; or reject the report and require corrective actions when evidence is unsupported.
Mitigation Actions
• Apply surprise audits, risk-based spot checks and independent and second-line verification for high-value, high-risk packages and milestones
• Separate supervision and progress reporting from certification and payment approval roles
• Require verifiable defect and non-conformity report closure evidence
• Maintain an auditable record of material delays, defects, agreed remediation plans and a performance record (including baselines, revisions, approvals, and supporting evidence)
• Publish project information based on recognised infrastructure data standards such as the OC4IDS
Mitigation Resources
Require and verify progress reports, schedule records, inspection logs, measurement records, test results, defect records, and defect-closure evidence before approving certification, rebaselines, or payment.
Change control, delivery verification, and payment integrity — https://toolbox.infrastructuretransparency.org/resource/change-control-delivery-verification-and-payment-integrity/Set clear approval limits, sign-off steps, and separation of duties for progress reports, schedule updates, defect records, rebaseline decisions, and payment approvals; ensure no single official prepares, approves, and records the same action.
Approval authority and segregation of duties — https://toolbox.infrastructuretransparency.org/resource/approval-authority-and-segregation-of-duties/Publish and maintain public access to key progress and defect records, including approved rebaselines, material delays, defect status, remediation plans, and reasons for material changes, with only lawful redactions.
Transparency and data disclosure standards — https://toolbox.infrastructuretransparency.org/resource/transparency-and-data-disclosure-standards/Failure Cases
Good Practices
Stakeholder Exposure
Exposure includes mislieading progress reporting; limited access to true performance data; high risk of defects; delayed accountability; and risk of retaliation when challenging project delivery.
Decision Point
During project execution, submit access to information to clarify project progress and delivery milestones. Decide whether to (a) escalate through oversight channels to report non-delivery and lack of transparency, or (b) monitor while safely gathering evidence.
Mitigation Actions
• Mobilise communities to identify evidence of project delays, defects, and service impacts against public milestones and observable site conditions
• Engage available grievance channels and oversight bodies to report credible signs of non-delivery (use safe, confidential reporting and anonymisation where the risk of retaliation is significant)
• Advocate for disclosure of project information based on recognised infrastructure data standards such as the OC4IDS
Mitigation Resources
Use independent monitoring or social accountability to compare disclosed progress and defect records with observable site conditions, delivery on the ground, and service impacts; document unexplained gaps, track follow-up actions, and raise them through oversight channels.
Independent monitoring, assurance, and social accountability — https://toolbox.infrastructuretransparency.org/resource/independent-monitoring-assurance-and-social-accountability/Review publicly disclosed progress and defect records, such as progress certificates, inspection summaries, and defect or NCR status; identify disclosure gaps, missing justifications, or inconsistencies with observable delivery, and raise concerns about non-disclosure with an oversight body.
Transparency and data disclosure standards — https://toolbox.infrastructuretransparency.org/resource/transparency-and-data-disclosure-standards/Request access to non-public decision records, such as approvals of rebaselines, decisions on defect closure, or internal explanations for delayed or incomplete works, so hidden decisions, missing rationales, or unexplained changes can be examined and raised through oversight channels.
Access-to-information and demand-side transparency — https://toolbox.infrastructuretransparency.org/resource/access-to-information-and-demand-side-transparency/