Proof of Work on Invoices: Why Documenting What You Delivered Protects You

Proof of work on an invoice is a written record of what was delivered to the client — separate from the payment demand itself. While the invoice says "you owe me £2,400 for website design", the proof of work says "on [DATE], I delivered five pages of website designs via Figma link, confirmed by your reply on [DATE] saying ‘these look great, please proceed to development’."

The distinction matters: an invoice is a legal claim for payment. Proof of work is the evidence that the obligation to pay has been earned. UK invoices must also meet HMRC invoice requirements to be legally valid.

In practice, proof of work usually lives as a note attached to the invoice — a brief paragraph created at the time of billing that describes what was completed, when, and how it was delivered. It does not need to be long. It needs to be specific, accurate, and dated.

Payment disputes are more common than people expect. But even more common is the quiet version: a client who drags their feet, claims they are "reviewing the work", or suddenly raises concerns about quality that were never mentioned before. In almost every case, the resolution depends on documentation.

Consider the most common situations where a delivery record changes the outcome:

• Client claims the work was never delivered. Without a delivery record, your word against theirs. With a delivery record referencing the email you sent, the files attached, and the client's acknowledgement reply — your position is unambiguous.
• Client claims the work was substandard. A specific delivery record describing what was delivered and how it matched the agreed scope is your first line of defence. Combined with any feedback or sign-off the client gave during the project, it is usually conclusive.
• Small claims court or debt collection. Both processes rely on written evidence. A chase log showing your follow-up attempts and a delivery record showing the work was completed are the two most important documents in any formal claim for an unpaid invoice.
• Protecting your reputation. Some clients will raise concerns as a negotiating tactic — hoping you'll accept a partial payment to avoid confrontation. Specific delivery evidence makes it clear that you have the stronger position and that raising spurious objections will not work.

Good delivery notes are specific, factual, and brief. Here is a practical framework:

The five elements of a strong delivery record

1. What was delivered. Be specific. Not "website work" but "five-page website redesign: homepage, about, services, contact, and blog index". Not "branding" but "logo, colour palette, typography guide, and brand guidelines PDF".
2. When it was delivered. The exact date, not "early February". Timestamps matter in disputes — they establish the chronology of the project.
3. How it was delivered. "Sent via email to billing@client.com", "shared via Google Drive folder link", "uploaded to the client's CMS on [DATE]", "presented and handed over in person at [LOCATION]".
4. Client acknowledgement (if any). Quote the specific line from the client's reply that confirms receipt. "Client replied on [DATE]: ‘Thanks, received everything’" or "Client approved designs via email on [DATE]."
5. Any outstanding items. If something was agreed to be delivered in a second phase, or there is a known outstanding item, note it explicitly so there is no ambiguity about what this invoice covers.

Example delivery note

This takes approximately two minutes to write and covers every question that might arise in a dispute: what was done, when, how it was delivered, and whether the client acknowledged it.

Write your delivery notes at the time of invoicing — the same day you send the invoice. This is the single most important principle.

Notes written at the time of delivery are:

• Timestamped before any dispute arose
• Based on fresh memory, with accurate dates and details
• Much harder to challenge as retrospective or fabricated
• Consistent with other contemporaneous records (emails, file logs)

Notes written after a dispute has started are:

• Potentially challenged as self-serving and retrospective
• Less accurate (memory fades, dates blur)
• Not automatically aligned with your other records

The two-minute habit of writing delivery notes when you invoice removes almost all of these risks. It is among the highest-return habits in freelance and small business invoicing.

When a client disputes payment or claims work was not delivered, your response should include your delivery record alongside your invoice. The sequence:

1. Respond in writing. Always in writing, so there is a record. State calmly that you are attaching your delivery record, which documents what was delivered and when.
2. Reference specific evidence. "As you can see from the delivery record dated [DATE], the work was delivered via [method] and you acknowledged receipt on [DATE]." Specific dates and references are far more credible than general assertions.
3. Ask the client to be specific. "Please let me know specifically what you believe was not delivered, with reference to the agreed scope, and I will respond to each point directly." This forces a concrete response rather than vague objections.
4. Set a payment deadline. Give the client a specific deadline to respond and pay. If they do not respond or do not pay, your next step is a formal demand letter.

Your complete paper trail in any dispute is: the original invoice + delivery record + chase log showing every follow-up attempt. InvoiceGrid's Evidence Pack generates this complete document automatically — you can see it in InvoiceGrid Pro.

The barrier to writing delivery notes is not knowledge — it is habit. Most people know they should document what they delivered. Few do it consistently. Here are three approaches that work:

• Attach it to your invoicing workflow. The moment you create an invoice, add your delivery notes to it before you send it. Make it a non-negotiable part of the invoicing step, not a separate task.
• Use a template. Start with the five-element framework above (what, when, how, acknowledgement, outstanding items) and fill it in. A template removes the blank-page problem and keeps your records consistent across projects.
• Keep it brief. Two to four sentences is enough for most projects. The goal is specificity, not length. A single precise sentence is better than a paragraph of vague description.

InvoiceGrid has a "Proof of Work" field built into every invoice for exactly this purpose. Add your delivery notes when you add the invoice — they are stored alongside the invoice, included in the Evidence Pack automatically, and available instantly if a dispute ever arises.