← Free tools
Revision policy generator
Generate a clear revision policy: included rounds, consolidation rules, and what happens beyond the boundary.
Preview
# Revision Policy ## Included rounds This engagement includes **2** consolidated revision round(s) per deliverable (or milestone, if specified). ## What counts as a round A round is a packaged set of feedback on the current version. Micro questions and clarifications may be treated as feedback, not a full round, at the Creative’s reasonable discretion. ## Consolidated feedback Client consolidates feedback into one round before work resumes ## Beyond the boundary Additional rounds require $150/hr or a signed change order. Work does not continue on unpaid extras until accepted in writing (Change Order). ## Approval When the Client approves a version (or the review window expires without actionable feedback, if contracted), that version may proceed to Approval Lock™ / delivery handoff as agreed.
Want more playbooks like this?
Tell us you are interested. We only record that you used this tool — no inbox signup here.
Finite rounds protect both sides
Unlimited revisions sound friendly and create infinite unpaid cycles. A written boundary makes feedback sharper and delivery predictable.
Deeper template
See also the revision policy guide for longer prose examples, then enforce the boundary in Zlaip where usage is visible.
Common questions
- How many rounds?
- Many studios use 2–3 consolidated rounds per deliverable.
- Are questions a round?
- Usually not: clarify in your policy that micro-questions can be feedback.
- What about rush?
- Call out rush turnaround separately or combine with your revision cost calculator.
- Next step?
- Set your revision boundary on a Simple Zlaip project in minutes.
Ready for live accountability?
Create a Simple project in minutes. Set boundaries, review requests, and lock approvals without building an agency workspace first.