Documented client sign-off means a clear, recorded moment where the client accepted a specific piece of work. It names the version, the date and who approved it, and it lives somewhere both of you can see. Record it at every milestone and most "I never approved that" disputes disappear.
Most disputes are approval disputes
Dig into a project that went wrong and you rarely find bad work. You find two people who thought they agreed and did not.
Geneca surveyed about 600 business and technology executives and found that only 23% say they are always in agreement about when a project is done. That is a software study, so treat it as a pointer, not a measurement of your trade. But it matches what small businesses see: "looks good" on a call, a thumbs-up in a chat thread or silence read as a yes is not a decision anyone can point to later. Memory is generous and self-serving on both sides.
Without a record, the disagreement cannot be won, because there is nothing to be right about.
For a service business, rework hurts more than it does for an employee, because nobody pays for it. Every revision round that exists only because approval was vague is time billed to nobody. You quoted the job once and you are doing it one and a half times. The client is rarely acting in bad faith. They genuinely do not remember agreeing, because there was nothing to agree to.
This is the same root as scope creep, with the same fix: pin the decision down when it happens, not when it is disputed. Our guide to covers the scripts for the change side.
Written by
The Delivvo team
Delivvo runs the client cycle for service businesses: inquiry, quote, contract, deposit and delivery. Payments go straight to your own account.
If you are self-employed and use part of your home only for work, you can deduct it on your US return. This post covers who qualifies, the simplified and regular methods with a worked example, the mistakes that cause trouble, and the records to keep.
AI editing is cheaper in dollars when you publish often, and a human editor is cheaper when your time is worth more than the edit. This guide compares real tool prices with editor pay and walks through a break-even calculation you can run in five minutes.
A UAE client contract holds up when it is written, specific, signed and backed by a valid licence and tax set-up. This post covers e-signatures under UAE law, VAT and e-invoicing basics, what to put in the contract and what your options are when a client stops paying.
8 min read
Your inquiry link is free.
Free plan. No card needed.
Blog
Guides for service businesses, from the first inquiry to the final payment. Written by the team behind Delivvo.
Two people leaning in across a table in a tense, serious conversation, hashing out a disagreement
Without a record, the person holding the money wins
Sooner or later the ambiguity reaches the invoice. Late and missing payment is already the norm. In Remote's contractor report, 85% of freelancers said their invoices are paid late at least some of the time. Some of that is cash flow. A real part is dispute: the client is not paying because they disagree about what they received.
And most have nothing to stand on. Freelancers Union found that only 28% of freelancers use a contract for any given gig. That figure is from 2015, so it may have moved, but the direction is clear: if fewer than a third have a signed agreement, far fewer have a documented sign-off on the deliverable itself. When it is your word against theirs, whoever holds the money wins by default.
What a proper sign-off contains
A sign-off is not a thumbs-up. It has five parts.
What was approved. Name the deliverable and the version: "Homepage design, version 3."
Who approved it. The person with the authority to say yes, by name.
When. A date, and ideally a time.
What happens next. "Development begins on 10 March. Changes after this point are quoted separately."
Where it is recorded. A place both sides can find it later, not a private message.
Keep the wording short and plain. "I approve version 3 of the homepage design for development" is enough.
When to ask for sign-off
Ask at the end of every stage where later work depends on earlier work. For a typical project that means five moments.
The brief. The client confirms they agree with the scope and goals you wrote down.
The concept or outline. Before you invest in the full build, they approve the direction.
The first draft. They confirm what is in and what needs changing. This is where the revision count starts.
The final version. They approve for delivery, with an explicit note that further changes are new work.
The handover. They confirm they received everything in the list, and the project is closed.
You do not need all five on a small job. But the final version and the handover are the two you should never skip, because they are the ones tied to the final invoice.
Make it easy to say yes
A sign-off that takes effort will not happen. Send one clear request that includes the file, the question and a deadline: "Please approve version 3 by Friday so we can start development on Monday. If I do not hear from you, I will check in on Friday afternoon."
Offer a single action: a button, a reply of "approved", or a signature. Avoid asking for comments and approval in the same message, because comments become a negotiation and the approval gets lost. If the client has changes, take the changes, produce a new version, and ask again.
Sign-off for different kinds of work
The idea is the same everywhere, but the shape changes with the work.
For design, approve against a named version and attach the file. For writing, approve the outline, then the draft, then the final copy, so the client cannot rewrite the brief at the last step. For software or web builds, approve the specification before development and a staging link before launch. For video, approve the script, the rough cut and the final cut, and record the timestamp of any change request, because "make it shorter" means different things to different people.
For events or services without a file, a short written summary works: "We agreed the shoot will run from 10 to 2, with two outfits and one location." Ask the client to reply "confirmed".
Whatever the work, keep the sign-off proportional. A 200 dollar project needs two approvals, not seven. A 20,000 dollar project can justify a short formal sign-off at each phase.
When the client goes silent
Silence is not approval, and treating it as approval is how disputes start. Set expectations in the contract: "If I do not receive feedback within five business days, I will assume the milestone is accepted and move to the next stage." That clause needs to be in writing before the project starts, and the client has to have agreed to it. A lawyer can check that it holds in your jurisdiction.
When silence happens, remind once, then once again, then send a final note citing the clause. Keep each message polite and short. Our guide to a client who goes silent mid-project covers the longer version.
How Delivvo records sign-off
Delivvo puts approvals in the client portal, next to the file they refer to, so the record exists without anybody remembering to write it.
Quote and contract first. The client picks a package, signs and pays the deposit on one page. The contract has a signing record with a SHA-256 hash, IP address, device and an archived PDF.
Upload each stage to the portal as a new version. The client sees the current version and the history, so there is no doubt about which one they are looking at.
The client approves in the client approvals flow inside the portal. The approval sits on the project with the file, not in a private inbox.
Messages stay in the same place, so a comment like "change the headline" is attached to the version it was about.
The final invoice goes out with a pay button, and the client pays through your own gateway. Reminders run at 7, 14 and 30 days if it is late.
Clients open the portal with a one-time code, with no password to forget, which removes the usual excuse for not approving.
A realistic example: you send version 3 of a logo set. The client opens the portal, approves it and the project moves to final files. Two weeks later they ask for a different colour. You open the project, show that version 3 was approved on a stated date, and offer the change as a small paid revision. The conversation stays friendly because you are pointing at a record, not at your own memory.
One detail that matters in a dispute: documents carry a verification code. Anyone can enter it on the public verify page and see the issuer, number, dates, amount and status. That does not replace a lawyer if things go to court, but it answers the "is this document real" question in seconds.
FAQ
What counts as client approval?
A clear, specific acceptance of a named version, from someone with authority, with a date, in a place both sides can see. A comment like "looks good" on a call does not count unless you write it down and confirm it.
Is an email enough as a sign-off?
It is better than nothing. A reply that says "approved" to a message naming the version works. A portal or signed approval is easier to find later.
What if the client approves and then asks for changes?
Treat the changes as new work. Refer to the sign-off and quote the change separately.
What if the client never replies?
Use the silence clause from your contract, send reminders and then act on the clause. Have a lawyer check the wording.
Delivvo runs the whole client cycle for service businesses, from the first inquiry to the quote, contract, deposit, invoice and delivery, so every approval is recorded next to the work it covers. Clients pay you directly through your own gateway, and Delivvo takes 0%. Start free
