Made for Graphic Designers
Control Feedback and Revision Rounds
Also useful for: people in Creative, people in Designers
75 min
Advanced
Boundaries
Communicate Better
Difficult Conversation
Build one controlled path from raw client feedback to approved revisions without letting conflicting notes, hidden scope, or late opinions derail the work.
Create a free account to save your progress and use this Playbook.
Use this when
You received feedback from several stakeholders, comments are spread across tools, requested changes conflict, or a revision round risks expanding beyond the agreed scope.
You'll need
- Project name
- Project stage
- Approved direction
- Revision terms
- Current revision round
- Decision owner
- Feedback material
- Known concerns
You'll get
- All feedback captured in one register
- Every item classified and matched to an affected deliverable
- Contradictions, unclear requests, and scope risks isolated
- Client decisions recorded before production begins
- Revision work completed in dependency order
- Revised files checked against the approved plan
By the end of this playbook
You will have:
- All feedback captured in one register
- Every item classified and matched to an affected deliverable
- Contradictions, unclear requests, and scope risks isolated
- Client decisions recorded before production begins
- Revision work completed in dependency order
- Revised files checked against the approved plan
Sample
This is sample data, not your prompt. Pro unlocks this higher-stakes Playbook. On Free Playbooks you can still copy the assembled prompt into any AI.
Sample input
Project: Northline Coffee packaging refresh Stage: Client revision round Approved direction: Concept B, using a restrained typographic hierarchy, dark green lead color, and minimal illustration. Revision terms: Two consolidated rounds. New concepts and added deliverables require a separate estimate. Round: 2 Decision owner: Maya Chen, Marketing Director Feedback: Maya asked to increase the product name by 15%. Ben asked to enlarge the logo. Priya asked to preserve the current hierarchy. A follow-up email requested two seasonal flavor labels. A PDF note says, "Make the front feel more premium." Known concerns: The seasonal labels appear out of scope. Increasing both the product name and logo could undermine the approved hierarchy.
Sample assembled prompt
REVISION DECISION SUMMARY P1 REQUIRED CORRECTION... HOLD FOR DECISION F-02 and F-03:... Recommendation: keep the logo size and... Decision owner: Maya Chen. F-04: "Make the front feel more... Clarify whether the issue is typography,... LIKELY OUT OF SCOPE F-05: Two... EXECUTION ORDER 1. Confirm the hierarchy decision. 2. Adjust the product name on... 3. Check copy fit, clear space,... 4. Apply the approved master change... 5. Run production and export checks. ROUND STATUS Open pending one hierarchy...