How a backup compliance score is calculated
Count your protected objects: each mailbox, OneDrive, SharePoint site, Team, each Google Workspace user’s Gmail, Drive, Calendar and Contacts, and each QuickBooks company. Then count how many were backed up within the 24-hour backup SLA. Divide the second number by the first.
Each service gets its own score the same way, so you can see where a problem sits. In this example (illustrative figures, from the demo organisation on our homepage), 129 of 139 objects backed up on time:
| Service | Protected objects | Backed up within 24 hours | Score |
|---|---|---|---|
| Microsoft 365 mailboxes | 50 | 43 | 86% |
| Microsoft 365 OneDrive | 54 | 52 | 96% |
| Microsoft 365 SharePoint | 17 | 16 | 94% |
| Microsoft 365 Teams | 16 | 16 | 100% |
| QuickBooks | 2 | 2 | 100% |
| Overall | 139 | 129 | 93% |
Why score objects, not backup jobs
A backup job that reports success tells you the job ran. It doesn’t tell you which mailboxes, drives or sites inside it were protected, or how recently. Scoring every object against the same 24-hour window answers both questions, and names anything that missed it.
What the score doesn’t prove
A 100% score means every protected object was backed up within the last 24 hours. That’s the precondition for a restore, but it isn’t the same as a restore. The NCSC advises testing your backups regularly and knowing how to restore files before you have to do it for real (10 Steps: Data security), and checking that a backup contains all your important data (Backing up your data).
Reading the score in the Daily Backup Report
The CloudVision Daily Backup Report arrives every morning and puts the score in context:
- A one-line headline, such as how many objects need attention today.
- Your overall compliance score and how it moved since yesterday.
- Compliant, non-compliant and total protected objects.
- Results by service, each with its own score.
- Every failing object by name, grouped by service.
- The full data as a CSV, attached to every email.
Using the score for audits, insurers and the board
Every daily report is kept in your CloudVision portal. You can filter by the last 30 days, this quarter, this year or all time, show only the days below 100%, and export to PDF or Excel when an auditor, a cyber insurer or your board asks what was protected and when.
Below 100%, we fix it
Anything that misses the 24-hour backup SLA is listed by name in the report, and our UK team picks it up and fixes it, 24/7. You see the result in your dashboard and in the next morning’s report. See the CloudVision Daily Backup Report.
Backup compliance scores: common questions
How is a backup compliance score calculated?
Divide the number of protected objects backed up within the 24-hour backup SLA by the total number of protected objects. If 129 of 139 objects backed up on time, the score is 93%. Each service gets its own score the same way.
What is a good backup compliance score?
100%: every protected object backed up within the 24-hour backup SLA. Anything lower means specific objects missed the window. The CloudVision Daily Backup Report lists each one by name, and our UK team fixes them, 24/7.
Does a 100% score mean my data can be restored?
It means every protected object was backed up within the last 24 hours, which is the precondition for a restore. The NCSC also advises testing that you can restore from your backups before you need to.
Why did my compliance score drop?
Because one or more objects missed the 24-hour backup SLA. The report shows how the score moved since yesterday and lists every failing object by name, grouped by service.
Sources used in this guide
This guide is general information, not legal or insurance advice. Requirements and product limits change, so check the linked sources and your own policies, and take professional advice where needed.