
Design Feedback Workshop / Action kit
Design feedback workshop & revision template
Replace contradictory preferences with consolidated feedback tied to the design brief.
Made for designers reviewing concepts with clients.
Price and availability
Catalog price: $9 USD
One-time purchase · No subscription
- FilesZIP with five editable Markdown documents, an offline HTML workbook, a reading edition. A five-document worked case follows one fictional project.
- To useExtract the ZIP. Open the workbook in a current desktop browser; edit Markdown in a text editor. No account needed for the workbook or Markdown files.
- LicenseUse for your own or client work; do not redistribute the original templates or tools. Full terms.
- SupportProduct questions and corrections by email; no custom implementation or professional review. 14-day refund policy.
Checking the live price and secure checkout…
The task
What you'll make
A structured feedback session producing one coherent revision direction.
Gather before you start
- Design brief
- Current version
- Approval roles
Mark missing information so you can check it before using your work.
When to skip this kit
- You need a native Excel, Canva, or Word template. This download contains Markdown documents and an offline HTML workbook.
- You need autosave or cloud sync. Export Markdown or save a backup before closing the offline workbook.
- You need someone to complete the work. These are worksheets to fill in yourself.
Read the first worksheet below to see whether its questions help with your task.
Included files
What's inside
- 01Review frame
- 02Silent assessment
- 03Evidence questions
- 04Conflict resolution
- 05Revision handoff
Each document has instructions, questions, and space for your answers. The final document includes a common mistake to check for before using your work.
The worked case contains five completed documents, one for each worksheet. Follow the evidence, decisions, and corrections across the same fictional project. The case is included in the workbook, reading edition, Markdown example.
Your completion check
Preserve independent comments and evidence categories, resolve conflicts through the named approver, issue one bounded revision list, retest exact candidates, and keep factual and functional release gates open until verified.
Before you finish
Check this before you use it
Conflicting stakeholder comments are sent directly to the designer.
Resolve conflicts against the brief before assigning revisions.
Use the final worksheet to record what needs fixing and what you still need to check.
Free worksheet
Start with worksheet one
Review frame
Jump to a section
{{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.
View plain worksheet text
{{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.This is the complete first worksheet from the current edition. The full kit adds the remaining four documents, a worked scenario, and the offline editing workbook.
Worked example
See the worked-case summary
Fictional example included in edition 2.49.1.
Fictional case: three stakeholders review a workshop homepage and disagree about the primary action. Nine independent comments are consolidated into four issues, two optional ideas, and one question. Five completed documents show how “make it pop” becomes a specific hierarchy concern, a calendar feature is held as new scope, and the approver chooses booking over a competing newsletter action. Two candidate corrections pass a limited retest while publication remains on hold for an unresolved venue fact.
Before you choose
What should I have ready for this kit?
Bring design brief, current version, approval roles. Mark anything you still need to check.
How do I know the work is finished?
A structured feedback session producing one coherent revision direction. Check your answers against the original records and note anything unresolved before sharing your work.
Does it include a spreadsheet or native app template?
No. You receive editable Markdown documents and an offline HTML workbook. These are not native Excel, Canva, Notion, or Word templates. Extract the whole ZIP before opening the HTML files. Mobile file managers may not run local scripts; the text files and reading edition remain available.
Will this do the work for me?
The kit supplies structure, questions, and examples. You provide the facts, make the decisions, and adapt the finished output. You are responsible for checking the finished work. Custom implementation and professional review are not included.
Created by Pagemage with AI-assisted writing and development. Read how the content and tools are checked. Questions or corrections: hello@pagemage.tech. 14-day refund policy.