Security Officer Instruction and Training
Domain 1: Security Officer Instruction and Training
This domain tests how a protection officer instructor builds training that changes on-the-job behavior. Expect questions on the training cycle, writing learning objectives, lesson-plan structure, security-specific content, and training documentation.
Core rules
- Use a systematic cycle: assess needs, design, develop, implement, evaluate. Training starts with a performance gap, not a topic.
- Write objectives with observable action, condition, and standard. 'Understand post orders' is not measurable; 'state the three response steps for an unauthorized entry' is.
- Build each lesson plan with title, terminal and enabling objectives, materials, time, method, content outline, instructor notes, and evaluation.
- Tie content to post orders, site emergency plans, use-of-force policy, report-writing standards, and legal updates.
- Document attendance, test results, practical evaluations, and certificates; records prove due diligence.
Worked example
A site reports incomplete incident reports. The instructor writes: 'Given a written scenario and blank incident report form, the officer will complete a report that names the who, what, when, where, why, and how, lists elements of the offense, and contains no critical omissions, within 20 minutes.' The lesson then uses a sample report, guided practice, and a scored practical. The objective names the condition, behavior, and standard, so assessment is direct.
Traps that cost marks
- Objectives that use vague verbs such as know, understand, or appreciate.
- Designing training without a needs assessment or post-order review.
- Omitting evaluation or failing to keep attendance and test records.
- Teaching policy as lecture only, with no practice or feedback.