Work clarity
Client Asks for One More Change? Check What Was Agreed First
Published by OneCell
Before answering a client’s “one more small change,” compare the request with the work you actually agreed. A result that misses an agreed requirement needs a correction. A different deliverable needs a proposal and agreement. If you cannot tell which it is, clarify the request and the earlier commitment before starting.
“Small” describes how the request sounds; it does not establish whether it is included. You can make the next conversation specific without treating every client request as a problem.
Bring the agreed output beside the request
Find the brief, confirmed messages and any changes already agreed. Identify the output, its intended use and the relevant delivery requirements. Use those records together: the latest email may not contain every earlier commitment.
Consider Nia, a fictional freelance illustrator. She agreed to deliver three static icons, each a 512px transparent PNG, for a client’s launch. In this example, the confirmed description says nothing about animation or print versions. Three later requests need different answers.
A white background is a correction to the agreed file
The client notices that one exported PNG has a solid white background. Transparency was part of the agreed output, so this file does not meet that requirement. Nia should address the export problem rather than automatically presenting it as additional work.
She can reply: You’re right—the agreed PNG should have a transparent background. I’ll correct that export and check the replacement. I’ll confirm when the checked file is ready.
In the fictional example, the next check is the replacement export itself. Changing the source file alone would not establish that the delivered PNG is correct. Nia should inspect the new file against the agreed requirements before replacing the earlier handoff.
An animated version is a different deliverable
The client then asks whether one icon can move. That request adds animation to the stated static output. Nia first needs enough detail to assess it: what movement is wanted, where it will be used, and what file or delivery requirements apply?
She can answer: The current delivery covers the three static PNGs. An animated version would add another deliverable. Where will you use it, and what movement do you need? I’ll check the work involved and come back with a proposed delivery and any fee change for agreement before starting.
Use the actual terms and client process. Do not assume that the person forwarding the request can approve additional work or its cost. If this is unclear, ask how the proposal should be confirmed.
A request is not yet an agreed addition. If Nia needs to investigate animation requirements before estimating, she can use the same approach as estimating a task you have not done before. She should assess the work before promising a price or date, rather than inventing one because the request sounds quick.
The Association for Project Management’s change-control guidance separates evaluating a proposed change and its effects from approving it and updating the plan. For a small freelance job, the useful adaptation is a clear comparison and an agreed response in the conversation already being used; it need not become a separate administrative system.
“Suitable for print” needs a more precise question
Now the client asks for files suitable for a printed leaflet. Nia cannot classify that request from those words alone. She needs to know what the printer requires and whether that use was already part of the agreement.
She can ask: Could you send the printer’s required size and file specifications? I’ll compare those with the files and the print use we agreed, then confirm whether anything needs changing.
Do not assume that print means a particular file format, or that the current files will necessarily meet the printer’s needs. Equally, the absence of print instructions from the latest message does not establish that print work is additional.
Change one fact: Nia finds an earlier confirmed message that includes print-ready versions. She must now assess the request against that commitment. It belongs with the agreed work in this example, rather than becoming a new addition simply because the latest brief was shorter. If the records still leave the required output unclear, take the specific gap back to the client.
Keep the pending choice separate from work you can finish
While the animation proposal is awaiting a decision, Nia can correct the white-background PNG if that correction is independent and still useful. She should not begin the animation on the assumption that silence means approval, then surprise the client with a charge.
When a change is confirmed through the actual client process, restate the agreed output, any price change and the delivery arrangement in the existing thread. Keep the earlier brief and the confirmed change available together. If the change affects another promised delivery, resolve that too before treating the plan as settled.
The next action should match what you know: correct an unmet requirement, assess and agree a new deliverable, or ask the question that establishes what was included. That is more useful than deciding how to respond from the word “small.”