Why the follow-up matters more than the meeting
A client sits through a 30-minute audit walkthrough, nods along, understands the score, understands the top findings, agrees the payment processor issue needs fixing this week. Then they go back to their inbox, their next three meetings, their actual job. By the following morning, the specifics have already started to blur — what exactly was the score, which fix was urgent, who agreed to do what.
The follow-up email isn't a courtesy. It's the artifact that survives the meeting. It's also usually the thing a marketing director forwards to their own boss or finance team to get budget or developer time approved — which means it needs to stand on its own, without you in the room to explain it.
Send it within 24 hours. The value of a follow-up degrades fast; by day three, you're re-explaining things instead of confirming them.
The five-part structure
Every effective audit follow-up has the same five components, in the same order. Skipping any one of them is what turns a follow-up into something the client skims and forgets.
One line. The number, and what it means. This anchors the email exactly the way it anchored the meeting.
Not all 15–20 findings from the full report — just the "fix now" tier. Each one gets a sentence on what it is and a sentence on what it's costing the business. If the client wants the full list, it's already in the PDF you sent; the email is not the place to repeat it.
Specific dates, not "soon." "Payment processor exclusion — this week. Consent Mode v2 — scheduled for the CMP renewal in three weeks." A timeline with no dates is the first thing that gets deprioritized.
Name a person for every item — you, the client's developer, their marketing coordinator. An action with no owner is an action nobody does.
What happens next, and when. A scheduled check-in date, a request to confirm developer availability, a link to approve a quote. End on an action, not a summary.
The template
Copy this structure directly. The bracketed sections are the only parts that change from client to client.
Hi [Name],
Thanks for the time today — here's a written summary of what we covered, so you have something on hand if you need to loop in [developer / finance / your team].
Overall scoreYour property scored [XX]/100. [One sentence on what that range typically means and what we're working toward.]
Top priority findings1. [Finding name] — [plain-English description]. Business impact: [what it's costing them].
2. [Finding name] — [plain-English description]. Business impact: [what it's costing them].
3. [Finding name] — [plain-English description]. Business impact: [what it's costing them].
[Finding 1] — by [date], owned by [name].
[Finding 2] — by [date], owned by [name].
[Finding 3] — by [date], owned by [name].
[Specific next action — e.g. "I'll check in on [date] to confirm the payment processor exclusion is live, and we can schedule the Consent Mode work once your CMP renewal date is confirmed."]
Full findings are in the attached report if you want the complete picture. Let me know if anything above doesn't match what you remember from the call.
[Your name]
A filled-out example
Here's the same structure applied to a real audit outcome — a property that scored 58, with a payment processor attribution issue and an unimplemented Consent Mode v2 as the top findings.
Hi Sarah,
Thanks for the time today — here's a written summary of what we covered, so you have something on hand if you need to loop in your dev team or ops lead.
Overall scoreYour property scored 58/100. That's below average — a few significant issues are affecting data accuracy, not catastrophic, but enough that your reports are underreporting real performance. Getting to 80+ is realistic within the timeline below.
Top priority findings1. Payment processor attribution — purchases completed via PayPal are being credited to PayPal as the traffic source instead of the ad or search result that drove the sale. Business impact: your paid campaign ROAS is understated, and budget decisions based on it are working from incorrect numbers.
2. Consent Mode v2 not implemented — EU visitors who decline the cookie banner are currently invisible to GA4. Business impact: in markets like Germany and France, this can mean 35–50% of EU traffic isn't being measured, which weakens your Google Ads bidding algorithms in those markets.
Payment processor exclusion — by Friday (this week), owned by me — a 10-minute config change.
Consent Mode v2 — by end of month, owned by your dev team, pending CMP selection.
I'll make the payment processor fix this week and confirm it's live. For Consent Mode, can you let me know which CMP options your dev team is considering by Wednesday so I can scope the implementation?
Full findings are in the attached report if you want the complete picture. Let me know if anything above doesn't match what you remember from the call.
Travis
Three mistakes that make clients ignore it
An email with 18 bullet points reads like the PDF you already sent. Nobody re-reads a PDF in email form. Restate only what's urgent — the rest is reference material, not follow-up material.
"We'll look at fixing this soon" is not an action item — it's a sentence that lets everyone assume someone else is handling it. Every line in the timeline section needs a name and a date, even if the date is approximate.
The meeting was translated into plain language. It's easy to slip back into GA4 terminology when writing quickly afterward — "consent signals absent" instead of "EU visitors are invisible to GA4." Read the draft back as if you're the client before sending it.
