Freelancers and consultants · The edges of the job

A change request shouldn’t quietly rewrite the whole job.

When a client asks for “just one more thing”, the useful move is not a quick yes or no. It is to see what changed and agree what happens next before the extra work begins.

A practical method · 6 min read

A white project brief and a translucent peach change slip stay distinct along a periwinkle thread.

The scene

The message looks small. The job changes anyway.

The project is already moving when a note arrives: add another format, revisit something that was approved, bring in another person. On its own, the request may sound quick. In the actual job it can move tasks, dependencies, delivery or the fee.

If you answer before reopening the agreement, the change enters the project without a clear moment when it was understood and accepted. Later, you remember an extra; the client remembers an ordinary revision.

Before replying

When does a request become a change to the job?

It is not about the length of the message. Compare the request with the starting point and make four things visible.

1
The original agreementThe deliverable, revisions and conditions you had already confirmed.
2
The exact changeWhat is being added, removed or redone, stated without vague shorthand.
3
The impactWhich tasks, dependencies, timing or costs may actually move.
4
The decisionWhat must be confirmed before the additional work begins.

The method

Pause before turning the request into a task.

Show that you understood: summarise the change in one sentence and connect it to the work already agreed. Then name what needs a decision — perhaps a different priority, a later delivery or a fee adjustment — without assigning motives the client never expressed.

Only after confirmation should the job and its next step change. If the request remains suspended in a chat while you start anyway, ambiguity grows with the project. If the decision stays beside the agreement, even a no or an alternative can remain professional and easy to understand.

With Avanlio

Agreement, change and next step stay on the same thread.

Avanlio is built so a request does not live apart from the client, the job and the documents that explain its context. Assist can prepare a proposal from the sources you choose, but it neither sends nor saves changes without clear confirmation.

The benefit is not automating a delicate negotiation. It is seeing the difference between what was already included and what has changed, so you can decide without relying on memory.

If the boundary begins at the proposal stage, also read how to decide the follow-up after a proposal. Or see how Avanlio works for freelancers and consultants.

Questions

Short answers.

When does a client request become a change to the job?

When it changes the deliverable, the order of the work, the agreed timing or the expected fee.

How can you answer an extra request without making the relationship rigid?

Summarise the request, connect it to the original agreement and propose a clear decision before starting the additional work.

Does Avanlio approve or send the reply to the client?

No. Assist can prepare a proposal from the sources you choose, but it neither sends nor saves changes without clear confirmation.

Open beta

If every extra request makes you rebuild the agreement, tell us how you work.

The beta is open: sign up, confirm your address and get the link to join. No card required.

Join the beta