Client problems

What to do when a client asks for free extra work: 32 ways to respond clearly

When a client asks for free extra work, check whether the request is already included, corrects an error, or adds a new deliverable. Explain the specific difference and offer a clear next step: complete the included work, make a defined courtesy adjustment, or agree on an additional scope before starting. Do not surprise the client with a charge for work they did not approve.

The size of the request is only part of the decision. A small change may affect several files, a new task may replace something already planned, or the original proposal may have been unclear. Start with the actual agreement and the current project, not with a blanket assumption that every request is an attempt to take advantage.

The example messages are hypothetical wording for ordinary service conversations. They are not contract clauses or statements about legal rights. Adapt them to the agreed work and the client’s circumstances.

What to do first when a client requests an unpaid addition

1. Identify the exact task and compare it with the approved scope.
2. Separate provider errors, included refinements, and new work before discussing a fee.
3. Assess the real effect on production, checking, dependencies, and timing.
4. Choose an appropriate response: include it, make an explicit courtesy concession, propose a substitution, or quote additional work.
5. Obtain agreement on the next step before starting a chargeable addition, then record the changed scope.

What to do when a client first asks for something extra

Make the request concrete before answering. A clear description allows both sides to distinguish a new task from a correction or a misunderstanding about what the project includes.

1. What to do when a client says a task should only take a minute

Ask what the finished result needs to include and assess the task before agreeing. A visible edit may also require checking, exporting, or updating connected materials. Explain only the work that actually applies; do not exaggerate a small request to justify refusing it.

If the task is genuinely minor and a courtesy adjustment is appropriate, state the boundary. If it has a wider effect, explain that effect and offer an assessed next step. The client’s time estimate is a starting assumption, not a reason to argue about expertise.

• “Let me check the full effect before confirming the adjustment.”
• “The visible edit also changes the matching files that need to be checked.”
• “I can include this specific minor adjustment as a courtesy.”
• “For the broader change, I will outline the work before proceeding.”

2. What to do when a client adds a request casually at the end of a call

Acknowledge the request and repeat what is being asked. Do not let a polite “sure” become an accidental commitment to an undefined deliverable. Explain that the scope and timing need checking before the task can be confirmed.

Include the request in the call summary with a clear status such as awaiting assessment. Keep it separate from work already approved. Once assessed, return with the available options rather than leaving the client to assume it has entered production. A short clarification now prevents a larger misunderstanding later.

• “I have noted the additional one-page summary.”
• “I need to check its scope and timing before confirming it.”
• “The call summary will mark this as awaiting assessment.”
• “I will send the options before beginning that additional task.”

3. What to do when a client asks for an extra through a quick chat message

Clarify the intended output and where it fits in the project. A short message may omit important details such as format, length, or deadline. Do not infer the missing specifications or treat the casual channel as evidence that the work must be free.

Move the confirmed request into the agreed project record if needed. Explain the next step in the same simple tone: assess, clarify, or implement if already included. Avoid forcing the client through an elaborate process for a genuinely straightforward item, but keep any new scope visible.

• “What format and length are needed for the additional summary?”
• “Is this intended to replace an existing item or add another deliverable?”
• “I will record the confirmed request with the project scope.”
• “Once the details are clear, I can confirm how it will be handled.”

4. What to do when a client says the extra was obviously included

Ask which wording or discussion created that expectation, then review it fairly. The proposal may be ambiguous, or the task may indeed have been promised. Do not respond with an internal checklist that the client never saw.

If the work is included, acknowledge that and arrange completion. If the interpretation differs, explain the specific scope language and seek a practical resolution. Avoid pretending that a vague proposal becomes clear simply because the provider intended something narrower. The next step should resolve both the current request and the remaining boundary.

• “Which part of the proposal led to that understanding?”
• “Let us compare the request with the wording we agreed.”
• “If it is included, I will confirm its place in the delivery plan.”
• “If the wording is unclear, we should resolve that before discussing additional work.”

What to do when the request may be a correction rather than extra work

Check responsibility before discussing price. A request to fix the agreed deliverable differs from a new preference, and neither side benefits when those categories are mixed together.

5. What to do when a client asks to fix a provider’s mistake

Compare the reported issue with the approved instruction and delivered version. If the wrong text, file, or setting was used, acknowledge the error and identify the correction. Do not describe repeating the original instruction as a new task merely because production was already completed.

Explain the correction process and check related elements that may have been affected. Follow the actual agreement rather than making broad legal claims about responsibility. A clear fix can restore the working process more effectively than a defensive conversation about how small the error is.

• “The delivered version does not match the approved instruction at this point.”
• “I will correct that mismatch and check the related files.”
• “This should be discussed as a correction to the agreed work.”
• “I will confirm when the corrected version is ready for review.”

6. What to do when a client asks for work needed to meet the original brief

Check whether the requested task is necessary for the promised deliverable to function as described. A missing required section may be incomplete work, while an optional enhancement may be an addition. Use the brief and intended use to make the distinction.

Acknowledge omissions rather than relying only on a narrow task list that conflicts with the promised outcome. If the requirement was not agreed, explain the difference and discuss it. The guide on a client disliking the first draft helps when the mismatch is broader than one missing task.

• “Let us check whether this is necessary for the deliverable described in the brief.”
• “The required section is missing and needs to be completed.”
• “The optional feature is a separate addition to that correction.”
• “I will distinguish the two in the next work summary.”

7. What to do when a client changes a preference after the work was approved

Ask what prompted the change and assess its effect. A changed preference may be perfectly reasonable, but it is different from correcting an implementation error. Explain that distinction without implying that approval makes every later request illegitimate.

Refer to the actual review arrangement and offer the relevant option. A small adjustment may fit a courtesy decision; a substantial change may need a separate scope. Do not begin with an accusation that the client is wasting completed work. Focus on what needs to happen from the current version.

• “What has changed since this version was approved?”
• “This appears to be a new preference rather than a correction to the instruction.”
• “I will assess the work involved in updating the approved version.”
• “Then we can agree on the appropriate next step.”

8. What to do when a client combines corrections and additions in one list

Separate the list into clear categories with a brief reason for each. Identify provider errors, included review items, and new deliverables. Ask the client to confirm any ambiguous request before assigning it to a category.

Do not hold all corrections hostage to approval of the extras. Explain which items can proceed and which need a scope decision, subject to the actual project arrangements. For a larger review-process issue, see handling unlimited revision requests. Keep the working list easy to understand rather than turning it into a dispute ledger.

• “I have separated the corrections from the proposed additions.”
• “These two items address the existing brief.”
• “The additional format requires a separate scope decision.”
• “Please clarify item five so it can be handled appropriately.”

What to do when a small extra could reasonably be included

A courtesy adjustment can be a sensible choice when it is explicit and manageable. Explain what is included without creating a vague ongoing promise or making the client feel indebted.

9. What to do when the extra is genuinely quick and low impact

Check that the change does not affect other deliverables, review stages, or commitments. If it is straightforward and the provider chooses to include it, say exactly what will be done. Avoid turning a small courtesy into an elaborate favor that demands gratitude.

Record the adjustment in the project update so the final version remains traceable. Make no broader promise about future requests. A clear one-time inclusion is easier for both sides to understand than silently completing the task and later becoming frustrated when another request arrives.

• “I can include this specific text adjustment in the current update.”
• “It does not affect the remaining layout or delivery steps.”
• “I will note the change in the version summary.”
• “Any separate additions can be assessed when their scope is clear.”

10. What to do when a courtesy extra could resolve a misunderstanding

Identify the misunderstanding and acknowledge any contribution from unclear communication. A small defined inclusion may be an efficient resolution when both sides understand the remaining scope. Do not offer it merely to avoid clarifying the issue.

Confirm what the courtesy covers and how similar requests will be handled prospectively. Avoid describing the concession as proof that the client was wrong. The useful outcome is a shared understanding for the rest of the project, not a vague compromise that leaves the same question open.

• “The earlier wording could reasonably have been clearer.”
• “I can include this specific item to resolve the current misunderstanding.”
• “Let us confirm the remaining deliverables in the updated summary.”
• “Future additions will be discussed against that clarified scope.”

11. What to do when a long-term client asks for an occasional favor

Assess the task on its actual merits while considering the working relationship. Familiarity may make a small courtesy appropriate, but it does not remove the need to understand the request. Avoid promising an undefined favor before checking its effect.

If including it, state the specific task and timing. If it is too substantial, explain that without making the client feel punished for asking. The relationship should support a clear conversation, not require either side to guess when generosity ends and normal scope begins.

• “Let me check what the adjustment involves.”
• “I can include this particular item as an occasional courtesy.”
• “The larger request needs its own scope and timing.”
• “I will explain the options so we can choose a practical route.”

12. What to do when a client treats one free extra as a standing entitlement

Refer to the earlier inclusion accurately and clarify that it covered a specific task. Do not rewrite history if the original wording suggested a broader promise. Review what was actually said before drawing a boundary.

Explain how the new request differs and offer an assessment. Keep the tone neutral; the client may have inferred a pattern from previous behavior. Going forward, label discretionary inclusions clearly and keep the standard scope visible. Avoid alternating between silent favors and sudden frustration.

• “The earlier inclusion covered the specific adjustment discussed at that time.”
• “This request adds a different task, so I need to assess it separately.”
• “I will confirm the scope before any new work begins.”
• “The project summary will make future courtesy inclusions explicit.”

What to do when a client offers a trade instead of paying for the extra

A proposed trade may be workable, but its value and obligations need to be clear. Do not accept an informal exchange that creates an unmanageable promise or depends on benefits that may never materialize.

13. What to do when a client offers exposure for extra work

Ask what the proposed exposure actually involves only if the arrangement is relevant to the service. A vague promise of visibility is not a defined exchange. Avoid mocking the client or assuming bad intent; simply assess whether the proposal is something the business wants to accept.

If declining, state that the additional work is available under the normal scope process. Do not claim that exposure never has value or promise to evaluate speculative reach as cash. Any collaboration should be explicit and appropriate, with the actual deliverables understood.

• “The additional work is normally handled through a separate scope.”
• “I am not offering this task in exchange for an undefined visibility arrangement.”
• “If there is a specific collaboration proposal, it can be considered separately.”
• “For this project, I can provide the terms for the requested addition.”

14. What to do when a client offers referrals in return for free work

Separate possible introductions from the confirmed task. Thank the client for considering referrals without treating them as guaranteed business. Do not create a reward arrangement that has not been assessed or approved for the service.

If the business has an appropriate established referral arrangement, explain it accurately. Otherwise, keep the additional work on its own terms. Avoid pressuring the client to disclose other people’s private details to prove the offer. The request is a scope decision, not permission to contact their network.

• “I appreciate the possibility of referrals.”
• “The current task still needs to be scoped on its own.”
• “I do not treat unconfirmed future introductions as payment for additional work.”
• “I can outline the available options for the requested deliverable.”

15. What to do when a client offers future projects for an unpaid addition

Ask whether there is a defined recurring requirement if that would change the service arrangement. An informal possibility should not automatically determine the current scope. Keep the conversation factual rather than questioning the client’s sincerity.

Assess any concrete ongoing arrangement separately, including what work is actually committed. Do not accept an open-ended free addition now while relying on later projects to make it worthwhile. For an ordinary one-off task, explain the current options and let the client decide.

• “Future work may be worth discussing as a separate arrangement.”
• “The current proposal is based on the work confirmed now.”
• “If there is a defined recurring scope, I can assess it.”
• “For this addition, I will provide a clear standalone option.”

16. What to do when a client offers to remove another task in exchange

Compare the tasks before accepting the substitution. Two deliverables may require different preparation, skills, or checking even if they appear similar in size. Work already completed may also change what a practical exchange looks like.

Explain which substitution is feasible and update the scope accordingly. Do not imply that deleting one item always creates equal capacity for another. If the client’s priorities have shifted substantially, use the guide to a changing client brief to reset the remaining work coherently.

• “I can assess whether replacing that task would accommodate the new request.”
• “The effort and dependencies are different, so it is not an automatic exchange.”
• “Some work on the original item has already been completed.”
• “Let us confirm the revised scope before scheduling the replacement.”

What to do when the requested extra changes production or delivery

Describe the actual work and its dependencies. A client cannot make an informed decision from the phrase “out of scope” alone. Explain what changes and offer a feasible route before discussing a new commitment.

17. What to do when a client asks for another format of the finished work

Check whether the requested format was included in the agreed handover. If it was, arrange delivery. If it is new, assess whether conversion requires adaptation, checking, or different assets rather than assuming it is a simple export.

Explain the specific requirement and offer the available option. Do not claim every format change is substantial, but do not promise a usable result before checking it. If the source files cannot support the request, discuss a suitable alternative and keep the limitation visible.

• “The agreed handover includes these formats.”
• “The additional version needs a compatibility and layout check.”
• “I will confirm whether a straightforward export is sufficient.”
• “If adaptation is required, I can outline that work before proceeding.”

18. What to do when a client asks for an extra deliverable near completion

List the requested item separately from the work ready for delivery. Ask whether it is essential to the current release or can follow later. A new deliverable should not silently keep a completed project open indefinitely.

Assess its scope and timing, then explain how it would affect the existing handover. If the original deliverable still has unresolved issues, address those on their own merits. Do not use the addition as a reason to blur completion status or avoid finishing the agreed work.

• “The additional handout is a separate deliverable from the presentation.”
• “Is it needed for the same release or a later stage?”
• “I can assess it without changing the status of the completed presentation.”
• “The proposed timing will show any effect on the current handover.”

19. What to do when a client wants the extra completed by the original deadline

Show the remaining work and assess whether the addition can fit. A small task may be manageable, while another may require a different sequence or extra review. Avoid promising the original date before checking actual capacity.

Offer realistic choices: keep the current scope, reduce another agreed element if feasible, or revise the timing. Explain the trade-off without using urgency as leverage. For a wider deadline discussion, see what to do when a client wants work delivered earlier.

• “The new task needs production and checking in addition to the current work.”
• “I will assess whether it can fit the existing schedule.”
• “We can also compare a smaller first delivery with a later completion date.”
• “Please confirm the priority before the plan is revised.”

20. What to do when a client says the extra is easy because the files already exist

Explain which parts can be reused and which still need work. Existing assets may reduce effort without eliminating adaptation, coordination, or final checks. Do not deny the benefit of reuse merely to defend a fee.

Assess the actual request and describe the remaining task. If it is genuinely straightforward, handle it proportionately. If the client expects a different result from the same files, show the difference. A clear explanation is more useful than a general lecture about the value of professional time.

• “The existing files will reduce the preparation needed.”
• “The new use still requires adapting the layout and checking the final version.”
• “I will assess only the remaining work, including what can be reused.”
• “That will give us a realistic basis for the additional scope.”

What to do when a client questions the additional fee

Return to the actual request, scope, and available options. A pricing question may reveal a misunderstanding, a budget limit, or a different priority. Keep the conversation factual rather than treating the question itself as disrespect.

21. What to do when a client asks why a small addition costs anything

Explain the relevant work in plain language, including any necessary checking or coordination. Keep the explanation proportional to the task. Avoid claiming that every message creates a billable event if that is not the actual service arrangement.

Ask whether the client wants the full addition or a smaller alternative. If the original wording was unclear, address that before insisting on the fee. A useful answer connects the proposed charge to an agreed task; it does not require the client to accept a vague statement about professional worth.

• “The additional task includes adapting the file and checking the final output.”
• “That work is separate from the deliverables in the current proposal.”
• “If a smaller version would meet the need, I can assess it.”
• “Let us resolve any scope ambiguity before agreeing on the addition.”

22. What to do when a client compares the extra with a cheaper alternative

Ask what the alternative includes and compare only the relevant work. Another provider or tool may genuinely fit a simple task. Do not invent quality problems or hidden costs to discourage the client.

Explain the additional service being offered and let the client assess its fit. If they choose another route, clarify any appropriate handover requirements without assuming permission to share working files. The guide on a cheaper competitor comparison covers that decision more fully.

• “What does the alternative include for this specific task?”
• “My option includes the adaptation and checking described here.”
• “If another route meets the need more suitably, that is understandable.”
• “We can clarify any agreed handover requirements separately.”

23. What to do when a client says there is no budget for the addition

Acknowledge the limit and ask whether the new task is essential now. Consider a smaller suitable scope, a feasible substitution, or a later stage. Do not pressure the client to disclose private financial information to justify the constraint.

If no workable option exists, keep the original scope clear and leave the addition unstarted. Avoid promising the same outcome after removing a necessary task. The client should know what can be delivered within the current arrangement and what remains optional or deferred.

• “I understand that there is no additional budget for this stage.”
• “Is the new item essential now, or could it be deferred?”
• “I can assess a smaller option or a practical substitution.”
• “Otherwise, we can complete the agreed scope and leave the addition for later.”

24. What to do when a client asks for a discount on the extra work

Assess the request against the actual task and service. Ask whether scope or timing can change if that would create a useful alternative. Do not offer a discount automatically while leaving an unworkable commitment in place.

If a concession is appropriate, state it clearly and update the offer. If not, explain the price for the proposed addition and leave the decision with the client. For a broader negotiation, see what to do when a client asks for a discount. Avoid fabricated limited-time pressure.

• “I can assess whether a smaller scope would meet the need.”
• “The current price covers the addition described in the proposal.”
• “Any concession would be explicit in the revised offer.”
• “Please confirm whether that option works before the task is scheduled.”

What to do when approval or responsibility for the extra is unclear

A request is not always approval to incur a charge or change the project. Establish who can authorize the addition and what has actually been agreed. Keep tentative discussion separate from production instructions.

25. What to do when an employee requests extra work without approval authority

Ask how additions are approved within the client’s project process. The employee may be gathering options rather than authorizing work. Do not infer authority from their access to the project or familiarity with the team.

Provide a concise scope summary they can send to the appropriate approver. Avoid bypassing the contact or contacting a manager without agreement. Begin the addition only after the required approval is clear. Meanwhile, continue unrelated agreed work where feasible.

• “Who needs to approve additions to the current scope?”
• “I can prepare a short description for that review.”
• “Please confirm the authorized instruction before I begin the extra task.”
• “The existing approved work can continue independently.”

26. What to do when a client says go ahead without confirming the price

Clarify what the response approves. The client may be agreeing to an assessment, a draft, or the full addition. Restate the scope and proposed terms in a concise message rather than assuming the broadest possible interpretation.

Use the actual approval process and wait for the necessary confirmation before starting chargeable work. Do not create urgency by claiming that production has already begun if it has not. A brief clarification can prevent a later disagreement about whether the client knew the addition would be billed.

• “To confirm, does that approve the additional task at the terms provided?”
• “The scope is the two adapted files described in the proposal.”
• “The next step after approval is scheduling production.”
• “Please confirm that understanding before I begin.”

27. What to do when extra work was started before the client approved it

Stop adding to the unapproved task and establish what was actually communicated. Acknowledge if the provider began prematurely. Do not present completed effort as automatic proof that the client owes a charge they never accepted.

Explain the current status and seek an appropriate resolution under the actual agreement. Keep further work paused while the scope and terms are clarified. If a material dispute remains, obtain suitable advice rather than inventing a legal conclusion. The immediate lesson is restoring a clear approval process.

• “The additional task was started before the approval was fully clear.”
• “I should have confirmed the scope and terms first.”
• “Here is the current status; let us agree on an appropriate next step.”
• “No further work on the addition will begin until that is resolved.”

28. What to do when a client denies requesting the extra

Review the request and approval record carefully. Distinguish an exploratory question from an instruction to proceed. Share the relevant context neutrally without selectively quoting a message that changes its meaning.

If the record is ambiguous, acknowledge that and work toward a resolution. Do not insist that the existence of a conversation proves authorization. Keep the disagreement focused on the specific task, and avoid threats or unsupported claims about payment obligations. Clarify how future additions will be confirmed.

• “Let us review the message and what it was intended to authorize.”
• “It may have been a request for an option rather than approval to proceed.”
• “If that was unclear, we need to resolve the current task fairly.”
• “Future additions should have an explicit scope confirmation before production.”

What to do when extra requests become a recurring project problem

Look for a pattern in the workflow: unclear boundaries, changing priorities, or a need for continuing support. Resolve the process rather than handling every new request as an isolated confrontation.

29. What to do when a client asks for a free extra in every review

Summarize the recurring additions and ask whether the original scope still reflects the client’s needs. The project may have evolved, or the client may not understand what a review round covers. Explain the pattern through tasks, not accusations about motives.

Agree on a process for collecting and assessing additions together. Keep corrections separate and define the next decision point. If the issue is endless changes within a deliverable, return to the guide to unlimited revisions. A clearer scope may be more useful than another one-off refusal.

• “Several recent requests add tasks beyond the original deliverables.”
• “Does the current scope still match the intended outcome?”
• “Let us collect the proposed additions and assess them together.”
• “Corrections to the agreed work will remain a separate category.”

30. What to do when a client expects free ongoing support after delivery

Ask what support is being requested and check the actual handover arrangement. A question about using the delivered file differs from recurring content updates or a new task. Do not assume everything after delivery is outside the service.

Explain the support that was included and assess any ongoing need separately. Offer a suitable arrangement only if one exists and fits the client’s workflow. Avoid describing a one-off courtesy answer as unlimited future support. Keep the route for later requests clear and practical.

• “Which part of the delivered work needs help?”
• “The included handover support covers these specific items.”
• “Recurring updates would need a separate arrangement.”
• “I can explain the available options if ongoing help is needed.”

31. What to do when a client becomes upset after an extra is declined

Acknowledge the disappointment and explain the decision through the task and scope. Ask whether there is a specific misunderstanding about what was promised. Do not respond to frustration with a lecture about respecting professionals.

Restate the available options calmly: complete the original scope, assess a smaller addition, or discuss the proposed terms. If the conversation becomes abusive, use an appropriate communication boundary and avoid escalating the exchange. The aim is a workable next step, not forcing the client to agree that the refusal is emotionally satisfying.

• “I understand that this is disappointing.”
• “The requested deliverable is not part of the scope currently agreed.”
• “We can complete the original work or assess a smaller addition.”
• “If the proposal created a different expectation, let us review that wording.”

32. What to do when a client agrees to the additional scope

Confirm the exact task, approval, timing, and any effect on the original project. Use a clear version of the scope so earlier alternatives are not mistaken for the final agreement. Identify the inputs still needed before production.

Keep the addition visible in the delivery and review process. Do not assume acceptance means every related task is also included. Once completed, explain what was delivered and how it fits the agreed request. A well-recorded addition can become an ordinary project change rather than a continuing dispute.

• “The approved addition is the two-format adaptation described in the revised scope.”
• “It requires the final source file before production begins.”
• “The delivery plan reflects the agreed timing and review stage.”
• “I will identify the completed addition in the handover summary.”

What to avoid when discussing unpaid additional work

Do not call included work an extra, charge for an unapproved task, or treat every client question as a production instruction. Do not use a minor courtesy change to imply that the client owes a future favor. Keep corrections, discretionary inclusions, and new deliverables distinct.

Avoid vague scope boundaries and surprise invoices. Do not promise an addition before checking dependencies, then quietly reduce the original deliverable to make room. If the agreement or responsibility is disputed, resolve that question before adding more work or making claims about either party’s rights.

Frequently asked questions about free extra work

What to do when a client asks whether every extra needs a formal quote?

Use a process proportionate to the task and consistent with the agreement. A small defined change may need a concise written confirmation rather than a lengthy document. What matters is that the scope, terms, and authority are clear before chargeable work begins. Do not let a simplified process become an ambiguous one.

What to do when a client asks for a free sample before approving an addition?

Clarify what the sample should demonstrate and whether it is part of the current service. A focused sample may help assess a real uncertainty, but it is still work that needs a clear boundary. Do not provide a complete usable deliverable under the label of a sample unless that is the intended arrangement.

What to do when a client says another provider includes the task for free?

Ask what the alternative package includes and compare the actual scope. The task may be priced within a different package rather than being a standalone concession. Explain the current offer without criticizing the other provider. If the alternative suits the client better, acknowledge that possibility.

What to do when a client asks for a free extra after giving positive feedback?

Thank them for the feedback and assess the new task separately. Praise does not automatically change the scope, and a courtesy inclusion should not be treated as a reward owed for a compliment. Explain the available option in the same practical terms used for other requests.

What to do when a client asks to decide about the fee after seeing the completed extra?

Clarify that the scope and terms need agreement before production if the task is chargeable. Offer an outline, estimate, or suitable assessment step where appropriate. Do not begin with the expectation of negotiating payment afterward. If a different arrangement is proposed, assess and document it explicitly before proceeding.