Describe observable completion
Use named formats, approved requirements, supported environments, counts, and documented quality checks. Avoid criteria such as perfect, best, or completely satisfied.
Criteria should evaluate the deliverable against the agreed scope, not against a new idea introduced during review.
Set the review procedure
State how the deliverable is submitted, who reviews it, how issues are reported, and how long the client has to respond.
Require material mismatches to reference the agreed requirement. Minor preferences can follow the revision process.
Close the approval loop
Define written approval and any deemed-acceptance rule appropriate to the engagement. Explain what happens when a valid issue is found and when the corrected item is reviewed again.
Get legal advice before relying on acceptance language for high-risk, regulated, or large engagements.