{{project}} / facilitator {{business}} / approver {{contact}} / review {{deadline}}

Purpose: decide what this review can change before anyone gives feedback.
Audience/task [ ]; brief/version [ ]; exact candidate/version/view [ ]; design stage [ ]; evidence available [ ]; critical assumptions [ ]; constraints [ ]. State whether copy, hierarchy, interaction, styling, or production is open and which decisions are already approved.
Open decisions: question | relevant brief criterion | evidence needed | decision authority | outcome sought. Closed or out-of-scope matters [ ]; how a valid new issue can be raised without silently expanding scope [ ].
Roles: approver [ ]; consulted stakeholders and expertise [ ]; designer [ ]; facilitator [ ]; factual/technical owner [ ]. Consulting a stakeholder does not automatically give them approval authority. Set a resolution route for incompatible requests.
Review plan: independent inspection minutes [ ]; evidence questions [ ]; conflict decision [ ]; handoff [ ]; total and recovery if discussion runs long [ ]. Give each person the same candidate/content/conditions; distinguish live behavior from a screenshot review.
Prompts: find [task information/action]; describe what you observed and where; connect the effect to the task/brief; separate a suggestion from a requirement. Avoid leading “don't you think” questions or presenting the designer's favorite solution before inspection.
Mandatory holds: missing source facts, unsafe/unsupported flow, unresolved required approval [owners/dates]. A group vote does not convert an unknown fact or failed requirement to pass.
Output: one owned decision register and prioritized revision list, with deferred/new-scope items and explicit tests. This meeting record does not authorize release unless the named authority and all actual gates do so.

Your decision
What decisions should this review make?
My answer: [ ]
Source and date: [ ]
Still to check: [ ]
Next action, owner, and due date: [ ]

Before you start
- Design brief: [Source or notes]
- Current version: [Source or notes]
- Approval roles: [Source or notes]

What you will make
A structured feedback session producing one coherent revision direction.
