The handover document arrives by email. Sixty-eight pages, the brand book. Logo files in a folder, fonts in another folder, a colour palette as a screenshot and as a separate .ase file. The brand agency's project lead writes "let me know if you need anything else!" and signs off. They've delivered.

Three weeks later the website designs come back to the founder for review, and the colour palette in the designs doesn't quite match the brand book, the typography is using a substitute font instead of the licensed one, and the photography style on the homepage looks nothing like the moodboard the brand agency produced. The founder asks the web studio what's going on. The web studio says they're working from the brand book and they did what was there.

This is the median experience of a brand-to-web handover in Australia, and it's the reason why so many rebrand-and-rebuild projects launch with the visual identity diluted from what the brand agency intended.

My position: the handover everyone treats as a documents-and-files transfer should actually be a live, structured, multi-session collaboration between two teams, with explicit deliverables on both sides. Without that, the rebrand budget produces a website that's a faded copy of the brand work — and nobody's really to blame, because the process didn't set them up to do better.

What's wrong with the documents-and-files handover

A brand book is a reference document. It assumes the reader will sit with it, read every page, internalise the rules, and apply them with judgement. It's written like a manual.

Web design work doesn't happen that way. A web designer is solving specific problems — what does the homepage hero look like, how does the navigation behave on mobile, what's the visual rhythm of a service page — and they're solving those problems quickly in design tools. They're not opening a 68-page PDF every five minutes to check whether what they're doing matches the brand intent. They scan it once, extract the essential constraints, and design from memory.

The gap between "what the brand book intended" and "what the designer remembers from a five-minute scan" is where the dilution happens. It's not negligence. It's that the format is wrong for the use case.

The fix is to translate the brand book into the artifacts a web designer actually uses, and to do that translation collaboratively with the brand agency, not afterward in the web studio's head.

What the handover should produce

The handover should produce six distinct artifacts, not one big document.

1. A design tokens file

Modern brand systems express colour, typography, spacing, and animation as tokens — named values that can be referenced consistently across every surface where the brand exists. The handover should produce these tokens in a format the web studio's design tool and codebase actually consume. For most modern web studios, that's a JSON file or a Tailwind CSS config or shadcn/ui theme that the developer imports directly.

Specifying "primary blue is #0F4C81" in a brand book PDF is not the same as having color.brand.primary = #0F4C81 in a tokens file that the web designer and developer reference. The first form has to be transcribed; the second form is consumed directly.

This is a 2 to 4 hour task at the end of the brand project. It almost never happens because brand agencies aren't set up to produce code-readable outputs and web studios assume they'll do it themselves. The result is that two people independently translate the same colour from a PDF, sometimes with subtle differences.

2. A typography specimen

Not the typography section of the brand book — which usually says "Headings: GT America 60pt regular, body: Söhne 16pt regular." That's not a specimen. A specimen is a living document showing every typographic style with the actual rendered text:

H1 with three example headlines
H2 with three example sub-headings
H3 down to H6 same treatment
Body paragraph with two example paragraphs at the real line length
Captions, eyebrow text, button text, link text
Mobile equivalents for each
Edge cases: long headlines that wrap, short headlines, headlines with punctuation, body text with bold and italic emphasis

This is the document the web designer references while designing. The brand agency producing it ensures the typography hierarchy survives translation to web. The web studio adapting it for the actual implementation removes the guesswork.

3. A photography and illustration direction document

Brand books often include a "photography direction" page with three or four representative images and adjective lists ("warm, natural, candid"). This is insufficient for a web designer who's about to specify hero imagery, service page imagery, team photography, and product imagery across forty pages.

The handover should include:

15 to 25 reference images showing the photography style across different contexts
An explicit note on what's appropriate where (homepage hero, service pages, team, blog)
A "do not use" gallery showing the kind of imagery that's off-brand — this prevents the designer from defaulting to stock photography that doesn't match
Specifications for image treatment (cropping conventions, colour grading, any overlay or treatment that's part of the brand system)

For illustration, the same: real examples of the illustration style, an icon library if there's one, specifications for when illustrations are used versus photography.

4. A voice and tone reference for web content

The brand voice document in a brand book typically covers voice attributes ("conversational, direct, technically credible") and a few brand examples. Web content is more specific — homepage hero copy, value proposition statements, CTA microcopy, form labels, error messages.

The handover should include a web-specific voice document with:

The brand voice attributes from the brand book
10 to 20 examples of brand voice applied to common web patterns: a hero headline, a sub-headline, a CTA button, a form label, a confirmation message, a 404 page message
A "do not write" list — common patterns to avoid because they undermine the voice

This is the document the web copywriter — whether that's the web studio's internal writer or the founder doing their own copy — uses while drafting site content.

5. A component-level brand application guide

The brand book shows the logo, the colours, the typography in isolation. The web designer needs to know how they apply in combination on common UI components: buttons (primary, secondary, tertiary, destructive), form fields (default, focused, error, disabled), cards (default, hover, selected), navigation items, badges, alerts.

A component-level application guide either is part of the brand agency's deliverable (in which case it's been specified by people who understand the brand intent) or is produced by the web studio at the start of the build (in which case the brand agency should review and sign off on it before development proceeds).

Without this, every component gets a small interpretation decision made by the web designer in isolation. The cumulative effect is a site that's slightly off-brand across the board.

6. A live handover session

The single highest-impact item, and the one almost never costed.

90 minutes, both teams in a room (or on a call), brand agency walks the web studio through the brand book. The brand strategist explains why each decision was made, what the brand is trying to be versus its competitors, where the brand is flexible and where it isn't. The web designer asks specific questions: what does this look like at this size, what's the smallest legible version of the logo, what's the right typography pairing for body text under 14px on mobile, when is the secondary palette appropriate.

This conversation is the difference between the web studio applying the brand by following rules and applying it by understanding intent. It costs roughly $300 to $500 of each agency's time. It saves entire projects.

Who pays for the handover

The honest version: nobody currently pays for proper handover, which is why it doesn't happen.

The brand agency's scope ends with the brand book deliverable. The web studio's scope starts with the kick-off meeting. The handover work falls in the gap and either nobody does it (and the result is the diluted-brand website I described at the start) or one party does it for free at the expense of their own margins.

The fix is to include handover as an explicit line item on one of the two proposals. Either the brand agency includes "handover to web partner" as a $2,000 to $4,000 line item that covers the artifacts above and the live session, or the web studio includes "brand integration" as a similar line item that covers the same work from the other direction. The client either pays the brand agency or the web studio for the same work, but the work gets done.

If the client engages a single studio that does both — and there's a real case for this on projects under $60k total — the handover happens internally and isn't a separate line item, but the work still has to happen. The studio that pretends the handover doesn't exist because both functions are under one roof is the studio whose internal brand and web teams aren't actually talking.

What the founder should expect from a good handover

Three questions to ask both your brand agency and your web studio before they engage, that signal whether they understand handover or not:

To the brand agency: "What format do you deliver design tokens in, and how do they get into the web studio's codebase?" If the answer is "we provide the brand book as a PDF and they extract what they need," they don't understand handover. If the answer mentions JSON, a Tailwind config, a shared Figma library, or a code-readable format — they get it.

To the web studio: "How do you handle the typography pairing if the brand agency specifies a licensed font that's expensive for web use?" If the answer is "we substitute a similar font that's cheaper," that's the dilution path. If the answer is "we sit down with the brand agency to either negotiate web licensing for the original font or jointly select a substitute that's been approved by the brand strategist," they get it.

To both: "What does the brand-to-web handover session look like, who runs it, and is it costed in the proposal?" If neither agency mentions a session, neither agency is planning to do one. Insist on it before signing.

The honest bottom line

A rebrand is an expensive strategic exercise. The brand book that comes out of it represents 8 to 16 weeks of thinking and design work. Letting that work get diluted in the handover to the web studio is the most preventable form of waste in any rebrand-and-rebuild project.

The fix is mechanical. Six artifacts, a live session, explicit budget for the handover work, and an agreed expectation that both teams collaborate during the transition rather than throwing files over the wall.

If you're scoping a rebrand-and-rebuild and you want to make sure the handover is actually built into the project plan, book a free audit. I'll look at both proposals you've been given, identify the handover gap, and help you negotiate it back into one of the scopes before either agency starts.

Brand to Web Handover: The 5 Steps That Actually Work