Managing Client Revision Requests as a Solo Business: Four Checks Before Saying Yes

Judge the changed result, not the length of the request

When a client asks for a revision, first establish what changes from the agreed deliverable instead of immediately estimating the work. Distinguishing your own error, a revision within the agreed scope, and an additional deliverable gives you a basis for explaining costs and timing.

“Please change one line” can mean very different things. Correcting a typo and changing the target audience of an approved advertisement may involve a similar number of characters but require different reviews. What matters is the changed result, not the length of the request.

Not every request is additional work

Start with these three categories. They are an operating framework; always check the actual terms agreed with the client.

• Error correction: fixing something you produced differently from the agreed requirements. Entering a supplied phone number incorrectly is your error, not a change of mind by the client.
• In-scope revision: refining the agreed deliverable without changing its direction, under the included revision terms. Compare the requested change with those terms.
• Additional work: a new or changed number, purpose, audience, or direction of deliverables. Confirm the changed scope and timing before starting.

Check four things before starting

1. What deliverable is currently agreed? Use the latest quote, scope document, or approval email. If memories differ, review the same source together instead of immediately declaring one person right.
2. What does this request change? Write a before-and-after sentence covering wording, screen count, channel, audience, or file format. Ask for a concrete example when a phrase such as “make it more premium” does not define an assessable result.
3. Does it affect other work or the schedule? Include review, testing, and changes to related deliverables, not just editing time. A small request does not automatically justify promising the original deadline.
4. Who needs to decide what, and when, before work can begin? Identify the client approver, required materials, and feasible start date. Acknowledging receipt is different from committing to start.

You do not need to send the client a long explanation of all four checks. Review them carefully internally, then make the changed elements and available next steps clear.

How to assess a request for one more page

Here is a hypothetical example. You are creating one service introduction page, and the client asks for an event registration page as well.

A page for the same brand is not automatically included in the original revision scope. Check whether registration fields, completion instructions, and submission confirmation require separate preparation and review. Conversely, correcting a date you entered incorrectly on the original page should not be classified as additional work by the same logic.

If the initial agreement was unclear, acknowledge that first and clarify what will be done now together. Do not describe a newly introduced criterion as a rule already agreed in the past.

Reply in the order: receipt, impact, options

Do not promise an unverified deadline immediately after receiving a request. You can first acknowledge it and say when you will share the assessment. Adapt this example to the actual situation:

After reviewing, present feasible options with their actual conditions. Explain whether the original scope can stay, selected items can be replaced, or separate work is needed, and obtain the client's confirmation before starting. Do not hide changes in price or dates.

Do not start at your own discretion just because the client has not replied. Separately assess whether other already-agreed work needs to pause. One change request should not become an indefinite wait for the entire project.

Keep requests and approval outcomes together

Before introducing another management tool, keep a concise record for each request:

• Date received and the location of the original request
• What changes from the existing agreement
• The assessed category: error correction, in-scope revision, or additional work
• Schedule and conditions communicated to the client
• Approver and their actual response
• Next action and review date

A brief recap of phone decisions sent to the client for confirmation can also align understanding. A written record alone does not prove that agreement is complete; distinguish unanswered items from confirmed ones.

Frequently asked questions

Does every quick request require a new quote?

Not necessarily. Check the agreed scope and schedule impact first. If you decide to include it, record exactly what is included this time and what remains in scope. The aim is not to bill for every small request, but to make recurring judgments visible.

What if requests arrive through several channels?

Rather than making the client repeat the same explanation across channels, start by having the recipient consolidate the requests and send an up-to-date summary. If instructions conflict, ask the client's final approver to confirm priorities.

Can AI classify the requests?

It can help organize a draft after you check that sensitive client information will not be sent to an external tool. However, a person who has reviewed the actual agreement and feasibility must decide what to include, what price to communicate, and what deadline to promise.

Start with one recent request today

Choose one recent “just one more thing” request and answer the four questions. Even if work has already started, you can begin by separating confirmed facts from open decisions.

If your quotation criteria need work, review what to check before setting a first service quote. For repeated questions, see how to write an FAQ that helps clients choose their next action.

To reuse these criteria on the next project, continue with turning recurring work into a one-page operating manual. Teams that exchange requests by email can also consult primary email and inquiry-record operating principles from OfficialMail, operated by KAVENIX. Before choosing a tool, decide who evaluates requests and what response they should leave.