Brief versus specification
A specification describes the hardware: pitch, cabinet size, brightness, driver type, control platform. A brief describes the problem. Confusing the two is the most common reason a first proposal misses, because a supplier asked to quote a specification will quote exactly that and nothing about whether it suits the room.
Writing the brief first does not mean avoiding technical detail. It means recording what is known about the site and the outcome, and being explicit about what is not known yet. Where a technical choice genuinely has to be made early, say so and give the reason, then let the proposal address it.
The useful test is this: if two suppliers receive the same brief, should their proposals be comparable? If the answer is no, something material is missing.
Start with the outcome, not the hardware
State what the display is meant to achieve and for whom. Advertising to passing traffic, wayfinding for first-time visitors, a backdrop for scheduled broadcasts, an internal dashboard for a control room and a commissioned piece in a gallery produce different answers from the same room dimensions.
Then state what the content actually is. A screen carrying a static logo, a live data feed, scheduled video and an operator-driven presentation each impose different requirements on resolution, control system and update workflow. If the content does not exist yet, say that too, and say who will produce it.
Finally, name the measure. Not a number nobody can verify, but something observable: dwell time, legibility from a specific point, whether a visitor can find the right desk, whether the room still works when the screen is off. A stated outcome lets you judge a proposal. Without one you are left judging how it looks.
The site information that changes the design
Location and environment come next, and they carry more weight than most briefs give them. Indoor or outdoor, the ambient light level at the intended position, whether the sun reaches the surface and at what time of day, the distance from which the content has to be read, and the angles a viewer can occupy.
Dimensions should be given as the space available, not the screen size wanted. A wall that can take four metres by two and a half is a constraint; a requirement for a specific screen size is a conclusion drawn from it. Where the available area is uncertain, give the range and any obstruction: columns, doorways, sprinklers, signage, existing services.
Then the building itself. Floor loading, ceiling height, what the wall or structure is made of, where power and data currently terminate, and whether new cable can be run at all. These are the items that turn a plausible proposal into an impossible one, and they are usually known already by someone in facilities.
Content, sources and who operates it
Say where the content comes from and who is responsible for it after handover. A display that depends on a person who leaves the organisation is a display that stops being updated, and that is a design question as much as an operational one.
State the update frequency and the mechanism. Scheduled playlists, a live source, an operator with a laptop before each session, or a remote schedule managed by a central team all imply different control systems and different network requirements.
Note any constraint on the material itself: brand guidelines, licensing, languages, accessibility requirements for captions or contrast, and anything that must not appear on screen. These are cheap to record in a brief and expensive to retrofit into a content workflow.
Access, programme and installation windows
When can the work physically happen? Retail floors are installed overnight, airports and transport hubs outside operational hours, occupied offices at weekends, heritage buildings under a consent process with its own timetable. If installation is constrained to specific hours, say so in the brief.
Describe the delivery route as well. Door widths, lift dimensions, loading dock availability, parking for a vehicle, and any security or induction requirement for contractors. A display that arrives and cannot be moved into position is a programme problem, not a product one.
Then give the timeline that actually matters: the date the screen must be live, and whether that date is fixed by an event, a launch, a lease or a budget year. Suppliers plan backwards from a hard date and forward from a soft one, and those are different plans.
Service expectations over the life of the screen
Briefs usually stop at installation, and that is where expectations later diverge. State who is expected to look after the display, what response time is acceptable when something fails, and whether that expectation is contractual or informal.
Say whether spares should be held on site and by whom. A module, a power supply and a receiving card kept in a cupboard turns a multi-day outage into an afternoon; whether that matters depends entirely on what the screen is for.
Also state the expected operating pattern. Continuous running, daily start and stop, seasonal use, or occasional events all affect thermal design, service intervals and the realistic service life of the installation.
Budget range and decision process
A range is more useful than a fixed figure, and more useful than silence. It tells a supplier whether to propose a fine-pitch indoor wall or a coarser outdoor one without committing anyone to a number. Where the budget is genuinely unknown, say that and give the outcome instead; that still allows scope to be shaped.
Name the decision process. Who signs off, how many people are involved, whether procurement requires a set number of comparable bids, and what the approval sequence looks like after a proposal arrives. A technically excellent proposal that cannot pass through the buyer's own process is a wasted cycle for both sides.
If there are constraints that will not move, mark them as fixed. Consent conditions, structural limits, brand requirements and heritage restrictions are not negotiating positions, and a brief that flags them prevents a proposal built on something that will later be refused.
Common gaps that slow a proposal down
The recurring omissions are predictable. No statement of viewing distance, no information about ambient light, no confirmation of where power terminates, no access window for installation, and no named decision maker. Each one converts into a round of questions before anything can be costed.
The second pattern is a brief that specifies hardware without context. Naming a pixel pitch and a brightness figure tells a supplier what to quote, not what to solve, and it removes the possibility of being told that a different choice suits the room better.
The third is silence on content. A display is commissioned for material that does not exist yet in more projects than most teams admit, and the content plan is usually the longest lead item in the programme.
The six inputs to gather before the first meeting
Most of the value in a brief comes from six classes of information. None of them requires technical knowledge, all of them can be gathered by the person who owns the project, and each one removes a question that would otherwise come back as an email three days later.
<strong>The outcome and the audience.</strong> Who the screen is for and what they are meant to do with it. Advertising to a queue, wayfinding in a lobby, a live feed in a control room and a backdrop for a stage all lead to different proposals from the same wall.
<strong>The space, measured.</strong> The available opening in millimetres, the finished floor to the underside of the ceiling, and the position of anything that cannot move: columns, ducts, sprinkler heads, handrails, and doors that must still open. A rough tape measurement beats a drawing that shows what was intended four refurbishments ago.
<strong>The viewing geometry.</strong> Where the closest viewer stands and where the furthest one sits, at what height, and from what angle. Two numbers and a sketch usually cover it, and they carry more weight in the proposal than any other single input.
<strong>The environment and the hours.</strong> Indoor or outdoor, direct sun or controlled light, dust, humidity, kitchen grease, salt air, and how many hours a day the screen runs. The operating pattern decides brightness targets and cooling assumptions, and both are expensive to revisit later.
<strong>Power and data positions.</strong> Where the supply terminates, whether the route to the screen position is clear, and who is responsible for the circuit. Do not attempt to size it; state what exists now and let the proposal confirm capacity.
<strong>The decision and the date.</strong> Who signs, what the approval sequence looks like, when the screen has to be live, and whether an event makes that date immovable. A fixed date shapes a proposal more than most buyers expect.
Write these as six short answers, add anything already fixed as a constraint, and send it. One page is enough, and the supplier's questions will show you what is still missing.
A brief that started with pixels
A project opened by specifying pixel pitch, then discovered the space and content needed a different approach. Rewriting the brief around outcome saved a wrong-order cycle.
No operator, no owner
A wall was installed without naming who would run content. Months later it showed a stale loop because the brief never assigned the operator.
From brief to decision: writing an led display project brief
- Start with the outcome, not hardware State what the screen is for and who reads it before naming any product. The hardware follows the purpose, not the other way round.
- Gather the site facts that change design Record the available space, viewing distance, ambient light, access window and operating pattern. These decide pitch, brightness and service, not preference.
- Name content, sources and the operator Say what will be shown, how many sources, and who runs it day to day. The brief that omits the operator produces a wall nobody owns.
- State budget range and decision process Give a realistic budget band and how the decision will be made. Suppliers then propose to the real constraint instead of guessing.
What people get wrong about writing an led display project brief
“The brief must specify pixel pitch.” — Pitch is an output of the brief, set by viewing distance and content. Starting with hardware skips the facts that actually choose it.
“A brief should be long and detailed.” — A good brief is short and factual, organised around outcome and the six site inputs. Length does not replace clarity; it usually hides the missing facts.
The one detail to confirm on writing an led display project brief
A good brief is short, factual and organised around the outcome. The hardware comes out of it, not the other way round. State the purpose, the space available, the environment, the access window, the operating pattern and the decision process, and mark the constraints that cannot move. Two suppliers reading it should be able to propose comparable solutions, and you should be able to tell which one understood the room.