ISPS Security Drill and Exercise Log
Log quarterly security drills and annual exercises for vessels or facilities, with MARSEC level coverage, crew familiarity checks, and corrective actions tied to each deficiency.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Maritime Shipping · Port And Terminal Operations · Offshore Energy · Ship Management
Overview
This ISPS Security Drill and Exercise Log template records security drills and exercises for vessels and facilities that need to verify preparedness under changing MARSEC levels. It captures the event basics, the scenario practiced, who led it, what communications and controls were tested, how crew members performed, and what deficiencies or non-conformances were found.
Use it when you need a repeatable record of quarterly drills, annual exercises, or additional security testing required by your ship security plan or facility security plan. It is especially useful when you must show that crew members understand their assigned duties, can follow the reporting chain, and can adjust actions as the MARSEC level changes. The log also helps you document follow-up retraining and corrective actions in a way that is easy to review later.
Do not use this as a generic incident report or as a substitute for a full security plan. It is not meant for unrelated safety drills, fire drills, or maintenance checks unless those events are part of a security exercise objective. If the event did not test a defined security procedure, did not involve crew familiarity verification, or did not include a clear corrective-action path, it should not be logged here as a compliant drill or exercise record.
Standards & compliance context
- This template supports ISPS Code recordkeeping expectations by documenting drills, exercises, crew familiarity, and corrective actions in a structured way.
- The MARSEC level section helps demonstrate alignment with maritime security procedures used by vessel and facility security plans and related Coast Guard expectations.
- Where your operation also follows port, terminal, or facility security requirements, the log can support broader security management practices consistent with recognized maritime security guidance.
- If your organization uses a formal management system, the corrective-action fields can also support ISO-style non-conformance tracking and verification of closure.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Inspection Details
This section establishes the who, what, when, and under which security plan the event was conducted.
- Vessel or facility name recorded
- Drill or exercise date and time recorded
- Event type selected
- MARSEC level in effect
- Security officer or drill lead identified
-
Reference to ship security plan or exercise plan
Record the applicable SSP, drill matrix, or exercise plan reference used for this event.
Drill or Exercise Scope
This section proves the event tested a real security objective instead of a generic walkthrough.
-
Scenario matches the required security objective
Verify the scenario addresses a realistic security threat or response objective appropriate to the selected MARSEC level.
- Required security procedures were practiced
- Drill/exercise duration recorded
- Communications and notifications tested
- Security equipment or controls used during the event
Crew Participation and Familiarity
This section shows whether the people on board or on site actually know their security duties and escalation steps.
- Crew attendance documented
- Crew members demonstrated familiarity with assigned security duties
- New or relief crew received security orientation verification
- Crew could identify reporting chain and escalation steps
-
Personnel requiring follow-up retraining identified
List names or roles in a non-PII manner if needed, or describe the role-based follow-up required.
MARSEC Level Coverage
This section confirms the team practiced the right procedures for the current and higher threat levels.
- MARSEC Level 1 procedures verified
- MARSEC Level 2 procedures verified
- MARSEC Level 3 procedures verified
-
Level-specific adjustments or escalation actions documented
Capture any changes in access control, patrols, screening, communications, or response posture by MARSEC level.
Deficiencies and Corrective Actions
This section turns observations into accountable follow-up so deficiencies do not remain open after the drill.
- Deficiencies or non-conformances recorded
- Critical security deficiencies identified
-
Corrective actions assigned with owner and due date
Document the corrective action, responsible role, and target completion date.
-
Follow-up verification scheduled
Record when the corrective action will be rechecked or closed out.
How to use this template
- 1. Enter the vessel or facility name, date and time, event type, MARSEC level, drill lead, and the ship or exercise plan reference before the event starts.
- 2. Select a scenario that matches the required security objective and note the specific procedures, communications, notifications, and controls that will be tested.
- 3. Run the drill or exercise, record the duration, and document who attended and how each crew member demonstrated familiarity with assigned security duties.
- 4. Mark which MARSEC Level 1, 2, and 3 procedures were verified and describe any level-specific adjustments or escalation actions that were required.
- 5. Record each deficiency or non-conformance, assign a corrective action owner and due date, and schedule follow-up verification before closing the log.
Best practices
- Record the exact scenario and objective, not just a generic label like "security drill."
- Document communications tested by channel and recipient so you can prove the reporting chain worked.
- Capture the names of new or relief crew separately when they need orientation verification.
- Flag any security deficiency that could delay detection, reporting, access control, or escalation as critical.
- Assign one owner and one due date to each corrective action so closure does not drift across departments.
- Photograph or attach supporting evidence for equipment used, access points tested, or control failures when your process allows it.
- Verify that the drill lead references the correct ship security plan or exercise plan before the event begins.
- Close the loop by scheduling follow-up verification and documenting the result, not just the repair or retraining.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this ISPS Security Drill and Exercise Log cover?
This template records security drills and exercises for a vessel or facility under the ISPS Code framework. It captures the event details, scenario scope, crew participation, MARSEC level coverage, and any deficiencies found. It is designed to document both routine drills and larger exercises so you can show what was practiced and what needs follow-up.
How often should this log be used?
Use it for each required security drill and for the annual exercise cycle, or whenever your security plan calls for additional testing. Many operators also use it after any significant change in threat posture, staffing, or procedures. The log works best when it is completed immediately after the event while observations are still fresh.
Who should run and sign off on the log?
The security officer, vessel master, facility security officer, or designated drill lead should complete the log, depending on your plan and operating model. The person running the event should also confirm attendance, observed performance, and any deficiencies. If your process requires it, a second reviewer can verify corrective actions and closure.
Does this template help with MARSEC Level 1, 2, and 3 requirements?
Yes. The template includes a dedicated section to confirm which procedures were verified at MARSEC Levels 1, 2, and 3 and to note any level-specific escalation actions. That makes it easier to show that your team is not only drilling routine procedures but also understanding how actions change as the security posture changes.
What are the most common mistakes when using a security drill log?
The most common mistake is writing a vague summary instead of documenting the exact scenario, duration, communications tested, and equipment used. Another issue is failing to identify who needs retraining after a missed step or weak response. Teams also sometimes record the drill but forget to assign an owner and due date for each corrective action.
Can this log be customized for a vessel, terminal, or offshore facility?
Yes. You can tailor the scenario list, security equipment references, reporting chain, and escalation steps to match the ship security plan or facility security plan. The structure is flexible enough for a vessel, port facility, terminal, or other regulated operation, as long as you keep the required evidence fields intact.
How does this compare with an ad hoc drill note or email recap?
An ad hoc note usually misses the details auditors and inspectors look for, such as MARSEC level context, crew familiarity verification, and follow-up ownership. This template standardizes those fields so each event is documented the same way. That makes trend review, corrective action tracking, and audit preparation much easier.
Can this log connect to corrective action tracking or training records?
Yes. The corrective action section is built to feed directly into a CAPA or issue-tracking workflow, and the crew familiarity section can point to training or orientation records. Many teams link the log to incident management, LMS, or compliance systems so retraining and verification do not get lost after the drill.
Related templates
Go deeper on the topic
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
See how bank branch managers use MangoApps scheduling to fill shifts, communicate policy updates, and eliminate last-minute coverage chaos.
-
See how connected 1:1 tracking, employee audit history, and LMS completion records turn scattered processes into verifiable workforce documentation.
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
-
MangoApps in Okta Integration Network automates user provisioning, SSO, and access management for stronger security and less admin work.
Ready to use this template?
Get started with MangoApps and use ISPS Security Drill and Exercise Log with your team — pricing built for small business.
