Your yearly testing plan

Set your tests per year and audit period, then read what ran, who was covered, which teams were missed and when the next test is due.

The page titled Compliance and yearly plan shows what you committed to, what ran in the audit period, who was covered, and when the next test is due. Its address is /red-team/compliance. The numbers come from your campaigns and their calls.

The auditor pack is evidence that supports the controls you chose. It is not proof of compliance. The page says so at the bottom.

​

Before you start

• At least one campaign that has run. See Build a campaign.
• Your audit period and the number of tests a year you promised your auditor or insurer.

​

Steps

1. Set the compliance settings

   Open the settings page titled Fair testing and scroll to Compliance and audit period. The Frameworks and audit period button on the plan page goes straight there.

   Field	What to enter	Limits and defaults
   Frameworks you answer to	Tick the frameworks the auditor pack should map to	None ticked
   Audit period starts	First day of the period your auditor or insurer looks at	Empty
   Audit period ends	Last day. Leave both empty to use the last 12 months	Empty
   Tests per year	How many tests you committed to. The help text says: “Reviewers usually expect two.”	1 to 12. Default 2
   Signatory name and Signatory role	Who signs the pack for your organisation	Empty

   Click Save compliance settings.

2. Open the plan

   Open Red Team, then the page Compliance and yearly plan. The Audit period card shows the dates and the frameworks, then four numbers.

   Number	What it means
   Tests committed	Tests per year scaled to the length of the period, at least 1
   Tests run in the period	Campaigns that completed, are in progress or are paused, whose start date falls in the period
   Staff reached at least once	The share of your active people who answered a test call in the period, with the count in brackets
   Next test due	The period start, or the last test, plus the period length divided by the tests committed. It reads Next test was due in red when overdue, and Next due (period complete) once the committed number has run

   The note under them: “Coverage counts a person once they answered a test call in the period.”

3. Read the rest of the page

   Section	What it shows
   Next test	A template picker and Schedule the next test, which opens the wizard from that template. Any retests already planned are listed with their date
   Tests run in the period	One row per campaign: name, date, status, people called, people reached, and the retest date or not planned
   Teams with no test in the period	Each team where nobody was reached, with how many people are in it. A green line reads “Every team had at least one person reached in the period.” when there are none

4. Schedule the next test

   Pick a template and click Schedule the next test. The wizard opens with the set-up filled in. Pick the people and the date, then record the authorisation. See Save and reuse a campaign template.

​

Retests

A retest date is set on a campaign when you build its auditor pack. It appears on the plan under Next test and in the Retest column. See Export for auditors.

​

What happens next

The plan updates itself from your campaigns. Run the next test before the due date and the coverage rises. Teams drop off the gaps list once one person in them answers a call.

​

Problems

The period says the last 12 months

No audit period is set. Set Audit period starts and Audit period ends on the Fair testing page to match your auditor.

Coverage is low although everyone was called

Coverage counts people who answered and talked. No answer, voicemail and failed calls do not count. The line under the numbers shows how many were called at all.

A team shows as Team not recorded

Those people have no department on their contact. Add one under Add the people you will call.

It says No saved templates yet

Schedule the next test opens a blank wizard. Save a campaign as a template to reuse it next time.