Ready for the client review?

• □The review link opens the intended version.
• □The reviewer has the access needed to use it.
• □The pages and goal of this round are named.
• □Deliberately unfinished areas are identified.
• □The reviewer knows where to leave comments.
• □The deadline and decision owner are clear.
• □The review surface does not expose information the reviewer should not see.

• □Each comment can be connected to a page or element.
• □The expected outcome is clear enough to discuss.
• □Missing details have a specific follow-up question.
• □Conflicting requests have a decision owner.
• □Defects, preferences and new scope are distinguished.
• □The original comment remains available alongside any summary.

• □The intended change has been agreed.
• □Open questions are not disguised as instructions.
• □The developer or agent can reach the relevant context.
• □Someone knows how to check the result.
• □The person making the change knows what is outside this round.

• □The relevant changes have been checked.
• □The reviewer knows what changed and what is still open.
• □Anything that needs a further decision is recorded.
• □Formal project acceptance is handled separately where required.

Keep it short enough to read. Use the question library to pick two or three questions for this round.

A checked box is not client acceptance, release approval or permission for extra scope. This list helps you find the decisions that still need an owner.

Read the full review process · See the client review workflow