Client Sign-Off: Turning Acceptance Into Something You Can Rely On

When a client accepts a deliverable, something legal happens: the firm has discharged an obligation, a payment milestone may become due, and the window for objecting to that piece of work begins to close. When that act is recorded as an email saying it looks good, the firm has a fragment of evidence whose meaning is arguable. When it is recorded as a decision, by a named person, against a specific version, on a date, it is not.

The gap between those two costs money at exactly one moment, which is when a client says late in an engagement that a deliverable was never satisfactory. A firm with verbal acceptance argues from memory. A firm with recorded acceptance shows the record and the conversation ends.

What a sign-off has to capture

• Who accepted, as a person rather than an organisation, because a company cannot form an intention and an individual can.
• What they accepted, meaning the specific version, frozen, so that later edits cannot retroactively change what was signed.
• When, to the moment, because contractual windows run from it.
• What decision they took, because acceptance is not binary in practice.
• What they said, where they said anything, because a conditional acceptance carries its conditions.

Three decisions, not two

A sign-off control offering only approve and reject forces clients into a false choice, and the result is that they either approve something they have reservations about or reject something that is substantially fine. Both outcomes damage the record.

The version that matches reality has three: approve, approve with comments, and request changes. Approving with comments accepts the deliverable and puts the remark on the record alongside the acceptance, which is what a client means when they say it is fine but the third section needs a caveat. Requesting changes does not accept it and returns the work to the firm. Those are genuinely different events with different commercial consequences, and collapsing them loses information the firm will want later.

Freezing the version is the part people skip

A sign-off against a living document is close to worthless. If the deliverable can be edited after acceptance, then what was accepted is unknowable, and a client who disputes the content has a straightforward argument that the version they saw was different.

The mechanic that solves this is capturing a version at the moment sign-off is requested, and binding the acceptance to that capture. The working document may continue to evolve; the accepted artefact does not. This is also what makes it safe to ask for sign-off early, because the firm is not committing to freeze the work, only to freeze what is being signed.

The gate before you ask

Asking a client to sign off something that is not ready wastes their attention and trains them to sign without reading, which is worse than not asking. A useful discipline is a short set of conditions that must hold before the request can be made: the acceptance criteria are met or explicitly waived, the internal quality review is complete, and nothing is outstanding that would change the content.

That gate should be visible as a list rather than enforced silently, because the person about to request sign-off needs to know which item is blocking. A refusal without a reason is indistinguishable from a broken button.

Making it easy enough that clients actually do it

• Put the decision on the deliverable itself, not in a separate approvals area the client has to find.
• Give the deliverable its own address so a request for sign-off links directly to it rather than to a list.
• Show what is being accepted alongside the control, including the description, so the decision is taken with the content in view.
• Ask for a typed name. It is a small friction that converts a click into an act, and it is what makes the record legible later.
• Do not require an account for a one-off signature if the relationship does not justify it, but do record identity in some form.