Campaign Recap Templates: How to Document What You Just Shipped

Editor's note: This is the bookend to the creative-brief-template article. The brief opens the work; the recap closes it. The two documents should mirror each other, field for field.

A campaign teaches a creative team more in its final week than in its first month — which concept overdelivered, which asset got reused everywhere, which round of revisions was the one that actually moved the work. Then the team rolls onto the next brief and most of that hard-won knowledge goes undocumented, waiting to be rediscovered the expensive way the next time a similar campaign comes around. The recap is the document nobody writes until the quarter they wish they had, when leadership asks why the new campaign is repeating a mistake the last one already paid for.

Treat the recap as the cheapest insurance against repeating expensive mistakes. It’s the bookend to the brief template — the brief sets a campaign up and the recap closes it out, and a team that writes one but skips the other only ever learns half the lesson.

Why Most Teams Skip the Recap#

Recaps don’t get skipped on purpose. A campaign wraps with the team already exhausted and the next brief in the queue, so whoever was going to write it pushes the job to next week, then to the retro that gets canceled, then to the post-mortem doc nobody opens once the project is closed in the project tool. By the time someone asks for the recap six months later, the people who could have written it have moved on, the analytics tabs have rolled over, and the institutional memory is in DMs and screenshots.

The reason teams skip the recap is that the recap people imagine doing is the four-hour version: tab through every analytics dimension, write a five-page narrative, hold a 90-minute retro, distribute three different summaries to three different stakeholders. That recap deserves to be skipped. The version this article describes is a 30-minute exercise that produces a three-paragraph document, a numbers table, and three bullet lists. It’s short enough that the team writing it agrees to do it. It’s structured enough that the team reading it six months later gets value.

The cultural fix matters as much as the template. The recap has to land while the team still remembers what happened: the day the campaign closes or the first working day after. Push it past two weeks and most of the texture is gone. Past four, the recap becomes a chore — and chores produce documents nobody reads.

The Recap Field List (with Full / Repeat / Edit Sizes)#

The recap mirrors the brief, field for field. Every promise in the brief gets a result in the recap; every plan gets a delivered outcome. Three sizes, fitting three campaign types.

Full recap. Every field. Used after the campaign that owned a quarter or marked a meaningful shift (a brand refresh, a major product launch, an OOH activation). Two pages of structured fields plus a numbers table; written within a week of close.

Repeat recap. The campaign is in a known series — the third holiday push, the second product-launch wave. Most fields inherit from the prior recap; capture only the deltas (what changed this time, what surprised us, what the numbers did relative to the prior cohort). One page; written within three days.

Edit recap. A small variant of an existing campaign or a routine cadence post (the weekly newsletter, the monthly social calendar). Three bullets: what shipped, what worked, what to change. Written the day the cadence closes; lives as a comment on the project record, not as a separate document.

Each recap field has a brief counterpart. The brief said “objective: drive 5,000 demo signups in EMEA”; the recap says “objective met: 6,200 EMEA demo signups.” The brief said “mandatories: lead with discounted pricing in the hero”; the recap says “mandatory delivered, contributed measurably to conversion.” The mirror is the point: anyone reading both documents can see exactly which promises landed and which slipped.

Here is a Full recap, filled in — copy it, delete the lines that don’t apply, and the structure is done. It is the closing bookend to the brief template’s worked example: the same campaign, six weeks later.

CAMPAIGN RECAP — Full
Spring 2026 Demo Push — Hero Banner Set
Owner: Jordan Park, Creative Director
Campaign closed: 2026-06-30 · Recap written: 2026-07-01

OBJECTIVE vs RESULT
Creative brief: ship a hero set that carries the Spring demo push and replaces the 2025 evergreen.
Delivered: full scope on plan. Concept B (product-in-use hero) emerged as the winning direction and is now the 2026 evergreen.

AUDIENCE REACHED
Planned: marketing-ops managers at 50–500-person companies.
Delivered: 1.2M impressions, ~68% in-target — the creative direction tested correctly with the segment.

CHANNEL MIX vs PLAN
Built for paid social (6 sizes), email (3 creatives), partner placements (2 sizes), and 1 landing page.
Added mid-flight: 2 story-format cuts after Round 2 picked the winning concept.

DELIVERABLES SHIPPED vs SCOPED
Scoped: hero set (6 sizes), 3 email creatives, 1 landing page.
Shipped: all on plan, plus the 2 story cuts.

CREATIVE THAT PERFORMED
Concept B (product-in-use hero) beat Concept A (studio-shot hero) by 31% on click-through.
Warm, founder-led tone outperformed the product-feature-led tone on email.
"Set up in minutes" angle outperformed the discount-led angle on paid social.

ASSETS TO REUSE / RETIRE
Reuse: product-in-use hero (now the evergreen), the 15-second story cut, the founder-led tone-of-voice for copy.
Retire: studio-shot variants, the discount-led headline set, the 90-second gated demo video.

TIMELINE vs PLAN
Hero set and email creatives: on plan.
Landing page: 2 days late — blocked on a Round 3 copy revision Maya didn't expect to need.

BUDGET vs SPEND
Production budget £40k · Spend £38.6k · under by £1.4k.
The 2 added story cuts came in at £600 vs the £1,000 quoted; the unspent capacity funded a second photography session that landed the winning hero.

KPIs HIT / MISSED
Creative-process: 2 concept rounds (hit), 1 hero review round (hit), 3 landing-page rounds (miss — scoped 2).
Downstream marketing (per marketing's read): signups 247 vs 200 (hit); CTR 1.4% → 2.1% vs 2.0% goal (hit); brand-lift study cut for time.

WHAT SURPRISED US
The simpler product-in-use shot beat the staged hero on mobile.
Story-format cuts outperformed the hero set on platform-native sizing — we'd treated them as a B-tier add.

WHAT WE'D DO AGAIN
Lead concept exploration with the product-in-use direction before booking the photoshoot.
Hold 20% of production budget back to fund a second shoot once Round 1 picks the winning concept.

WHAT WE'D NEVER DO AGAIN
Gate the demo behind a 90-second hero video — completion dropped to 14%; the format was wrong for the funnel position.

Repeat and Edit recaps are the same structure, trimmed: inherit the campaign-level fields from the prior recap and capture only the deltas.

Numbers and Stories: Both Belong#

A recap has two halves — the numbers (audit trail) and the stories (learning) — that serve different readers. Either one alone reads as something else: a finance close-out without the lessons, or a post-mortem without the receipts.

The audit-trail half answers “did we do what we said we’d do?” Delivered vs scoped, on-time vs plan, on-budget vs estimate, KPI hit-rate. These are facts; they don’t require interpretation. They protect the team next quarter when leadership asks why the new campaign is over budget: the audit trail shows whether the new campaign is worse or whether the comparison baseline was inflated.

The learning half answers “what would we do differently next time?” Three lists are enough: what surprised us (the unexpected wins and losses), what we’d do again (the moves that worked and we didn’t expect to), what we’d never do again (the moves that failed and we’d like to spare the next team from). The lists are short on purpose. Four items read as the four things to remember; push past ten and the reader has to work out what mattered on their own.

The two halves earn different reads. The numbers half gets read by leadership reviewing campaign performance and by finance closing the books on the spend. The learning half gets read by the next team starting a similar campaign and by the head of creative spotting patterns across campaigns. The recap document is one artifact, but it serves two audiences with different attention budgets.

The Performance Metrics Worth Capturing#

What goes in the numbers half of the recap. Keep the list short: capture what the team agreed the campaign was for, not every analytics dimension that exists. The dashboards stay in the analytics tool; the recap captures the line items the team will be asked about next quarter.

• Reach and audience. Impressions, audience size delivered to, reach across channels, segmentation breakdown. Whatever the brief said the audience was, the recap quantifies what was actually reached.
• Engagement. Clicks, click-through rate, time on page, organic vs paid split where relevant. Engagement is the leading indicator of conversion; the numbers explain why conversion landed where it did.
• Conversion. Conversion rate, demo signups, downloads, subscriptions, completed actions matching the campaign objective. The single most important section. If the brief had a primary KPI, this is where it gets a number.
• Spend. Total spend, spend by channel (paid ads, paid advertising on social platforms, email campaigns, partner placements), cost per result. Finance reads this section; producing it accurately is the audit-trail half of the recap.
• Return. Return on ad spend (ROAS)(opens in new tab), return on investment, attributed revenue, business outcomes vs campaign goals. Where attribution is messy, name the attribution model(opens in new tab) used (last-click, multi-touch, MMM) and the confidence the team places in it. Honesty about attribution beats false precision.
• Channel performance. Performance across channels with a flag for where it over-performed plan and where it under-performed. The deltas from plan are more interesting than the absolute numbers; that’s where the next campaign learns.

How to measure each one is your analytics tooling’s problem, not the recap’s. Marketing-analytics setup is its own discipline; this article doesn’t cover Power BI(opens in new tab) dashboards, GA4 funnels(opens in new tab), or Looker Studio(opens in new tab) reports. The recap captures the agreed numbers; the underlying instrumentation is upstream.

What the Creative Team Captures#

The performance numbers tell you the campaign worked; they don’t tell you which of the work made it work. For a creative team that’s the half of the recap with the most reuse value — and the half a media report leaves out.

• The creative that performed. Which concept, hero, or cut carried the result — and the one number that proves it. “The product-in-use hero beat the studio shot on click-through” is worth more to the next campaign than the blended channel average.
• What to reuse, what to retire. Which assets earned a second life — the evergreen cut, the template, the photography that keeps getting pulled — and which were one-offs. Flag it on the asset itself so the next team finds the winner, not the whole shoot.
• Where the process bottlenecked. Revision rounds versus plan, where approval stalled, what the real turnaround was. Three rounds of feedback that should have been one is a process lesson the next brief can design out.

This is where the recap and the asset library belong together. When the written recap lives in the DAM alongside the campaign’s assets — not in a doc tool the next team won’t think to open — the lesson and the work that taught it stay in one place. The next person picking up a similar brief finds the recap next to the folder, sees which assets won, and reuses them instead of rebuilding from scratch.

Who Reads the Recap (and How to Make Them)#

An unopened recap has the same outcome as one that was never written. The fix is multi-format distribution: the same content shaped for three different audiences, each at the length and format that audience will actually read.

• The 30-minute team retro. A working meeting where the stories get told out loud. Walk through the audit-trail numbers in five minutes; spend the rest on the three lists (surprised us, do again, never again). The retro produces verbal context that the written recap can’t fully capture; it also pressure-tests the recap before it goes to leadership.
• The 5-bullet exec summary. Sent to leadership the day after the retro. Five bullets: what we set out to do, what we delivered, the one number that mattered most, the one thing that surprised us, the one change for next time. Short, blunt, action-oriented. The exec who reads it should be able to ask one good question after; that’s the metric for whether the summary worked.
• The written recap on the project record. The persistent artifact. Lives in the project record in the DAM or the project-management tool, attached to the campaign assets. The next team picking up a similar brief reads this version first. Same for a new hire during onboarding. Make it findable: tag it with the campaign type, link it from the asset folder, mention it in the next brief.
• Optional public post-mortem. Rare; reserved for genuinely interesting work. A blog post about a campaign that did something novel, with the numbers it’s safe to share. Useful for recruiting, brand, and the team’s sense of ownership.

The Creative Operations Manager owns recap distribution. Making sure the doc gets read is part of running the system. Writing a recap nobody reads doesn’t count — the work of the role is in the distribution: the right person reading the relevant section, the next brief actually citing it.

Feeding the Recap Into the Next Brief#

The recap closes one campaign; it also opens the next one. The “what we’d do again / never do again” lists become inputs to the next brief’s mandatories and out-of-scope sections. The recap is the upstream of next quarter’s brief, and the loop closes itself if the documents are linked.

In the brief template, the “Mandatories” section explicitly carries forward learnings from the most recent recap on the same channel or campaign type. Name the linkage in the brief itself: “Mandatory: lead with discounted price in the hero (per Q3 holiday recap, 12% lift over premium-led creative).” The recap’s lessons become the brief’s constraints, not folklore in someone’s head. Three months later, when the team that wrote the recap has rotated, the next team inherits the lesson because it’s in the brief, not in the institutional memory.

The same pattern works in reverse. The “never again” list goes into the brief’s out-of-scope section: “Out of scope: gated demo videos longer than 90 seconds (per Q2 launch recap, completion rate dropped to 14%).” The brief is where constraints live; the recap is where they come from. Documents that cite each other build a compounding record — lessons survive team rotations and land in the next brief. Without that link, every quarter pays the tax of relearning what the last one already paid for.

The test is whether the next brief cites the last recap. If a campaign brief pulls three things from a recap that’s six months old, the recap earned its 30 minutes. If briefs ignore prior recaps and the team keeps making the same mistakes, the loop is broken somewhere: either the recap didn’t capture the lesson clearly, or the brief template doesn’t have a place to carry it forward, or the role that owns both documents isn’t doing the connection work.

The decision the reader has to make is small and concrete. Pick the next campaign on the calendar. Block the recap slot now, the day it closes, not the week after. Assign it to a name, not to “the team.” Choose Full, Repeat, or Edit based on the campaign’s scope, and write the version that fits. Then link the recap into the next brief on the same channel.

The brief template is one end of the loop; the recap is the other. Run both and the institutional memory stops living in DMs.

Viacheslav Shuranov

Co-Founder at YetOnePro

Entrepreneur and software engineer with 20+ years building products that matter. From payment systems to telemedicine to media encoding, Viacheslav has led technical teams as CTO and Tech Lead across multiple startups. He co-founded YetOnePro to solve the creative workflow problems he encountered firsthand.

Contact author

If you want to leave feedback, suggest an addition, or report something outdated — reach out.

Related Articles

Guide20 min read

Creative Brief Template: What to Include So Nobody Asks Twice

Guide10 min read

The Creative Operations Manager: Role, Responsibilities, and Day-in-the-Life

Guide15 min read

Design Approval Process: Stop Revisions from Killing Deadlines