Start with the decision the brief needs to support
A creative brief is a short explanation of what someone is making and why. It gives a collaborator enough context to make sensible choices without asking permission at every step. You might use one for a flyer, a workshop handout, a short video or a set of product descriptions. The goal is not to predict every detail of the finished work. It is to make the important decisions visible before work begins.
Write one or two sentences describing the purpose. Try “Create a one-page flyer that helps first-time visitors find and register for the workshop” rather than “Make an exciting flyer.” The first version identifies what the work should help a reader do. If you cannot name that action yet, pause and clarify it with the people involved. A polished brief cannot compensate for an unclear purpose.
Describe the audience and the deliverable
Next, identify who will use the finished work and what they are likely to know already. “New workshop visitors who have not seen our registration process” is more useful than “everyone.” Include the situation in which they will encounter it if that affects the work: on a noticeboard, in an inbox or as a printed handout. Avoid guessing at personal traits you do not need to know. Focus on information that helps the creator choose language, format and level of detail.
Then state exactly what needs to be delivered. Specify the number of items, their intended use and any known size, length or file requirements. Separate firm requirements from preferences: “Must fit on one page” is different from “A calm visual style would be nice.” If production details still need to be settled, mark them as open questions rather than letting a collaborator mistake a guess for a requirement. For adjacent production topics to browse while thinking about deliverables, explore Print Production · Emulsion Creative.
Provide material without prescribing every choice
Gather the facts, wording and assets the creator must use, such as a confirmed event name, contact details, logo or existing style guidance. Say which details are approved and which are provisional. A useful brief might say, “Use the attached schedule; the room number is awaiting confirmation.” That gives someone a way to proceed while keeping the unresolved detail visible.
References can help, but explain what you mean by them. Instead of sending an example with “Make it like this,” identify the quality you want: perhaps its clear headings, readable spacing or welcoming tone. Also say what should not be copied. Leave room for the person doing the work to propose a better approach. A brief that dictates every sentence and layout choice may prevent the collaborator from using their skills, while a brief with no boundaries forces them to guess.
Explain the review process before work starts
A small project can still stall if no one knows who approves it. Name the person who will collect feedback, who will make the final decision and when a first draft is needed. If several people will comment, ask them to send feedback through one contact where possible. This can reduce conflicting requests and make it easier to distinguish essential changes from individual preferences.
Describe how the draft will be judged. For example, reviewers might check whether the main action is easy to find, whether required details are accurate and whether the format works where it will appear. These criteria are more actionable than “We’ll know it when we see it.” If you are also working on the words themselves, browse Copywriting · Emulsion Creative for related topics; keep the brief focused on the decisions your collaborator needs to make.
Use a short test before sending
Read the brief as though you have never discussed the project. Can you identify the purpose, audience, deliverable, firm constraints, available materials and next review step? Look for words such as “modern,” “engaging” or “professional” that could mean different things to different people. You do not have to remove them all, but pair them with a concrete example or an outcome when they matter.
Finally, invite questions: “What would you need to know before starting?” That question can reveal a missing deadline, an unclear approval or a requirement you assumed was obvious. Update the brief when an answer changes the work, so everyone can refer to the same version. A good brief is not a promise that a project will need no discussion. It is a practical starting point for a better one.
