Separate a Freelance Correction From a Request for a New Deliverable

A client returns comments on a draft and asks for a few changes. Most are straightforward, but one asks for a new document for a different audience. Before treating the entire message as routine revision, identify which parts correct the agreed work and which parts may change the project. The useful decision is how to clarify that difference while keeping the conversation specific and constructive.

This is a project-planning exercise, not a determination of anybody's contractual rights. The actual agreement and circumstances matter. Your private comparison can help you explain the request, estimate its practical effect and ask for an agreed next step. It should not become a unilateral declaration that every inconvenient comment is outside scope or that a friendly request automatically changes the existing terms.

Reopen the current brief before estimating effort

Find the description of the work that both parties are using. Identify the deliverable, intended audience, format and relevant review process. If those details are spread across several messages, assemble the references without silently rewriting them into your preferred version. The first question is what was agreed, not how much time you would like the latest request to take.

A correction may involve bringing the draft into line with a requirement already present in the brief. A new deliverable may require a different output, research question or audience. Some requests sit between those categories and need discussion. You do not need to settle every possible category in advance. You need enough clarity to ask a useful question about the particular request in front of you.

Avoid judging only by the number of words in the client's message. A short instruction can change the purpose of an assignment, while a long comment may simply explain a small correction. Equally, a task taking longer than you expected is not by itself evidence that the client changed the scope. Compare the requested outcome with the brief before deciding what the extra effort means.

Mark the comments without turning them into a dispute

Make a private list of the requested changes. Beside each, note the relevant part of the brief and whether the connection is clear. Useful labels are correction under the existing brief, clarification needed and possible additional deliverable. These are working labels for your own reasoning. They are more helpful than marking every comment accepted or rejected before you have checked the facts.

If a comment corrects an error you made, acknowledge it plainly. If it asks for something the brief did not clearly address, describe the uncertainty without attributing motives. A message that says the requested summary appears to serve a new audience is easier to discuss than an accusation that the client is trying to get free work. Keep the conversation tied to outputs and decisions.

Check dependencies between comments. A requested change in the main draft may affect an accompanying summary, and the order of decisions can matter. You can ask to resolve the audience question before rewriting both documents. This is a planning request about avoiding unnecessary work, not an assumption that the client must adopt your preferred process or pay a fee you have not agreed.

Follow a fictional revision request

Imagine that a freelancer named Jules is preparing a short internal process guide for a fictional client. The brief identifies employees as the audience and includes one review stage. The client returns a terminology correction, a request to explain an omitted step already in the brief and a suggestion to turn the guide into a public customer handout. These comments concern different decisions even though they arrived in one email.

Jules can address the terminology and missing step as part of meeting the stated brief. The public handout needs clarification because its audience and purpose differ. Jules asks whether the client wants that handout in addition to the internal guide or instead of it. The answer determines which output is needed and whether the existing plan, timing or fee should be discussed before work proceeds.

If the client says the handout was always intended, Jules should compare the actual earlier communications rather than rely solely on memory. If the brief was ambiguous, both parties may need to clarify it. A useful outcome is an agreed current description of the work. Winning an argument about the label revision is less helpful than knowing which deliverables the client expects and which commitments Jules is making.

Present options with their practical consequences

You might offer to complete the existing guide first and discuss the handout separately. Another option could be to replace the planned output with a newly defined one. You may also agree that the additional request is small enough to accommodate within the existing arrangement. The appropriate choice depends on the actual terms, capacity and relationship. Do not promise all options simultaneously just to keep the message agreeable.

The Canadian Freelance Guild recommends describing tasks and deliverables specifically in its contract guidance. That supports a practical conversation about what the current project includes. The guidance is not a ruling on your agreement or a substitute for advice about a particular legal dispute. Use it to improve the question and the written description rather than to declare an automatic entitlement.

For wider context on freelance work in Canada, Talyca discusses contracts and other setup questions. Keep the present scope discussion focused on the actual deliverables and agreed process. Tax treatment, ownership and employment status are separate matters that cannot be settled merely by deciding whether one comment is a revision. Seek the appropriate information for those questions when they arise.

Confirm the next version before producing it

After the discussion, record which comments you will address and which deliverables the next version will contain. Include any agreed changes to timing or other terms through the appropriate process. Do not treat an unsent estimate or an internal planning note as accepted. Keep a copy of the client's response so the work proceeds from a shared understanding rather than from your intention alone.

Preserve the earlier brief and draft as history. A current version should be easy to identify, but overwriting every earlier record can make a later question difficult to reconstruct. Use simple names and a short change note. You are not building a courtroom archive; you are keeping enough context to explain why the next version differs from the one first proposed.

Before starting, ask yourself one final question: can I describe the next deliverable in a sentence that the client would recognise? If not, clarify the remaining difference. A well-managed revision process allows corrections and useful changes while keeping new commitments explicit. The practical result is a clearer piece of work and a clearer conversation about what happens after the comments arrive.