How to use this planner
Three steps. Restore into a test location — never over your live data.
1. Name the test
Enter the business, the person running the test and the date below. Names and dates only — never type a password, a backup encryption key or a recovery code into this page. The planner records that a test happened and what it found, never the secrets that protect the backup.
2. Work the data sets top to bottom
Money records come first because they are the hardest to rebuild. For each data set, restore into a separate test folder, spare computer or the backup tool’s restore area — never over the live copy — then open at least three real items from the restored copy and check they are complete and readable. Check an item only when it is actually done.
3. Print the record and set the next test date
Print or copy the dated summary and keep it where the owner controls it. Any gap you found gets a fix date in that data set’s notes — and that one data set gets re-tested within days, not at the next routine test.
Privacy: this tool runs entirely on your device. Nothing you type or check is uploaded, stored on a server, or shared. Closing the tab clears it — print your record before you close it.
What this planner does not do: it does not connect to your backup tool and cannot verify any copy. It records what you mark as done. Backups are layer three of seven — not a certification, not a guarantee, and not legal or security advice.
The 4 checks, for every data set
The same four checks repeat for all 5 data sets (20 items in total):
1. A current backup copy exists outside the device it lives on — cloud, off-site drive or second location — and its date is recorded. · 2. The restore went into a separate test location; live data was not overwritten. · 3. At least 3 real items were opened from the restored copy and checked complete and readable — not just file names. · 4. Every gap found was written in the notes with a fix date — or “no gaps found” was written.
The planner
Progress updates as you check items off. 5 data sets × 4 checks = 20 items.
The example is fictional template data, marked as an example — replace every field with your own before you print.
0 of 20 items done — not started yet.
Start with data set 1. Money records are the hardest to rebuild from memory — test them first.
Your dated record
The printed record lists, data set by data set, where the backup lives, when it was made, the test result, what is done and what is still open, with your notes. Keep it with your other business records — it is the proof the test happened, and the list to re-run every few months.
Not sure your other layers would hold up either?
Backups that actually restore are the third of the seven layers in the CyberShield audit — a written $99 review of your business’s public-facing setup and questionnaire answers, with no passwords or account access needed. Every weak spot, how risky it is, and what to fix first, in plain English. If you want the fixes done for you, the report quotes the done-for-you Setup (from $299) before you decide; the Care Plan is $49/month if you want monthly check-ins after that. Full refund if we have not started the work; once work has begun, payments are non-refundable, as described in our Refund Policy.
Start with the free 2-minute cyber checklist, read how backups fit the full picture in the ransomware prevention guide, or go straight to the audit:
Start the $99 auditCommon questions
Is my data uploaded anywhere?
No. This planner runs entirely in your browser. Business names, dates and checkmarks never leave your device. Never type a password, a backup encryption key or a recovery code into this page — it records that a test happened and what it found, never the secrets that protect the backup.
What counts as a passed restore test?
A pass means three things all happened: a copy was restored into a separate test location without touching the live data, at least three real items from the restored copy were opened and checked complete and readable, and the result was written down with a date. A backup job that reports 'success' is not a test — opening real files from the restored copy is the test.
How often should we test a restore?
Test the data set you would miss first — usually money records — at least every few months, and again after you change backup tools, computers or staff roles. This planner does not set a legal schedule; it gives you a dated record each time so the habit is visible.
What if the restore fails or files are missing?
That is the test working, not the test failing you. Write the exact gap in that data set's notes with a fix date, fix the backup (a fresher copy, a second location, a different tool), and re-test that one data set within days — not at the next routine test.
Should we overwrite our live data to test?
No. Always restore into a separate folder, a spare computer or the backup tool's test/restore area first. Overwriting live data to 'test' can turn a healthy business file into the damaged copy. Only replace live data during a real recovery, after the restored copy has been checked.
Does completing this planner prove our backups are good?
No. The planner records what you mark as done; it does not connect to your backup tool and cannot verify a copy itself. Opening real items from the restored copy is your proof for that data set, on that date. Backups are layer three of seven in a basic small-business checkup, not a certification and not a guarantee.