A milestone acceptance clause breaks a project into stages, and payment is released only when each stage is formally approved. For example, a software development contract might have milestones: "design approved," "prototype delivered," "testing completed," "final launch." This is high-risk because disputes often arise about whether a milestone has truly been met—one party thinks the work is acceptable, the other disagrees. Under US and English law, if the contract requires "acceptance," you generally cannot withhold payment just because you're unhappy; you must have a legitimate, documented reason based on the contract's standards.
Define each milestone with extremely specific, measurable criteria—not "design looks good" but "design includes [list of specific features] reviewed by [named person] against [attached specification]." Include a clear process for what happens if a milestone is rejected: how many days the other party has to fix it, and whether they get paid for partial completion. Build in a neutral third party (like an inspector or engineer) to verify acceptance, rather than leaving it entirely to one party's judgment, because this reduces disputes and makes payment obligations clearer.
Frequently Asked Questions
What does this clause mean in simple terms?
A milestone acceptance clause breaks a project into stages, and payment is released only when each stage is formally approved.
Why should I care about this clause?
For example, a software development contract might have milestones: "design approved," "prototype delivered," "testing completed," "final launch." This is high-risk because disputes often arise about whether a milestone has truly been met—one party thinks the work is acceptable, the other disagrees.
What are my options?
Under US and English law, if the contract requires "acceptance," you generally cannot withhold payment just because you're unhappy; you must have a legitimate, documented reason based on the contract's standards.