What to record the moment a client asks for “one small change”

Leon Silcott

Capture a client's change request before promising the work: describe it, check the scope and price it. Then ask for an explicit decision about the proposal.

You are on a call when the client asks for “one small change”. It might be a correction already covered by the brief, a new output or something you cannot estimate yet. Your first task is to identify which, rather than saying yes to an undefined amount of work.

This is a capture checklist for that moment. Keep it beside your normal project tools and use it to prepare a proposal when one is needed.

Record the request in their words, then clarify it

Write a plain description and ask enough questions to remove ambiguity. “Add a calendar attachment to the booking confirmation email” is more specific than “improve confirmation”. Ask which bookings, which email and what the customer expects to receive.

Capture a reason if it helps explain the decision, such as a new launch date or a change of platform. Do not invent a motivation or add personal judgements to the record. The purpose is to help another person understand the request later.

Check whether it is already included

Open the accepted scope and relevant feedback terms. A typo you introduced is not automatically an extra because someone has asked you to fix it. A new language version may be outside the agreed output even if the client calls it a tweak.

If you cannot tell, say so:

“I'll check this against the scope and come back with the proposed next step. I don't want to promise a price or date before I understand the change.”

That acknowledges the request without authorising yourself to charge for it or committing to absorb it.

Estimate the work before quoting

List what you need to investigate, build, review and hand over. A visible change can have less visible work around it. For a calendar attachment, that might include checking the expected format and testing the agreed behaviour.

Keep your internal effort estimate separate from the price you propose. If you quote a fixed £110 addition, do not call that “two hours at £55” unless that accurately describes the pricing basis you intend to offer.

A hypothetical change note

Daniel's booking-flow project is £2,800 fixed. Before any new payment activity, the client asks for the calendar attachment, which the accepted scope does not include. After assessment, he writes:

“The proposed addition is a calendar attachment to the booking confirmation email, covering the agreed booking types. The fixed addition is £110, bringing the project total to £2,910. Handover would move from Friday to Tuesday. Please review the revised scope and price; the current accepted terms remain until you explicitly accept the proposal.”

The client can ask a question, accept or decline. Daniel does not describe the additional £110 as owed while the proposal is still pending.

If the request comes after payment activity

In AsAgreed, a new payment report or receipt prevents further scope and price revisions on that agreement. Later extras require a fresh agreement. The original project remains its own record, with its existing payment history.

For Daniel, that means a separate £110 proposal if the relevant payment activity already exists. His message should explain that it covers the additional attachment and does not duplicate the £2,800 original job.

Money already paid before setup is a historical starting record, distinct from a new report or confirmed receipt. Use the actual agreement state rather than guessing from the word “deposit”.

If you include it at no extra charge

Say what you are including and whether it affects dates. A clear note might read: “I'll add the extra export format at no additional charge for this project; handover stays Friday.” That records the decision without claiming it creates a rule for every future request.

Do not turn the note into a running account of the client's supposed generosity or demands. It is a work record. If the volume of small additions becomes difficult, discuss the remaining scope and schedule directly.

Finish with a decision and a location

Your capture note should identify the request, scope check, price basis, date effect and what response is needed. Keep the proposal where both people can find it, rather than leaving the only description in your private task list.

AsAgreed holds scope, exclusions, deliverables and price alongside the payment record. Revision rounds are written terms, not automatically counted limits. The freelancers overview explains the pattern. For your next job, describe the starting scope and how you will discuss additions.

Prepare your next freelance scope