What Should the First Report a New Client Sees Contain?

What should the first report a new client sees contain?

A baseline, one headline metric, the known lags, and what happens next. Not results, because there are none yet, and not a dashboard, because a dashboard invites a person to find their own story before you have agreed what the story is measuring.

The first report is the most consequential document in the whole engagement and it is usually the most rushed. It establishes what counts as progress, and once that is established you will be judged against it for as long as the relationship lasts, whether or not it was the right choice.

Across six years and more than 70 projects, almost every reporting relationship that went badly went badly because of something omitted from the first one, not because of a bad result later.

Why is the first report not a performance report?

Because nothing has had time to happen, and pretending otherwise starts a habit you cannot sustain. If the first report shows movement, the second one has to show more movement, and you have quietly promised a rate of change that the work does not actually produce.

The honest framing is that this report describes the starting position. Here is where things stand, here is what I am going to change, here is when you will know. A client who understands that is a client who does not panic in week three.

There is also a practical reason. The numbers this early are mostly noise. Any movement you show is as likely to be a weekday, a seasonal shift, or a data lag as it is to be your work, and claiming it costs you the credibility you will need when a real result arrives.

What belongs in the baseline?

The small number of figures you will report every single time, captured before you touch anything. That set should be short enough to fit in a paragraph, and it should be chosen so you would still report it if the numbers went the wrong way.

That last condition is the test. A baseline you would quietly drop if it declined is not a baseline, it is a marketing selection, and clients work that out eventually. Choose metrics you are willing to be wrong in front of.

Capture it properly rather than approximately. Note the date, the source, the exact filter or view, and the window. Six months later somebody will ask what the starting point was, and a baseline nobody can reproduce is worth nothing, which is the same discipline I argued for in deciding which source wins when two tools disagree.

Which single metric should lead?

The one closest to the client's actual outcome that you can genuinely influence. Not the easiest to move, and not the most flattering, which are usually the same thing and usually wrong.

The temptation is to lead with something that reliably goes up. Impressions go up. Pages indexed goes up. Those make comfortable first reports and they teach a client to value a number that does not pay them, which means the conversation in month six is about why the good number did not become revenue.

Pick the uncomfortable one instead, and then be explicit that it moves slowly. A client who is told up front that the number they care about is slow, and why, is far more patient than one who is shown a fast number and later asked to care about a different one.

Why does naming the lag matter so much?

Because the lag is real, documented, and invisible to your client, and every one of those facts works against you if you do not say it first. Google's own documentation about its Performance report says there can be a lag between when the numbers are calculated and when they are visible, and that collected data is usually available in 2 to 3 days.

The same applies to anything newly published. Google says indexing typically takes only a day or so but can take much longer in some cases, and that submitting a request does not guarantee the page will appear in the index. Those are Google's words, not mine, and putting them in the first report is far better than reciting them defensively in week two.

I would put a short section in every first report headed simply what will look wrong and why. Data appearing late. A page not showing up yet. The time zone question, since Google's documentation notes that outside the 24 hour view the Performance report tracks and labels daily data in Pacific Time. None of those is a problem, and all of them look like one.

What should you say about what you cannot measure?

Say it plainly, early, and without apology. Every reporting setup has blind spots, and a client who learns about yours from you treats it as rigour. A client who discovers it independently treats it as concealment.

The clearest example is the one Google publishes about itself. Its documentation states that to protect user privacy the Performance report does not show all data, and gives the example that it omits some queries searched a very small number of times. That is a permanent, structural gap in what anyone can report, and it is better introduced on day one than defended on day sixty.

The same goes for the gaps that are yours rather than the platform's. If something is not instrumented yet, say when it will be. If a number is an estimate, label it as one every time it appears, not just the first time.

Should the first deliverable be a dashboard?

No, and I would resist it even when a client asks. A dashboard is a good ongoing artefact and a poor first one, because it hands somebody a hundred numbers before they have agreed which three matter.

What works better is a short written note, one page, that a person can read in three minutes and forward without editing. Baseline, headline metric, what will look wrong, what happens next, and when the next report arrives. The dashboard can exist underneath it and be linked, but the note is the thing that sets the frame.

Build the dashboard second, once the vocabulary is agreed, and build it to answer the questions the note raised rather than to display everything available. A dashboard designed after the conversation is a tool. One designed before it is a shrug.

How do you set the cadence without trapping yourself?

Match the interval to how fast the thing you are measuring can actually move, then say so in the first report. Weekly reporting on a monthly metric manufactures anxiety out of noise, and it also consumes a slice of your delivery time forever.

State the next date explicitly rather than saying regularly. Regularly means weekly to the client and monthly to you, and that gap surfaces at the worst possible moment. A named date is a small commitment that buys a large amount of trust.

Then protect the cadence when nothing has happened. A report that says nothing meaningful moved this month, here is what I did, here is what I expect next, is a good report. Skipping it because the news is dull is how clients start wondering what you do all day, which is the same erosion I described in the things I stopped charging for.

What should never be in a report?

Anything you cannot explain when asked. That sounds obvious and it is routinely violated, usually by a metric inherited from a template or auto included by a tool because it was available.

Go through the draft and ask, for each number, what decision changes if this goes up or down. If nothing changes, cut it. Most first reports get shorter by half under that test, and every one of them improves.

The other thing to keep out is the argument. A report states what happened. If there is a disagreement about direction or priority, that belongs in a conversation where the client can respond, not buried in a document they read alone. Reports that argue turn into documents nobody opens, and proof works the same way, as I argued in what you can show before you have case studies.

What should you do next?

Open the last first report you sent and check it for four things: a reproducible baseline with its source and date, one clearly named headline metric, an explicit note about lags and blind spots, and a named date for the next one. Most reports have one of the four.

Then write the what will look wrong and why section once, properly, and reuse it. It is the single highest leverage paragraph in client reporting, it takes twenty minutes to write, and it prevents most of the difficult conversations you would otherwise have in month two.

If you are about to start an engagement and want a second pair of eyes on which metric to put at the top, reach out. Getting that one choice right is worth more than everything else in the document.