← Resources

Templates

Creative project brief template

A project-management-grade creative brief template. Built around timelines, deliverables, owners, and approval gates - not just creative direction. Includes 3 worked examples and a downloadable file.

Updated

The template

The structure to copy and adapt

  • Project overviewRequired
    Project name, sponsor, lead creative, lead PM, version, date. One sentence describing the project. The header that anchors all other sections.
  • Business objectiveRequired
    What outcome the project delivers to the business. Tied to a KPI with a target number. 'Increase activation by 15% within 90 days' beats 'improve onboarding'.
  • Scope (in / out)Required
    Explicit two-column list: what's IN scope, what's OUT. The OUT column is mandatory - prevents scope creep. 'IN: homepage hero rebuild. OUT: navigation, footer, checkout flow.'
  • Deliverables registerRequired
    Table: deliverable name, format, owner, due date, dependency. Every line ships or the project doesn't ship. Treat as the project's bill of materials.
  • Timeline & milestonesRequired
    Gantt-style timeline with named milestones and explicit approval gates. Each milestone has an owner and a date. Gates are red-line moments; missing one delays everything downstream.
  • Approval gates (RACI)Required
    For each gate: who's Responsible (does the work), Accountable (owns the gate), Consulted (provides input), Informed (updated). Prevents the 'whose approval do we need' bottleneck.
  • Audience & angleRequired
    The creative direction layer - audience, angle, hook archetype, do-nots. Compressed to one section because in project-led briefs, the creative direction supports the PM structure, not the reverse.
  • Budget & resourcing
    Total budget broken down by line item (creator fees, production, paid media). Plus internal resourcing - hours per role per week through project duration.
  • Risk register
    Top 3-5 risks: what could derail the project, probability, mitigation. Vendor delays, creator booking falling through, regulatory review - name them in advance.
  • Success metrics & review schedule
    Pre-launch: what we'll measure. Post-launch: when we'll measure (7-day check, 30-day check, 90-day retrospective). Without scheduled reviews, no one learns.

Filled-in examples

See the template in use

DTC quarterly creative refresh (in-house, 60 days) · DTC ecommerce - in-house

  • Project overviewGREENLINE Q3 CREATIVE REFRESH | Sponsor: Head of Growth | Lead Creative: M. Park | Lead PM: A. Reyes | v1.0 | 20 May 2026. Refresh the paid-social creative library across Meta and TikTok with 20 new variants spanning 4 hook archetypes.
  • Business objectiveReduce blended CAC by 12% in Q3 by replacing fatigued creative (60+ days alive, CTR dropping >20% week-over-week). Target: $26 CAC by 30 September from current $30.
  • ScopeIN: 20 new video variants (4 hook archetypes × 5 cuts), 8 static variants, refreshed audience targeting in Meta. OUT: landing page changes, email sequence, organic social, influencer activations - all separate projects.
  • Deliverables register20 video variants (9:16 + 4:5, 15s + 30s) - Creator team - 15 July. 8 static variants (1:1) - Design - 22 July. Refreshed audience targeting briefs - Growth - 5 July. Tracking setup in Triple Whale - Analytics - 30 June.
  • Timeline & milestones20 May: brief lock. 30 May: creator booking confirmed. 15 June: first cuts delivered. 20 June: GATE 1 - Head of Growth review. 30 June: revisions complete. 5 July: GATE 2 - legal/compliance review. 15 July: all video finals. 22 July: all statics complete. 30 July: launch in Meta.
  • Approval gates (RACI)GATE 1 (creative review): R=Creative Lead, A=Head of Growth, C=PM+Analytics, I=CMO. GATE 2 (legal/compliance): R=Legal Counsel, A=Head of Growth, C=Creative Lead, I=PM. GATE 3 (launch approval): R=PM, A=CMO, C=Head of Growth, I=Whole team.
  • Audience & angleAudience: endurance athletes 28-45 training 5+ hours/week, using LMNT or Liquid IV. Angle: 'Built for the second half of a long ride.' Hooks: problem-solution (primary), day-in-the-life (secondary). Do-nots: no price-led, no bottle-shot static, no founder-to-camera, no discount-lede.
  • Budget & resourcingTotal: $45K. Creator fees: $25K (5 creators × $5K). Production/editing: $12K. Paid media test budget: $5K. Tracking/tooling: $3K. Internal resourcing: Creative Lead 20hrs/wk, PM 10hrs/wk, Growth 8hrs/wk through project duration.
  • Risk registerCreator no-shows (med prob, mitigation: 1 backup creator booked). Legal hold on supplement claims (high prob, mitigation: pre-brief legal session). Q3 ad-platform pricing spike (med prob, mitigation: budget reserve 15%). Production overrun (med prob, mitigation: cuts delivered staggered, not bulk).

Shuttergen

Generate the brief; manage the project.

Shuttergen generates a project-ready creative brief - including audience, angle, deliverables checklist, and gate recommendations - that drops into your PM tool of choice.

Generate a brief freeLive brief builder →

Why a project brief differs from a pure creative brief

A creative brief answers 'what should we make?' A project brief answers 'what should we make, by when, with whom, against what budget?' The two overlap in the creative-direction layer (audience, angle, hook archetype, do-nots) but diverge sharply on project structure (deliverables register, RACI, gates, timeline, budget, risks).

The project brief is what ships work; the creative brief is what shapes work. A great creative brief without a project structure produces drift - decisions revisited weekly, scope creep, missed launch windows. A great project brief without creative depth produces bland output that ships on time but doesn't perform. You need both.

Use the project brief template when: (1) the project has >2 stakeholders, (2) the project has a hard launch date, (3) the budget is >$25K, (4) the team is split across functions (creative + engineering + paid media + legal), or (5) the project has approval gates that span more than 1 review cycle.

The deliverables register: the project's bill of materials

Every project ships a defined set of artifacts. The register lists them all - every video, every static, every landing page, every approval document - with owner and due date. If something isn't in the register, it won't ship. If something is in the register without an owner, it won't ship on time.

The register is the single document the PM tracks daily. Status updates, sprint reviews, and gate reviews all reference the register. A deliverable hitting 'late' status triggers a conversation; a deliverable hitting 'at risk' triggers a mitigation plan; a deliverable hitting 'shipped' moves to verification.

Common register failures. (1) Deliverables defined too vaguely ('paid media setup' versus 'Meta + TikTok campaigns live with 3 ad sets each, audiences segmented by funnel stage'). (2) Multiple owners per deliverable - one owner per line, always. (3) Due dates that aren't backwards-planned from the launch milestone - they should be.

Generate the brief; manage the project. Shuttergen generates a project-ready creative brief - including audience, angle, deliverables checklist, and gate recommendations - that drops into your PM tool of choice.

Generate a brief free

RACI and approval gates: where projects actually fail

Most creative projects don't fail on creative direction - they fail on approval bottlenecks. A brief without explicit gates produces a project where reviews happen ad hoc, approvers are unclear, and revisions cycle indefinitely. The fix is RACI per gate: who's Responsible (does the work), Accountable (owns the gate), Consulted (provides input), Informed (updated).

Two-gate minimum for any project >$25K: Gate 1 (rough cuts / first draft - catches direction errors early) and Gate 2 (finals / launch approval). Three gates for projects >$100K or with regulatory exposure - add a legal/compliance gate between Gate 1 and Gate 2.

The Accountable role is load-bearing. One person, not a committee. If 'the team' approves, no one approves. The Accountable is the single person whose 'yes' moves the project past the gate; everyone else (Consulted, Informed) contributes opinion but doesn't block.

Risk register: what to put in it and what not to

A risk register isn't a worry list - it's the top 3-5 named risks with probability and mitigation. More than 5 and the register becomes wallpaper; fewer than 3 means you haven't thought hard enough about what can derail the project.

Categories of risk to consider: vendor risk (creator no-show, agency delay), regulatory risk (legal/compliance hold), technical risk (tooling failure, ad-platform changes), resource risk (team member out, budget cut mid-project), and timeline risk (dependencies slipping, gate delays).

Mitigations should be specific. 'Creator no-show, mitigation: 1 backup creator pre-booked at 50% rate, contractable within 24 hours' beats 'have a backup plan'. The specificity of mitigations is what separates a useful risk register from a defensive document.

Working with the template across PM tools

The template above is tool-agnostic. The structure works as-is in Notion, Asana, Linear, Jira, Monday, or a Google Doc. Tool-specific notes: in Notion, the deliverables register works as a database with status columns; in Asana, each deliverable becomes a task with a milestone parent; in Linear, deliverables map to issues under a project label; in Jira, deliverables map to stories under an epic.

Whichever tool you use, the brief should be the canonical source. PM tools track state (status of each deliverable); the brief defines the *what* and *why*. When the two drift apart (common in long-running projects), the brief is the source of truth and the PM tool gets updated to match.

Internal links: for pure creative direction, see creative brief template. For sample filled-in briefs, see creative brief examples.

FAQ

Frequently asked

What's the difference between a creative brief and a creative project brief?
A creative brief shapes the work (audience, angle, hooks, do-nots). A creative project brief ships the work (deliverables register, timeline, RACI, gates, budget, risks). Use both - creative direction without project structure produces drift; project structure without creative direction produces bland output.
When should I use a project brief versus a regular creative brief?
Use the project brief when the project has >2 stakeholders, a hard launch date, budget >$25K, cross-functional teams, or approval gates spanning multiple review cycles. Regular creative briefs work for single-stakeholder, single-cycle creative tasks.
How many approval gates should a project have?
Minimum 2 for projects >$25K: rough cuts review (Gate 1) and finals/launch approval (Gate 2). Add a third gate for regulatory or compliance review on projects with legal exposure or >$100K spend.
What is RACI and why does it matter?
RACI defines per gate who is Responsible (does the work), Accountable (owns the gate), Consulted (provides input), Informed (updated). One Accountable per gate, not a committee - this is the role that makes the 'yes/no' decision. Most project bottlenecks come from missing or unclear Accountable assignments.
How detailed should the deliverables register be?
Every line is a single artifact with a single owner and single due date. 'Paid media setup' is too vague; 'Meta campaigns live with 3 ad sets segmented by funnel stage' is specific. If you can't write the line specifically enough that an external auditor would know whether it shipped, it's not specific enough.
Should every project have a risk register?
Yes, but keep it short - top 3-5 named risks with probability and mitigation. More than 5 and the register becomes wallpaper. The mitigations should be specific actions, not 'have a backup plan'.
Can I use this template in Notion, Asana, or Linear?
Yes - the structure is tool-agnostic. In Notion, the deliverables register becomes a database; in Asana, deliverables map to tasks; in Linear, to issues. The brief is the canonical source; PM tools track state.

Related

Keep reading

Resource

Creative brief template

Pure creative-direction brief.

Resource

Creative project brief

Sister keyword variant.

Resource

Creative brief process

The end-to-end brief workflow.

Resource

What makes a good creative brief

Quality properties.

Research

Creative Brief Builder

Shuttergen brief workflow research.

Generate the brief; manage the project.

Shuttergen generates a project-ready creative brief - including audience, angle, deliverables checklist, and gate recommendations - that drops into your PM tool of choice.

Generate a brief freeLive brief builder →