Why this playbook exists
The Core Principle
Reporting exists to trigger decisions, not to show work.
If a report cannot clearly answer the question, “What should we do differently next?”, it is noise.
The Reporting Hierarchy (Non-Negotiable)
Level 1: Signals (Raw Reality)
Signals represent what actually happened. They are facts and do not explain themselves.
- Traffic
- Leads
- Calls
- Impressions
- Conversions
- Spend
Rule: Signals are inputs, not conclusions.
Level 2: Insights (Interpretation)
Insights explain why signals changed.
Every insight must follow this format:
- Signal
- Cause
- Impact
No cause means no insight.
Level 3: Actions (Decisions)
This is the only level that truly matters.
Every report must end with clear actions:
- Stop
- Start
- Continue
- Test
If no action is proposed, the report is incomplete.
What We Do Not Report on by Default
Some metrics create false confidence and distract from outcomes:
- Keyword counts
- SEO tool scores
- Vanity rankings
- Generic site health scores
- Isolated CTR without context
If a metric does not connect to revenue, pipeline, or intent, it stays internal.
Channel-Wise Reporting Logic
SEO Reporting (Correct Model)
We report on:
- Page-level movement
- Directory-level performance
- Intent alignment
- Qualified organic traffic
We avoid:
- Top 100 keyword lists
- Random ranking screenshots
Action examples:
- Kill underperforming page clusters
- Consolidate cannibalised URLs
- Double down on converting directories
Paid Media Reporting
We report on:
- Cost per qualified lead
- Conversion quality trends
- Ad fatigue indicators
- Funnel drop-offs
We avoid:
- CTR celebrations without conversions
- Platform vanity metrics
GBP & Local Reporting
We report on:
- Calls versus impressions
- Direction request anomalies
- Review velocity changes
- Location-level outliers
We avoid: aggregate averages that hide poor-performing locations.
The One-Page Rule
Every client-facing report must:
- Fit on one page or one screen
- Be scannable in under two minutes
- Contain a maximum of five insights
Long reports signal unclear thinking.
Reporting Cadence Designed for Sanity
- Weekly: Signals and exception tracking
- Monthly: Insights and decisions
- Quarterly: Strategy recalibration
Daily dashboards are internal tools, not client reports.
Ownership Model
- Analyst / Executive: Data accuracy
- Account Lead: Insights
- Strategy Lead: Decisions
- Client: Business context
If the account lead cannot explain the report in five minutes, they do not own it.
Reporting Anti-Patterns to Kill Early
- Auto-generated dashboards sent as reports
- Identical templates every month
- Explaining numbers instead of implications
- Over-reporting to justify fees
The Silent Client Warning Sign
If a client repeatedly responds with “Looks good” and no follow-up questions, you are losing them.
Good reporting creates questions, trade-offs, and decisions. Silence signals decay.
Final Reality
Good reporting makes agencies harder to replace.
When clients understand what is happening, why it is happening, and what to do next, they stop shopping.
This playbook exists so reporting becomes a decision engine—not a monthly ceremony.