How to document unpaid work

Work was requested. You did it. Payment hasn't come. This is the basic shape of most unpaid work disputes, and it's one of the most common problems freelancers, contractors, and small business owners face. The strength of your position depends almost entirely on what you can prove was agreed to, performed, and owed.

Communication records are usually the best evidence available. They capture the request, the scope, the price, the delivery, and the excuses.

Establishing the agreement

The first thing to document - ideally before the work starts, but retroactively if necessary - is that the work was requested and agreed to. You need records showing that the other party asked for the work, that you agreed to do it, and that both sides understood the terms.

Look for:

• The initial request or project brief, in whatever form it arrived (email, text, DM, message on a freelancing platform)
• Your response with a quote, proposal, or rate confirmation
• Their acceptance of those terms
• Any subsequent changes to the scope or price, with confirmation from both sides

If the agreement was verbal, look for any written communication that references it. A text that says "Thanks, looking forward to getting started on the website" after a phone call where pricing was discussed isn't a contract, but it establishes that an agreement was in place. A message saying "Can you also add the contact page we discussed?" confirms scope.

The weakest position is one where nothing was written down at any point. If that's where you are, start documenting now. Send a message summarizing the work you've completed, the agreed price, and the payment status: "Just following up - I delivered the final designs on March 4 per our agreement of $2,400. I haven't received payment yet. Can you let me know when to expect it?"

Proving the work was performed

Payment disputes sometimes involve the other party claiming the work wasn't completed, wasn't satisfactory, or wasn't what they asked for. Your records should establish that the work was delivered and, ideally, that it was accepted.

Save:

• Delivery confirmations: emails or messages where you sent the finished work, with dates
• Acknowledgment of receipt: any response indicating they received the deliverables ("Got it, thanks" counts)
• Approval or sign-off: messages where they confirmed the work was acceptable, requested final files, or began using the deliverables
• Revision history: if they requested changes and you made them, the back-and-forth establishes that the work was performed to their specifications

For service work (consulting, repair, installation), document completion with photos, time logs, or a written summary sent to the client upon finishing.

If the work is live and visible - a website, a social media campaign, a physical installation - screenshot or photograph it with dates. This proves the deliverable existed and was accessible.

Documenting payment attempts

Once work is delivered and payment is late, every communication about payment matters.

Invoice records. Every invoice you sent, with the date, the amount, and the delivery method. If you sent invoices by email, those emails are your proof. If you used an invoicing platform, export the records showing when invoices were sent and viewed.

Payment promises. Any message where the other party acknowledged the debt or promised payment. "I'll send it Friday" is an acknowledgment of the obligation. "Things are tight this month but I'll catch up next week" is both an acknowledgment and a promise. These messages undermine any later claim that the work wasn't agreed to or that the price was different.

Follow-ups and responses. Keep every follow-up message you sent and every response received. A pattern of follow-ups met with vague promises, deflection, or silence is relevant evidence. It shows you made reasonable efforts to collect and the other party failed to pay.

Non-response. If your messages go unanswered, that's also documentation. Unanswered invoices and follow-ups establish that you pursued payment and were ignored.

Building a record for collections or small claims

If informal collection efforts fail, you may need to send a formal demand letter, engage a collections agency, or file in small claims court. All of these processes require documentation.

Organize your records into a simple package:

1. The agreement: Messages establishing the scope and price
2. The work: Evidence of delivery and acceptance
3. The invoices: Copies of all invoices sent, with dates
4. Payment history: Any partial payments received, with dates and amounts
5. Collection attempts: Messages requesting payment, with responses (or lack of responses)
6. The amount owed: A clear calculation of what's due, including any late fees if they were part of the original agreement

Arrange everything chronologically. The narrative should be obvious from the sequence: work was agreed to, work was performed, invoices were sent, payment was not received, attempts to resolve were made.

Preventing the problem

The same documentation habits that help you collect unpaid work also prevent nonpayment in the first place.

Written agreements - even informal ones via email or text - establish expectations before work begins. Milestone-based payment structures (deposit before starting, payment at delivery, final payment upon approval) reduce the risk of completing all work before receiving any payment. And sending invoices promptly with clear due dates and follow-up policies makes it harder for payment to slip into a gray area.

The time to start documenting is before the work begins. But if you're already in a dispute, the time to organize what you have is now.

Receipts helps organize communication records into structured, chronological timelines - turning scattered messages into clear documentation for disputes and collections.