Freelance revision clause: organise feedback and changes.

Explain what counts as a round of feedback.

A revision clause organises how the planned work is reviewed. It should explain the relevant deliverable, the version examined and how a round works. A round might include presenting a version, receiving consolidated comments and then addressing them in an updated version.

Connect feedback to a particular stage

For a video edit, distinguish reviewing the structure, the detailed edit and the checks before export. The decisions needed are not identical at each stage. Explain when the client can request the included adjustments and what needs another discussion if a previously chosen direction changes.

A round should not be counted differently depending on who responds. Explain how requests for clarification, conflicting feedback and the next version will be handled. The client can then consult colleagues and prepare a usable response, while you can identify the material and decisions needed before making changes.

Agree the process before production

Present these arrangements with scope and price. A legally formed contract binds its parties under French law; the number of rounds is a commercial choice to agree for the project. A boundary first revealed after work is presented is much harder to use as a shared reference.

Bring comments together around the right version.

Feedback is easier to address when it refers to the same material. Give each version a clear reference and explain where the client should respond. For a video, timestamps can locate a request; for a mock-up, name the page and relevant element.

Identify who consolidates the views

Ask who collects comments on the client’s side and who can confirm decisions for this phase. Several contributors can take part, but conflicting requests need reconciling. A title change proposed by one person and rejected by another needs a client decision before you make the change.

Specify the chosen channel and a useful feedback format: the relevant element, observed problem, desired result and priority. For a comment such as “this feels too slow”, ask which passage is concerned and what the client wants to communicate more clearly. You get a request you can work on without guessing the intention.

Keep the response and its treatment together

In Dealokr, the preview gives the client material to review and the option to request the agreed revisions. The terms and signature stay in the project as a reference. Identify the client contact and agree a consolidated response for each version: that organisation remains a decision to make together.

Agree the number of rounds and realistic deadlines.

The number of included revisions depends on the service, price and how decisions will be made. A short engagement, film and brand identity do not need the same process. Choose the rounds alongside the work stages and the actual availability of the people who need to respond.

Define what the limit organises

Identify the relevant adjustments and how a request beyond the planned rounds will be considered. The client should understand whether an additional response needs a discussion about time, price or organisation. Avoid making a counter the answer to every situation, particularly when a mismatch with the agreed result is reported.

You can arrange intermediate reviews where the project justifies them. They help confirm a direction before more detailed work. The choice should serve a concrete decision and fit the budget, rather than multiplying presentations with nobody available to examine them.

Specify the starting event and what the period means

Start the response period from an identifiable event, such as making the announced version and review instructions available. Explain which days count and the applicable calendar if you use “business days”. Also agree how a new date will be arranged if a contributor is unavailable. Two rounds or seven days are not universal legal standards.

Distinguish a mismatch, planned revision and added need.

Before responding about price or remaining rounds, compare the comment with scope and the version presented. A request may identify a missing agreed element, propose an included adjustment or introduce a new result. These situations deserve different consideration.

Name the issue before choosing the next step

These examples do not automatically classify a real complaint. A comment can combine issues; separate them and check the facts. The client calling something a “correction”, or the freelancer calling it an “extra”, is not enough to decide how it should be handled.

Preserve applicable commitments and remedies

A revision allowance organises agreed adjustments; it does not, by itself, erase commitments to the commissioned work. French Civil Code article 1217 provides remedies for non-performance or imperfect performance, subject to applicable conditions. Reaching the limit therefore does not automatically make every correction chargeable.

Record the reported mismatch and examine a response suited to the contract and circumstances. For a significant disagreement, seek advice on the approach. The clause should not be used as a general waiver of the client’s ability to have a defect or breach examined.

Price added work and have it accepted before production.

When a request changes the planned result, start by restating it. Explain what is added or replaces an element, the resources required and the effect on timing. You can offer an addition, another priority or a separate phase, according to what addresses the client’s need.

Present a complete decision

For the fictional video, a new interview can change file collection, editing and versions to review. The addition concerns more than a few seconds visible on screen. Explain what needs to be redone and request agreement on price and timing before beginning that work.

Under French law, article 1193 provides for contractual change or revocation by mutual consent or on grounds authorised by law. Article 1104 requires good faith in negotiation, formation and performance. These principles support a clear discussion, without treating an additional request as automatic permission to charge more.

Keep a record of what was agreed

Retain the restated need, agreement on its consequences and the new work reference alongside the original basis. If you include a small adjustment without an additional fee, identify that gesture and its scope. An exception is then less likely to be understood as a permanent expansion of scope or a change to every future review.

Follow up without inventing approval.

A review date helps organise the project, but missing it should not be treated as a decision the client has not expressed. Plan a follow-up identifying the available version, expected response and effect of the wait on later steps.

Have a new deadline clarified

First check that the client received the right link and can view the material. Ask what is needed to respond and propose a date to confirm. If waiting affects production, explain the consequences and agree a revised schedule rather than leaving each party to assume a different next step.

Under French law, Civil Code article 1120 sets the principle that silence does not amount to acceptance, with exceptions arising from legislation, usage, business relations or particular circumstances. Wording that creates automatic approval should therefore not be presented as a rule suitable for every project.

Distinguish review and transfer in Dealokr

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 hosted final files. The bank payout is separate.

Approval or the passage of time does not automatically trigger that transfer. Explain the actual steps to the client and consult the project status before announcing handoff. The follow-up seeks a clear response and helps prepare the next step with the right information.

Adapt an illustrative clause to the project’s choices.

This illustrative wording concerns a fictional video editing engagement between businesses in France. It shows how to connect versions, rounds, a client contact and the handling of requests. The chosen values need discussion and the wording should be reviewed with the rest of the contract; this is not a universal clause.

A fictional example of the process

Example — editing the presentation video defined in the scope.

The service includes two rounds of adjustments within the agreed scope. For each round, the provider makes an identified version available. The client’s designated contact collects contributors’ comments and sends a consistent list through the agreed channel within seven business days of that version becoming available. The calendar used to count those days is specified in the project terms.

The provider examines requests, clarifies unclear points and presents the version resulting from the agreed adjustments. Requests reporting a mismatch with the agreed result are examined separately from adjustment rounds. Any new need or additional work is covered by a proposal specifying price and timing, accepted before it is carried out.

If no response arrives within the planned period, the provider follows up with the contact and the parties clarify the remaining schedule.

Review the example against the real project

Replace fictional choices with the actual agreed deliverables, person, channel and deadlines. Check the definition of a round and how additional requests are handled too. The wording should remain consistent with service commitments, other terms and applicable rules, rather than being treated as a ready-made answer for every engagement.