📋 GRC compliance for CMMC 2.0, CPCSC, CPA Canada, IIROC…SaaS discovery for data governanceFree enriched web chat widget🚀 Enriched remote support without your laptop

Continuity Tests

Keep a record of every tabletop exercise and recovery test, and prove your recovery plans actually work.

Where to find it
Business continuity › Continuity Tests
Who can use it
Anyone whose compliance (GRC) role includes viewing this page; recording tests and attaching evidence needs edit permission, deleting needs delete permission, and the spreadsheet export needs export permission
Plan
Resilience: Vendor Risk & Business Impact add-on
For
Everyone

What the page is for

A recovery plan nobody has tested is a guess, and proof of testing is one of the first things an auditor or insurer asks for. This page is your register of tabletop exercises, disaster recovery tests, business continuity walkthroughs, failover tests and backup restore tests.

Each record says what was tested, who took part, how long recovery actually took compared with the target from your business impact assessment, what went wrong, and when the next test is due. You can attach evidence such as a restore log, a tabletop sign-in sheet or a screen recording. Files are encrypted when they arrive and are filed as compliance evidence against the control the test supports.

The page flags any test where recovery took longer than the target (RTO missed) and any process whose latest test is past its next due date (Overdue). It also lists mission-critical processes that have never been tested.

What you see

The Continuity Tests page, with the toolbar, summary tiles, untested processes notice, test table and record a test numbered 1 to 5.
The Continuity Tests page. Numbers match the list below.
  1. Toolbar: Export XLSX and Record a test.
  2. Summary tiles: Tests recorded, Most recent test, Overdue retests and Tests that missed the RTO.
  3. Untested processes notice: mission-critical processes with no test on record.
  4. Test table: Date, Test, Process, Target RTO, Actual, Outcome, Next due and Evidence, with RTO missed and Overdue badges, plus buttons to open or delete each test.
  5. Record a test: the form for a new or existing test, including evidence upload.

How to record a test

  1. Select Record a test.
  2. Choose the Kind of test, enter a Title (for example "Q3 ransomware tabletop") and the Date of the test.
  3. Describe the Scenario (what was simulated and what the team had to do) and the Participants, including anyone who was missing but should have been there.
  4. Choose the Business process tested, or Not tied to one process. The Target RTO (hours) comes from the business impact assessment.
  5. Enter the Actual (hours) recovery time and the Outcome.
  6. Under Findings and actions, record what went wrong, what nobody knew, what will change and who owns it.
  7. Check Next test due. It defaults to twelve months after the test.
  8. Select Save.

How to attach evidence to a test

  1. Save the test first. The upload is available once the test exists.
  2. Under Evidence, choose the Control it supports (search by name, for example "backup testing").
  3. Enter an Evidence name and choose the File.
  4. Select Upload and file as evidence. Large files and screen recordings are fine.
  5. Select Close when finished.

How to edit or delete a test

  1. Select the open button on the test's row to edit it, change the details and select Save.
  2. To remove a test, select Delete on the row and confirm. Evidence already filed stays in the evidence register.

How to export the test register

  1. Select Export XLSX to download every test as a spreadsheet.

Tips

  • If recovery took longer than the target, the form warns you. Record why in the findings, and either fix the recovery or agree a new target with the process owner.
  • Test mission-critical processes first. Until they are tested, your recovery objectives are targets, not demonstrated capabilities.
  • Older tests of the same kind for the same process show as superseded, so only the latest one counts toward overdue retests.
  • Tests appear in the Continuity Testing section of the BIA Report.
  • Reminders are sent before tests fall due.

Troubleshooting

  • The upload button is greyed out. Save the test first, then attach evidence.
  • "Your GRC role does not include viewing this page." Ask an administrator to change your compliance role.
  • The Target RTO is empty. The process has no recovery target yet. Add one on Business Impact Assessment.
  • I don't see Record a test or Delete. Your compliance role does not include edit or delete permission.

Task guides that use this page

Still need help?

Search the support centre, or contact our support team and tell us which page you were on.

Names, companies, devices and figures in the pictures are examples. Other product and company names are trademarks of their respective owners.

We use privacy-friendly, cookieless analytics to count visits, and one cookie to run our live chat. Both load only if you accept. We do not use advertising trackers, and we do not profile you across other websites. The essential cookies that keep the site working are always on. See our privacy policy.