Design sign-off — what you are actually approving

Design sign-off is the formal point at which a client approves a specific version of the visual design, and build work then proceeds against that exact version. It is treated as a discrete, recorded step rather than an informal nod in a meeting, because of what happens immediately afterwards. Development time gets committed against the approved design. Changing it later means reworking build work that has already started, not just adjusting a drawing.

What the design sign-off approval actually covers

Sign-off is not approval of the general idea of the site. By this point the general idea was settled at design concepts. What is being approved here is a specific, near-final version — exact colours, exact typography, the layout of every page type the project includes, and any remaining detail that was left open during the concept stage. It is worth treating this distinction seriously: “I like the direction” was the concept decision; “this exact version is what gets built” is the sign-off decision, and they commonly happen weeks apart after a round or two of refinement.

What sign-off covers	What it does not cover
The exact visual design of every agreed page type	Content that has not yet been loaded into the design
Colours, typography and layout as shown	Functionality that has not yet been built and tested
The specific version approved, dated and recorded	Future changes requested after build has started

Why a sign-off document beats a verbal agreement

A verbal “yes, that looks good” in a meeting is easy to remember differently by two different people a few weeks later. That is particularly true once build work has begun and the abstract design has become a concrete, functioning site — one that inevitably looks and feels slightly different from a static image. A written or emailed sign-off, naming the specific design file or version, removes that ambiguity. It is not a formality for its own sake — it is the reference point both sides return to if a disagreement later arises about whether something built matches what was agreed.

A candid point worth naming: some suppliers deliberately keep sign-off informal, because a loosely defined approval gives them more room to argue that a later change request was “always part of the plan” rather than new work. A client is entitled to ask, plainly, for design approval to happen in writing against a specific, dated version. This is a reasonable request, not an adversarial one. A supplier who resists it without a clear reason is worth asking about directly.

The sign-off process for change requests afterwards

Once build has started against a signed-off design, further design change requests are usually treated differently from the revision rounds that were included before this point. This is not suppliers being difficult — it reflects real cost. A colour change requested before sign-off might mean editing one design file. The same change requested after build has started might mean editing styles across every already-built page, re-testing each one, and potentially delaying everything scheduled after it. Suppliers vary in how they price this: some quote it as billable additional work, some absorb small changes and price only substantial ones, and some have a defined number of post-sign-off “minor adjustment” allowances built into the contract. Whichever approach applies, it is worth knowing in advance rather than discovering it when a change is requested.

What a client’s business and staff should check before the sign-off decision

Before a business approves a design, it is worth deliberately checking it against real content, rather than the polished placeholder text most design mockups use. A heading that reads well as a short placeholder phrase can look wrong once the business’s actual, longer service name replaces it. It is also worth checking the design across the page types that will be reused many times, such as a service page template, rather than only the homepage. A problem in a reused template repeats itself on every page built from it.

Whoever inside the business will use the finished site day to day is worth including in this business review, not only the person who will pay the invoice. The two people often notice different things. A design that looks right to a business owner reviewing it once can look wrong to a staff member who will navigate it daily. Making this part of the standard sign-off process — not an optional extra step — is a small process change most businesses can make immediately, and it costs nothing beyond arranging the review before the decision is made rather than after.

Sign-off documents for each page template, confirmed separately

On a site with several distinct page types, sign-off is worth confirming for each template separately rather than assuming approval of a homepage design implies approval of every other page type built from a related template. A homepage concept can look finished and polished while a service page template, a contact page, or a product listing template built in the same visual style has not actually been shown or approved in its own right. A supplier presenting only a homepage at sign-off, on a project scoped to include several distinct templates, has not yet shown the client everything that is about to be built. Raise this directly before approval is given, rather than discovering the gap once build work is already underway on pages nobody actually saw first.

Why sign-off protects the supplier as much as the client

It is easy to read sign-off as existing purely to protect the client from a supplier who might otherwise claim a change was always agreed. It equally protects a supplier from the opposite problem: a client who, after seeing the finished, populated site, decides they preferred an earlier draft and asks for it to be reverted at no cost. A dated, specific sign-off record settles that question the same way in either direction. That is precisely why it is a fair and reasonable step for both sides to insist on, not a one-sided protection for whichever party proposes it.

Where design sign-off sits in the build process

Design sign-off is the last stage before development work begins in earnest. See build for what happens immediately after this approval, and general information on what a supplier’s engagement typically documents around approval points like this one on website design company.