Every agency has been there. Project delivered, client says 'looks good', two weeks pass, then a 23-point list lands in your inbox with things they 'hadn't noticed before'. No written sign-off. No approved proof. Just an 'ok' on a call. The result: three weeks of unpaid revisions, a burned-out project manager, and a disputed final invoice.
A production director at a 14-person web agency once calculated that 31% of her team's non-billable time was absorbed by unstructured post-delivery revisions. That's close to a full FTE evaporating every year on this single issue alone.
Why Client Sign-Off Is the Most Underestimated Project Phase
Most agencies invest heavily in their brief, their roadmap, their tech stack. But the sign-off phase? Treated like a formality. You send a link, wait, and hope. That's a strategic mistake. A deliverable sign-off is not just a quality checkpoint. It's a legal act. A contractual milestone. Without it, you can't legitimately trigger an invoice, close a sprint, or push back against a client demanding free changes months later.
We lost an 18,000-euro balance payment because we had no written proof the client had approved the final website version. He claimed it wasn't what he asked for. We had nothing. Since then, every deliverable goes through a signed acceptance form, full stop. -- Sebastien R., co-director, e-commerce agency, Bordeaux
Building a 5-Step Deliverable Sign-Off Process
In Agile, we talk about a Definition of Done. The idea applies to any agency, tech or not. Before starting a deliverable, the client and team agree in writing on what 'done and ready to approve' looks like. Takes 20 minutes. Saves 20 hours of rework.
- Visual deliverables (mockups, branding, videos): maximum two revision rounds, with a review checklist given to the client upfront. If the checklist isn't filled out, the feedback isn't actionable.
- Technical deliverables (dev, integrations, APIs): formal UAT with a test plan, validated environment by environment, each test timestamped or signed off.
- Strategic deliverables (audits, recommendations): mandatory live presentation plus a meeting summary with explicit validation within 5 business days.
- Recurring deliverables (reports, content, newsletters): tacit approval with a short window (48h); if no objection is raised, the deliverable is considered accepted.
That last point, tacit approval, solves 80% of friction on recurring projects. It must be explicitly stated in the contract or terms of service. Without that, it's worth nothing legally.
Link Validation Directly to Invoicing
Many agencies shoot themselves in the foot here: they invoice before sign-off, or they get sign-off and forget to invoice. Deliverable validation should automatically trigger the milestone invoice. Tools like Clynt can automate this link between validated milestone and invoice generation, eliminating cash flow gaps caused by manual follow-ups.
A project manager shared a concrete case from a B2B SaaS client: their average validation cycle was 19 days per deliverable. After introducing a 5-day contractual deadline with tacit approval, they dropped to 6 days per cycle within one quarter. Simple clause, massive operational impact.
What a Good Client Portal Actually Changes
A client portal is not a nice-to-have. When properly configured, it centralises deliverables, approval requests, and comments, with a timestamped record of every action. The client sees what needs approving, clicks, confirms, and it's logged. No more ambiguity around 'I said ok verbally' versus 'I never validated that'. Clynt integrates this directly with project tracking and invoicing, which is precisely what's missing when agencies piece together Drive, HubSpot, and a spreadsheet.
FAQ
What is the difference between an email approval and a formal acceptance form?
An email approval has limited legal value and is hard to enforce in a dispute. A structured acceptance form, signed electronically or validated via a timestamped portal, constitutes solid and enforceable evidence. In a contentious situation, that distinction can mean the difference between winning and losing.
How many revision rounds should be included in an agency contract?
Two rounds is the market standard for most creative or strategic deliverables. Beyond that, each additional round should be billed at an hourly or fixed rate. The contract must spell this out explicitly, with a clear definition of what constitutes one 'round' of revisions.
How do you handle a client who refuses to sign off without giving specific reasons?
This is the trickiest scenario. Best practice: send a formal written notice referencing the contractual deadline and requesting specific, documented objections. If the client cannot list concrete issues against the acceptance criteria defined at project start, the refusal is not contractually valid.
Can tacit approval clauses hold up legally?
Yes, provided the clause is explicitly included in the signed contract or terms of service, with a clearly stated deadline. The client's silence past that deadline constitutes acceptance. A lawyer specialising in digital contracts can help you draft this clause to make it airtight.