Two reports, one site
Open the last maintenance plan report you sent. If the first thing on it is a count of updates applied, a backup log or an uptime percentage, it is an activity report. If the first thing on it is a problem on the client's site, where it is and what you are doing about it, it is a findings report.
Both are honest. Both take work. But they land very differently with the person paying, and the difference is worth understanding before you decide which one your studio sends by default.
What an activity report says
An activity report is a record of effort. It usually contains:
- Updates applied, with version numbers
- Backups taken and where they are stored
- Uptime for the period
- Security scans run and their result, usually "clean"
- Hours used against the plan's allowance
Everything on that list is true and most of it is useful to you. It is the evidence you would reach for if a site went down and a client asked what you had been doing. It is also what the client sees when they ask themselves whether the plan is worth it, and the honest answer the activity report gives is "nothing went wrong this month". That is the right outcome and the wrong story. It describes the plan as a cost that has not yet paid out.
There is a second problem. An activity report is largely the same every month. Version numbers change, the rest does not. After three of them the client stops opening the email, and a report nobody opens cannot do its job.
What a findings report says
A findings report is a record of the site's condition. It contains the things that are wrong, or could be better, on the pages the client's customers actually see:
- A service page with no title, so search results show the URL instead
- A contact page with no phone number, email address, form or booking link on it
- Placeholder text left on a page that went live last month
- Text that is too small or too low in contrast to read on a phone
- A page that overflows sideways on a narrow screen
- Images without alt text on the pages that sell
- A key or credential sitting in a public file
Each item is on a named page, has a reason it matters and has a fix. Some will be fixed by the time the client reads the report; those go in a "fixed this month" section, which is the part of the document that reads as progress.
A findings report changes every month because the site changes every month. Someone edits a page. A plugin update drops a tag. A new team member publishes a post with four H1s. The report has something new to say, so the client opens it.
Why the findings report keeps the plan
A client renews a maintenance plan when they believe two things: that someone is paying attention to their site, and that the attention produces results they could not get on their own. An activity report proves the first and says nothing about the second. A findings report proves both, every month, in the client's own language.
It also changes the conversation at renewal time. With an activity report, the client is weighing a monthly fee against a year in which nothing broke. With a findings report, they are weighing it against a list of specific things that were found and fixed, on their site, that they did not know about. The second comparison is the one you want.
There is a quieter benefit. A findings report makes the plan's scope visible. When a client asks for a redesign of their homepage "under the plan", the report is the record of what the plan actually covers.
Keep the activity, move it down
None of this means dropping the activity section. Updates, backups and uptime belong in every report as the evidence that routine work happened. The change is in the order and the emphasis. Findings first, in plain language, ranked by what matters to the business. Fixed items second. Routine work third, as a short table. Next steps last.
The activity section should be the most boring part of the report. If it is the most interesting part, the site has had a bad month, and the findings section should say so at the top.
Where the findings come from
Most studios already have the activity data; it comes from the tools they use to maintain the site. The findings are harder, because they come from looking at the site the way a visitor or a search engine does, page by page, and nobody has time to do that by hand every month across thirty client sites.
That is the job our hosted website audit does. It fetches the public pages of a site on our servers, checks each one for the structural, readability and conversion basics and reports every finding with the page it is on, why it matters and the fix. It never logs in and never touches a file. The white-label Website Audit Report is the same engine across every public page up to 100, under your studio's name, so the findings section of your maintenance plan report is written before you open the document.
See what a website audit report finds on a real site. Get a free website audit: enter a URL and an email, and we check the public pages on our servers. We never log in and never touch your files.