Howtobriefawebsitesoitactuallyships

Delays are almost always upstream

When a build runs late, the visible cause is usually a revision round or a missing asset. The real cause is older: a decision nobody made at the start, which stayed invisible until the work reached the point where it could no longer be dodged.

A brief is not paperwork. It is the list of decisions you are choosing to make now instead of in week five.

Name the one thing the site has to do

Not three things. One. Book a treatment, request a quote, apply for a role, buy a product. Everything else is allowed to exist, but the primary action is what the layout gets arranged around.

If the honest answer is more than one, the site has more than one audience. That is a structural fact worth knowing before the first page is drawn, not after.

Settle the copy question first

Decide who writes the words and when they are due. This is the single most common reason a project sits at ninety percent finished for a month.

Design against real copy wherever you can. A layout tested on placeholder text will break the first time a real headline runs three lines instead of one.

Bring the assets, or budget for them

Logo files in vector, photography at full resolution, whatever brand rules already exist. If something is missing that is fine, but it needs a line in the budget and a date, not an assumption that it will turn up.

Write down what you are not doing

A short list of what is explicitly out of scope prevents most of the awkward conversations later. Multi-language, e-commerce, a blog, a client login. Naming them as out is not a refusal, it is a phase two.

Agree how feedback arrives

One person consolidates comments, in one place, by an agreed day. Feedback arriving from four people across three channels over two weeks is not four times the input, it is four times the calendar.

That single line in a brief tends to save more time than every other line combined.