Discussion starter: an agency question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- Agency
Has anyone replaced monthly reports with decision logs or impact memos, and did clients accept the change?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
adminAdmin
It can work, but a clean swap is a risky way to do it. The chart pack is the expendable part. The handful of numbers a client forwards to their own boss is not. A decision log with short impact memos works when it still answers the questions the monthly report was answering: are we on track, what did you do, what happens next, and what do I tell leadership. It fails when it removes the figures that feed someone else’s report, or when it reads like less work for the same fee.
Public evidence on client acceptance is thin, and there is no controlled comparison to point to, so treat this as a pilot with one or two clients, not a policy for every account.
The deciding factor is what happens to your report after it lands. If it is pasted into a board pack or a finance review, keep a small fixed set of numbers on a fixed date and move the thinking into the log. If nobody beyond your main contact reads it, and the contract allows it, you can replace most of it.
What a monthly report does besides reporting
Monthly reports survive because they do several jobs at once, and analysis is only one of them. Each job needs a replacement or a deliberate decision to drop it.
Job the report does Who relies on it Does a decision log cover it? What to keep or add Early warning: is anything broken? Your main contact Partly, if memos fire on agreed thresholds Automated alerts and a one-screen KPI view Material for upward reporting The contact’s manager, board or finance team No Three to five numbers in a fixed format on a fixed date Proof of activity Whoever approves the invoice Yes, and better: each entry shows the work and the reasoning The log itself, shared with the client Contract compliance Procurement or legal Only if the contract changes Revised deliverable wording in the scope of work A reason to meet Both sides Yes, if open decisions set the agenda A standing review of decisions due for review Expect pushback on the second row: a manager who pastes your organic chart into a leadership deck will not care how good the memo is if the chart disappears. Solve that first.
Why decision logs suit SEO’s delayed feedback
SEO changes show up weeks or months later, mixed with algorithm updates, SERP layout changes and changes in how the data is measured. A calendar report compares this month with last month, which invites everyone to credit or blame whatever the agency did recently, and that attribution can be wrong in both directions.
The
&num=100change is a good example. When Google stopped supporting that results parameter in September 2025, many sites saw desktop impressions fall and average position improve in Search Console, while clicks were affected far less, according to Brodie Clark’s analysis. A monthly report that month would have shown a drop and an improvement that were both artefacts of measurement. A one-page memo explaining that it was a reporting change, not a demand change, would have told the client more than any chart in the pack. The same applies to the March and May 2026 core updates: when the client asks what happened, a log lets you separate your changes from Google’s.A monthly report works like a bank statement: it tells you the balance moved. A decision log is closer to the minutes of an investment committee: what was bought, why, what return was expected, and when it will be reviewed. You still need statements, which is why the log should sit on top of a thin set of numbers rather than replace them. The difference in SEO is that returns arrive late, so the minutes are what let anyone judge a decision months after it was made.
Search Console has supported custom annotations on performance charts since November 2025, and GA4 has its own annotations, so log dates can sit on the charts the client already looks at. Keep the log itself in a shared sheet or document; annotations are pointers, not the record.
What goes in the log, and what goes in a memo
A decision log is a running record, one entry per decision, with these fields:
- Date, owner and the decision in one sentence, including decisions not to act.
- Alternatives rejected, and why.
- Evidence at the time, linked rather than pasted.
- Expected effect: which metric, which direction, a rough size and a time window.
- Review date and how the decision will be judged.
- Outcome, filled in at review: what happened, how confident you are that the change caused it, and what you would do differently.
The expected-effect field gives the log its value, and it is the one teams are tempted to skip. Writing the prediction before the change is the same discipline as pre-registering a hypothesis. Without it, every outcome gets explained after the fact and the log turns into a diary.
Also log decisions waiting on the client, such as a fix sitting in a development backlog, written neutrally. Three months of “awaiting development” in writing is a clearer prompt to act than a passing mention in a meeting.
An impact memo is event-driven and short, one page at most. A structure that holds up:
- What changed, in one sentence with the number.
- Likely causes, ranked, with the evidence for and against each.
- How confident you are, and what evidence would change your view.
- What you are doing next, and what you need from the client.
- The three or four numbers the client can forward, in the same format every time.
Hypothetical example:
Log entry, 14 March. Decision: merge 38 thin suburb pages into 9 regional pages with 301 redirects. Rejected: noindexing them, which leaves internal links pointing at pages that cannot rank. Evidence: 31 of the 38 had fewer than 10 organic clicks in 12 months. Expected effect: non-brand clicks to the regional pages up within about eight weeks, old set flat or slightly down meanwhile. Review: 16 May. Outcome: regional pages up overall, but one merged suburb lost a high-intent query, so it is being restored as a standalone page.
When to replace the report and when to layer the log on top
Condition Replace most of the report Keep a slim report and add the log Who reads it Your main contact only Forwarded to a board, finance or a parent company Contract Deliverables are flexible Procurement or a framework agreement specifies a reporting template Relationship stage Established, with a track record First few months, while the client is still deciding whether to trust you What the client asks after reading “Why did that change?” and “What should we do?” “Just tell me whether leads are up” Type of work Project-heavy: migrations, content programmes, technical fixes Mostly monitoring and maintenance How to run the switch as a pilot
- Find out what happens to the current report. Ask who opens it, which charts get copied into what, and which questions come back. The answers tell you which numbers must survive.
- Build the thin number layer first. Three to five metrics, automated, in the same format on the same date: for example non-brand organic clicks (Search Console’s branded queries filter makes that split easier), organic leads or revenue, and one health metric such as the share of priority pages indexed.
- Agree the memo triggers in advance. For example: non-brand clicks outside an agreed band for two consecutive weeks, a confirmed Google update, a release that touches page templates, or a recommendation waiting on approval for more than a set number of days. Agreed triggers stop the memo from looking like a way to report only good news.
- Run both formats in parallel until the new one has fed the client’s own reporting, so they see the memo survive contact with their boss before the old pack disappears. For monthly leadership reporting that is about two months; for a quarterly board, at least one board cycle.
- Rewrite the deliverable in the contract. Replace “monthly SEO report” with: decision log maintained continuously, an impact memo within a set number of business days of a trigger and at least monthly, an automated KPI view, and a quarterly review of logged decisions against outcomes. If a procurement framework specifies the format, agree the change in writing before the pilot starts.
- Review the pilot with the client. Ask what they used, what they forwarded and what they missed.
Where the change goes wrong
- The log exposes thin months. On a retainer that is mostly monitoring, the log will be short. That is honest, and it can start a conversation about scope and fee, so decide in advance whether you are ready for it.
- Predictions miss in writing. That is the point, but set expectations early: the log is there to calibrate judgement over time, not to score each guess. Review the hit rate each quarter instead of defending individual misses.
- Only wins get logged. Record reversals and null results too, or the log becomes marketing and the client will notice.
- Memos grow into essays. Hold the one-page limit and link to the evidence.
- The cost moves up the seniority ladder. A chart pack can be assembled by a junior or a script; a memo needs someone who understands the account. Price the senior hours in rather than absorbing them.
How to tell whether it worked
Client satisfaction is a weak test on its own, because people tend to prefer the format they already know. Measure whether decisions got faster and better:
Metric What it shows Where the baseline comes from Median days from recommendation to client approval Whether the format speeds up decisions The last six months of emails, tickets or meeting notes Share of recommendations implemented within the agreed window Whether decisions turn into work Same sources Share of log entries reviewed by their review date Whether the log is maintained or quietly abandoned Starts at the pilot “What happened?” questions between memos Whether memos answer questions before they are asked Count for the months before the pilot Reporting hours per client per month, by seniority The real cost of the new format Timesheets Decision latency is the metric I would weight most. The hours spent building a monthly report are visible. The cost of decisions waiting for the next report or the next meeting is not, and on SEO work that delay can matter more.
A practical starting point
If this were my agency, I would pilot with the two clients who complain most that reports are “just numbers”, keep the three to five figures they forward, and judge the pilot on decision latency and implementation rate rather than on whether the client says they like the new format. A change that speeds up decisions is easy to defend at renewal. A change that only saves reporting hours is a cost saving for the agency, and a client can tell who benefited.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.