Why construction progress needs a separate quality acceptance check

A progress percentage is only part of the story

A contractor reports that a work package is 60% complete. The figure can be useful, but it leaves several questions unanswered: which quantity was installed, who measured it, whether inspections are complete and whether any work is on hold. An owner report needs those distinctions to support a decision.

In a fictional example, a bathroom waterproofing package contains 80 square metres. The contractor reports 48 square metres installed. That is 60% of the planned quantity. If a required inspection is unresolved, the report should still show the installation claim while making the pending acceptance visible.

Keep three quantities distinct

These measures may coincide after inspection, but the report should not assume that they always do. Partial acceptance may be appropriate where the project rules and evidence support a clearly identified portion. The acceptance rules must be agreed before the report becomes a basis for payment.

Use a consistent work-package code across the budget, schedule, progress record and quality record. Otherwise the owner may see a percentage without being able to locate the scope behind it.

Treat a hold as a decision with an owner

A hold should identify the affected work, the reason, the responsible reviewer and the evidence required for release. “QC pending” alone gives the team little guidance. “Waterproofing inspection record missing for Zone B; supervisor to review submitted evidence” is actionable.

Releasing a quality hold does not automatically approve payment or certify the entire project. It changes one control state. The project may still require measurement review, commercial approval and other inspections.

Connect the issue to the next activity

A quality issue matters partly because of what depends on it. If a following activity would cover the work, make that dependency visible to the project manager. The site team must decide the safe sequence under its procedures and qualified engineering guidance.

For reporting, show the planned milestone, the current constraint and the person responsible for the next decision. Avoid converting every hold into an invented number of delay days. Assess actual schedule relationships before reporting an impact.

Give the owner a concise decision view

A useful owner summary brings together reported progress, accepted progress, outstanding quality issues and decisions required. The owner should be able to open the record behind an exception without reading every inspection note.

• Work-package code, location and planned quantity
• Reported and accepted quantities with units
• Current hold reason and supporting record references
• Responsible reviewer and next required action
• Schedule or commercial impact that has actually been assessed

Start by reviewing one work package from budget through acceptance. If that chain is clear, the same reporting pattern can be reused across other packages. Software supports the record; it does not replace engineering judgment or contractual certification.