Website maintenance report template: one page a client reads to the end
A care plan is paid for every month and mostly invisible. The report is the one place the client sees the work. Keep it to a page, lead with what changed, and give every figure a source.
Who reads it, and for how long
The person who pays is usually not technical and gives the report a minute. They want three answers: was the site working, did anything go wrong, and is there anything they need to decide. Everything else is backup for those three.
So the first lines carry the answers in words, and the figures come after them. A report that opens with a table of plugin versions gets filed unread.
The template, section by section
| Section | What goes in it | Where the figure comes from |
|---|---|---|
| Summary | Two or three sentences: the month in plain words, and anything the client has to decide. | You write it last. |
| Availability | How many checks ran and how many could not load the site, with the dates of any outage. | Your uptime monitor. |
| Updates | What was updated (core, plugins, themes), and anything held back with the reason. | Your update log. |
| Backups | When the last backup was taken and when one was last restored as a test. | Your backup tool. |
| Accessibility | The score now and a month ago, and the critical findings still open. | An accessibility check, with its date. |
| Security and certificate | Whether https works, when the certificate expires, and any change to the security headers. | A server health check. |
| Changes made | The edits you made for the client this month, one line each. | Your tickets or sheets. |
| Next month | What is planned and what is waiting on the client. | You. |
How to write each line
- Write what happened, not that you checked. "Updated 6 plugins, held back the booking plugin because its new version breaks the date picker" says more than "plugins checked".
- Give a figure its date. "Accessibility score 84 on 31 October, 79 on 30 September" can be checked; "accessibility good" cannot.
- Name a problem once, with what you are doing about it and by when.
- Put the decisions the client has to make in the summary, not on page three.
What to leave out
- Raw logs and long version tables. Attach them if a client asks.
- Scores without a source or a date.
- Words like "compliant" or "secure" as a verdict. A measurement is a measurement; say what was measured.
- Work you did not do. A care plan that promises backups and a report that skips the backup line will be noticed eventually.
Which parts Site Watch fills in
Site Watch checks each client site once a day and mails you at the start of the month. For every site you get the accessibility score at the end of the month and where it started, the critical findings still open, how many checks ran and how many could not load the site, and a link to that site's report under your name and logo.
That covers the availability count, the accessibility section and the certificate. Updates, backups and the edits you made stay yours to write, because Site Watch does not do them. Prices and the trial are in the white-label monitoring guide.
Questions people ask
- What should a monthly website maintenance report include?A short summary, availability, updates, backups, accessibility, security and the certificate, the changes made that month, and what is planned next. Each figure with its date and its source.
- How long should the report be?One page for the client, with the detail attached for anyone who wants it. The summary at the top should answer the question on its own.
- Can I send the Site Watch report to a client as it is?Yes. It carries your name, your site and your logo, and is drawn from the month's last good measurement. The link in the monthly mail works for 60 days.
- Should I put an accessibility score in a client report?If the client has been asked about accessibility, yes, with its date and the number of critical findings. Do not present it as a statement that the site conforms; automated checks find part of the problems, not all of them.
Get the figures without collecting them by hand
Site Watch measures each client site daily and sends you the month's figures and a report under your logo.
$12 per client site a month, $9 from 50 sites. The check needs no account. The trial is 30 days on up to 3 sites: the card is taken at checkout and nothing is charged until the trial ends.
More for agencies
- UptimeRobot alternative, compared
- ManageWP alternative, compared
- The best white-label monitoring tools
- MainWP alternative, compared
- ManageWP vs MainWP
- WP Umbrella alternative, compared
- Better Stack alternative, compared
- StatusCake alternative, compared
- Pingdom alternative, compared
- White-label monitoring for agencies
- Accessibility monitoring for agencies
- Pricing website care plans
- White-label website monitoring for agencies
