Glossary
Revision Boundary
The line between included feedback and billable extra work. A Revision Boundary caps how many consolidated revision rounds each milestone includes, and what must happen when client feedback keeps coming.
What is a revision boundary?
A revision boundary is the maximum number of revision rounds included in a milestone before additional feedback is treated as out of scope or billable. In freelance and agency contracts, it turns "a few tweaks" from an open-ended favor into a countable, enforceable limit.
On Zlaip, Revision Boundary is a product primitive: the locked agreement stores the limit, Accountability Chat shows usage (for example, 2/3 rounds used), and crossing the boundary routes the next request to a Change Order instead of silent unpaid work.
What happens when you hit the boundary?
When included rounds are exhausted, the next material feedback should trigger a change order: documented scope, fee, timeline, and bilateral acceptance.
Zlaip posts revision usage inline in the agreement timeline and warns when teams approach or cross the limit.
FAQ
Common questions
- Is Revision Boundary the same as a revision clause in a contract?
- Yes in intent. The contract states the limit; Zlaip tracks and enforces it in the live project timeline.
- How many revision rounds should my contract include?
- Two to three per milestone is common for design and content. See our freelance revision rounds guide.
Related
Run your next project with clearer gates
One agreement timeline for review, revisions, approval, and payment — built for creative work accountability.
Create free account