How to write a creative brief that a design team can use
Build a creative brief that explains the audience, message, deliverables and decisions your campaign needs before design work begins.
Start with the decision the brief must support
A creative brief is a working agreement about what a campaign should achieve and what the team needs to produce. Its purpose is to give designers enough context to make good choices without asking them to guess the organisation's priorities. A brief does not have to specify every visual detail. It should make the important boundaries clear while leaving room for a thoughtful creative response.
Begin with the business or communication problem. “We need six social graphics” describes an output, but it does not explain why those graphics matter. A more useful starting point might be that people understand the event but do not know registration has opened. That problem suggests a message, a call to action and a way to judge whether a proposed design is doing its job.
Write the objective in ordinary language. Avoid combining awareness, sales, recruitment, education and reputation into one equally weighted aim. If several outcomes matter, identify the primary one and explain the others as supporting goals. This gives reviewers a shared basis for decisions when a design cannot emphasise everything at once. The brief should help the team resolve tradeoffs, not conceal them behind broad ambitions.
Describe the audience as a real situation
An audience description should explain what a person already knows, what they need and where they will encounter the campaign. A demographic label alone rarely tells a designer how to communicate. Consider the person's immediate context: are they scrolling on a phone, reading a poster from a distance, comparing services or receiving an invitation from someone they trust?
Include the barrier the message must overcome. The audience might be unfamiliar with the offer, unsure whether it applies to them, worried about the time required or simply unaware of a deadline. Distinguish what the team knows from what it assumes. If the audience insight is a working hypothesis, say so and identify what evidence could confirm it. A plausible guess should not silently become an established fact in every later review.
Keep the audience focused enough to guide the work. If two groups need different information or language, consider separate variants. Asking one small graphic to address everyone often produces a crowded message that helps nobody. Explain the differences between the variants so the design partner can create a consistent family of assets without pretending that all audiences have identical needs.
Choose one message and one main action
State the single most important idea a viewer should remember. Then explain the action you want them to take. These are related but different: a campaign may communicate that an application window is open and ask the viewer to read eligibility information before applying. Putting both into the brief helps the designer build a clear hierarchy rather than treating every line of copy as equally important.
Separate mandatory wording from suggested wording. A product name, approved statement or event date may need to appear exactly as supplied. A supporting headline may be open to creative development. Label those differences clearly and identify who can approve a change. Otherwise, a designer may spend time polishing text that must remain fixed, while reviewers assume that optional draft wording is already final.
If a claim needs evidence or specialist review, record that requirement before artwork begins. Do not ask the designer to invent statistics, endorsements or guarantees to make a layout more persuasive. Link to the approved source or provide the exact wording the organisation is prepared to use. The creative brief can identify the review owner without attempting to replace the organisation's own approval process.
Turn deliverables into a usable specification
List each output in a way that the designer and recipient can check. “Social assets” is too vague when a campaign needs several placements, languages and file types. Specify the destination, dimensions or aspect ratio, quantity, language, required copy, file format and any relevant constraints. Confirm current placement specifications with the destination or production partner rather than copying an old campaign's assumptions.
A deliverable list should also distinguish the master concept from adaptations. For example, approve the main layout before producing twelve language and size variants. This reduces unnecessary rework when the core message changes. Record whether editable source files are part of the agreed handover and which linked assets, fonts or instructions the recipient needs. A preview image and an editable production file serve different purposes.
- Name the channel or physical placement.
- List the required sizes and variants.
- Identify the copy and image source for each item.
- State the review and final delivery dates.
- Explain which formats the recipient needs.
- Assign one person to confirm the specification.
Give references a reason
Visual references are most useful when they explain an intention. Instead of attaching several images and saying “something like this,” describe what each example demonstrates: a calm tone, a strong headline hierarchy, a restrained colour palette or a clear treatment of multiple speakers. This helps the designer extract the relevant principle without copying unrelated details.
Include examples to avoid when the reason matters. A previous campaign may have looked attractive but made the registration link too small, or it may have used a tone that did not suit the audience. Explain the communication issue rather than rejecting a style with no context. References should support the brief's objective, not become a collection of personal preferences that compete with it.
Provide current brand assets and identify the authoritative version. A folder containing several logos with similar filenames creates an avoidable decision for the designer. Point to the approved logo, colour guidance and any existing templates. If the organisation has no formal brand guide, state the practical rules that do exist and name the person who can answer questions about the rest.
Make the timeline include decisions
A production deadline is only meaningful if the earlier review dates are realistic. Work backwards from the launch or handover date and include time for concept review, revisions, final approval and technical checks. Ask reviewers when they are available rather than assuming that a file delivered late on Friday will be approved before Monday morning.
Identify dependencies that could stop the work. These may include final copy, photography, a translated text, a confirmed venue or a decision about the offer. Give each dependency an owner and a due date. If something is not ready, explain what the designer can safely begin and what should wait. This makes the brief useful as a planning tool rather than merely a document attached to a deadline.
Agree what happens when the brief changes. A new audience, message or format can alter the amount of work and the review sequence. Record the change and confirm its effect before continuing. Keeping the original brief and a visible update history helps the team understand why a delivery date moved or why an earlier concept no longer meets the current requirements.
Assign approval responsibility before the first draft
List the people who need to contribute and the person who can make the final decision. Not every reviewer needs to approve every detail. One colleague may check factual accuracy, another brand consistency and another technical delivery requirements. Explaining those roles keeps feedback focused and reduces contradictory instructions sent directly to the designer.
Choose a person to consolidate comments before the next revision begins. Their job is to resolve conflicts, identify the required changes and distinguish a suggestion from a blocker. Silence should not be interpreted as approval unless the team has explicitly agreed a process for that situation. A clear decision record is more useful than a long message thread in which several people sound generally positive.
Example: a community workshop launch
Imagine a team promoting a free weekend workshop. The objective is to help local residents understand who the event is for and visit the registration page. The brief identifies adults with no prior experience as the primary audience, gives the confirmed date and location, and makes the beginner-friendly message more prominent than the organisation's internal programme name.
The deliverables are one approved master concept, a square social image, a portrait social image and a print poster with production requirements confirmed by the printer. The organiser supplies approved copy and photographs, while the design partner proposes the visual approach. One programme manager checks the details and consolidates feedback. The final decision is scheduled early enough to correct the files before distribution.
This example is deliberately specific without prescribing the entire design. A designer can suggest a stronger visual hierarchy or a different photograph while still understanding the campaign's boundaries. If the workshop date changes, the team can identify every affected variant from the deliverable list instead of relying on memory.
Review the brief together before production
Hold a short review with the people doing the work. Ask the designer to explain the audience, message and deliverables back in their own words. Differences in interpretation are easier to resolve before a concept has been developed. Capture questions and decisions in the same campaign record so that later reviewers can see the agreed context.
Campaign Bay can keep the brief, design partners, artwork reviews and final files together. The tool supports the process, but the team still needs to supply accurate requirements and timely decisions. A brief becomes effective when people use it during reviews, update it when the scope changes and close the campaign against its agreed outputs.
Frequently asked questions
How long should a creative brief be?
Make it long enough to explain the objective, audience, message, deliverables, constraints and approval process. A concise main brief with linked specifications is often easier to use than a long document that mixes essential requirements with background material. Remove repetition, but keep information that changes a design or delivery decision.
Can design start before all the copy is final?
Some exploratory work can begin with clearly labelled draft copy, but the team should agree which decisions remain provisional. Do not treat a layout built around placeholder text as ready for production. Confirm the final copy before completing detailed adaptations, translations and technical checks that depend on its length and meaning.
Who should write the brief?
The person accountable for the campaign usually coordinates it with input from stakeholders and the design partner. The designer can help clarify missing information, but should not have to invent the organisation's objective, factual claims or approval rules. One owner should maintain the agreed version and communicate changes.