Client boundary template
Set revision rules before feedback becomes unpaid scope creep
Copy seven plain-language clauses covering included rounds, consolidated feedback, late feedback, extra rounds, out-of-scope requests, and final approval.
Copy this before kickoff: a freelance revision policy should define included rounds, consolidated feedback, late feedback, extra rounds, out of scope requests, and final approval.
nThis page gives you seven copy-paste clauses plus two client emails you can adapt before the project starts.
nQuick answer: copy this revision policy before the project starts
nA freelance revision policy explains how many revision rounds are included, what counts as a revision, what counts as a new request, when feedback is due, and how extra changes are priced.
nUse the seven clauses below before kickoff. They are written for freelancers, consultants, designers, writers, developers, marketers, and small agencies that need a plain-language boundary without sounding hostile.
nSimple rule: a revision changes approved work inside the original direction. A new request adds scope, changes direction, adds a deliverable, changes the platform or format, arrives after final approval, or reopens work after the feedback window.
nThis article is a practical template library, not legal advice. Adapt the wording to your contract, local law, service type, and client agreement.
nWhen to use a freelance revision policy
nUse a revision policy when a project has any of these risk signals:
n- n
- The client says the project is "simple" but has not defined deliverables. n
- More than one stakeholder will review the work. n
- The timeline is tight and feedback delays would affect delivery. n
- The client asks for "unlimited tweaks" or "small changes until it feels right." n
- The quote includes creative work, copy, design, development, strategy, video, ads, landing pages, or website pages. n
- The project has a fixed fee instead of hourly billing. n
- You have been burned by unpaid extra work before. n
A good policy does not punish the client. It makes the process predictable before emotions rise.
nClause 1: included revision rounds
nUse this when you want to define the number of included rounds clearly.
nCopy block 1
nnINCLUDED REVISION ROUNDSnThis project includes [NUMBER] round(s) of revisions for each listed deliverable.nnA revision round is one consolidated set of feedback sent by the client within the agreed feedback window. I will apply feedback that stays within the original project goal, deliverable, format, and approved direction.nnAdditional revision rounds can be estimated separately before the extra work begins.nBest for: design, copywriting, landing pages, websites, brand assets, paid ads, presentations, editing, and implementation projects.
nCommon setting: one or two rounds for small projects, two or three rounds for larger creative projects. The exact number depends on project size, risk, budget, and stakeholder complexity.
nClause 2: what counts as a revision
nUse this when clients confuse a normal edit with a new deliverable.
nCopy block 2
nnWHAT COUNTS AS A REVISIONnA revision means a change to work that has already been created within the approved scope, direction, deliverable, audience, platform, and format.nnExamples include clarifying wording, adjusting visual details, refining layout, correcting minor errors, or improving the approved concept without changing the original assignment.nThis clause is useful because it gives the client a fair definition. It also prevents you from sounding arbitrary later.
nClause 3: what counts as a new request
nUse this when scope creep usually arrives as "just one more thing."
nCopy block 3
nnWHAT COUNTS AS A NEW REQUESTnA new request means work that changes or adds to the approved scope.nnThis includes new deliverables, new pages, new features, new concepts, new copy directions, new audiences, new file formats, new platform versions, work after final approval, feedback after the agreed feedback window, or changes caused by new business requirements.nnNew requests are paused, summarized, and estimated separately before work begins.nThis is the most important boundary. The client can still ask for more work, but the extra work becomes a priced change instead of an unpaid favor.
nClause 4: consolidated feedback rule
nUse this when several stakeholders send comments separately.
nCopy block 4
nnCONSOLIDATED FEEDBACKnEach revision round should be sent as one consolidated feedback document or message.nnIf multiple stakeholders are involved, the client is responsible for collecting their comments and sending one approved set of feedback. Conflicting comments, separate stakeholder messages, or new feedback after a round has started may be treated as a new revision round or a change request.nThis protects the project from review chaos. It also gives the client a process they can share internally.
nClause 5: feedback window and late feedback
nUse this when delays can push delivery dates or create rush work.
nCopy block 5
nnFEEDBACK WINDOWnClient feedback is due within [NUMBER] business days after each review delivery.nnIf feedback, files, access, or approvals arrive late, the project timeline may move. If the client needs the original deadline after late feedback, rush work may require a separate approval and fee.nThis clause matters because silence is not neutral. Late feedback can damage your calendar and other client commitments.
nClause 6: extra rounds and out-of-scope pricing
nUse this when you want a calm way to charge for additional work.
nCopy block 6
nnEXTRA ROUNDS AND OUT-OF-SCOPE WORKnIf the client requests additional revision rounds or work outside the approved scope, I will send a short change summary before starting.nnThe summary will include what changed, why it is outside the original scope, the added work, the timeline impact, and the additional fee or billing method.nnExtra work begins only after written approval.nIf you know the price, add it. If every project is different, leave room for a short estimate.
nClause 7: final approval and post-approval changes
nUse this when clients approve work and then reopen it later.
nCopy block 7
nnFINAL APPROVALnAfter final approval, the deliverable is considered complete for the agreed scope.nnChanges requested after final approval, after handoff, or after publication may be treated as new work unless they correct an error caused by me within the approved deliverable.nThis is especially important for websites, ads, launches, brand files, video, and content that can keep changing forever.
nShort email to send when a request is out of scope
nUse this when the client asks for more work and you want to stay polite.
nCopy block 8
nnSubject: Quick scope check on the new requestnnHi [Name],nnThanks for sending this over. I can help with it, but it looks like this request goes beyond the approved scope because [brief reason].nnThe original scope included [included item]. This new request adds [new item / new direction / extra round / new format].nnI can send a quick change summary with the added work, timeline impact, and fee before starting. Would you like me to prepare that?nnBest,n[Your Name]nThe point is not to argue. The point is to document the boundary and offer a paid path forward.
nShort email to reset unlimited revision expectations
nUse this when the client has already started sending repeated changes.
nCopy block 9
nnSubject: Revision rounds and next stepsnnHi [Name],nnI want to keep the project organized as we move through feedback.nnThe project includes [NUMBER] revision round(s). So far, we have completed [NUMBER] round(s), and the next round should include one consolidated set of feedback.nnIf new requests come up after that, I can summarize them as additional work and send the timeline and fee before starting.nnThanks,n[Your Name]nThis works best before the relationship becomes tense. Send it as a process note, not a complaint.
nRevision policy checklist before you send a proposal
nBefore you quote the project, confirm these items:
n- n
- How many revision rounds are included? n
- Does a round mean one consolidated set of feedback? n
- Who is the final decision maker? n
- How long does the client have to send feedback? n
- What happens if feedback is late? n
- What counts as a revision? n
- What counts as a new request? n
- How are extra rounds priced? n
- What happens after final approval? n
- Are urgent changes or launch-week changes priced differently? n
If any answer is vague, write it down before kickoff.
nRevision policy examples by freelance service
nDifferent freelancers need different boundaries. Use these examples as starting points.
nWeb designer or developer
nCopy block 10
nnThis project includes [NUMBER] revision round(s) for the approved pages and components. New pages, new features, new integrations, new responsive layouts, new content sections, or changes after approval are estimated separately.nCopywriter or content writer
nCopy block 11
nnThis project includes [NUMBER] revision round(s) for the approved topic, angle, audience, and word count. New angles, new briefs, major restructuring after approval, added sections, or changes to the target audience may be treated as new work.nGraphic designer or brand designer
nCopy block 12
nnThis project includes [NUMBER] revision round(s) for the selected concept. A new concept direction, new asset type, new format, new campaign use, or additional stakeholder direction may require a separate estimate.nMarketing consultant
nCopy block 13
nnThis project includes revisions to the agreed strategy document or campaign plan. New channels, new campaign goals, new reporting requirements, implementation work, or extra workshops are outside the original revision scope unless listed in the proposal.nThe mistake to avoid: unlimited revisions
nUnlimited revisions sound generous, but they usually create three problems:
n- n
- The client has no reason to consolidate feedback. n
- The project can stay open without a clear endpoint. n
- You absorb the cost of unclear decisions, late stakeholders, and changed business priorities. n
A revision policy is not about doing less work. It is about making sure paid work, included work, and new work are not mixed together.
nLink this policy to your client intake form
nA revision policy works best when it is connected to your intake process. Before quoting, ask:
n- n
- Who approves the final work? n
- Who gives feedback? n
- Are there internal stakeholders who may join later? n
- What deadline are you working toward? n
- What would count as a successful final deliverable? n
- What changes are likely after the first draft? n
If you need the full intake workflow, use the related BigBears guide: Freelancer Client Intake Form: Scope Creep Prevention Kit.
nnRevision policy mini builder: choose the right clause set
nUse this decision tree when you do not want to copy every clause. Pick the branch that matches the project risk, then paste the matching blocks into your proposal, intake form, or kickoff email.
n- n
- Small fixed-scope project: use included revision rounds, what counts as a revision, feedback window, and final approval. n
- Multiple stakeholders: add the consolidated feedback rule and name one final decision maker before work starts. n
- Fast deadline or launch week: add late feedback, rush-change pricing, and a written approval checkpoint before urgent work begins. n
- Client asks for “unlimited tweaks”: use the new request definition plus extra rounds and out-of-scope pricing before accepting the project. n
- Unclear deliverables: start with the Freelancer Client Intake Form, then return here after the scope is defined. n
- Price is not settled: estimate revision rounds and rush work with the Freelance Project Quote Calculator. n
- The client adds work after approval: move the request into the Freelance Change Request Form Template before doing the extra work. n
Copyable revision policy starter pack
nREVISION POLICY STARTER PACKnIncluded rounds: This project includes [NUMBER] revision round(s) for the approved deliverables.nRevision definition: A revision improves work within the original direction, deliverable, format, and scope.nNew request definition: New deliverables, new direction, new format, new stakeholder requirements, post-approval changes, or late feedback may be estimated separately.nFeedback window: Client feedback is due within [NUMBER] business days after each review delivery.nApproval rule: Extra work begins only after written approval of the added scope, timeline impact, and fee.nRecommended workflow: intake form → quote calculator → revision policy → change request form. This keeps the page useful as a work kit, not just a list of prompts or generic advice.
nnnFAQ
nHow many revisions should a freelancer include?
nMany freelancers include one to three rounds, depending on the project. Small fixed-scope projects may need one round. Larger creative or website projects may need two or three. The key is to define what a round means and what happens after the included rounds are used.
nShould freelancers offer unlimited revisions?
nUsually no. Unlimited revisions can turn a fixed-fee project into open-ended work. A better option is to include a clear number of rounds and offer additional rounds as paid work.
nWhat is the difference between a revision and a new request?
nA revision improves work inside the approved scope. A new request changes or adds to the scope, such as a new deliverable, new concept, new page, new format, new platform, or work after final approval.
nWhat if the client sends feedback late?
nSay in advance that late feedback may move the timeline. If the client still needs the original deadline, rush work may require a separate approval and fee.
nCan I add a revision policy after the project has started?
nYou can clarify the process, but it is stronger to define it before kickoff. If the project is already active, send a polite reset email that explains remaining rounds and how new requests will be handled.
nIs this revision policy legal advice?
nNo. These are general business workflow examples for freelancers and small operators. They are not legal, financial, tax, or contract advice. Adapt them to your agreement, service type, local law, and professional requirements.
nnnFor freelancers and agencies
Turn revision-policy readers into qualified service leads.
A revision policy is not just legal copy. It can qualify scope, protect delivery time, and connect readers to a measurable revenue-ops offer.
🛑 Tired of Chasing Clients for Payment?
Get 20 copy-paste email templates that cover every stage of the payment cycle — from friendly first reminder to final legal notice. Used by freelancers worldwide.
- ✅ 7 late payment reminders (friendly → firm → final)
- ✅ Templates for disputes, ghosting, and payment plans
- ✅ 20 subject lines that actually get opened
- ✅ Contract payment clause included
⚡ Instant download · 30-day money-back guarantee