Write a creative brief that a team can use

Give the team a decision to make.

A creative brief should help a team choose what to produce. It becomes less useful when it collects every thought the client has had about a campaign without distinguishing the important decisions. Before opening a template, write one sentence describing the job. For an illustrative example, imagine an independent brand launching a training bag. The campaign needs to show a prospective customer how the bag works during the trip from home to a session.

That sentence already provides direction. It suggests use, movement, and the objects a person carries. It also gives the team a way to question ideas that look attractive but do little to explain the product. The brief can still leave room for creative interpretation. Its role is to define the problem, the practical constraints, and the decisions the client is prepared to make.

Describe the audience in a recognizable situation.

“Ages twenty to forty who like fitness” offers little help when choosing a location or a scene. A more useful description follows a situation: someone carrying work essentials and training equipment on the same journey, with limited time to repack. The team can imagine what that person needs to see. If this audience description is only a hypothesis, label it as such and identify who can confirm or refine it.

Avoid inventing a complete personality for the customer. The brief needs the details that affect the work. Where will the campaign be encountered? What does the person already know about the product? Which question is likely to stop them from considering it? Write those points plainly. A crew member who has never attended a planning meeting should be able to understand the intended viewer from the document alone.

State the message and its support.

Choose one main message for the campaign. In the bag example, it might be that the product keeps training equipment organized during a busy day. Then list the observable details that support that message: a particular compartment, an opening, or a way the bag is carried. Confirm those details with the product team. The production team should not have to infer a feature from a prototype or improvise a claim on set.

Separate a factual product statement from an emotional direction. “Show an easy transition from commute to training” is a creative instruction. “Fits every locker” is a factual claim that would need support and may be inappropriate. Keeping those categories distinct helps the team build a compelling scene without accidentally introducing an unsupported promise. If a statement still needs approval, mark it clearly and assign an owner.

Make the deliverables countable.

List the actual files needed for launch. An example package might include a short horizontal film, two vertical edits, several selected stills, and a clean product detail image. For each one, specify duration or dimensions, intended placement, and any required text-safe area. The exact list should come from the campaign plan. A fashionable format has little value if no one knows where or how it will be used.

Clarify which versions are separate edits and which are simple exports. Cropping a horizontal frame may not create a useful vertical sequence. Different opening shots, captions, or calls to action can add work. Ask the production team to flag those implications before the scope is agreed. A small delivery table is often easier to use than a paragraph that mixes creative wishes with technical requirements.

Explain references rather than attaching a moodboard.

References are most helpful when each has a note about what matters. One image may show the desired quality of light. A film may demonstrate a pace of editing. A layout may show how much space is needed for product copy. Explain those points individually so the team does not assume every element of every reference should be reproduced. Conflicting references should prompt a discussion before production begins.

Include a few things to avoid when they are relevant to the actual project. The bag campaign might need to avoid an elite competition setting because the product is intended for ordinary training days. That is a useful boundary tied to the audience. A long list of vague dislikes can make the brief harder to interpret. Keep each restriction connected to a decision the team will face.

Put constraints where people can find them.

The budget, schedule, location access, sample availability, and approval deadlines affect what can be made. Give these facts a clear place in the brief. If the available product is a prototype, explain what can and cannot be shown. If a location is only available for a short window, say so before a treatment depends on changing light across a full day. Uncertainty should be visible rather than hidden in a separate conversation.

A constraint can also open a productive creative choice. One location may encourage a simple sequence built around movement through that space. A limited cast may lead to a more intimate demonstration. The team can work with those boundaries when they know them early. Problems arise when the brief appears open and the restrictions arrive only after an idea has been developed and approved.

Name the person who can approve the work.

Choose an approval owner and explain how feedback will be collected. A producer needs to know whether comments from several departments have been reconciled or whether they still conflict. For each review point, state what is being approved: the concept, the shooting plan, the edit structure, or the final files. That keeps late feedback from reopening decisions without acknowledging the effect on scope and timing.

Ask the client team to provide consolidated feedback in a usable form. Time-coded notes help with video, while marked selections help with stills. A comment should describe the problem when possible. “The product detail is hard to understand” gives an editor more room to solve the issue than an unexplained instruction to remove three seconds. A short discussion can resolve ambiguity before it becomes another revision round.

Read the brief as a handover.

Before sending it, give the document to someone who has not been involved. Ask them to describe the audience, the message, the deliverables, and the next decision. Where they hesitate, the brief probably relies on shared context that has not been written down. Add the missing explanation rather than expanding every section. The aim is a clear handover that remains easy to scan while people are working.

For the training bag example, the final page might open with the use situation, identify three product details, list the agreed assets, and close with schedule and approval ownership. Supporting references can sit in an appendix or a clearly labeled folder. The next step is to draft that single page for a real upcoming campaign, then ask the production team which unanswered question would prevent them from estimating or planning the work.