The download is a plain text file with three parts: a twelve-item checklist for the month, a report template with an executive summary, a performance table, completed work and next steps, and a short review-and-delivery section. It contains no tracking, no account access and no client data. The full text is printed below, word for word, so you can judge it before downloading anything.
What’s inside
- The monthly checklist — twelve checks from confirming the period to logging the client’s questions.
- The report template — client, period, owner and goal, then four sections: summary, performance, work completed, decisions and next steps.
- Review and delivery — what a second person checks, how to store the final version and when to update the checklist.
Nothing in the file is specific to SEO, paid media or design. The performance table takes whatever metrics your client agreement names; the value is the order of the checks, not the metric list.
The checklist and template in full
This is the text of the download, with the writing space after each prompt removed. If the download changes, this section changes with it.
A useful client report answers three questions: what happened, why it matters and what happens next. Use this checklist to deliver a consistent report without turning every month into a new project.
Before you start
Confirm the reporting period, client goals, the person responsible for review and the delivery date. Compare the period with a useful baseline: the previous month, the same month last year or a target. Explain your choice. For a new client, the first period may be a baseline rather than evidence of improvement.
Copyable monthly checklist
- ☐ Confirm the client, reporting period and delivery date.
- ☐ Check access to each source and investigate missing connections.
- ☐ Verify the date range, time zone, currency and filters.
- ☐ Compare important figures with their original sources.
- ☐ Flag missing data, tracking changes and known limitations.
- ☐ Summarize the two or three insights that matter to the client's goal.
- ☐ Explain major changes without claiming a cause you cannot support.
- ☐ Record completed work and unfinished commitments.
- ☐ Propose next steps with owners and dates.
- ☐ Have a second person review sensitive numbers and permissions.
- ☐ Send through the agreed channel and store the final version securely.
- ☐ Track client questions and decisions.
Copy this report template
Client: [name]
Period: [start–end, time zone]
Prepared by: [name]
Goal: [measurable business objective]
Executive summary
- Result: [metric, value and comparison period].
- Interpretation: [why this matters for the goal].
- Limitation: [missing data or important context].
Performance
| KPI | Current period | Comparison | Source | Context |
|---|---|---|---|---|
| [Metric] | [Value] | [Value and period] | [Tool] | [Explanation] |
Work completed
- [Deliverable and completion date]
Decisions and next steps
| Action | Owner | Due date | Client decision needed |
|---|---|---|---|
| [Action] | [Name] | [Date] | [Yes/no and details] |
Make the numbers useful
A rising traffic graph is not automatically a business result. Connect it to a relevant conversion or explain why that link is not yet measurable. Separate facts from hypotheses: “leads fell by 12%” is a measured change if the data supports it; “the landing page caused the decline” requires evidence.
Review and deliver
A reviewer should check the most consequential figures and open any client links using appropriate permissions. Agree on a deadline for questions and log decisions in the client workspace. Update the checklist when errors repeat.
See the client reporting workflow for a process that keeps human review in the loop.
Add a delivery record
The file covers the report. It does not record what was sent, when, and from which data snapshot. Keep that beside the report in your project tool or the reporting platform’s log. Without it, a question about the March figures six months later has no answer.
| Field | What to record | Why |
|---|---|---|
| Report ID | Client and period plus a version, for example acme-2026-03-v2 | Ties the client copy to the internal version |
| Data through | The date the sources last refreshed, separate from the send date | Distinguishes source lag from a reporting error |
| Template version | The version of this checklist or your report design | Explains a change in layout or metric order |
| Recipients | Named client contacts only | Supports access review and incident checks |
| Sent and accessed | Send time and channel; confirmation the client opened it | “Scheduled” is not “delivered” |
| Known limitations | Missing measure, tracking change or partial period | Shows what you knew at the time |
| Follow-up owner | The person answering the client’s questions | Assigns the next action |
Three review gates
The checklist asks for a second review. Make that review specific by giving each gate a pass condition.
| Gate | Question | Pass condition |
|---|---|---|
| Data | Did every source refresh for the intended period? | Each chart shows the expected property, date range and data-through date |
| Meaning | Do the written conclusions match the figures? | Every claim cites a visible figure or is labelled as a hypothesis |
| Delivery | Can the client open only their report? | A client login shows one client’s data and nothing else |
When a source fails, do not replace it with zero. Mark the figure unavailable, say why, and choose explicitly whether to send with the gap, delay, or send an interim note. All three are defensible; a silent zero is not.
Owner, version and review
The page shows the download’s version number, currently 1.0. Treat that number as the file’s identity: if you or your team change the checklist, the version must change with it, and the text on this page must be updated in the same edit. A file and a page that disagree are worse than no template.
- Owner: the account lead or operations lead who controls the template.
- Review: once a quarter, and after any change to sources, metrics or the client agreement.
- Done when: one named person owns the report, the delivery record is kept with the project, the three gates have pass conditions, and the last send was confirmed as accessed.
What a reporting tool can automate
The checklist does not assume a platform. If you use one, decide which rows it owns and which stay with your team.
| Checklist step | Tool can | Team must |
|---|---|---|
| Confirm the period and delivery date | Store the schedule | Agree the date in the contract |
| Check source access | Alert on a broken connection | Confirm the property is the right one |
| Compare figures with sources | Show both values | Decide whether a difference matters |
| Summarise the insights | Draft a summary | Sign the interpretation |
| Review permissions | Hold the permission model | Test a client login |
| Send and store the final version | Deliver and log the attempt | Confirm access and keep the record |
Frequently asked questions
Is the download the same as the text on this page?
Yes. The checklist, the report template and the review section above are the content of the download. The file adds space to write after each prompt; nothing else differs.
Should the report be a PDF, a portal or a dashboard?
It depends on what the client does with it. A PDF suits clients who read and forward a document; a portal suits clients who sign off work or ask questions monthly; a dashboard suits clients who check numbers between meetings. The checklist works for all three, but the delivery gate changes with the format.
What if a data source is late?
Label the figure unavailable, state the reason and the expected date, and decide whether to send or delay. Google documents that Search Console data is normally available in 2-3 days and that Analytics daily processing can take 24-48 hours, so a report sent on the 2nd is early for both. Sending a labelled gap is usually better than moving the delivery date without telling the client.
How do we record the client’s questions?
Log them with the report ID and the date. A question asked twice is a design signal: the label, the context or the order of the sections needs changing. Update the template rather than answering the same question from memory each month.
Does this work for paid media or design clients?
Yes. Replace the performance table’s metrics with the ones in the client agreement and keep the four-section order. The structure — result, work, next action — is what makes the report useful; the metric names are local to the client.
Can we use this alongside a reporting platform?
That is the intended use. The platform handles refresh, assembly and scheduling; the checklist keeps the data, meaning and delivery gates with a named person. See the automated client reporting workflow for the full process.
Related resources
- Client reporting workflow for the process behind the checklist.
- Automated client reporting for owners, gates and failure tests.
- SEO client reporting tools for the comparison scorecard.
- How to choose client reporting software for the decision record.
- All agency templates for the rest of the set.
Next step: download the checklist, fill in the client, period and goal, and add the delivery-record fields to your project tool before the next reporting cycle. If a check has no owner, either assign one or delete it.