MSPs, IT consultants, and infrastructure agencies need to show their work. A clean, branded diagnostics report turns a 30-minute investigation into a deliverable the client can read in two minutes. This guide explains what to include, how to format it, and how to make reporting a calm, repeatable workflow.
The reporting workspace stores your branding (logo, colour, footer) on-device, so every report inherits it automatically. Pick the diagnostics you ran, add a summary line, and generate. Save the report to history and you can re-export it next quarter without redoing the work.
Treat reports as a habit, not a fire drill. Schedule the diagnostics you want to monitor (DNS, SSL, blacklists, uptime) from the dashboard, review the alert feed weekly, and bundle the highlights into a monthly client report. That single rhythm is what separates a calm infrastructure practice from a reactive one.
Run through these steps in order. Each step links to the right diagnostic tool.
Pick checks for the report
Recent diagnostics appear in the builder. Tick the ones to include.
Open Report builderThe minimum useful report has four parts: who it's for, what was checked, what was found, and what to do next. Skip the raw command output — clients want the conclusion, not the transcript.
Monthly works for retainer clients. Weekly is right during incident-heavy stretches or migrations. Quarterly is fine for low-touch maintenance accounts. Set the cadence with the client up front.
Yes — that's the value. A list of green ticks isn't a report, it's a screenshot. Each finding should be paired with a status, an explanation a non-engineer can read, and a recommended next step.
PDF is best for executive sign-off. HTML is great for inline email delivery. A live dashboard suits embedded teams. Most agencies need at least PDF — it's the only format that survives forwarding.
Monitor it continuously
Save this check, get alerts on changes, and track multiple domains in one dashboard.