How to Write Client Reporting Emails for Your Agency: Results, Bad News & Monthly Updates

Every agency account manager eventually has to write the same email twice: the one where the numbers are great and the one where they're not. Learning how to write client reporting emails for your agency is less about formatting a monthly PDF and more about mastering that second version, because the first one writes itself. Clients don't fire agencies over a single soft month. They fire agencies over how that soft month gets communicated — or doesn't. A reporting email is the one recurring piece of writing that either builds the case for renewal every single month or quietly erodes it, one vague update at a time.

This guide covers the whole cycle: what a monthly report email needs to include, how to structure it so a busy client actually reads it, a full example for routine results, and — the part almost nobody writes well — exactly how to tell a client their campaign underperformed without triggering a churn conversation. You'll get templates for both directions, a framework for delivering bad news, and the tone rules that keep a reporting email from reading like either a sales pitch or an apology.

None of this requires a new reporting tool, a new dashboard, or a different cadence than whatever you already use. It's a writing problem, not a data problem — most agencies already have the numbers; what's missing is a repeatable way to turn those numbers into an email a busy client actually reads, trusts, and replies to, on the months that go well and, more importantly, on the ones that don't.

Why do client reporting emails matter more than the report itself?#

Most agencies over-invest in the report and under-invest in the email that delivers it. The dashboard, the PDF, the slide deck — these are proof. The email is the interpretation, and clients act on the interpretation, not the raw numbers. A client who receives a beautifully designed report with no narrative attached has to do the work of deciding what it means themselves, and when they're left to draw their own conclusions about a flat month, they tend to draw the worst one.

The reporting email is also the most frequent, most predictable touchpoint you have with a client outside of active problem-solving. A kickoff call happens once. A renewal conversation happens once a year. But a monthly (or weekly) report email happens on a schedule the client can set their watch to, which makes it the single biggest lever you have for shaping how a client perceives the relationship over time. Twelve strong reporting emails a year do more for retention than one great quarterly business review, because they compound: each one either reinforces that you're on top of the account or reinforces that you're going through the motions.

That's also why this is a genuinely underserved topic. Search for agency client emails and you'll find plenty of onboarding sequences and template packs, but almost nothing written from the agency's side about the two hardest reporting scenarios: explaining a routine result well enough that it reads as proactive rather than perfunctory, and explaining a bad one without sounding defensive. Those are the two skills this guide is built around.

Before the templates, it helps to separate two documents that get conflated constantly: the report and the report email. The report is the evidence — dashboards, charts, a PDF export, whatever your reporting tool produces. The email is the argument built on top of that evidence: here's what changed, here's why, here's what it means for your goals, here's what we're doing about it. A client who only ever receives the report, with a one-line "here's this month's numbers, let me know if you have questions," is being handed data without an opinion. Your opinion — reasoned, specific, and slightly ahead of their own worry — is the actual product of a reporting email.

What should every agency monthly report email include?#

A reporting email that consistently lands well has the same five components whether the month was great, fine, or rough. Skipping any of these is usually where things go wrong — most bad reporting emails are missing the context or the next-step, not the numbers.

• A one-line headline result up top — the single number or outcome the client cares most about, stated plainly before anything else.
• The context that explains the number — seasonality, a platform change, a client-side delay, a competitive shift, or simply steady, expected performance.
• Progress against the client's actual goal, not just raw metrics — leads booked against a target, not just "clicks were up 12%."
• What you're doing next — one or two concrete actions for the coming period, tied directly to the result just reported.
• An easy, specific way to engage — a single question, a proposed call time, or an invite to reply, not a generic "let us know if you have questions."

Does reporting differ between a retainer client and a project-based client?#

Yes, and treating them the same is a common source of friction. A retainer client is buying an ongoing relationship, and their reporting email should read like a running narrative — this month builds on last month, and the recovery plan you mentioned three weeks ago should visibly connect to this month's result. Retainer clients are also the ones most sensitive to a report that feels like it's starting fresh every time, because it signals the account isn't actually being watched between reports, only assembled at reporting time.

A project-based client, by contrast, is usually buying a specific outcome on a fixed timeline — a website launch, a campaign flight, a rebrand rollout — and their reporting email should read against milestones and deadlines more than trailing trends. "We're on track for the November 15 launch, with the staging review completed this week" matters more to a project client than a month-over-month CPL comparison, because there often isn't enough history yet for a trend to mean anything. The goal-translation step still applies, but the goal is a milestone date, not a recurring KPI.

The practical implication: don't reuse the exact same monthly template across both client types just because it's convenient for your team. A project client reading a retainer-style trend report will wonder why you're not talking about the deadline, and a retainer client reading a project-style milestone update will wonder why nothing connects to last month. Ten extra minutes picking the right frame per client type pays for itself in how competent the report feels on the other end.

How do you write reporting emails when there are multiple stakeholders on the client side?#

Larger accounts often have a marketing manager who reads every detail, and a VP or founder who only skims the headline before a board meeting or budget review. Writing one email for both audiences at once is possible, but it requires a specific habit: put the entire argument in the first two sentences, so a stakeholder who never reads past the subject line and opening line still walks away with the right takeaway, then let the rest of the email serve the more detailed reader.

This is also where cc'ing matters more than agencies usually think about it. If you know a report is likely to get forwarded up the chain — to a CMO, a founder, a board — write the headline sentence as if that forward is inevitable, because it usually is. "Leads were down 18% against goal this month; here's what happened and what's changing" survives being forwarded without context far better than an email that only makes sense if you've read the last three months of history alongside it.

When stakeholders disagree with each other about what the report means — one person satisfied, another alarmed by the same number — resist the urge to write two different follow-up emails with two different framings. Address both concerns in one reply, openly acknowledging that reasonable people can read a flat month differently, and let the recovery plan (or the case for staying the course) do the reconciling. Trying to tell each stakeholder what they individually want to hear is the fastest way to get caught contradicting yourself later.

How do you structure a monthly performance update email step by step?#

Structure removes the guesswork every time you sit down to write one of these, whether it's your fifth client this month or your fiftieth. The order matters as much as the content: lead with the takeaway, then support it, then point forward. Reversing that order — leading with methodology or a wall of metrics before the headline — is the single most common mistake in agency reporting emails, and it's why clients skim past the parts that actually needed their attention.

1. 1

   Open with the headline, not a greeting-and-preamble

   After a brief hello, state the one result that matters most in the first sentence. "This month we booked 34 qualified demos against a goal of 30" beats three sentences of throat-clearing before the number shows up.

2. 2

   Give the two or three supporting numbers

   Back the headline with the metrics that explain it — spend, conversion rate, cost per result, whatever the client's dashboard tracks. Keep this to what supports the headline, not everything the platform reports.

3. 3

   Add context for anything that moved

   If a number is up or down more than the client would expect, say why in one or two sentences. Silence on a big swing reads as either not noticing or not wanting to explain — both are worse than a short, honest reason.

4. 4

   Connect it to their goal, not just the channel

   Translate platform metrics into business language: pipeline, bookings, revenue, applications — whatever the client actually reports up to their own boss. This is the step that makes a report feel like it's about their business, not your dashboard.

5. 5

   State what changes next month

   One or two specific actions, ideally tied directly to what just happened. "Because CPL crept up on the retargeting audience, we're refreshing creative and shifting 15% of spend to prospecting" is concrete; "we'll keep optimizing" is not.

6. 6

   Close with one easy next step

   A single question, a proposed time to talk, or an explicit invitation to reply — never a vague open door. The easier it is to respond, the more likely the client actually engages instead of just archiving the email.

The table below maps that structure against what each section is actually for, so you can see why the order isn't arbitrary. Each piece is doing a different job, and cutting one doesn't shorten the email so much as it removes a piece of the argument.

What does a full agency monthly report email example look like?#

Here's how that structure reads end to end, for a routine, on-track month. This is the version most agencies need most often, and it's worth getting genuinely good at, because a well-written routine update is what earns you the benefit of the doubt on the months that aren't routine.

Notice what's absent: no apology for anything, no defensive hedging, no ten-paragraph methodology recap. It's short because the news is good and doesn't need padding. The discipline of writing a tight update on an easy month is what makes the harder months possible to write well too — if every report is long and dense regardless of outcome, the client has no signal for when something actually needs their attention.

How do you write a client campaign results email when the numbers are strong?#

A strong-results email has its own failure mode: overclaiming. It's tempting, when the numbers are good, to let the win carry the whole email and skip the context and next steps — but a client campaign results email that's just "great news, everything's up!" reads as thin the same way a bad one that's all excuses does. The instinct to attribute every win entirely to your own work, without acknowledging market conditions, seasonality, or a client-side change that helped, also erodes trust over time, because clients remember when you take full credit for an easy month and compare it to how you handled a hard one.

The fix is simple: apply the same five-part structure to good news that you apply to bad news. State the result, give the honest context (including anything outside your control that contributed), translate it to the goal, say what you're doing to sustain or build on it, and close with a specific next step. A good-news email that's honest about why the number is good reads as more credible, not less — and it banks trust you'll need the month something doesn't go as well.

How do you tell a client their campaign underperformed?#

This is the scenario almost nothing is written about from the agency's side, and it's the one that actually determines whether an account survives a rough patch. The instinct under pressure is to soften the headline, bury the number in paragraph three, or lead with everything that's being done before saying what happened — all of which make the email longer and the client more suspicious, not less. Clients can tell when an email is trying to get somewhere without saying it directly, and that feeling — more than the bad number itself — is what triggers the trust conversation you're trying to avoid.

The better instinct, and the one that consistently protects accounts, is to say the number plainly, early, in your own words, before the client's own dashboard-checking or gut feeling beats you to it. A client who hears "leads were down this month, here's why, here's the plan" directly from you experiences that as being taken care of. A client who has to notice the dip themselves and then wait for your report to confirm it — or worse, never see it addressed at all — experiences the same dip as being managed around.

What's the framework for delivering bad news to a client over email?#

Delivering bad news well is a structure, not a talent, and it's close to the same five-part shape as a routine update — with one addition: the recovery plan has to be specific enough that the client can evaluate it, not just trust it.

1. 1

   State the result plainly, in the first two sentences

   No preamble, no "I wanted to reach out because" softening. "Leads were down 18% this month against our goal" — said directly, before any explanation follows.

2. 2

   Give the real cause, even if it's uncomfortable

   If the cause is partly on your side — a slow creative refresh, a targeting miss, a delayed test — say so. Attributing every miss to external factors when part of it wasn't is the fastest way to lose credibility on the next report.

3. 3

   Separate what's in your control from what isn't

   Be specific about which part of the shortfall the team is addressing directly and which part is market or platform-wide, ideally with a data point that shows it's not isolated to this account if that's true.

4. 4

   Give a concrete recovery plan with a timeframe

   Not "we'll keep an eye on it" — a specific action, already scheduled, with a date it goes live and a rough sense of when you expect to see it move the number.

5. 5

   Offer a call proactively, don't wait to be asked

   A live conversation is often the fastest way to keep a rough month from turning into a review of the whole relationship. Offering it yourself signals confidence; waiting for the client to request it can read as reluctance.

6. 6

   Follow through publicly on the next report

   Whatever you promised in the recovery plan, reference it explicitly in the next reporting email — did it launch, what did it do. Clients forgive a bad month far more easily than a bad month followed by a report that acts like it never happened.

That sixth step is the one agencies skip most often, and it's arguably the most important. A recovery plan that's mentioned once and never followed up on is worse than no recovery plan at all, because it teaches the client that your promises in reporting emails don't get tracked. Put a reminder on the account, and open next month's report with a direct callback: "as mentioned last month, we launched the creative refresh on the 12th — here's what it did."

What does an underperformance email actually look like, written out?#

Here's a full example applying that framework to a real scenario: a lead-gen retainer where volume dropped against goal. The tone is direct without being clinical, and it never apologizes for the number — it explains it and acts on it.

Notice the sequencing again: the number first, the honest attribution (including the part that wasn't external), the specific fix already underway, and a proactive offer to talk. There's no line reassuring the client that "we're confident things will turn around" — confidence is demonstrated by the specificity of the plan, not asserted separately from it. Vague reassurance is what makes bad-news emails feel hollow; specificity is what makes them feel handled.

What mistakes turn a rough month into a lost account?#

Most churn after a bad month doesn't come from the number itself — clients generally understand that performance fluctuates. It comes from how the bad month was communicated, or whether it was communicated proactively at all. Two accounts can post the exact same underperforming month and end up in completely different places six weeks later, purely because of how the email handled it. The table below lines up the most common mistakes against what tends to work instead.

There's no fixed word count that makes a reporting email correct, but there's a useful test: could the client's boss read it on a phone, in the time it takes to wait for coffee, and come away with the right takeaway? A strong month usually passes that test in four or five short paragraphs. A bad month is often slightly longer, not because it needs padding, but because the cause and the recovery plan both genuinely need a sentence or two of specificity — cutting those short to keep the email brief is a false economy, since a bad-news email that's too thin reads as evasive rather than efficient.

The practical rule: length should track the amount of explaining the news actually requires, not a template you reuse regardless of outcome. If you notice every reporting email you send is roughly the same length no matter what happened that month, that's usually a sign the template is doing the writing instead of the result.

What tone should a marketing agency performance update email use?#

Tone is where a lot of otherwise well-structured reporting emails go wrong, in both directions. Too corporate and it reads as a form letter the client has seen a hundred times from other vendors; too casual and it undercuts the client's confidence that you're treating their budget seriously. The right register is closer to how you'd actually explain the month to the client's face — direct, specific, a little informal, but never flippant about their money.

• Write like you're talking to the person, not the account — use their name, reference something specific from last month's conversation if relevant.
• Avoid jargon the client wouldn't use themselves — "cost per demo" over "CPA optimization vector," plain business language over platform terminology.
• Never use passive voice to soften bad news — "leads declined" hides the actor; "we came in under goal" or "the campaign underperformed" is honest about who's accountable.
• Match length to news, not habit — a great month deserves three tight paragraphs, not the same six-section template stretched to fill space.
• Don't perform enthusiasm on a flat month — an email that's artificially upbeat about mediocre results reads as either tone-deaf or manipulative.

How often should reporting emails go out, and what should the subject line say?#

Monthly is the default cadence for most retainer relationships, but the right frequency depends on how fast the account moves and how anxious the client naturally is. Fast-moving paid media accounts with real budget at stake often benefit from a brief weekly check-in alongside the full monthly report — not a repeat of the same data, just a one-line pulse: on track, ahead, or behind, with one sentence why. That short cadence is what prevents a client from ever being surprised by the monthly number, because they've already seen the trend building.

The subject line matters more than most agencies treat it. A subject like "October Report" gets opened out of habit and read passively. A subject that states the headline — "October results: 34 demos booked (goal: 30)" or "October results: leads down against goal — here's the plan" — gets opened with the right expectation already set, and the client reads the rest of the email as confirmation and detail rather than as a reveal. This single change, putting the actual result in the subject line instead of just the month name, is one of the cheapest improvements you can make to how reporting emails land.

A weekly pulse doesn't need any of the depth of the monthly report — it exists purely to keep the client oriented between the full updates, so the monthly number never lands as a surprise. Keep it to two or three sentences, no dashboard link required.

How do you keep a reporting email from turning into a data dump?#

The failure mode on the other end from being too thin is being too dense — a reporting email that tries to narrate every metric on the dashboard instead of the two or three that matter. Clients don't want proof you tracked everything; they want confidence that you know which things matter and are watching those closely. A shorter email that clearly prioritizes is read as more competent than a longer one that lists everything, because prioritization is itself the skill the client is paying for.

• Pick the one metric the client's goal actually depends on, and make it the headline — everything else is supporting detail.
• Push full metric breakdowns to the linked dashboard or attached report; the email is the interpretation, not the export.
• If a metric didn't move meaningfully, don't force a sentence about it — silence on a flat number is fine; forced commentary on everything reads as padding.
• Use one comparison point, not five — month-over-month or against goal, not both plus quarter-over-quarter plus year-over-year in the same paragraph.
• If the client asked a specific question last month, answer it explicitly near the top — it signals you remembered, which matters more than most of the report.

How do you handle a client who wants to litigate every number over email?#

Some clients respond to any reporting email — good or bad — with a long thread of follow-up questions, sometimes challenging the methodology itself. This is worth handling carefully, because the instinct to answer every question fully in writing can turn a five-minute clarification into a week-long email chain that leaves both sides more frustrated than when it started.

The better move, after one or two rounds of written back-and-forth, is to offer a short call: "happy to keep going over email, but I think we'd get through this faster on a quick call — got 15 minutes tomorrow?" This isn't avoidance; a live conversation resolves ambiguity in real time in a way email threads often can't, and it signals that you take the client's questions seriously enough to give them real time rather than a rushed reply between other accounts. Reserve the fully-written-out answer for questions that genuinely need a documented, precise response the client can reference later.

What do you do when a client never replies to reporting emails at all?#

The opposite problem is just as common and gets far less attention: a client who never engages with the report at all, good or bad. It's tempting to read silence as approval — no news is good news — but silence on a reporting email is genuinely ambiguous, and treating it as satisfaction is a risky assumption to build a renewal case on. A client can go quiet because everything's fine and they trust you, or because they've quietly disengaged from the relationship and are already shopping around, and those two states look identical in an inbox.

The fix isn't to escalate urgency on every report — that reads as needy and can make an otherwise satisfied, simply-busy client feel chased. Instead, build in a lightweight, periodic check that isn't about the numbers at all: every third or fourth month, close the reporting email with a direct, low-pressure question about the relationship itself rather than the metrics — "stepping back from the numbers for a second, is this still hitting what you need from us?" — and treat a non-answer to that specific question differently than a non-answer to a routine monthly report.

If a client goes quiet for two consecutive reporting cycles despite a direct question like that, it's worth a phone call rather than a third email. Persistent silence after a specific, easy-to-answer prompt is one of the more reliable early warning signs of churn, well before a cancellation notice arrives, and it's far easier to address in a live conversation than to keep restating in an email the client has already stopped reading closely.

How does AI Emaily help agencies write client reporting emails faster and more honestly?#

The structure in this guide is straightforward to describe and genuinely hard to execute consistently, every month, across every account, especially on the accounts where the news isn't good and writing the email is the task you most want to put off. AI Emaily is an AI-native email client built for exactly that gap between knowing the right structure and actually sitting down to write it, on time, for every client, every month.

AI Emaily connects to Gmail, Outlook, and standard IMAP, and can draft a client reporting email in your voice, following the five-part structure — headline, context, goal translation, next steps, close — instead of starting from a blank page or a stale template. For a good month, it drafts the tight version. For a soft month, it's built to include the harder parts honestly: naming the underperformance directly, separating what's controllable from what isn't, and drafting a specific recovery plan section rather than a vague reassurance line, because a bad-news email that soft-pedals the cause tends to do more damage than the number itself.

Control matters most on exactly this kind of email, which is why nothing goes to a client without you seeing it first. In Copilot mode, every drafted reporting email — good news or bad — waits for your review and approval before it sends; nothing about a client-facing performance update goes out unattended. Autopilot exists for lower-stakes, internal-facing drafts within rules you set, but a reporting email to a paying client is the kind of message this guide assumes stays in Copilot, reviewed by a human, every time. Both modes carry a full audit trail and undo, so you can see exactly what was drafted, what was sent, and when.

If you're building out a fuller client email library beyond reporting — onboarding sequences, scope-creep pushback, status updates — the templates in our companion agency email templates guide cover those adjacent scenarios, and the inbox automation approach in our digital agency inbox automation guide covers how to make sure a reporting email deadline never gets buried under the rest of a busy agency inbox in the first place. You can try AI Emaily free at app.aiemaily.com/signup.

Putting it all together#

A client reporting email is not the report — it's the argument you build on top of it, and it's the single most frequent, most predictable piece of writing that shapes how a client feels about your agency over the life of the account. The structure is the same whether the month was great or rough: headline first, honest context, translation to the client's actual goal, a specific next step, and an easy way to respond. What changes between a good month and a bad one isn't the shape of the email — it's the courage to lead with the number even when it's not the one you wanted to send.

Clients rarely leave an agency over one soft month. They leave over a pattern of vague updates, buried bad news, and recovery plans that get mentioned once and never followed up on. Get the reporting email right — consistently, honestly, on a predictable cadence — and it becomes one of the strongest retention tools you have, doing quiet work every single month that no single great campaign result can replace on its own.