Skip to main content
Get started
Back to all examples
Compliance & RiskComplianceSchools and multi-academy trusts
Compliance training examplesTraining examples for universities & schoolsCyber security training examples
C

Example detail

Stored learning example with evidence status below

School Staff Cybersecurity and Data Protection Refresher

A phishing and pupil-data-protection refresher example for secondary school staff. Its UK GDPR and school-policy references need qualified review before use.

Structure

14

Screens with 8 interactive checkpoints

Difficulty

Intermediate

About 25 minutes, estimated from the example data

Delivery

Preview

Interactive learner preview and on-demand SCORM 2004 package

What this example proves

ComplianceEnglish contentStored generator-pipeline exampleCapture date not recordedSubject-matter approval not recordedSame creator toolkit on standard plans; release controls apply

Section types in this stored example: context, question, reading, flashcard, decision, feedback. Later edits not independently recorded. SCORM 2004 generated on download request; no per-example lms test recorded. Preview and package creation do not establish learner outcomes.

Try this exampleGenerate something like this
C

Interactive preview

Compliance · 14 sections · Fully interactive

Answered
0/8
Correct
0
Time
0:00

Urgent Request Before Parents' Evening

Scenario
2 min
At 3:40 pm, a teacher receives an email that appears to be from the deputy head, marked urgent before parents' evening. It asks for a spreadsheet of pupil contact details and attendance concerns to be sent immediately, using a reply address the teacher does not recognise. In schools, a rushed response to an unusual request can expose personal data before anyone notices the warning signs.
  • Urgency is a common manipulation tactic.
  • Unusual requests for pupil data need extra checking.
  • Sender, links, and requested action should all be verified.

Legitimate school emails vs phishing cues

Use these clues together. A phishing message often combines urgency, unusual requests, and links or attachments that do not fit normal school practice.

Side-by-side comparison of Legitimate cue, Phishing red flag across 5 criteria. Sender: Legitimate cue: Recognisable school domain; Phishing red flag: Lookalike or external address. Tone: Legitimate cue: Routine and specific; Phishing red flag: Urgent pressure to act now. Links: Legitimate cue: Known school system URL; Phishing red flag: Mismatched or shortened link. Request: Legitimate cue: Normal role-based request; Phishing red flag: Asks for bulk pupil records. Attachments: Legitimate cue: Expected file type/context; Phishing red flag: Unexpected file or password.
Side-by-side comparison of Legitimate cue, Phishing red flag across 5 criteria. Sender: Legitimate cue: Recognisable school domain; Phishing red flag: Lookalike or external address. Tone: Legitimate cue: Routine and specific; Phishing red flag: Urgent pressure to act now. Links: Legitimate cue: Known school system URL; Phishing red flag: Mismatched or shortened link. Request: Legitimate cue: Normal role-based request; Phishing red flag: Asks for bulk pupil records. Attachments: Legitimate cue: Expected file type/context; Phishing red flag: Unexpected file or password.

Prompt in

Create a compliance refresher for secondary school staff on identifying phishing emails, protecting pupil data, handling device security, and reporting a suspected data breach. Make it practical, policy-aware, and suitable for non-technical staff.

Inside this example

What the stored output shows

Audience fit

Curated for schools and multi-academy trusts with a intermediate learning curve.

Interaction mix

8 interactive checkpoints across context, question, reading, flashcard, decision, feedback.

Example structure

A four-line brief became a 14-section package: a phishing scenario opener, a six-card flashcard deck, eight scored questions across six response modes, a breach-response timeline, and a branching lost-USB decision with an 80% pass mark.

Delivery format

SCORM + hosted plus a reusable prompt seed for your review workflow.

Learning objectives

Understand the key principles of phishing email warning signs
Identify critical aspects of protecting pupil personal data
Apply secure device use in school concepts in practice
Demonstrate awareness of suspected data breach reporting requirements

Section walkthrough

What the learner sees

Navigate through sections using the interactive preview above.14 screens with 8 interactive checkpoints.

Regulation context

Compliance references carried into the output

UK GDPR Article 5(1)(f) integrity and confidentiality; Data Protection Act 2018; school information security policy
UK GDPR Article 5(1)(c) data minimisation and Article 5(1)(f) integrity and confidentiality; Keeping Children Safe in Education principles
UK GDPR Article 5(1)(f) integrity and confidentiality; school acceptable use and device security policy
UK GDPR Article 32 security of processing; UK GDPR Article 5(1)(f); school clean desk and device policy
UK GDPR Articles 33 and 34 breach response duties; school data breach reporting procedure
UK GDPR Article 33 personal data breach notification; school breach management procedure
UK GDPR Article 5(1)(f) integrity and confidentiality; school cyber incident and acceptable use policy
UK GDPR Articles 5, 32, and 33; school data protection and information security policies

Related examples

Keep browsing adjacent use cases.

View the full gallery
Preview screenshot of the Food Allergen Awareness for Front-of-House Staff: UK Practical Quiz example
Compliance & RiskQuiz

Food Allergen Awareness for Front-of-House Staff: UK Practical Quiz

A twelve-section UK allergen awareness quiz example for front-of-house teams. Review its legal references and current local procedures before training staff.

8 scored questions6 response modes80% pass mark
Preview screenshot of the Quarterly Cybersecurity Briefing: Phishing, MFA Fatigue, and Safe Hybrid Working example
Compliance & RiskPresentation

Quarterly Cybersecurity Briefing: Phishing, MFA Fatigue, and Safe Hybrid Working

An estimated 20-minute cybersecurity briefing example with scored checkpoints on phishing, MFA fatigue, hybrid working, password managers and incident reporting.

6 scored checks5 visual sections80% pass mark

Build your own version

Start from this prompt and make it yours.

Use this as an illustrative starting point, then generate and review a version tailored to your team, policy context and delivery workflow.

Get started free