A monthly report the client actually reads

The report, section by section

Reports are generated on the 1st of each month at 06:00 in the account’s time zone and emailed to the recipients you set. You can also build a report for any earlier month on demand, which is handy when a client asks about March in July. The document has six parts.

• Summary: uptime percentage, number of incidents, total downtime and average response time, each with the change from the previous month.
• Incidents: one row per incident with start, duration, the regions that confirmed it, the error, and whether somebody acknowledged it.
• Response time: a chart per monitor group and a list of the slowest monitors.
• Certificates and domains: expiry dates for every HTTPS and domain monitor, flagged when under 30 days.
• Heartbeats: missed runs for each cron job you monitor.
• Notes: a free-text section where you write what you did, such as plugin updates, a restored backup or a recommendation.

Who gets which version

Starter sends the account owner a plain monthly summary email, useful for yourself, not for forwarding. Pro ($29 per month) adds one branded PDF with your logo and colours and a footer line of your choosing. Agency ($59 per month) produces a separate branded report for every client workspace, with the client’s logo on the cover and your name in the footer, sent automatically on the 1st. Free has no report.

The distinction matters if you run one site for yourself on Pro or fifteen clients on Agency. On Pro the one report covers the account; if you want fifteen separate documents with separate recipients, that is the Agency design, and client workspaces is the feature that makes it work.

Recipients, and the quiet value of the Notes box

Recipients can be any email addresses, per account or per client workspace, and optionally all viewers of that workspace. Reports are also stored in the app for 24 months, so a client who loses the email can find last quarter’s numbers, and so can you when a contract renewal comes up.

The Notes section is the part clients remember. Uptime figures are the same dull number most months. A paragraph that says “updated PHP from 8.1 to 8.3, replaced the abandoned slider plugin, renewed the domain for two years” is the proof that the care plan is doing something. Writing it takes five minutes before the 1st; leaving it empty produces a perfectly valid, slightly lonely report.

A realistic month

Say a clinic’s website has one incident on the 14th: a 502 for 11 minutes after an update, confirmed by all live regions and acknowledged within three. In a 30-day month that is about 99.97% uptime. The report shows the incident row with the error and the acknowledgement, the response-time chart shows the dip and the recovery, and you add a note about the rollback. The client sees a calm document that explains an event they may not have noticed. Compare that with the usual alternative, which is hearing about it from the receptionist.

If the same month contained a two-hour planned migration inside a maintenance window set to exclude downtime, the uptime figure ignores that window. The report still lists it, so nothing is hidden.

What a report cannot do

It reports what the monitors saw. A site with no monitor on the checkout page cannot show checkout uptime, so choose monitors that match what the client cares about. Reports are monthly only; there is no weekly or quarterly cadence today. White-label removes any Tenium mention, but the numbers are ours: the underlying uptime math follows the rules on the maintenance windows page.

For selling the report as part of a package, the for agencies page walks through pricing and positioning, and the reports documentation lists every setting.