DealokrKey idea
Revision clauses
Use this guide as an operational starting point, then adapt it to the client, the scope and the rules that apply to your work.
Decide the rule before the project moves.
Revision clauses is easier to manage when both sides can see the expected result, the person who decides and the next action. Start with the facts that affect the project rather than a vague promise.
Put the decision in a shared record.
Write down the scope, date, amount or approval step that applies to this project. A clear record helps a client act and helps you avoid rebuilding the context from scattered messages.
Do not mistake a workflow for legal, tax or financial advice.
This guide offers operational guidance for freelancers. Check the official source relevant to your situation and seek qualified advice whenever the decision has legal, accounting or tax consequences.
Operational example
Revisions: an example that removes ambiguity
A readable rule can be: two consolidated rounds of feedback on the mock-up, within five business days of sending it. Requests outside scope or after approval require a new quote. Adapt it to your project and agree it before creating final files.
- Define what counts as one round of feedback.
- State the expected response channel and timeframe.
- Explain how an extra change will be priced and scheduled.
