How to write a brief that lets work begin
A good opening document defines the problem, deliverable and decision process. Give a professional clear direction without trying to do their job.
Start with what needs to change
A good brief is not a list of attractive things you have seen. It is a short explanation of what you need to achieve. Before requesting design, text or video, write one sentence describing the current situation and another describing the desired result. For example: customers reach the service page without understanding whom it suits; after the work, they should recognise whether the service is relevant and know the next step. These two sentences give the project a direction to revisit when choices arise. Add a real example of the message being misunderstood if useful. A question asked by several customers may be more helpful than a full page of slogans about business values.
Define the audience and the moment
The audience description should help the person doing the work make decisions. Instead of saying everyone, describe the person likely to encounter the result: what they already know, their question and what could confuse them. State where the encounter happens too. An advert seen briefly on a phone requires different choices from a document sent after an introductory call. If there are several audiences, choose which is central to this deliverable and which needs can wait.
Write exactly what should be delivered
Separate the project's purpose from its deliverables. If you need a webpage, list its sections and who supplies text and images. For a post series, state the number, languages and versions required. Add the final file types you need where known. You do not have to guess unfamiliar technical details. Mark them as questions to resolve so they do not become hidden assumptions discovered only at handover.
Attach materials with an explanation
A logo, existing text and examples can shorten the process, but an overloaded folder without guidance can add work. Beside each example, state what you want from it: information order, use of colour or reading experience. Note what does not suit you too. Check that filenames are clear and files open. Separate mandatory material, such as approved wording or a fixed brand colour, from material supplied purely for inspiration.
Agree on how decisions are made
Choose one person to collect comments and provide agreed feedback. If every participant sends a different direction, the professional has to guess which request takes precedence. Plan an early checkpoint to approve the direction before investing in detail. Record when feedback is expected, who must approve and when the final deliverable is needed. If an event or publication date cannot move, say so at the start rather than after a different schedule has been proposed.
Check that the document allows a response
Before sending, read the brief as though you do not know the business. Is it clear what needs doing, what is missing and who can answer questions? Add a budget range if known so the proposal can suit the possible scope. Invite the professional to flag contradictions or suggest a different work sequence. A brief is not a test that forbids questions. It is a shared starting point to refine before committing to delivery and discovering that both sides imagined different results.
