Weekly Comms Lead Briefing
A Monday-morning routine that turns last week's notes, inbox and tracker into a one-page briefing: what moved, where you are the blocker, what is coming, and the four or five things that deserve the week.
Keep in mind The briefing only knows what you paste: check the blocker list against your inbox, and strip anything confidential before it goes into a tool your AI policy does not allow.
Version 1.1 · Updated 30 October 2026
What you'll get
The opening of a worked example. Anonymised and shortened; yours will follow your inputs.
Fictional example. An invented in-house comms lead; all details are illustrative.
Week of: 21 September 2026
Priorities this quarter: (1) Launch the new website; (2) Cut approval time on releases; (3) Build the spokesperson bench.
1. What moved last week
| Item | Progress | Against priority | Note |
|---|---|---|---|
| Website copy, six of nine pages | Advanced | 1 | Product pages still with product team |
| Approval workflow redesign | Done | 2 | Signed off Thursday; first release under it this week |
| Media training, cohort two | Slipped | 3 | Trainer unavailable; rebooked 6 October |
2. Where I am the blocker
| Waiting on me | Since | Who | What they need | Do by |
|---|---|---|---|---|
| Sign-off on the homepage headline | 12 Sep | Web lead | A yes, or the change | 21 Sep |
| Reply on the conference speaking slot | 10 Sep | Events agency | Accept or decline | 22 Sep |
| Budget line for the photography | 15 Sep | Finance | The code | 21 Sep |
Next step
The prompt ends with questions for you. Answer them with this, in the same chat.
Here are my answers to your questions: [YOUR ANSWERS] Revise the draft using them. Remove the [Assumed] and [Confirm] marks my answers resolve, keep the rest, and update the questions and checks.
Human review checklist
Go deeper
Variations
Team version
Use this when the briefing is for the whole team rather than just you.
This briefing is for my team: [WHO IS IN THE TEAM, BY ROLE]. Instead of "Where I am the blocker", write "Decisions needed, and from whom". Add one line per person on their main item this week, taken only from the inputs. End with three questions we should settle in a 15-minute Monday call. Leave out anything I would not say to the whole team.Feeding the quarterly review
Use this when you have several weeks of briefings and the quarterly review is coming up.
Here are my weekly briefings for this quarter so far: [PASTE THEM, WITH THEIR DATES]. Instead of a weekly briefing, write a summary of the quarter of no more than two pages: a table with the columns Priority | What moved | What slipped | Weeks of effort it got; then work that served no priority; items carried more than three weeks; and blockers that recurred. Use only what the briefings record, and say where weeks are missing.Full example output
Example output
Anonymised and shortened. Real outputs will vary based on your inputs.
Fictional example. An invented in-house comms lead; all details are illustrative.
Week of: 21 September 2026 Priorities this quarter: (1) Launch the new website; (2) Cut approval time on releases; (3) Build the spokesperson bench.
1. What moved last week
| Item | Progress | Against priority | Note |
|---|---|---|---|
| Website copy, six of nine pages | Advanced | 1 | Product pages still with product team |
| Approval workflow redesign | Done | 2 | Signed off Thursday; first release under it this week |
| Media training, cohort two | Slipped | 3 | Trainer unavailable; rebooked 6 October |
| Stakeholder newsletter | Done | none | Recurring; consider delegating |
2. Where I am the blocker
| Waiting on me | Since | Who | What they need | Do by |
|---|---|---|---|---|
| Sign-off on the homepage headline | 12 Sep | Web lead | A yes, or the change | 21 Sep |
| Reply on the conference speaking slot | 10 Sep | Events agency | Accept or decline | 22 Sep |
| Budget line for the photography | 15 Sep | Finance | The code | 21 Sep |
5. This week’s priorities
- Clear the three blockers on Monday morning; all are under fifteen minutes.
- Get the three product pages back by 23 Sep so the site stays on track (priority 1).
- Run the first release through the new workflow and time it (priority 2).
- Confirm the cohort-two trainer and send the invitations (priority 3).
- Hand the stakeholder newsletter to Sam with the template.
6. Carried over: Spokesperson bios, carried two weeks. Scheduled 24 Sep, 45 minutes, or it moves to the parked list.
The template
Briefing header
Week of: [Date] Prepared: [Date and time] Priorities this quarter: [Three to five, one line each]
1. What moved last week
| Item | Progress | Against priority | Note |
|---|---|---|---|
| [Project or task] | [Done / Advanced / Slipped] | [Which priority, or none] | [One line] |
2. Where I am the blocker
| Waiting on me | Since | Who is waiting | What they need | Do by |
|---|---|---|---|---|
| [Decision, approval, reply, input] | [Date] | [Name] | [The specific thing] | [Date] |
3. Coming this week
| Date | What | Prep needed | Owner |
|---|---|---|---|
| [Date, e.g. 21 Sep 2026] | |||
4. Outside signals worth knowing
[Two to four lines: sector, competitor, media or policy items that bear on this week’s work. Pull from the Weekly Monitoring Brief if you run one.]
5. This week’s priorities
Sort candidate tasks by whether they are important (move a quarterly priority or protect the organisation) and urgent (dated this week):
| Urgent | Not urgent | |
|---|---|---|
| Important | Do first: [items] | Schedule: [items] |
| Not important | Delegate or shrink: [items] | Drop or park: [items] |
The four or five things that get the week: 1. 2. 3. 4. 5.
6. Carried over
[Anything from last week’s list that did not happen and why. If it has been carried three weeks, decide whether it is a priority or not.]
When to use it
What it is
A weekly briefing is a short, structured summary a comms lead produces for themselves, or has produced for them, at the start of each week. It gathers what happened last week, what is scheduled this week, what is waiting on a decision, and what the quarterly priorities say should matter, and turns them into a page: progress, blockers, upcoming, and a short prioritised list. The point is to begin the week from a synthesis rather than from whichever email arrived last.
The routine is the template; AI does the assembly. Once your notes, calendar and tracker are in a form you can paste or connect, the briefing is quick to produce and gets better each week because the previous briefing is one of the inputs. Over a quarter you also have a dated record of what the function did, which the quarterly review otherwise has to reconstruct.
When to use it
Use this template when:
- You lead a small comms team, or are the comms team, and the week starts in the inbox
- Decisions are waiting on you and you find out on Thursday
- A Monday team meeting has become a status round that could be a page
- You want a record of the quarter as it happens
- You are trying a first automated routine and want one that pays back quickly
Don’t use this template if:
- Your organisation already runs a weekly operating rhythm that produces this
- You need a monitoring brief on the outside world; that is the Weekly Monitoring Brief, and it can feed this one
- The week is too unstructured to plan (a live crisis); use the crisis playbook and come back after
Inputs needed
Before starting, gather:
- Last week’s notes: meeting summaries, a task list with completions, sent emails, the previous briefing
- This week’s calendar, including deadlines and anything external
- The team tracker, project list or content calendar, in any exportable form
- The quarter’s priorities, written down, so the briefing can score the week against them
- A note of anything you already know is stuck
Tips for success
Make the blocker section honest.
Its only purpose is to show you what is waiting on you. If it is empty two weeks running, the inputs are missing something.
Feed it last week’s briefing.
The carried-over section only works if the previous briefing is an input. Save each one in the same place.
Cap the priorities at five.
A list of twelve is the inbox in a new format.
Let the inputs be messy.
Raw meeting notes and an exported task list are enough. Cleaning them first is the step that can kill the routine.
Automate the assembly and keep the judgement.
Once the inputs live somewhere a tool can read, schedule the assembly. Keep the fifteen-minute read and the priority calls for yourself.
Common pitfalls
Producing it and not reading it.
The briefing is a prompt for decisions. If Monday’s blockers are still there on Friday, the routine is decorative.
Treating every task as important.
Important means it moves a quarterly priority or protects the organisation. Many tasks are neither, and the sort is only useful if you let them fall into the other boxes.
Skipping the outside signals.
A week planned without reference to what is happening in the sector can get rewritten on Tuesday.
Letting carried-over items ride.
Three weeks is the limit. At that point it is either scheduled or parked, and the briefing should say which.
Pasting confidential material into a consumer tool.
Meeting notes contain names, figures and unannounced decisions. Use the tool your AI Use Policy allows for internal material, and strip what should not travel.
Related templates
Monthly Stakeholder Update
Executive reporting format that translates monitoring data and communications activity into Board or senior stakeholder briefing, balancing transparency with strategic narrative.
Weekly Monitoring Brief
Systematic approach to tracking media mentions and social conversation to identify emerging trends, sentiment shifts, and response opportunities.
Quarterly Comms Planning Grid
Create a 90-day communications calendar with activities, owners, and dependencies to align teams and ensure consistent execution.
Comms Workflow Audit
A structured framework for mapping existing communications workflows, identifying inefficiencies and bottlenecks, and pinpointing where AI can add the most value, before buying tools or redesigning processes.