CLIENT-03
CLIENT
P0
Why more reports don't produce more trust
A client asks for reports beyond the monthly report, or asks for more metrics in each report. The monthly report is sent on the 7th, with data through the end of the prior month. A request for anything more than that is usually not about the report. It is about a missing baseline or missing trust. This article explains how to tell which, and what replaces a bigger report.
What This Is
A client asks for reports beyond the monthly report, or asks for more metrics in each report. The monthly report is sent on the 7th, with data through the end of the prior month. A request for anything more than that is usually not about the report. It is about a missing baseline or missing trust. This article explains how to tell which, and what replaces a bigger report.
Two facts matter.
First, more numbers do not create trust. They create more numbers. A person who does not trust one number will not trust twelve.
Second, the monthly report already answers one question at a time. More detail than that dilutes the answer, it does not sharpen it.
Before you check
You know what the monthly report contains: GSC clicks and impressions, GA4 sessions, conversions, keyword rankings, work completed, and next month plan.
You have the last report in front of you.
You know which question the client is trying to answer.
Diagnostic tree
Run the checks in order. Each check ends in a resolution or the next check.
Check 1. Does the client have the baseline?
How: ask which one number they are trying to confirm, and whether they have the previous report that showed it.
Why: a request for more reports is often a missing baseline. If they never saw the starting point, they cannot see the change.
If they cannot name the baseline, go to Resolution A. If they have the baseline, go to Check 2.
Check 2. Is this about trust, not data?
How: ask what would change if the report showed a number they did not expect. Listen for whether the concern is the work or the reporting.
Why: a trust problem cannot be fixed with a chart. It has to be fixed with a written explanation and a cadence they can hold us to.
If the concern is trust, go to Resolution B. If it is a specific missing number, go to Check 3.
Check 3. Can one number answer it?
How: pick the single metric that answers their question, from GSC, GA4, or the rank data in GSC.
Why: one number per question is the rule. Twelve numbers answer no question.
If one number answers it, go to Resolution C. If no single number answers it, go to Resolution D.
Resolutions
Resolution | Condition | Action |
|---|---|---|
A. Missing baseline | They cannot name the starting point | Send the baseline and the current number side by side |
B. Missing trust | The concern is trust, not data | Point to the docs. Set the cadence. Escalate to Mahesh if it is about the work |
C. One number | A single metric answers it | Send that number, with the period and the comparison |
D. Real gap | No single metric answers it | Add that one metric to the report, not a new report |
Resolution B in detail
When the request is really about trust, we do not add reports. We do three things.
Point to the docs. Send the help docs article on the number they are questioning. For a traffic question, send AN-01. For a ranking question, send RANK-01.
Set the cadence. Restate the monthly report: sent on the 7th, data through the end of the prior month, by email. Nothing more is added.
One number per question. Every question gets one number, with its period and its comparison. We answer the question they asked, not the question we wish they asked.
If the trust problem is about the work itself, not the reporting, escalate to Mahesh.
When to escalate
Escalate when all three are true.
We have sent the baseline and answered with one number per question.
The client still asks for more reports.
The concern has moved from reporting to the work itself.
Everything else closes in the resolutions above.
Primary sources
Related articles
Last verified
·
Owner
Mahesh