01
Separate the record from each interpretation
A fictional project includes two revision rounds. After two rounds, the client asks for another set of changes and says the earlier rounds did not produce the intended result. The freelancer says the included revisions are exhausted.
Counting messages is not enough. The parties need to examine what a round meant, whether feedback was consolidated, whether earlier work met the approved direction, and whether current requests are corrections or a new direction.
Documented facts
- The proposal states that two revision rounds are included.
- Two sets of feedback and two subsequent submissions appear in the project record.
- The current request contains both possible corrections and new preferences.
What the freelancer believes
- The included rounds were used and additional changes require a written change.
- Some current requests reverse choices that the client approved earlier.
What the client believes
- The result still does not match the approved objective, so further work should be included.
- Some earlier comments may not have been implemented accurately.
What remains unknown
- How the agreement defines a round and whether feedback met the consolidation process.
- Which requested items correct a missed instruction or criterion versus introduce a new preference.
- Whether prior approvals, contradictory comments, or freelancer errors affected the count.
02
Consider both perspectives without assuming fault
Different concerns can be reasonable at the same time. Neither list proves a disputed fact; it shows what a workable response must address.
Freelancer perspective
Practical concerns from the freelancer’s side
- Respond item by item and correct verified misses without using the revision limit to avoid agreed responsibilities.
- For new direction, explain the boundary and propose a bounded change rather than refusing generally.
Client perspective
Practical concerns from the client’s side
- Tie each concern to an approved instruction, criterion, or observed defect and consolidate the response.
- Recognize when a newly preferred direction differs from the one previously approved, even if the business reason is valid.
03
Check these records before deciding what happened
Start with the material both parties can inspect. Preserve original messages and files; work from copies when adding notes.
- The definitions of revision, round, correction, acceptance, and changed scope.
- The dated feedback and submissions for each round, including the authorized approver.
- Whether feedback was consolidated, timely, and within the agreed stage.
- Each current item’s relationship to an accepted criterion, prior instruction, or new direction.
- The process for corrections, additional rounds, changes, schedule effects, and payment.
04
Choose the smallest proportionate next step
These steps are possibilities, not a required legal sequence. Adapt them to the actual risk, agreement, platform, and communication record.
Create a revision ledger
List each round, consolidated feedback, response, approval, and unresolved item.
Classify current requests
Mark each as a missed instruction, defect, clarification, included revision, or new direction—with evidence.
Resolve supported corrections
Agree on the correction and retest without consuming energy arguing over labels.
Record added work
For additional rounds or new direction, decide whether to add, swap, defer, or decline through the change process.
05
Adapt a neutral, answerable message
Replace every bracketed detail and verify the record before sending. Do not turn the example into a threat or claim a consequence you have not checked.
06
Know when the situation needs qualified help
A revision ledger helps the parties reason from the record, but it does not determine legal performance, payment, or breach. Seek qualified help if a material dispute remains after the project process is exhausted.
Get qualified help promptly when there is
- a threat to anyone’s physical safety or credible harassment or discrimination concerns;
- suspected crime, fraud, unauthorized account access, or a material exposure of personal or confidential data;
- a large potential loss, an imminent filing or response deadline, or a demand that depends on jurisdiction-specific rights; and
- a platform restriction, court order, insurance requirement, or other process with a deadline you cannot confidently interpret.
07
Use Lucy only after removing sensitive details
Lucy can group correction claims, prior decisions, and possible new direction. She cannot decide which factual account is true without evidence. Following this link opens the ordinary blank tool. It does not load this example, transmit content, or make an AI request until you choose to submit the tool form.
Compare redacted revision requests with the record →
Read how Lucy handles a request before submitting real project material.
Keep going
Continue from the actual record
Proposal record
Freelance Proposal Template
Define revision rounds, assumptions, deliverables, responsibilities, and the path to agreement.
Agreement record
Statement of Work outline
Connect revisions to acceptance, approver authority, changes, schedule, and payment.
Worked example
See a correction separated from future scope
Harbor Street corrects a reproducible mobile defect and defers online payments.
Related situation
Extra work beyond scope
Use the scope comparison when the request adds a deliverable rather than another review round.