The DR report your customer actually reads

TL;DR

The monthly DR report your customer actually reads is one page: 5 charts, 1 table, 3 paragraphs. Everything else goes in the appendix.

Main page structure

Top: 3 dominant KPIs

Large, readable in 3 seconds:

• Month uptime (e.g. 99.98%);
• Backups executed / scheduled (e.g. 124/124);
• Average RTO in drills (e.g. 11 min).

Middle: 5 charts

• month-over-month uptime line (12-month rolling);
• bar chart of backups executed / with errors;
• current retention distribution;
• average drill restore times;
• protected data volumes per workload.

Bottom: events table

| Date | Event | Class | Resolution | |---|---|---|---| | 04/03 | Backup failed DB02 | warning | retry OK 06:00 | | 12/03 | ERP partial drill | drill | RTO 9 min, OK |

Sidebar: 3 commentary paragraphs

1. What went well (1 sentence).
2. What to watch (1-2 sentences).
3. Next actions (planned drills, stack changes).

What does NOT go on the main page

• detailed technical logs (in appendix);
• list of all VMs (console link);
• multi-year trend analysis (in appendix).

The IT director reads the main page. The internal sysadmin reads the attachments.

Cadence that works

• weekly: 3 KPIs + event table (short, automatic format);
• monthly: full report (manual or semi-automatic);
• quarterly: report with attached drill record;
• annual: RTO/RPO objective review + recommendations.

Tools to generate it

• Sefthy Console: structured monthly and quarterly PDF;
• CSV export for customer BI integration;
• APIs for custom dashboards.

FAQ

How long to generate the monthly report?

With automation: 30 minutes per customer. Without: 2-3 hours.

Should it be customised per customer?

Logo and palette yes, structure no. The standard structure is the value.

For DR + monitoring bundle, Bundle DR + monitoring. For differentiation, Differentiate with managed DR.