01
Separate the record from each interpretation
A fictional freelancer submits the recorded deliverables and says the project is complete. The client responds that the result is unacceptable but does not identify a failed requirement or reproducible defect.
Neither the freelancer’s completion statement nor the client’s rejection resolves the question. The parties need a criterion-by-criterion record of what was promised, delivered, tested, and still disputed.
Documented facts
- The freelancer submitted files identified as the final delivery through the agreed channel.
- The client sent a written rejection within the review period.
- The rejection does not yet map each concern to an acceptance criterion or deliverable.
What the freelancer believes
- Every named deliverable is present and the agreed functional checks pass.
- The client is introducing a new creative direction after completion.
What the client believes
- The result does not meet the quality or business outcome discussed during the project.
- Final payment or acceptance should wait until the concerns are addressed.
What remains unknown
- Which concerns are reproducible failures, subjective preferences, unclear criteria, or new requests.
- Whether intermediate approvals or later instructions changed the usable acceptance record.
- What correction, clarification, independent review, or other process the agreement provides.
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
- Ask for specific examples and respond to each criterion rather than defending the work in general terms.
- Correct verified failures within the agreed responsibility and record separately quoted new direction as a change.
Client perspective
Practical concerns from the client’s side
- Describe observed behavior, location, expected criterion, and evidence instead of relying on ‘unacceptable’ alone.
- Keep preferences and newly discovered business needs visible without relabeling them as defects.
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 final deliverable list, acceptance criteria, testing environment, review window, and approver.
- Delivery evidence, intermediate approvals, revision records, and known exceptions.
- Each reported concern’s location, reproduction steps, expected result, and actual result.
- Whether the concern is a missing deliverable, defect, preference, new direction, or ambiguous requirement.
- The correction, dispute, milestone, and platform processes that may apply.
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.
Build a comparison list
Map each disputed item to the named deliverable and criterion, with evidence and current status.
Resolve clear defects
Agree on the reproduction, correction, retest, and confirmation record for genuine failures.
Classify other requests
Clarify preferences, ambiguous wording, and changed direction before deciding whether work is included.
Use the agreed review process
If a material disagreement remains, preserve the record and follow the contract or platform path without threats.
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
Do not use this guide to decide whether acceptance, payment, ownership transfer, refund, or termination has legally occurred. Seek qualified help when the dispute is material or the governing terms and evidence do not produce a safe commercial resolution.
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 separate documented criteria, observed issues, claims, and unknowns. She cannot determine legal entitlement or technical truth 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.
Organize a redacted acceptance dispute →
Read how Lucy handles a request before submitting real project material.
Keep going
Continue from the actual record
Acceptance record
Final Delivery Checklist
Connect each delivered item, approval, file, access step, and exception to evidence.
Project terms
Statement of Work outline
Review acceptance, revisions, responsibilities, and dispute handling together.
Worked example
See criteria-based review and revision
Watch Harbor Street separate a reproducible defect from a future feature idea.
Related situation
Disagreement over revisions
Classify requested changes when the dispute concerns included rounds or corrections.