Awareness and Training Programs
Purpose
A plan nobody knows about is a liability. This domain distinguishes awareness from training and education, defines audiences, and establishes how competence is maintained and evidenced.
Concepts you must know
- Awareness - everyone's baseline: what the program is, how to report an emergency, where to go, what to expect. Broad, low depth, high frequency.
- Training - role-specific skill building for ERT members, BC coordinators, plan owners, crisis communicators, IT recovery staff. Higher depth, scheduled, competency-checked.
- Education - deeper professional development (certification, advanced methodology).
- Audience segmentation - all staff, new hires, contractors, executives, recovery teams, third parties.
- Delivery methods - onboarding module, intranet, posters, drills, e-learning, briefings.
- Records and competency evidence - attendance, assessments, certification dates for audit purposes.
- Refresher cadence and triggers (plan change, role change, post-exercise lessons, org change).
Traps in questions
- Treating awareness campaigns as training, or vice versa.
- Forgetting executives and third-party suppliers need training too.
- Assuming a poster counts as competency evidence.
- Omitting records - auditors ask for proof, not intent.
- Training once at launch and never again.
Rule of thumb
Awareness = everyone; training = role holders; exercise = validation. If the question asks how to prove people can perform a role, the answer is training plus a record, verified by exercise.
Worked example: A new call-tree is implemented. Awareness: announce it to all staff. Training: walk team leaders through their calling responsibilities with a practice. Validation: a notification drill measuring contact rates and time-to-acknowledge, with attendance and results recorded.