A client who asks for “just one more thing” is not necessarily acting in bad faith. Requests grow because people see new possibilities as the work unfolds, or because they assume a small addition will not affect the schedule. The challenge for a freelancer is to respond without sounding defensive and without quietly absorbing the extra work. The approach in this guide is simple: restate the request, explain the tradeoffs, and record the agreed change. Each step keeps the focus on the work rather than on blame.
A practical example
“Could you also make the guide into slides?” is a reasonable question from a client. It is not necessarily a small change. Check the agreed deliverable before answering: correcting a mistake in your guide is different from producing a second format.
“The editable guide and its revision are included. Slides would be a separate deliverable. I can finish the guide on Friday as planned and quote the slides for next week. If the slides are more urgent, I can price a switch and confirm what happens to the guide. Which would help most?”
If the work was already promised, say so and do it. If the brief is ambiguous, show the client the relevant wording and clarify what each of you understood before discussing a fee. For genuinely new work, specify the extra price, the revised date, what is no longer included, and who can approve the change. A request is not approval to send a larger invoice.
Decline when the change does not fit
Sometimes the best answer is no, or not yet. If the request would compromise the quality of the agreed work or the timeline is fixed, say so politely and propose a later phase. You do not need to justify every boundary in detail. A clear explanation and a constructive alternative are enough.
Once the client decides, add the agreed change to the working brief and send both parties the same version. If the client declines the extra work, confirm the original deliverable and carry on. There is no need to renegotiate the whole project.
Restate the request in your own words
Begin by confirming that you understand the request. A short summary such as “You would like the pricing page to include a comparison table, and you want it ready before the launch on Friday” shows that you listened. It also gives the client a chance to correct any misunderstanding before you discuss effort or cost. Restating is especially useful when the request arrives in a quick message or during a call.
Avoid responding immediately with a price or a refusal. A brief pause to restate the request keeps the conversation calm and gives you time to think.
Compare the request with the agreed scope
Check the request against the brief, the quote, and any earlier emails. Is the new work already covered, partly covered, or outside the agreement? Be honest with yourself. Some requests are small clarifications that fit the scope, while others change the deliverables in a meaningful way. Making this comparison privately before you reply helps you respond consistently.
Explain the tradeoffs
Describe what the change would affect. Extra work may require more time, which can delay another deliverable. It may also change the quality of the rest of the project if the schedule becomes tight. Present these tradeoffs as facts rather than complaints. For example, “Adding the comparison table would take about three hours, which would move the final review to Wednesday” gives the client a clear choice.
Offer options where you can. You might suggest adding the table as a separate task with its own quote, or including a simpler version within the current scope.
Offer a clear set of choices
Most scope changes can be handled in one of three ways: the client accepts a revised timeline, the client approves an additional fee, or the client chooses a smaller version that fits the existing agreement. Name the options in a short list. Clear choices make it easier for the client to decide, and they keep the conversation productive rather than adversarial.
Record the agreed change in writing
Once the client chooses, confirm the decision in writing. Describe the new deliverable, the updated date, and any change in price. Ask the client to reply with approval. A short email is usually enough, though a formal change request may be better for larger projects. Written records protect both parties and prevent later disagreement about what was agreed.
Update the brief and invoice
Update the project brief so it reflects the agreed change, and send the revised version to the client. If the change affects payment, include the adjustment in the next invoice and refer to the change request. Keeping the documentation current makes the final project easier to close, and it helps you remember the reasons for each decision later.
Keep the tone factual
Avoid language that assigns blame, such as “You keep adding work” or “This was never included.” Instead, describe the situation neutrally: “This request is outside the original scope, so here are the options.” A calm tone helps the client accept the change without feeling criticized. It also protects the relationship, which may lead to future projects.







