Blog
A Guide to Onboarding a StratCom Unit Onto Weekly Briefs
Why weekly briefs matter in StratCom
Weekly briefs give a Strategic Communications (StratCom) unit a predictable rhythm for capturing outcomes, surfacing risks, aligning messages, and supporting leadership decisions. Done well, they reduce last-minute scrambling, create a single source of truth across campaigns, and make it easier to demonstrate value without turning reporting into an administrative burden.
The goal in the first month is not perfection—it’s to establish a repeatable cadence, a shared definition of “reportable work,” and a format leadership will actually read.
Step 1: Set the intent and audience (Day 1–2)
Start by clarifying who the brief is for and what decisions it should enable.
Define the primary audience
- Senior leader or executive team (decision-focused, concise)
- Interdepartmental stakeholders (coordination-focused)
- Internal unit leadership (management-focused)
Agree what “good” looks like
- Reads in 3–5 minutes
- Answers: What happened? Why does it matter? What’s next?
- Highlights risks and opportunities early, not buried
- Tracks work against priorities rather than listing tasks
Choose one owner Assign a single Brief Owner (often a deputy head of unit or ops lead) responsible for collecting inputs, editing, and publishing on schedule.
Step 2: Define the weekly cadence and deadlines (Day 2–3)
A weekly brief fails most often due to unclear cutoffs. Make time boundaries explicit.
A common rhythm:
- Monday: Publish the brief (covers previous week)
- Thursday: Input request sent (with prompts)
- Friday 12:00: Inputs due
- Friday afternoon: Edit, consolidate, resolve gaps
- Monday morning: Final sign-off and distribution
If your week starts with a standing leadership meeting, align publication to land just before it.
Set rules for late inputs
- Anything after the cutoff goes into next week unless critical
- Critical updates can be added via a small “late-breaking” box
Step 3: Create a simple, standard template (Day 3–5)
Your template should be stable, predictable, and skimmable. Keep it consistent for at least a month so people learn it.
Recommended structure
-
Executive summary (6–10 lines)
- 2–3 key outcomes
- 1–2 key risks/issues
- 1 key priority for next week
-
This week’s highlights (by priority/campaign) For each item:
- What happened (outcome)
- Impact or audience response (what it means)
- Next step (what’s coming)
-
Risks, issues, and mitigations
- Risk/issue statement
- Status (new / ongoing / resolved)
- Mitigation and owner
- “Decision needed” if applicable
-
Upcoming (next 7–14 days)
- Key moments: announcements, milestones, planned engagements
- Dependencies: approvals, data, partner alignment
-
Metrics (lightweight) Include only what you can reliably track weekly. Use directional trends rather than perfect measurement:
- Reach/engagement snapshots (approximate if needed)
- Media coverage themes (qualitative)
- Stakeholder temperature checks (e.g., “increased enquiries from X”)
Formatting tips
- Use headings and bullets, avoid dense paragraphs
- Lead with verbs and outcomes (e.g., “Secured approval for…”, “Aligned messaging with…”)
- Cap each campaign/update to 4–6 bullets
Step 4: Decide what counts as a “reportable” update (Week 1)
Many teams default to activity logs. Shift the culture toward outcomes.
Use a simple hierarchy:
- Outcome: What changed as a result of the work (best)
- Output: What was delivered (good)
- Activity: Meetings held, drafts created (only if it unblocks something)
Examples of reportable phrasing
- Outcome: “Ministerial lines approved; enables Tuesday briefing.”
- Output: “Stakeholder Q&A pack drafted and sent for clearance.”
- Activity (only if necessary): “Met policy team to resolve data assumptions for comms.”
Rule of thumb If it doesn’t affect decisions, delivery, risk, or alignment, it probably doesn’t belong.
Step 5: Assign reporting roles and inputs (Week 1)
Make reporting predictable by assigning each section to a role, not a person (people change).
Typical ownership:
- Campaign leads: highlights + next steps
- Media lead: media themes + risks
- Digital lead: performance snapshot + upcoming content
- Stakeholder/partnership lead: engagement + sentiment
- Ops/clearance coordinator: approvals, dependencies, resourcing pinch points
Use consistent prompts for inputs Ask contributors to submit in the same format every week:
- Top 2 outcomes
- Top 2 priorities for next week
- Risks/issues + mitigation
- Decisions/clearances needed (who, by when)
Step 6: Run a “Week 1” pilot brief (Week 1)
In the first week, keep it lightweight and focus on building the habit.
Actions
- Draft the template and circulate it
- Collect inputs using the prompts above
- Publish the brief on the chosen day—even if imperfect
- Hold a 20-minute internal review: what was unclear, too long, or missing?
What to look for
- People reporting tasks instead of outcomes
- Repeated ambiguity (“working on…”, “ongoing…”)
- Missing owners or deadlines on risks
- Lack of “so what” in highlights
Step 7: Calibrate for leadership usefulness (Week 2)
Week 2 is where you tune for what decision-makers actually need.
Ask leadership (or their office) three questions
- What did you read first?
- What did you ignore?
- What would help you decide faster next week?
Then adjust:
- Shorten the executive summary
- Bring risks to the top if risk-heavy environment
- Group by priority outcomes rather than channels (avoid “digital section” if leadership thinks in policy initiatives)
Add a “Decisions & Approvals Needed” box A small box can transform the brief from passive reporting into an enabling tool:
- Item
- Needed from whom
- Deadline
- Consequence if delayed
Step 8: Improve data discipline without overburdening (Week 3)
By Week 3, tighten your metrics and definitions. Avoid building a measurement system you can’t sustain weekly.
Choose 3–5 stable indicators
- Top-line digital trend (up/down/flat)
- Key content performance notes (what worked, what didn’t)
- Media narrative shifts (themes, not counts)
- Stakeholder signal (enquiries, feedback, concerns)
- Delivery health (on track / at risk / off track)
Introduce a simple status tag For each priority:
- Green: on track
- Amber: at risk; mitigation underway
- Red: blocked; decision needed
This makes the brief instantly scannable.
Step 9: Lock the process and build resilience (Week 4)
Week 4 is about making the cadence durable through leave, crises, and shifting priorities.
Standard operating practices
- Maintain a shared “briefing log” throughout the week (not just Friday)
- Keep a running risk register aligned to the brief
- Create a back-up Brief Owner
- Store last four briefs as a quick institutional memory
Do a month-end retrospective (30–45 minutes) Discuss:
- What sections consistently add value?
- Where inputs are weak or late (and why)
- Which decisions were enabled by the brief
- What to stop reporting (low signal, high effort)
Then lock the template for the next month with only minor tweaks.
Common pitfalls—and how to avoid them
Pitfall: The brief becomes a list of everything
- Fix: Enforce a limit (e.g., top 3 priorities, top 5 highlights)
Pitfall: Reporting is done “at” the end of the week
- Fix: Keep a living log; require contributors to update as work happens
Pitfall: No ownership of risks
- Fix: Every risk line must include an owner and mitigation
Pitfall: Leadership stops reading
- Fix: Shorten, sharpen the executive summary, and surface decisions needed
Pitfall: Contributors don’t know what to write
- Fix: Use prompts, provide examples, and edit firmly for outcomes
A practical first-month checklist
- Week 1: Publish a pilot using a simple template; establish deadlines
- Week 2: Tune content for leadership decisions; add approvals/decisions box
- Week 3: Stabilize metrics and status tagging; improve consistency of inputs
- Week 4: Formalize roles, back-ups, and living logs; run a retrospective
Weekly briefs work when they are predictable, brief, and decision-oriented. By the end of the first month, your StratCom unit should have a cadence that captures what matters, flags risks early, and makes it easier for leadership to act—without turning communications work into endless reporting.