The template
The structure to copy and adapt
- Intake metadata + receiving teamRequiredProject name, intake date, requesting team, design team receiving the work, project owner, design lead. The metadata block is what makes the brief routable inside a team. Treat the brief as a ticket - it needs metadata.
- Requested deliverables (per artifact)RequiredEach artifact named, with format and use case. 'Instagram static (4:5), email hero (600x300), landing page hero (1920x800).' Per-artifact specs let the design team estimate hours.
- Business context (1 paragraph)RequiredWhy this design exists and what business outcome it serves. Compressed - the design team doesn't need the strategy doc; they need to know the why so they can make tradeoff decisions.
- Audience (1 paragraph)RequiredWho sees the design. Same depth as a general creative brief, but compressed. The design team uses audience to make typography, contrast, and density decisions.
- Brand reference + asset library accessRequiredBrand book version, design system URL, asset library link, font licensing access, photography library access. The design team needs to know how to pull from the source - brief access, not duplicate content.
- Inspiration + do-notsRequired3-5 visual references (links or images) + 3-5 anti-references. Plus 5-7 design do-nots specific to this brief. The design team uses references and do-nots more than written description.
- Review cadence + sign-off ownersRequiredNumber of review rounds, named reviewers per round, sign-off owner for final delivery. Briefs without named reviewers turn into rolling-feedback purgatory.
- Deadline + dependenciesRequiredHard deadline + soft deadline. Dependencies (waiting on copy, photography, product spec). Briefs that don't surface dependencies surprise the design team mid-project.
- Handoff format (to dev / production)How the design delivers downstream. Figma dev mode, Zeplin link, exported assets in shared drive, print files to vendor FTP. Brief the handoff format up front so the design team builds the file accordingly.
Filled-in examples
See the template in use
Paid social asset pack request · DTC / paid social
- Intake metadataProject: Q3 cold acquisition asset pack. Intake date: 2026-05-20. Requesting team: Performance. Design team receiving: Brand Studio. Project owner: Maya Chen. Design lead: TBD by Brand Studio at intake review.
- Requested deliverables12 static variants in 3 ratios (36 files): 4:5, 1:1, 9:16. 6 motion variants in same ratios (18 files): 15s + 30s cuts. 4 carousel sets (5 cards each, 1:1). 2 catalog templates. Format: PNG + JPG for static; MP4 H.264 for motion.
- Business contextCurrent paid social pack is 9 months old, winning angles saturated. Need a refresh that retains brand signature but rotates angle + hook + treatment to unlock new audiences. Goal: drop CAC from $47 to $32 over 30 days post-launch.
- AudienceCold paid-social audiences (Meta, TikTok) on mobile. 4-second average view duration. Sound-off by default. Thumb-distance viewing.
- Brand reference + asset libraryPer Greenline brand v3.2 (brand book URL). Design system Figma library URL. Photography library (Bynder) URL. Font licensing via Adobe Fonts team account (access pre-provisioned for Brand Studio).
- Inspiration + do-notsReferences: Liquid Death paid social, Magic Spoon carousels, Athletic Brewing motion. Anti-references: designer paid social prioritizing aesthetic over hook clarity. Do-nots: no discount as hero, no bottle-only static, no 'as seen in' logos, max 8 words above the fold, no founder-to-camera, no price overlays in carousel.
- Review cadence + sign-off ownersRound 1: concepts (3 directions) reviewed by Brand Director + Performance Lead, 1-day turnaround. Round 2: 1 direction taken to executions, reviewed by Brand Director + Performance Lead + Founder, 2-day turnaround. Round 3: final QA, sign-off Brand Director.
- Deadline + dependenciesHard deadline: 2026-06-15 (launch). Soft deadline: 2026-06-10 (QA buffer). Dependencies: net new product photography from Studio team, due 2026-05-30.
Shuttergen
Shuttergen is for ad briefs - design team intake stays human.
Design team intake briefs need human routing, dependency tracking, and review-round orchestration. Shuttergen doesn't generate design intake briefs. For the paid social and search briefs that distribute your design team's output, it is the right tool.
Why design-team-receiver briefs are different
Most creative briefs are written for an audience of one - the creative director or design lead reading the doc. A design-team-receiver brief is written for an audience of many - the design lead who routes the work, the designer assigned to execute, the reviewers who weigh in, the production team that handles handoff. The brief is closer to a ticket than a strategy doc.
Metadata is what makes the brief routable. Intake date, requesting team, receiving team, project owner, design lead - these fields seem bureaucratic until you have 30 projects in flight and need to know who owns what. Treat the metadata block as required for any in-house team operating at scale.
Reviewers and sign-off owners get named explicitly. Briefs that say 'review by leadership' produce rolling-feedback purgatory where every senior person weighs in on every round. Named reviewers per round + named sign-off owner for final delivery is what closes the loop.
Shuttergen is for ad briefs - design team intake stays human. Design team intake briefs need human routing, dependency tracking, and review-round orchestration. Shuttergen doesn't generate design intake briefs. For the paid social and search briefs that distribute your design team's output, it is the right tool.
The per-artifact deliverable specification
List deliverables by artifact, not by category. 'Social asset pack' is not a deliverable; '12 static variants in 4:5 + 1:1 + 9:16' is. Per-artifact lists let the design team estimate hours, scope production work, and identify reuse opportunities.
Include format with each artifact. PNG, JPG, MP4, AI, INDD, PDF - each format has different production implications. Briefs that skip format produce projects that stall at delivery.
Specify ratios + lengths up front. For motion: 15s and 30s cuts. For social: 4:5 + 1:1 + 9:16. For print: bleed and safe zones. These are scope-defining specs; surfacing them late changes the project's effort estimate by 30-50%.
Handoff format - the field that prevents the last-mile slip
Brief the handoff format up front so the design team builds the file accordingly. Figma dev mode requires component-organized files. Print vendors require production-ready PDFs with specific color profiles. Asset library handoffs require named, organized exports. Each handoff format implies a different file structure; brief the handoff before the design team starts.
Dev team requirements vary by stack. A Webflow build needs different handoff than a Next.js build. Brief the dev team's tooling (Figma dev mode, Zeplin, Storybook, design tokens JSON) so the design team builds with the dev workflow in mind.
Production vendor requirements vary by print method. Litho vs digital vs flexo all have different ink limits, color profile expectations, and file structure conventions. Brief the print vendor up front (or note 'TBD - vendor selection in progress') so the design team plans accordingly.
Internal: creative brief design, creative design brief, design creative brief.
FAQ
Frequently asked
What is a creative brief for a graphic design team?
How is a design-team brief different from a creative director brief?
Why does the brief need intake metadata?
How many review rounds should the brief specify?
Why specify the handoff format up front?
What's the most common failure mode in design team briefs?
Who writes the design-team-receiver brief?
Related
Keep reading
Resource
Creative brief design
Design system constraints lens.
Resource
Creative design brief
Output-first design brief.
Resource
Design creative brief
Brand-identity-first design brief.
Resource
Graphic design creative brief
Graphic-design-specific variant.
Research
Creative Brief Builder
The Shuttergen brief workflow.
Shuttergen is for ad briefs - design team intake stays human.
Design team intake briefs need human routing, dependency tracking, and review-round orchestration. Shuttergen doesn't generate design intake briefs. For the paid social and search briefs that distribute your design team's output, it is the right tool.