Tying Payments to Contract Milestones: Lessons from a Public Infrastructure Project

Milestone-based payment structures tie contractor payments to the achievement of defined deliverables or project stages, rather than to calendar dates or time spent. In theory, milestone-based payments align the contractor's financial incentive with delivery performance: the contractor gets paid when they deliver, not before. In practice, the design of the milestones -- what they require, how they are measured, and what the process is for certifying achievement -- determines whether the payment structure supports good delivery or creates disputes and friction.

Here is a realistic scenario based on common patterns in public infrastructure project delivery, with the identifying details removed.

The Scenario

A regional water authority contracted a design-build firm to design and construct a water treatment facility upgrade. The contract included six payment milestones: preliminary design complete (10% of contract value), detailed design complete (20%), civil works complete (30%), mechanical and electrical installation complete (20%), commissioning complete (15%), and final acceptance (5%). Total contract value: $14.5 million.

What Went Wrong

• Milestone 1 -- 'preliminary design complete' -- was certified by the engineer of record on schedule. The authority paid the 10% milestone ($1.45M). Eighteen months later, during detailed design, the contractor submitted 140 design queries against the preliminary design. The preliminary design had been certified as complete, but it had not been sufficiently developed to support detailed design without significant rework. The milestone definition did not specify the level of completeness required -- only that the design was 'complete.'

• Milestone 3 -- 'civil works complete' -- was disputed. The contractor claimed the milestone was achieved; the authority's site representative found outstanding punch-list items. The contract did not define who had authority to certify milestone achievement, and the dispute escalated to formal notice. Work on subsequent phases slowed while the milestone payment was withheld. The 60-day payment clock, which started at the original certification claim, continued to run. When the dispute was eventually resolved, the authority owed interest on the delayed payment.

• Milestone 5 -- 'commissioning complete' -- was certified before a critical performance test had been run. The test revealed that the facility did not meet its treatment capacity target. The contractor argued that commissioning was complete (the systems had been tested) even though the performance target had not been met. The authority argued that commissioning could not be complete if the facility did not perform as specified. The contract language did not clearly distinguish between commissioning (the process of starting up systems) and performance acceptance (the facility meeting its operational targets).

Lessons Learned

• Define milestones with measurable, unambiguous achievement criteria. 'Preliminary design complete' is not a milestone definition; 'preliminary design documents issued to a level sufficient to support cost estimation within 10% accuracy and detailed design development' is a milestone definition.

• Specify who has authority to certify each milestone, and what the process is if the certifier and contractor disagree. Ambiguity about certification authority is a dispute waiting to happen.

• Distinguish between process milestones (a step has been completed) and performance milestones (a required level of performance has been achieved). Commissioning and performance acceptance are different milestones and should be defined and paid separately.

XNM provides contract management and project delivery advisory services to public-sector and capital-project clients, including milestone definition and payment structure design. Reach out to XNM's program & project delivery advisory team to discuss contract milestone design for your project.