What to Say When a Client Asks for One More Small Change

Clients often describe extra requests as tiny: one quick swap, one small copy change, one more export, one extra screen, or one little layout adjustment. Sometimes the change really is included. Sometimes it affects the scope, timeline, approvals, or files you already prepared.

The most useful reply does not debate the word small. It calmly decides which bucket the request belongs in: included revision, paid add-on, priority swap, or future phase. That keeps the conversation about the project process instead of personal flexibility.

If the request fits the agreed revision round, confirm it quickly and protect the review window: "Hi [Name], yes, that change is included in this revision round. I will update [specific item] and send the revised version by [date]. After that, please send any remaining feedback together so we can keep this milestone on track."

This kind of answer is helpful without opening the door to unlimited edits. It tells the client you are handling the request, names exactly what is included, and makes the next feedback step clear.

If the request is new work, be friendly and direct: "Hi [Name], I can help with that. It is outside the current scope because [reason], so I will treat it as a small add-on rather than folding it into this revision round. The added cost would be [price] and it would move the timeline by [timeline impact]. If you want to proceed, I can send the updated approval and payment link before I start."

The key is to reply before doing the work. Once you complete the change, the client may assume it was included. A short written approval keeps the project cleaner and gives both sides a shared record of what changed.

Some clients are not trying to expand the project; they are trying to choose what matters most. When the budget or deadline cannot move, offer a trade instead of a flat no.

Try: "If you want to keep the current budget and deadline, we can replace [included item] with [new change]. If you want to keep both, I will price the new change as an add-on before starting." That gives the client control while keeping the scope honest.

A revision changes something already included in the project. A new deliverable adds something the project did not already include. That distinction matters for websites, design files, videos, copywriting, brand assets, consulting deliverables, and development work.

Useful wording: "The text adjustment on the approved page is included. The new landing page section is a separate deliverable, so I can price that as an add-on if you want it included in this phase."

The easier your project is to understand, the easier these messages are to send. Clear deliverables, revision limits, review windows, milestone payments, approval steps, and final handoff rules make small-change conversations feel routine instead of tense.

MicroFreelanceHub helps freelancers draft safer client replies and create client-ready project links with scope, approvals, signatures, and payment links. It is software for clearer freelance communication and project admin, not legal advice or a guarantee of payment.