Construction Project Brief Preparation Checklist

Write a short paragraph describing the project as you would explain it to a relative, and keep it at the front of the brief as the statement everything else serves.

Long briefs drift. A plain paragraph at the top gives everyone a reference point to test later additions against.

State the problem the project is meant to solve, in terms of what does not work now, rather than jumping straight to the solution you have imagined.

A designer given a problem can offer options. A designer given only a solution can only draw it, even when a better answer exists.

Collect the things household members have said about the project over recent conversations and write them down as separate lines, including the contradictory ones.

Contradictions inside a household are normal and useful. Surfacing them in the brief means they get resolved deliberately rather than by whoever speaks last.

Write a short section on what you specifically do not want, and give the reason beside each entry rather than leaving it as a bare refusal.

Exclusions carry a lot of information. The reason matters because it may rule out other things you have not thought of.

Beside each requirement, record why it is there, so that if it turns out to be unachievable the underlying need can still be addressed another way.

Requirements without reasons become obstacles. Reasons without requirements can be met in several ways, which is what you want from a design process.

Date the document and give it a version label, then keep earlier versions rather than overwriting them as the brief develops.

Later disagreements are usually about which version someone was working from, and keeping the history makes that answerable.

Put your requirements into a stated order of importance rather than a flat list, and write down who agreed to that order and when.

Flat lists imply everything matters equally, which is never true and leaves the designer to guess at your real priorities.

Name the requirement you would drop first if the project had to be reduced, and the one you would protect above all others.

These two answers do more work than the rest of the brief combined, because they tell a designer where flexibility genuinely exists.

Go through the brief marking each entry as something the household needs or something it would prefer, and be honest where habit has disguised a preference as a need.

Owners routinely describe preferences as requirements, which narrows the options a designer can offer without anyone intending it.

Read the brief looking for requirements that pull against each other, such as wanting a room open to the garden and also wanting it quiet, and flag them rather than hiding them.

Flagged conflicts get designed around. Unflagged ones get discovered in a meeting where somebody feels caught out.

Record who holds the final say on the brief when household views differ, and make sure the person named has actually agreed to hold it.

A designer receiving instructions from two directions cannot resolve them, and the project stalls in ways that look like design delay.

Describe in your own words what would make you feel the project had gone well, avoiding measurable-sounding claims you are not in a position to set.

This is genuinely owner-side territory and it is the part of a brief designers most often say is missing.

For each space you have in mind, write what happens in it and who uses it, instead of relying on a room name that everyone will interpret differently.

The same room label means different things to different households, and the label alone rarely tells a designer why the space is needed.

State which spaces must be next to each other and which must be kept apart, and explain the reason in each case rather than stating it as a rule.

Adjacency requirements shape a plan more strongly than room sizes do, and they are the part an owner is unusually well placed to supply.

Note where you need to be able to see from one space into another, such as watching children or keeping an eye on an entrance, and where you would rather not.

Sightlines are hard to retrofit and easy to design in at the beginning, but only if someone says they matter.

List the furniture, equipment and possessions that must be accommodated, describing each in words and leaving the measuring to the design process.

A designer would far rather know about the piece that has to fit than find out about it after a plan has been developed around its absence.

Identify any space you expect to change use over the years, such as a room that starts as a study and later becomes a bedroom, and say so in the brief.

Spaces intended to change use are designed differently, and the intention is invisible unless it is written down.

Describe storage by naming the things that need storing and where they are used, rather than asking for storage in general terms.

Storage requests written in general terms produce cupboards in the wrong places, which is one of the most common regrets owners report.

Describe where you want daylight at particular times of day, such as morning light where breakfast happens, rather than asking for bright rooms in general.

Timing is the useful part. It tells a designer about orientation in a way that a general request for light never can.

Note the noise sources around the site and inside the household, and say which rooms need to be protected from which sounds.

Owners know their surroundings far better than any visitor can, and this information rarely appears unless it is specifically asked for.

State how you like a home to feel in terms of warmth, draughts and stuffiness, and write these as experiences rather than as performance requirements you have chosen.

Turning comfort into stated experience keeps the technical choices where they belong while still telling a designer what you are after.

Do not set values or specify systems for heating or ventilation. Put comfort preferences to a qualified designer and let them advise on the means.

Record any view you want kept or framed, and any outlook you would rather not have, standing on the site to check both rather than relying on memory.

Views described from memory are often wrong about direction, and correcting it later can mean moving a window that has already been made.

Describe what you want the experience of arriving at the home to be, from the point of leaving a vehicle to putting shopping down.

Entrance sequences are where practical failures concentrate, and they are almost never described in briefs.

Note how you want to use outdoor space and at what times of year, since a request to connect inside and outside means very different things in different climates.

Being specific here prevents a generic response, and it lets a designer test the idea against how the site actually behaves.

List the constraints that genuinely cannot move, such as an existing structure that is staying, and mark everything else as open to proposal.

Owners tend to over-fix. Marking only the true constraints gives a designer room to offer something better than what you imagined.

Flag every point in the brief that depends on something not yet confirmed, and note who is confirming it and what happens to the brief if the answer changes.

Briefs quietly harden around assumptions. Marking the unconfirmed points keeps them visible while they still matter.

Go through the brief marking which entries are decisions for you and which are really design or technical judgements you should be handing over.

This single pass usually shortens a brief considerably and improves what comes back, because it stops you constraining choices you cannot properly weigh.

Anything touching structure, ground, drainage or building systems belongs with a qualified professional even when you have a firm view about it.

Write down any decision already taken and acted on, including anything already ordered or committed to, so that the design starts from reality.

Anything already ordered narrows what a designer can propose, and it is far better stated at the outset than discovered halfway through.

Mark the points in the brief you know will need confirming with the local authority, and treat them as open questions rather than settled requirements.

Keeping these visibly open avoids building the whole brief on an assumption that turns out not to hold here.

Only the local authority can confirm what applies to your site. Do not record a requirement as settled on the basis of what applied elsewhere.

State plainly whether the project is intended to be carried out in one go or in stages, and which elements you would be content to leave until later.

Phasing intentions influence design decisions from the very beginning, and revealing them late usually means redoing work.

Write a line beside each reference image saying what specifically appeals in it, since the same picture can be admired for the light, the material or the layout.

Unannotated images are ambiguous, and a designer who guesses wrongly may spend effort on the wrong quality entirely.

Sort your images into those showing something you would like explored and those showing something you consider settled, and label the two groups differently.

Owners are often surprised by how firmly a casually saved image gets treated once it is handed over without any qualification.

Where an image is nearly right, note what is wrong with it as well, because the correction is often more informative than the admiration.

Saying what is wrong narrows the field far faster than adding another image that is nearly right in the same way.

Flag images that come from a very different climate, setting or type of building, and note that you understand they may not transfer to your site.

This keeps the image useful as an atmosphere reference while making clear you are not asking for it to be copied here.

Include a small set of images showing what you actively dislike, again with a line explaining what specifically is objectionable.

Dislikes are usually more precise than likes, and they are the part of a reference set that owners almost never assemble.

Photograph things you like in your own area rather than relying only on saved images from elsewhere, and note where and when each photograph was taken.

Local examples sit in the same light and setting as your project, which makes them a far better basis for discussion.

Circulate the brief inside the household and get everyone who has a view to read it before it goes to anyone else, then note who has read which version.

Objections raised after a designer has begun are far more disruptive than the same objections raised over the kitchen table.

Ask the designer to restate the brief back to you in their own words, and compare their version with yours before any drawing work begins.

Differences between the two versions are exactly the misunderstandings you want to find early, and they surface immediately in this exercise.

Agree in writing how a change to the brief is recorded and communicated, and who needs to be told when something in it moves.

Verbal changes are a frequent source of the wrong thing being built, and a simple written routine removes much of that risk.

Ask at which points in the design process the brief will be read against the drawings, and put those review points in your own notes.

Briefs drift out of alignment with drawings gradually rather than suddenly, which is why deliberate comparison points help.

Keep a running log of decisions taken during design, with the date and who was present, alongside the brief rather than inside it.

A decision log answers most later disagreements in a sentence, and it takes only a few moments to maintain as you go.

A decision log is a record, not an instruction. Anything with technical consequences still needs confirming with the appropriate professional.

Note the point at which the brief stops being the working document and drawings take over, and ask who tells you when that has happened.

Owners often keep referring to a brief that the design team has long since moved past, which produces confusing conversations on both sides.