Freelance scope creep: turn an added request into a shared decision.

Identify requests that gradually change the project.

Scope creep is a project expanding during the work without a clear decision about the consequences. An addition can seem small, then require new research, other contributors or a different handoff. Make that change visible early enough to choose how it will be handled.

Describe what the request actually involves

First listen to the need behind it. A client question may simply seek to understand the planned work. Ask what they expect, who the result is for and when it is needed. You can compare a specific result with the project rather than reacting to a phrase such as “just a small addition”.

Consider effects on deliverables, people involved, resources to collect and stages already completed. A change that is quick to describe can require work; a useful clarification can also prevent an error without expanding the order. The length of the message does not determine the price.

Make small exceptions visible

You can include an adjustment without an extra fee where that suits the relationship. Explain what you are covering and its limits. Tracking those decisions also helps you notice when several exceptions begin to transform the project or move its original priorities, while leaving both parties with different expectations.

Compare the request with the reference version and accepted changes.

Before classifying an addition, gather the chosen quote or agreement, appendices and changes agreed since. Identify the version describing deliverables, exclusions, client contributions and review arrangements. An initial proposal may have evolved; the comparison needs to account for what the parties actually decided afterwards.

Follow a fictional consulting project

Consider a fictional organisational review covering four interviews, a recommendations report and a presentation meeting. During the project, the client requests a workshop to train their team in a new method. First clarify duration, participants, exercises and expected materials.

Compare those elements with the planned presentation and discussions since the agreement. A presentation and practical workshop may need different preparation. If training has already been mentioned, find what was discussed and confirmed before concluding that it is entirely new. The name of the meeting alone does not settle its content.

Separate established points from questions

Record the current request, relevant passages and open questions. In Dealokr, terms and signature remain a project reference; compare them with useful commercial documents and communications. You and the client should be able to look at the same material, including anything that calls for correcting your first interpretation.

Distinguish a mismatch, revision and added result.

The comparison helps you choose the right discussion. The client may report an unfulfilled commitment, request a planned adjustment or want a new result. One comment can combine these issues; separate them before discussing an extra fee, remaining round or new date.

Consider each part according to its content

In the fictional review, part of the promised analysis may be missing: examine that mismatch against the commitment. A request to clarify a recommendation may fall within the planned work and review. A practical workshop with materials and exercises may be a change to discuss, depending on the agreed scope.

Ask the client to explain the intended use when the difference remains unclear. An explanation during the presentation, an expanded report and a training session do not necessarily involve the same work. Calling something a “correction” or an “addition” does not settle its treatment on its own.

Preserve applicable commitments

Under French law, legally formed contracts bind the parties and must be performed in good faith. Civil Code article 1217 also provides remedies for non-performance, subject to their conditions. A revision limit or scope disagreement therefore does not automatically make every correction chargeable.

For a disputed mismatch, examine the facts and an appropriate response. For an identified additional need, move to a clear proposal about its consequences. These discussions can proceed separately once you have distinguished the parts of the request.

Choose between adding, replacing and postponing.

An additional request can be handled in several ways. Present options addressing the need and consequences for deliverables, price, time and expected contributions. The client then has a decision to make, with the information needed to choose a priority and understand what that choice changes.

Compare options in the fictional case

A replacement is not automatically equivalent in workload or value. Check what it actually removes and adds. Postponing also leaves price and content to agree: a later date does not settle those questions by itself.

Explain the estimate and required contributions

Specify preparation time, resources and decisions expected from the client. For a workshop, participant numbers, their experience and cases to work through can change the proposal. Identify what still needs clarification to establish price or timing, then have the selected option confirmed before producing the added work.

Discuss a scope disagreement using the facts.

If the client thinks the request was included and you understand otherwise, start by restating both interpretations. Ask which documents or exchanges they rely on and share yours. The discussion becomes more useful when it concerns the expected result and decisions made, with the same versions available to both parties.

Reconstruct what each party understood

In our example, “presentation to the team” may have been understood as training. Examine what was described: presenting conclusions, answering questions, practical exercises or reusable materials. Insufficient wording can explain the difference without either party having tried to impose a hidden request.

Keep the points on which you agree, such as interviews completed, the planned report or presentation date. Isolate the disputed point next. Ask what the client wants to be able to do after the meeting and explain the work needed to produce that result.

You could say: “I understood a presentation of the recommendations. You also expect exercises so the team can apply the method. Let’s review that point and the materials needed so we can decide what happens next.” This invites clarification without immediately announcing who is wrong.

Agree a next step with an owner and date

Present alternatives, what they change and what still needs deciding. If you recognise an element was included, explain how it will be addressed. If you agree a commercial compromise, specify its scope and the commitments preserved. Identify who can confirm the decision and agree the next conversation.

If a significant disagreement persists, seek support to examine the circumstances and appropriate next step. A scope dispute does not automatically authorise suspension, withholding files or a particular payment outcome. This guide helps clarify the discussion; a legal decision needs its own assessment.

Have the decision and its effects accepted.

An option discussed needs to become an understandable decision before you produce added work. Summarise what changes, what remains planned, any price, dates and client contributions. Check that the person responding can commit to the decision you need.

Confirm a specific change

French Civil Code article 1193 provides for contractual change by mutual consent or on grounds authorised by law. In practice, keep the restated need and acceptance of its consequences with the original basis. Choose documents suited to the circumstances, particularly where the stakes justify an additional agreement.

If you offer an adjustment without another fee, identify the work and any effect on dates. If an amount will be estimated after receiving information, do not turn that future estimate into an already accepted price. An enthusiastic conversation does not resolve every condition for carrying out the work.

Prepare the next action

In Dealokr, the preview and revision requests support discussion of the work presented. Connect the new reference with the agreed decisions, then specify the next action. If confirmation is missing, follow up on that point and clarify together what can move forward in the project.

Keep the history and check that the next steps remain consistent.

Keep the original agreement, important requests and accepted decisions in a readable order. Identify versions and dates that explain what changed. This helps you find the actual project basis during the next review, including when a new person joins the discussion.

Prevent old expectations from remaining active

After replacement or postponement, recap the retained deliverables and what is no longer planned in the same phase. Check that the schedule and client messages reflect the decision. A consolidated version helps where it keeps a clear connection to the accepted change.

For fixed-price work in Dealokr, the client pays 100% before production through Stripe Connect, then views a preview and can request the agreed revisions. You request the transfer under the project’s conditions; confirmation opens access to hosted final files. The bank payout and external service permissions remain separate. A discussed change does not create an automatic additional payment.

Improve scope discussions for the next project

Note wording or a question that could have helped avoid the misunderstanding. Use that experience to clarify a future proposal without turning every exception into a rigid rule. The aim remains to make the choices changing the work visible and confirm them at the useful moment.