Every engagement I run sends the same one-page Monday morning report. Six numbers, two short narrative blocks, an explicit decision ask. It fits on a single screen, takes 15 minutes to write, and roughly 80% of my clients end up forwarding it (or copying its structure) to their board, CEO, or broader leadership team.
Not because it’s a clever format. Because it answers the four questions every non-outbound person wants answered about outbound, and it stops them from asking the 30 questions they don’t actually need answered.
Here’s the structure, why each piece is there, and the mistakes I see in 90% of outbound reports I audit.
The four questions a good report answers
Before showing the template, it helps to name what a report is actually for. Every stakeholder outside the outbound function is asking a variant of:
- Is it working? — versus plan, versus last week, versus acceptable range.
- If not, what are we doing about it? — concrete decisions, not vibes.
- What do you need from me? — budget, access, decisions, introductions.
- Should I be worried? — yes/no, and if yes, why specifically.
If your weekly report doesn’t answer all four in the first 60 seconds of reading, you’re going to spend the rest of the week on Slack clarifying. The template below forces the answers into the first half of the page.
The template
OUTBOUND WEEKLY — WEEK OF [DATE]
ENGAGEMENT: [client-facing codename]
SENT BY: [your name]
---
THE LINE:
[One sentence on the state of outbound this week.
Not a metric. A judgment.]
---
THE NUMBERS:
Sends this week: [n] (target: [n], last week: [n])
Unique reached: [n] (domain hygiene OK / flag)
Positive reply rate: [%] (target: [%], last week: [%])
Positive replies: [n] (of which: [n] new, [n] nurture)
Meetings booked: [n] (target: [n], last week: [n])
Opportunities created: [n] (of which: [$] in qualified pipeline)
---
WHAT HAPPENED:
[3–6 sentences. What we did, what worked, what didn't.
Concrete. No abstractions.]
---
WHAT'S NEXT:
[3–6 bullet points. Specific actions, specific owners, specific dates.]
---
DECISIONS I NEED FROM YOU:
[0–3 items. Name the decision, name the stake.
If none, say "None this week."]
---
RISK:
[Binary: green / amber / red.
One sentence explaining why, if amber or red.]
That’s it. One page when printed. Under 350 words.
Why each piece is there
“The Line”
A one-sentence human judgment of the week. Not “This week we sent 4,200 emails and booked 7 meetings” — that’s in the numbers. Something like: “This week confirmed we’ve hit the deliverability fix; reply rate is back to target for the first time since the outage, but we’re two weeks behind on meeting volume and that gap needs a plan.”
This sentence is the single most valuable piece of the whole report. It’s what the CEO reads. If you can’t write a sharp one-line judgment, you don’t understand the week well enough to send the report yet.
The Numbers
Six specific metrics, always in the same order, always with three columns: this week, target, comparison to last week.
Sends: the volume number. Keep it visible so anyone reading can calibrate everything else against input scale.
Unique reached: sends minus duplicates minus bounced. Catches the “we sent 5,000 but 1,200 bounced” problem that inflates other ratios.
Positive reply rate: the percentage of sends that got a genuinely positive reply — interested, want to learn more, asking qualifying questions. NOT total replies (which includes unsubscribes, rejections, and auto-replies). Every operator I audit conflates these and it destroys the usefulness of the metric.
Positive replies (absolute): because a 2% positive reply rate on 10,000 sends is a different operational situation than 2% on 500. Both go in the row.
Meetings booked: always the primary lagging indicator. Not “meetings held” — meetings booked, because “held” lags by another 1–2 weeks and you want this week’s report to be about this week’s work.
Opportunities created: the furthest-downstream number you can measure weekly. Opportunity volume plus $ in qualified pipeline, because the mix matters — 5 small opps are a different situation than 1 huge one.
“What Happened”
3–6 sentences of plain-language narrative. This is where operators overcomplicate. The rule I hold myself to:
- Name one thing that worked, with a specific example.
- Name one thing that didn’t, with a specific example.
- Name one surprise, if there was one.
Avoid: jargon, hedging, past-tense vibing. “We iterated on the messaging” tells the reader nothing. “We swapped the opener from a hiring-signal reference to a product-launch reference on the fintech segment — positive reply rate went from 1.4% to 3.1% over 1,100 sends” tells them something.
“What’s Next”
3–6 bullets. Each must have: an action, an owner, a date. “Launch the V3 sequence on Monday” is a headline, not a task. “Ship V3 sequence to 600 ICP-match rows in the financial services tier — owner: Syed — ship date: Monday 2026-04-28” is a task.
Stakeholders will fight you on this level of specificity for a week, then start copying it, then stop doing any other reporting this way because they realise how much ambiguity everyone was swimming in before.
“Decisions I Need From You”
Most weeks this is “None this week.” Some weeks it’s “Decide by Thursday: do we expand into the EU geo now or wait until after the new hire lands in June.” Name the decision, name the deadline, name the stake.
The moment you stop asking for decisions, stakeholders assume you don’t have any. Then they start inventing them for you.
“Risk”
Green / amber / red. This is the TL;DR for anyone who only reads one line.
- Green — everything is inside tolerance. Report is informational.
- Amber — something’s off. Here’s what, here’s what I’m doing about it, I don’t need you yet.
- Red — something’s broken and I need help or a decision.
Most weeks should be green. If you’re sending amber every week for a month, you’re not calling risk — you’re just confused about what’s normal.
The five mistakes in 90% of outbound reports
Mistake 1 — Too many metrics
I see reports with 18 metrics. Open rate, click rate, forward rate, demographic splits, time-of-send analysis. None of it helps the reader decide anything. If a metric wouldn’t change what you do next week, it’s not a KPI — it’s a curiosity, and it belongs in an appendix nobody reads.
Mistake 2 — No comparison columns
“Sends: 4,200.” Great. Is that good? Bad? Up or down? Without a target and a prior-week number, the reader can’t calibrate. And if the reader can’t calibrate, the whole report is decorative.
Mistake 3 — Confusing reply rates
Top three variants I see conflated:
- Total reply rate (anyone replying anything, including unsubscribes)
- Positive reply rate (genuine interest)
- Qualified reply rate (positive + ICP-match + budget-signals)
They are three completely different numbers. Pick one, report it consistently, label it clearly. Don’t switch between them across weeks. Readers can’t tell, but their mental model of “what’s good” gets corrupted week by week.
Mistake 4 — Narrative without numbers, or numbers without narrative
The report needs both. Numbers without narrative don’t tell you why. Narrative without numbers is a feelings report. Every operator pulls toward one side — narrative people skip the numbers, data people skip the narrative. Force yourself to do both every week.
Mistake 5 — Making the report about the operator, not the work
Bad: “This week I launched three new campaigns and iterated aggressively on messaging.”
Better: “Three new campaigns launched this week — fintech, healthtech, edtech. Fintech converted at 2.8% (above target), healthtech at 0.9% (below), edtech at 1.6% (in range). Copy iteration shipped on Wednesday moved the healthtech number to 1.4% across the 400 sends after the change.”
The first version is performance. The second is information. Readers can feel the difference, even if they can’t articulate it.
The 15-minute ritual
Every Monday 9am–9:15am I write this report. Before meetings, before Slack, before anything. The process:
- Minutes 0–3: pull numbers from the sequencer, CRM, and pipeline tool. (These should be dashboards you can read in < 90 seconds each, not reports you build from raw data every week. If they’re not — fix that first.)
- Minutes 3–6: write “The Line” and the narrative sections. Often this is the hardest part. If you’re struggling, it means you don’t fully understand the week, which is also useful information.
- Minutes 6–9: write “What’s Next” and “Decisions.” Go specific.
- Minutes 9–12: set Risk. Be honest. Amber is not a failure; it’s communication.
- Minutes 12–15: re-read, cut anything that doesn’t add information, send.
The discipline of doing it the same way every week is what makes it useful. Formatting drift kills reports faster than anything else.
Why clients forward it
The reason 4 out of 5 of my clients use this report structure for their own internal updates is simple: everyone above them in the org is asking the same four questions about every function, not just outbound. Finance gets it about the budget. Marketing gets it about the funnel. Product gets it about the roadmap. A weekly report that answers “is it working / what’s next / what do you need / should I worry” in under 350 words is a format that translates.
Most clients don’t ask permission before reusing it. They shouldn’t need to. If a format is useful it’s supposed to spread.
The final check before you hit send
Read your own report as if you were the CEO. Three questions:
- Do I know whether outbound is working this week or not?
- Do I know what the operator will do next, specifically?
- Is there a decision I need to make, or can I get on with my day?
If yes-yes-yes or yes-yes-no, send it.
If any answer is unclear — rewrite. Sending an unclear report is worse than sending nothing.