Reset Acceptance Criteria Before a Client Reviews a Key Deliverable

A key deliverable can be on time and still fail a client review when the team has not agreed how it will be judged. The delivery director should reset acceptance criteria before the final presentation when requirements are vague, reviewers have changed, or the work has evolved. That conversation gives both teams a fair way to assess readiness.

Ask what decision or activity the deliverable supports, who will use it, and which elements must be present. Compare the answers with the documented scope and prior review notes. If a new request changes the agreed work, describe the impact and follow the client’s process for deciding whether to include it.

In a fictional checkpoint, sponsor Inez says, “The steering committee expects something they can act on next week.” Director Cole replies, “Let us make that expectation explicit before the review. What decision will they make, and which three items must the document show for them to make it?” Inez says they need options, cost ranges from finance, and a clear owner for each recommendation. Cole asks the finance lead to confirm when its input will be available and schedules a review of the draft with the sponsor before the committee session.

Use a practice sheet with four fields: intended use, reviewers, acceptance points, and open dependencies. Roleplay a sponsor who adds a new requirement late in the process. Review whether you clarified the decision, recorded the change, and gave the client a visible choice about timing or scope.