How to Document a Freelancer Delivery Dispute

Freelancer disputes — whether you are the client or the freelancer — almost always come down to the same question: what was agreed, and what was actually delivered? Without a clear record of the original scope, the communication history, and what each party did or did not do, disputes are nearly impossible to resolve fairly. This guide helps both sides build that record.

The contract or brief: your starting point

Every freelancer dispute depends on establishing what was originally agreed.

• Written contract or statement of work specifying deliverables, formats, deadlines, revision rounds, and payment terms. If a formal contract was never signed, a detailed email brief confirming the scope functions as a substitute — save it.
• Platform job posting or proposal if hired through Upwork, Fiverr, Toptal, or a similar platform — screenshot the original posting and the accepted proposal including any scope description, delivery date, and agreed price.
• Milestone breakdown if the project was split into phases — what was due at each milestone and what payment was tied to each.
• Any revision or change orders agreed after the original brief. Scope changes agreed in conversation but not documented are a common source of disputes — if you agreed to changes verbally, follow up in writing immediately.

Screenshot deliverables as they were received

What was actually delivered, and in what state, is central to most disputes. Files get revised, links expire, and online work disappears.

• Download and save all delivered files the moment they are received — do not rely on a shared Google Drive or Dropbox link remaining accessible.
• Screenshot any web-based deliverables (designs in Figma, Google Docs drafts, website previews) with the timestamp visible.
• Note the date each deliverable was received and compare it to the agreed deadline — late delivery is relevant evidence if it caused harm.
• If a deliverable was incomplete or did not match the brief, document the specific gap: which element of the brief was not met, and how the delivered work differs from what was specified.

Preserve the full revision history

Revision rounds are frequently where freelancer disputes originate — disagreements about how many rounds were included, what feedback was given, and whether revisions were addressed.

• Export or screenshot all feedback you gave for each revision round, with dates.
• Save the revised version received after each round of feedback.
• If the number of revision rounds included in the contract was exceeded, note when that threshold was crossed and what was communicated about it.

Communication record

• Export the full message thread — platform messages, email chain, or Slack history — from project start to the point of dispute.
• Log any calls where commitments were made; follow up by message: "Confirming our call — you will deliver the revised logo files by Thursday."
• Save any written acknowledgement of delay or quality issue from the freelancer.
• If on a platform like Upwork or Fiverr, note whether a dispute was opened through the platform and what the platform's response was.

Payment records

• Payment confirmations for each milestone or deposit paid, with amounts and dates.
• Any invoice issued by the freelancer, compared against what was actually paid.
• If payment is being withheld pending satisfactory delivery, document in writing exactly what conditions must be met for payment to be released.