Knowledge base

How to write a brief for a wayfinding project

A wayfinding brief describes a problem, not a list of signs: who arrives at the site, where they need to get to, and how you verify they got there. The schedule of signs is an output of design, and the consultant produces it. A brief that opens with a sign count almost always yields a system that fails to solve the original problem.

In brief

A workable wayfinding brief has six parts: site boundaries and phasing; visitor scenarios with entry points and goals; interior and structural constraints; deliverables; sign requirements; and acceptance criteria. Sign counts and types do not belong in the brief — the designer determines them after analysing routes, otherwise the brief locks in a solution before the problem has been studied.

Key points

Core rule
A brief describes the problem and the deliverables, not a sign count
Minimum content
Boundaries, scenarios, deliverables, acceptance criteria
Who writes it
The client sets the problem; the designer helps articulate it
Common mistake
A fabrication quote presented as a brief
What is excluded
Sign types and counts, materials, artwork — these are outputs

Site boundaries and phasing

The first thing to fix is what counts as the site. External grounds and parking, the entrance, floors, separate buildings, the basement level: each of these may be in or out of scope. Ambiguity here is the most expensive kind, because a route does not end at a contract boundary — someone who has reached the car park keeps moving inwards.

If the system is rolled out in stages, the phasing is stated up front. The system is designed as a whole and fabricated by phase — that way the second phase does not force a rework of the first.

Visitor scenarios

This is the substantive part of the brief. For each category of visitor, describe where they enter from, what they are looking for, what they already know, and what happens when they fail to find it. A patient with an appointment, a walk-in patient, a companion, a courier, a member of staff, a contractor — each has their own route, and those routes coincide less often than expected.

Two or three lines per category is enough. The value is not in the volume but in the categories being listed at all: this is the step at which teams usually discover a flow nobody had designed for.

  • Entry point: from the street, the car park, an underpass, an adjacent building
  • Goal: a specific room, desk or waiting area
  • What is known in advance: a room number, a department name, nothing
  • Who accompanies them and whether that person has to find their way back
  • What a lost visitor does — who they ask

Constraints and deliverables

Constraints are what cannot change: brand guidelines, landlord requirements, ceiling construction, walls that cannot be chased, an approved interior. The earlier they are named, the fewer decisions have to be undone.

Deliverables define what the client actually receives. The minimum working set is a sign location plan tied to floor drawings, a schedule with dimensions and materials, artwork in source files, and rules for maintaining the system. That last item is the one most often skipped, and its absence is why systems fall apart within two or three years: new signs get added without rules, and the logic is lost.

Acceptance criteria

A brief without acceptance criteria can only be signed off on taste. Usable criteria are measurable: the route from every entry point to every destination can be walked without asking staff; every decision point has a sign before it rather than after it; zone names match across signs, documents and staff speech; signs read from their design distance under the actual lighting.

Verification is done by walking the routes with someone visiting the site for the first time. That is the only way to tell a system that works from one that looks right on a drawing.

Frequently asked questions

Should the brief specify how many signs are needed?

No, and this is the classic mistake in template briefs. The number of signs follows from route analysis: as many decision points as there are junctions. Fixing the number in advance locks in a solution before the problem is understood, and typically produces either a surplus of signs in the lobby or none at the point where people turn the wrong way.

Can a brief be written without a wayfinding consultant?

Boundaries, scenarios, constraints and acceptance criteria are the client's to write — that is their knowledge of the site. Help is usually needed with deliverables and sign requirements, where it is easy either to over-specify or to leave gaps that surface at handover.

How does a brief differ from a questionnaire?

A questionnaire gathers input and records the task as the client states it. A brief is the document the work is accepted against: it carries measurable criteria and a list of deliverables. A questionnaire normally precedes a brief rather than replacing it.

We will design the wayfinding for your building

Send us the floor plans and a short description of the building — we will come back with an estimate of scope and timescales. You can start with the audit: it forms the first stage of the project, and is billed separately if you decide to take it from there yourself.