Client problems

What to do when a client asks for unlimited revisions: 32 ways to set a workable finish line

When a client asks for unlimited revisions, find out what reassurance they need, check what was actually promised, and propose a clear review process. Define what counts as a revision, who approves the work, and how a round ends before accepting more changes. If unlimited revisions were already offered, acknowledge that promise and discuss a workable delivery process instead of quietly replacing it with a new limit.

A request for endless adjustments can mean several different things: fear of receiving unusable work, uncertainty about the brief, too many reviewers, or an expectation of ongoing support. Those problems need different responses. The aim is to help the client reach an agreed result without letting every new preference restart the project.

The messages below are illustrative wording to adapt to the actual project and agreement. They are not contract clauses or statements about either party’s legal rights.

What to do first when a client requests unlimited revisions

1. Find the relevant proposal, package description, emails, and approved brief. Separate what was promised from what was assumed.
2. Ask what the client worries might remain unresolved after the included review rounds.
3. Sort the current requests into corrections, refinements within the brief, and changes to the brief.
4. Agree on one feedback document, one person responsible for consolidating comments, and a clear review window.
5. Present a concrete next step: a defined revision round, a discussion of a revised scope, or a small checkpoint before further production.

What to do when a client wants unlimited revisions before booking

Start by understanding the concern behind the request. A clear finish line is easier to agree when both sides can describe the result and the review process before money or production time is committed.

1. What to do when a client asks for unlimited revisions in the first inquiry

Ask what type of changes the client expects and why a fixed process feels insufficient. Someone buying a first logo may worry about choosing a weak concept; an experienced marketing team may expect weekly campaign changes. Do not answer both requests with the same package explanation. Describe the actual deliverables, review checkpoints, and available ways to handle additional work.

Keep the response specific enough to support a decision. If the service includes two review rounds, explain what happens in each and how feedback is collected. Do not promise an arbitrary number simply to close the sale. Invite a short example of the revision the client is worried about, then check whether the proposed service addresses it.

• “Which changes do you expect to need after the first review?”
• “The package includes two consolidated review rounds against the agreed brief.”
• “Let us look at an example of a change that feels difficult to predict.”
• “Once that is clear, I can recommend a suitable review process.”

2. What to do when a client fears being stuck with work they dislike

Recognize the concern without agreeing that endless revisions are the only solution. Move uncertainty earlier in the process with a reference discussion, outline, rough concept, or sample section. Explain which decision each checkpoint is intended to settle. A small approved direction is more useful than a large finished deliverable that reveals a basic misunderstanding.

Avoid claiming that a checkpoint guarantees a happy outcome. Instead, describe how it gives the client an opportunity to identify a mismatch before detailed production. Record the chosen direction in plain language, including any unresolved questions. If the client still cannot describe what acceptable work would look like, spend time clarifying the brief before offering a larger revision allowance.

• “We can review a rough direction before I produce the finished version.”
• “Which result would make the work feel unsuitable for the intended use?”
• “The first checkpoint will focus on structure and tone, before detailed polishing.”
• “Let us document the approved direction so later feedback has a shared reference.”

3. What to do when a client compares the offer with an unlimited package

Ask what the competing package actually includes if the client wants to make a comparison. There may be different deliverables, response times, review periods, or subscription arrangements. Explain the structure of the service being offered without speculating about the competitor’s quality, motives, or hidden conditions. The client does not need a speech about why another business is wrong.

Make the comparison useful by connecting the process to the client’s project. A campaign that changes continuously may suit ongoing support; a defined presentation may suit a finite project with clear approvals. If the client prefers the other model, acknowledge the difference. Do not add an unlimited promise that the team cannot realistically support just to make two proposals look alike.

• “Does that package cover a single deliverable or continuing monthly work?”
• “My proposal uses defined review rounds and an agreed approval stage.”
• “For frequent updates, we can discuss an ongoing arrangement separately.”
• “I understand if a different service model is a better fit.”

4. What to do when a client will only book with unlimited revisions

Clarify whether the condition is genuinely non-negotiable or whether it stands for a more specific need. Ask what they want to happen if the first result misses the brief, if preferences change, or if new stakeholders join. These are different situations, and a useful agreement should not rely on one vague phrase to cover all of them.

If the requested model does not fit the service, decline the condition before starting work. Explain the process that can be offered and leave the client free to choose. Avoid accepting now with the intention of enforcing an undisclosed limit later. A respectful mismatch at the proposal stage is easier to handle than a dispute after several weeks of production.

• “Which outcome does unlimited coverage need to protect against?”
• “I can offer the review process described in the proposal.”
• “I cannot commit to an undefined number of changes on this project.”
• “If unlimited revisions are essential, this package may not be the right fit.”

What to do when a client misunderstands the revision allowance

Before discussing additional work, establish whether both sides understood the same process. A label such as “round” is only useful if people know what starts it, what it includes, and when it finishes.

5. What to do when a client thinks every small comment is free forever

Explain how related comments are gathered into a round and why the review process has a finish line. A single small wording change can be easy, but a continuing stream of changes can repeatedly interrupt production, testing, and delivery. Discuss the workflow without exaggerating the effort behind a genuinely minor adjustment.

Show the client how to collect their remaining comments in one place. If a quick courtesy change makes sense, identify it clearly and avoid suggesting that all future updates are included. When the original proposal was vague, acknowledge the ambiguity and agree on a process for the remaining work. Do not present an undocumented internal policy as something the client already accepted.

• “Please gather the remaining comments into one review document.”
• “Each round covers a consolidated set of changes to the current version.”
• “I can include this small adjustment as a courtesy on this occasion.”
• “Let us confirm how later updates will be handled before continuing.”

6. What to do when a client does not know what counts as a revision round

Use a real example from the project. A round might mean reviewing version two, submitting one consolidated feedback list, implementing that list, and checking the changes. The exact definition should follow the actual offer or a newly agreed clarification. Do not assume that an email, meeting, or file upload automatically counts as an entire round.

Specify how questions and incomplete feedback will be handled. A clarification about a requested change should not become a surprise additional round just because it required another message. If the current process is unclear, outline it prospectively and ask the client to confirm. The goal is a usable shared workflow, not a technical definition designed to consume the allowance quickly.

• “For this project, a round starts with one consolidated feedback list.”
• “I will implement that list and send a version showing the changes.”
• “Questions needed to understand the list remain part of that discussion.”
• “Can we use this definition for the remaining review stage?”

7. What to do when a client mistakes revisions for new concepts

Point to the specific change in direction. Refining the spacing of an approved layout differs from creating an unrelated layout; shortening an agreed script differs from writing a new story. Explain the distinction through the deliverable rather than accusing the client of trying to obtain free work. Some clients have never used a creative service before.

Offer a choice that preserves momentum: refine the selected concept or discuss an additional concept with its own scope and timing. If the initial concept genuinely missed the agreed brief, address that mismatch first. A provider should not use the word “concept” to reclassify an error as an optional extra. For repeated changes of direction, use the separate guide on a client changing the brief.

• “This request changes the approved direction rather than refining its details.”
• “We can continue developing concept B using the current feedback.”
• “Alternatively, I can outline the work involved in a new concept.”
• “First, let us check whether the current version follows the agreed brief.”

8. What to do when a client expects revisions after approving the final version

Locate the approval and ask what has changed since it was given. The client may have discovered an error, received a new requirement, or simply reconsidered a preference. Those reasons should lead to different conversations. Do not treat an approval email as evidence that every later concern is unreasonable.

Explain which stage the project has reached and what the requested change affects. An adjustment before delivery may be simpler than replacing files already supplied to several teams. Refer to the actual agreement about post-approval work, then propose a practical next step. Avoid asserting that approval automatically removes all obligations; focus on identifying the work and agreeing how to proceed.

• “I have the approval for version four. What prompted the new change?”
• “Is this a correction to the approved content or a new preference?”
• “The files have already been prepared, so I will check the downstream impact.”
• “I can then confirm the process for making this update.”

What to do when a client keeps sending revisions without a complete review

The number of comments is not always the real problem. Feedback arriving in fragments can keep a project open even when the total work is modest. Make the next review easier to complete and easier to trust.

9. What to do when a client sends changes across several channels

Collect the visible requests into one working list and ask the client to confirm it before implementation. Keep the original context where it affects meaning, such as which image a message refers to. Do not rely on memory or silently choose between an email, chat message, and comment in an old file.

Agree on a single place for future feedback. This does not require a new paid tool; a shared document or the existing review system may be enough. Explain that the purpose is to avoid missed instructions and duplicate work. Once the list is confirmed, label the version it applies to and keep later additions separate for review rather than mixing them invisibly into the current batch.

• “I have combined the email and document comments into one list.”
• “Please confirm that this captures the changes for version three.”
• “Can we keep further review notes in this document?”
• “I will flag later additions before including them in the implementation.”

10. What to do when a client sends a new change every day

Ask the client to complete a full review before production resumes, where the schedule and agreement allow. Offer a reasonable review window and explain what needs attention during it: content, layout, names, links, or other project-specific details. Daily messages sometimes mean the client has never been shown how to review the entire deliverable.

Avoid imposing an arbitrary silence rule or declaring late feedback invalid without discussion. Instead, distinguish the current consolidated batch from subsequent requests. If a genuinely urgent correction arrives, assess it separately. The useful change is a predictable cadence: review, consolidate, implement, check. That gives both sides a clear next action and reduces the temptation to keep polishing an unfinished feedback stream.

• “Could the team complete a full review before I implement the next batch?”
• “Please check the content, images, and links together by the agreed review date.”
• “I will work from the consolidated list once it is confirmed.”
• “If something is urgent, flag the reason so we can assess it separately.”

11. What to do when a client adds feedback while changes are being implemented

Make the current work visible: identify the confirmed list and explain which items are already underway. Ask whether the new comment changes something in that list or adds a separate request. A clarification may be easy to incorporate; a reversal of completed work may affect timing and effort. Do not assume all mid-round comments have the same impact.

If the addition can be included without disruption, say so. If it cannot, offer to place it in the next review or agree on an updated batch. Avoid making the client guess whether their message was seen. A short acknowledgement with a clear status prevents duplicate reminders and creates a useful record of what the next version will actually contain.

• “The confirmed changes are already in progress.”
• “Does this replace item six, or is it an additional request?”
• “I can include the text correction in the current batch.”
• “The layout change needs a separate timing check before I add it.”

12. What to do when a client reviews an outdated version

Pause the conflicting instructions and identify the current review file. Show the version name, date, or clearly visible label already used in the project. Ask whether the new comment still applies to that version. Do not implement feedback against an obsolete file merely because it arrived most recently.

Make the review path easier: provide one current link, clearly mark superseded files where appropriate, and explain how to recognize the active version. Keep necessary records rather than deleting history to eliminate confusion. If several comments remain relevant, transfer them into the current review list with the client’s confirmation. Version confusion is a workflow problem to resolve, not a reason to embarrass someone.

• “That screenshot appears to show version two; version four is now under review.”
• “Does the comment still apply to the current file?”
• “Please use this review link for the remaining feedback.”
• “I will carry over the confirmed points so nothing useful is lost.”

What to do when a client involves several reviewers in unlimited revisions

More reviewers can improve a project, but only when someone resolves differences and confirms the final instructions. Ask for an accountable decision process without requiring the client to share internal politics or private discussions.

13. What to do when different stakeholders request opposite revisions

List the incompatible instructions and explain their practical effect. For example, one reviewer wants a shorter page while another requests three additional sections. Ask the client to decide the priority rather than trying to satisfy both through a compromise nobody approved. A neutral comparison is more useful than quoting one colleague against another.

Request a consolidated decision from the agreed contact before implementing the conflicting items. Continue unrelated work only when it is genuinely independent. Do not allow unlimited revisions to become unlimited guessing. If disagreement extends beyond the review process, the guide on contradictory client feedback covers how to clarify priorities and resolve competing instructions.

• “These two comments lead to different versions of the page.”
• “Should brevity or the additional detail take priority?”
• “Please send the team’s agreed instruction for this section.”
• “I can continue the independent corrections while that decision is being made.”

14. What to do when a new decision-maker joins near the final review

Ask the existing contact to explain the new person’s role in approval. Provide a concise summary of the brief, previous decisions, and the current stage so the reviewer can give informed feedback. Do not make them reconstruct the project from a long email chain or assume they intend to overturn everything.

Then distinguish missed requirements from new preferences. If the new reviewer introduces a different objective, discuss the resulting scope and schedule instead of pretending the project is still at the same point. If the original review process omitted a necessary approver, acknowledge the gap and agree how to complete the remaining decisions. The next step should clarify authority as well as comments.

• “Will this reviewer make the final decision or provide recommendations?”
• “Here is the approved brief and a short record of the earlier choices.”
• “Which comments address the existing objective, and which introduce a new one?”
• “Let us confirm the remaining approval steps before another full revision.”

15. What to do when an agency passes through unfiltered client comments

Ask the agency contact to consolidate comments before sending production instructions. An agency may legitimately collect extensive feedback, but forwarding every internal note can create contradictory tasks and repeated rework. Clarify whether the agency is expected to resolve those decisions or whether a joint review meeting would help.

Keep the relationship structure intact. Do not contact the agency’s client directly or change the agreed communication route without permission. Offer a simple feedback format: requested change, reason, priority, and approved instruction. Where a comment is still a question, label it as unresolved. This allows the agency to do its coordinating role while giving production a list that can actually be completed.

• “Could the team resolve the conflicting comments before the next production round?”
• “Please mark which notes are approved instructions and which remain discussion points.”
• “A short joint review may help if that fits the agreed communication process.”
• “I will work from the consolidated list supplied by the agency contact.”

16. What to do when nobody will take responsibility for final approval

Ask the client to name the person or group authorized to confirm completion and explain the decision rule. Some teams need collective approval, but the process still needs a way to record a final outcome. Do not invent authority for the person who replies fastest or assume silence from everyone else means agreement.

Describe what can happen without approval: the work can remain at review stage, certain downstream tasks may need to wait, and the schedule may require discussion. Avoid turning this into a threat. Offer a short approval checklist focused on the agreed deliverable. If the client cannot choose between options, link the issue to making a client decision rather than producing endless alternatives.

• “Who can confirm that the deliverable is ready for final preparation?”
• “If approval is collective, how will the final decision be communicated?”
• “These three points are the remaining decisions before completion.”
• “Let us agree on the approval route before another revision is started.”

What to do when a client requests revisions because the work is not right

A revision allowance should not be used to avoid discussing quality. Check whether the current version meets the brief, whether instructions were implemented correctly, and whether the client has identified a real usability problem.

17. What to do when the work does not follow the approved brief

Compare the disputed section with the specific requirement, not with a general claim that the work looks professional. If the brief called for a concise product page and the draft is a long company history, acknowledge the mismatch. Identify what needs correcting and describe the intended result before producing another version.

Do not immediately present the correction as a paid extra or spend a review meeting defending the amount of effort already invested. Follow the actual agreement and discuss responsibility fairly. Once the correction is made, ask the client to check it against the same requirement. The guide on a client disliking the first draft helps when the underlying problem is broader than the revision allowance.

• “The draft does not yet meet the brief’s requirement for a concise product page.”
• “I will correct the structure and show how it addresses that requirement.”
• “Let us separate this mismatch from the new features requested afterward.”
• “Please review the revised section against the approved objective.”

18. What to do when a requested revision was implemented incorrectly

Check the original instruction and the delivered change together. If the wrong wording, image, or layout was used, acknowledge the implementation error and explain the correction. Avoid asking the client to submit the same request as though it were a fresh preference. A clear change record can resolve the issue quickly.

If the instruction was ambiguous, describe the two possible interpretations and ask which was intended. Do not label the client unclear merely because the result was rejected. After correcting the item, verify the specific details and nearby elements that may have been affected. The client should receive a version that closes the error rather than creating another cycle of avoidable fixes.

• “I applied the wrong image to that section. I will correct it.”
• “The comment could mean either the heading or the paragraph; which should change?”
• “I will check the related captions when I replace the image.”
• “The updated version will identify the corrected item clearly.”

19. What to do when a client reports that the revised work is unusable

Ask for the actual use case and the point where the work fails. A file that cannot be opened, a layout that hides essential text, or copy that omits a required detail needs investigation. Request only the information needed to reproduce or understand the problem. Do not dismiss “unusable” as an emotional reaction, but do not accept it as a complete diagnosis either.

Compare the use case with what was agreed and delivered. If the problem falls within the intended use, propose a correction and a focused check. If the client now needs a different format or application, explain that distinction and discuss options. Avoid promising a fix before checking the cause, especially when another tool, supplier, or altered file may be involved.

• “What happens when the file is used in the intended workflow?”
• “Please show the affected section or the exact error message.”
• “I will compare that result with the agreed delivery requirements.”
• “Once the cause is clear, I can propose the appropriate correction or update.”

20. What to do when a client cannot explain why no revision feels right

Stop generating variations long enough to identify the missing criterion. Ask the client to compare two specific versions and describe which better serves the audience or purpose. Offer neutral prompts about tone, hierarchy, clarity, and emphasis. Avoid forcing the client to use professional terminology or treating a vague reaction as dishonesty.

If the discussion reveals a different objective, update the brief before continuing. If it remains a matter of preference, reduce the decision to one dimension at a time instead of changing everything together. A short review call or annotated example can help. The next version should test a specific hypothesis, such as a calmer tone, rather than being another attempt to guess what “right” means.

• “Which version feels closer, and what specifically makes it closer?”
• “Is the main concern tone, structure, or the visual emphasis?”
• “Let us change one dimension so the next comparison is useful.”
• “Before another full revision, I would like to confirm the intended direction.”

What to do when a client turns revisions into additional project scope

Some requests are valuable but belong to a different scope. Describe the extra work and its dependencies before discussing price or timing. The client should be able to see what has changed and choose a practical route.

21. What to do when a client adds new deliverables during revisions

List the original deliverables beside the newly requested ones. Adding a second presentation, another language version, or a new page is different from refining an existing item. Explain that difference through the work involved, including adaptation and checking, rather than relying only on the phrase “out of scope.”

Ask which outcome matters most now. The client may prefer to replace a planned item, postpone the addition, or request a separate proposal. Check feasibility before offering a substitution, because two deliverables may not require equivalent effort. Record the selected option before production. Do not start the extra work on the assumption that a later conversation will resolve the commercial details.

• “The current scope covers one presentation; this adds a second deliverable.”
• “Would the new item replace an existing priority or sit alongside it?”
• “I can outline the additional work and timing for review.”
• “Please confirm the selected option before I begin the extra deliverable.”

22. What to do when a client supplies new materials after revisions are complete

Check how the new material affects the approved work. A replacement portrait may fit easily; a new product range may change the structure, copy, and layout. Explain the actual impact rather than treating all late files as equally disruptive. If the material corrects an error, separate that from a new content request.

Agree which version becomes the working source and whether further materials are still expected. Otherwise, the next revision may be obsolete before it is delivered. If missing inputs are the underlying issue, use the guide on incomplete client materials. Confirm the remaining dependencies and revised production plan before promising a final date.

• “Does this file replace the approved material or add new content?”
• “The replacement changes the page structure, so I need to assess the impact.”
• “Are any other materials still expected before this version is finalized?”
• “Let us confirm the complete source set before the next revision begins.”

23. What to do when a client wants to restart after approving a direction

Summarize the approved direction and ask what new information makes it unsuitable. A changed audience or product strategy may justify a restart, while uncertainty about a detail may be resolved within the existing concept. Do not assume the client is simply indecisive. Identify the smallest change that would meet the current objective without discarding useful work unnecessarily.

If a restart is needed, describe it as a new planning decision with consequences for remaining tasks and timing. Offer a revised outline for approval before detailed work resumes. Avoid using sunk effort as the only argument against change. The aim is an informed decision about the next stage, supported by a clear record of what will be kept and what will be replaced.

• “What has changed since the direction was approved?”
• “Could a targeted adjustment meet the new need, or is a restart necessary?”
• “I can identify which completed elements remain useful.”
• “Let us approve the revised direction and schedule before rebuilding the deliverable.”

24. What to do when a client expects continuing updates under a one-off project

Ask about the expected frequency and type of future changes. Monthly campaign updates, rotating staff details, or regular product additions may need an ongoing arrangement. Explain how that differs from finishing the current deliverable, without implying that a subscription is automatically required or the only available option.

Present practical choices if they fit the service: occasional separately agreed updates, a maintenance arrangement, or a handover that lets the client make suitable changes independently. Clarify what the current project still needs before completion. Do not use the ongoing-service discussion to leave existing issues unresolved, and do not describe future support as unlimited unless the service can genuinely honor that wording.

• “How often do you expect these updates after the initial delivery?”
• “We can separate completion of this project from future content changes.”
• “Occasional updates can be scoped individually if that suits the workflow.”
• “I can also explain the handover or ongoing support options available.”

What to do when a client expects endless revisions on a fixed schedule

An open feedback process and a fixed delivery date can conflict. Make the remaining work visible and ask the client to choose priorities. Explain capacity through the project plan rather than using urgency to pressure a decision.

25. What to do when a client wants another revision without moving the deadline

List the remaining production and checking steps, then assess the new request against them. A small correction may fit; a substantial redesign may not. Give the client a concrete choice between keeping the current scope for the deadline, reducing another agreed element, or discussing a later delivery. Do not promise all three outcomes at once.

Be clear about dependencies such as feedback and approval. If the client can respond promptly, say what that enables without guaranteeing an unverified turnaround. For a broader deadline discussion, see what to do when a client wants work delivered earlier. Document the chosen priority so the next message does not reopen the same trade-off.

• “The new layout request adds work before final checking can begin.”
• “For the current date, we can complete the already agreed version.”
• “Alternatively, I can assess a revised date for the additional changes.”
• “Which outcome should take priority: the current date or the expanded revision?”

26. What to do when a client uses every available day for small revisions

Look at the effect on completion rather than criticizing the number of comments. Repeated small changes can leave too little time for final checks, export, or handover. Show the client the remaining steps and propose a final consolidated review window. Explain what information is needed to move from review to preparation.

Do not invent a cutoff that contradicts the agreement. If a new deadline is needed, discuss it openly and explain why. Separate essential corrections from optional polishing so the client can make an informed choice. A useful finish line is based on readiness for the intended use, not on the provider becoming tired of the project.

• “We still need time for final checking and file preparation after review.”
• “Could we consolidate the remaining comments into one complete list?”
• “Which points are essential for the intended use, and which are optional refinements?”
• “Let us agree on the transition from review to final preparation.”

27. What to do when a client disappears and returns with more revisions

Check the project status and the actual agreement before responding. Establish what was last delivered, which decisions remained open, and whether the new comments refer to that version. Do not assume that a long silence means approval, cancellation, or forfeited support. State the facts that can be verified.

Explain current availability and any dependencies that need refreshing. A project paused for months may involve outdated content, unavailable materials, or a changed schedule. Offer a short restart review to confirm what remains relevant. The separate guide on a client stopping replies covers follow-ups; here, focus on agreeing the revision process before work resumes.

• “The last shared version was awaiting feedback on these two points.”
• “Do the new comments apply to that version and the same brief?”
• “I will check current availability before confirming a restart date.”
• “Let us review the remaining scope so the next round has a clear purpose.”

28. What to do when a client wants immediate revisions whenever a comment arrives

Distinguish the availability of revisions from the speed at which they can be delivered. Even a service with broad revision coverage needs an understood scheduling process. Explain the actual response and production arrangements already offered. Do not manufacture a service level that was never agreed or promise immediate work while other commitments make that impossible.

Ask whether a particular comment is time-sensitive and what event drives the urgency. Where feasible, prioritize a small essential fix and schedule the rest. Confirm the queue or next review date in plain language. The client should know when to expect an acknowledgement and when to expect completed work, since those are different milestones.

• “I have received the comments and will confirm their production timing.”
• “Is any item tied to a specific event or release?”
• “The essential correction may be handled separately from the broader changes.”
• “I will confirm the next delivery point once the batch is assessed.”

What to do when a client disputes the limit or the project needs closure

Use the original wording and the project record as the starting point. A fair resolution may involve clarifying a promise, acknowledging an error, or agreeing on a different arrangement. Avoid threats, surprise conditions, and arguments about motives.

29. What to do when unlimited revisions were already promised

Find the exact promise and acknowledge it directly. Check whether it was linked to a particular deliverable, review period, or service model, but do not invent missing qualifications. Explain the practical problem with the current workflow and invite a mutually understood way to continue. A process clarification should not secretly remove what was offered.

Suggest consolidated feedback, clearer acceptance criteria, or scheduled review batches while preserving the substance of the agreement. If the promise cannot be fulfilled as understood, discuss a resolution openly rather than unilaterally announcing a new cap. Where the disagreement becomes contractual, obtain advice appropriate to the actual agreement and location; a general communication guide cannot determine either party’s rights.

• “The proposal used the phrase unlimited revisions, and I acknowledge that.”
• “We need a clearer way to consolidate feedback and confirm each completed batch.”
• “I am proposing a review workflow, not an undisclosed retroactive limit.”
• “If our understanding differs, let us resolve that before further work is scheduled.”

30. What to do when a client refuses additional charges for new work

Return to the specific disputed request and the original scope. Explain why the work is being treated as an addition, and invite the client to point to any wording they believe includes it. Avoid repeating “policy” as though it resolves a genuine ambiguity. If the provider’s wording caused confusion, acknowledge that contribution.

Offer the available paths without starting unapproved work: finish the agreed scope, discuss a smaller addition, or resolve the disputed interpretation first. Do not create an invoice for work the client has not agreed to merely to force a decision. Keep the discussion focused on what will happen next, with any contractual dispute handled through appropriate advice rather than improvised legal claims.

• “This request adds a deliverable that is not listed in the current scope.”
• “Please show me the wording that led to a different expectation.”
• “We can continue with the agreed deliverable while discussing the proposed addition.”
• “I will not begin the extra work until its scope and terms are resolved.”

31. What to do when a client is upset about setting a finish line

Acknowledge the frustration and explain the proposed finish line in terms of project readiness. The client may hear a revision limit as “accept whatever is delivered,” especially if previous issues remain unresolved. Identify those issues and explain how they will be addressed. Do not blend legitimate corrections into a general complaint about excessive feedback.

Give the client a concise remaining-work list and ask whether it captures the essential concerns. Keep the tone calm, with no references to how difficult they have been. If a conversation becomes abusive, end that exchange respectfully and use an appropriate communication boundary. The objective is a clear completion process, not winning an argument about who has been more patient.

• “I understand the concern about closing the project before the issues are resolved.”
• “These are the remaining corrections and decisions I have recorded.”
• “Does this list capture the points needed for the intended use?”
• “I would like us to agree on completion based on those specific points.”

32. What to do when a client is ready to approve but keeps hesitating

Make approval concrete. Present the current version, the completed feedback list, any known limitations, and the remaining decision in one short message. Ask for confirmation of the agreed deliverable rather than a promise that the client will never want anything different. Perfection is not a practical approval standard.

If hesitation continues, ask which unresolved concern prevents the decision. Address that concern or explain the available next step. Do not treat silence as approval unless the actual process supports that interpretation and it is appropriate to rely on it. Once approval is received, confirm delivery and explain the route for later updates so the project can close with a clear handover.

• “Version six includes the confirmed changes listed below.”
• “Is there a specific unresolved issue preventing approval?”
• “Please confirm whether this version meets the agreed delivery requirements.”
• “After approval, I will complete the handover and explain how future updates can be requested.”

What to avoid when discussing unlimited revisions

Do not add a hidden cap after advertising unlimited work. Do not count every clarification as a new round simply to exhaust an allowance. Do not charge for a new direction before checking whether the original version followed the brief. Equally, do not accept an undefined stream of additions while hoping the client will eventually stop asking.

Avoid blaming individual reviewers, deleting the decision history, or threatening to withhold files without checking the agreement. Keep approval, payment, delivery, and later support as clear project topics. If the disagreement involves contractual rights or a material dispute, pause assumptions and seek suitable professional advice.

Frequently asked questions about unlimited client revisions

What to do when a client asks how many revision rounds are reasonable?

Explain the process needed for this particular deliverable rather than presenting one number as an industry rule. An outline, concept review, and final detail check may suit one project; another may need a different sequence. Define the purpose of each stage and discuss additional work before it begins.

What to do when a client asks whether a typo uses a revision round?

Check who introduced the typo and what the agreement says about corrections. A provider’s implementation error should be discussed as an error, not casually relabeled as a fresh preference. Clarify the correction and check nearby content. Avoid making an absolute legal promise about every possible mistake.

What to do when a client asks for unlimited revisions but accepts a fixed review period?

Clarify what work is covered, how feedback is consolidated, how delivery is scheduled, and what happens to requests received near the end of the period. A time window alone does not define the service. Make sure both sides understand the arrangement before describing it as a solution.

What to do when a client wants to buy extra revision rounds in advance?

Describe what each additional round would include and whether the project genuinely needs it. More rounds do not resolve an unclear brief or conflicting decision-makers. Offer the relevant option only if it fits the service, with the actual terms explained before the client commits.

What to do when a client asks for the simplest revision agreement?

Use plain language covering the deliverable, review stages, feedback method, approval responsibility, corrections, and changes of scope. A short process summary can support understanding, but it is not a substitute for appropriate contractual advice. Avoid copying generic clauses that do not match the service being provided.