Loading...
compliance

ISPS Ship Security Plan Implementation Audit

Audit the Ship Security Plan implementation on board a vessel, from access control and restricted areas to security equipment readiness and SSO duties. Use it to verify SOLAS Chapter XI-2 compliance and document gaps before they become findings.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Maritime Shipping · Passenger Ferries · Offshore Support Vessels · Port Operations

Overview

This audit template is for verifying that a vessel’s approved Ship Security Plan is being implemented as written on board. It walks through the inspection details, plan execution, Ship Security Officer duties, access control, restricted areas, security equipment, and final sign-off so you can document what was observed, what was missing, and what needs correction.

Use it when you need a practical shipboard audit for ISPS compliance, internal verification, or preparation for a company, flag, or port security review. It is especially useful after crew changes, security level changes, equipment faults, repeated access-control issues, or a security incident. The template helps you confirm that watchstanding assignments are posted, drills are current, records are legible and retained, and deviations from the plan are approved and traceable.

Do not use this as a generic safety checklist or as a substitute for the actual Ship Security Plan. It is not meant for cargo handling, navigation, or general ship condition inspections. It also should not be used to judge security performance without access to the approved plan, current security level requirements, and the vessel’s recordkeeping procedure. If the vessel has unique restricted areas, local port conditions, or company-specific controls, those should be added before use so the audit reflects the ship’s real operating environment.

Standards & compliance context

  • This template supports verification against SOLAS Chapter XI-2 and the ISPS Code by checking whether the approved Ship Security Plan is actually being followed on board.
  • Use it alongside company procedures and flag-state expectations for ship security officers, access control, restricted-area protection, and security record retention.
  • Security equipment checks should align with the vessel’s maintenance and testing program and any applicable maritime safety or security guidance from the flag, class, or port authority.
  • If the vessel operates in ports with additional local requirements, include those controls in the template so the audit reflects the authority having jurisdiction.
  • Where drills, incident response, or communications are reviewed, confirm the process matches the approved plan and any applicable industry security guidance rather than informal practice.

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 vessel, timing, and plan revision so the audit is tied to the correct ship and current security baseline.

  • Vessel name and IMO number recorded (weight 2.0)
  • Date, time, and location of audit recorded (weight 2.0)
  • Ship Security Officer identified and available for audit (critical · weight 3.0)
  • Current Ship Security Plan revision verified (critical · weight 3.0)

Ship Security Plan Implementation

This section checks whether the approved plan is being followed in practice, including duties, drills, records, and approved deviations.

  • Security measures in the Ship Security Plan are implemented as written (critical · weight 6.0)
  • Security duties and watchstanding assignments are posted and followed (critical · weight 5.0)
  • Security drills or exercises are conducted at the required frequency (critical · weight 5.0)
  • Security records are current, legible, and retained per procedure (weight 4.0)
  • Any deviations from the Ship Security Plan are documented and approved (critical · weight 5.0)

Ship Security Officer Duties

This section verifies that the SSO can explain and carry out current security responsibilities, not just hold the title.

  • SSO understands and can explain current security level requirements (critical · weight 5.0)
  • SSO verifies access control measures at all entry points (critical · weight 5.0)
  • SSO monitors restricted areas and responds to unauthorized access attempts (critical · weight 5.0)
  • SSO maintains communication with the Company Security Officer and Master (weight 3.0)
  • SSO logs security concerns, incidents, and corrective actions (weight 2.0)

Access Control and Restricted Areas

This section focuses on the first line of defense: who can board, who can enter restricted spaces, and how unauthorized access is handled.

  • All access points are controlled by authorized personnel or approved systems (critical · weight 6.0)
  • Visitor identification is checked and recorded before boarding (critical · weight 5.0)
  • Crew and contractor credentials are valid and visibly displayed where required (weight 4.0)
  • Restricted areas are clearly marked and physically secured (critical · weight 5.0)
  • Unauthorized access attempts are detected, recorded, and escalated (critical · weight 5.0)

Security Equipment and Monitoring

This section confirms that alarms, CCTV, lighting, and related monitoring tools are operational and supported by current maintenance records.

  • CCTV, alarms, lighting, and other security equipment are operational (critical · weight 5.0)
  • Security equipment maintenance and testing records are available (weight 3.0)
  • Restricted-area monitoring is continuous or performed at required intervals (critical · weight 4.0)
  • Any security equipment deficiencies are reported and tracked to closure (weight 3.0)

Emergency Response and Sign-off

This section captures whether crew understand the response actions and records the formal closeout of the audit.

  • Security incident response actions are understood by crew on duty (critical · weight 2.0)
  • Inspector signature captured (weight 1.0)
  • Master or authorized representative acknowledgment captured (weight 2.0)

How to use this template

  1. Enter the vessel name, IMO number, audit date, location, and current Ship Security Plan revision before starting the walkthrough.
  2. Confirm the Ship Security Officer is available and review the current security level, recent drills, and any known deviations from the plan.
  3. Walk the vessel in sequence from access points to restricted areas to security equipment, recording only observable conditions and supporting evidence.
  4. Mark each non-conformance, deficiency, or unauthorized access issue with a clear description, responsible party, and required follow-up action.
  5. Capture the Master or authorized representative acknowledgment, then route open items to the Company Security Officer or assigned owner for closure.
  6. Review recurring findings after the audit and update local procedures, training, or maintenance tasks where the same gap appears more than once.

Best practices

  • Verify the current Ship Security Plan revision before you inspect any controls, because an outdated revision can make otherwise correct actions look non-compliant.
  • Check access points in the order a person would actually board the vessel, so you can see whether controls work in real use rather than only on paper.
  • Ask the Ship Security Officer to explain the current security level and response expectations in plain language, then compare that explanation to the posted procedures.
  • Photograph or otherwise capture evidence of each deficiency at the time it is found, especially for broken locks, missing logs, or unsecured restricted areas.
  • Separate security-critical findings from administrative issues so urgent access-control or monitoring failures are escalated immediately.
  • Confirm drill records, maintenance logs, and incident logs are legible, current, and retained according to the vessel’s procedure before you close the audit.
  • Treat any undocumented deviation from the Ship Security Plan as a finding until you can verify approval and compensating controls.

What this template typically catches

Issues teams running this template most often surface in practice:

Visitor identity is checked at the gangway but not recorded consistently in the access log.
Crew or contractor credentials are valid but not visibly displayed where required by the ship’s procedure.
Restricted areas are marked on the plan but not physically secured or monitored at the point of entry.
Security watchstanding assignments are posted, but the actual watch routine does not match the posted assignment.
Security drills were performed, but the records are incomplete or do not show the required frequency.
CCTV, alarms, or lighting are installed but have no current maintenance or test record available during the audit.
Unauthorized access attempts were handled verbally, but the incident and corrective action were not logged.
A deviation from the Ship Security Plan was followed in practice without documented approval.

Common use cases

Fleet Compliance Manager — Passenger Ferry
Use this audit to verify boarding controls, visitor handling, and restricted-area protection before a busy port rotation. It helps the compliance team confirm that the Ship Security Plan matches day-to-day practice on a vessel with frequent passenger movement.
Ship Security Officer — Cargo Vessel
Use this template during a routine shipboard security review to confirm access control, watchstanding, and incident logging are working as written. It gives the SSO a structured way to document deficiencies before a port call or company inspection.
Port State Preparation Lead — Offshore Support Vessel
Use the audit to check security equipment readiness, restricted-area controls, and current records before arrival in a higher-risk port. It helps identify gaps that could trigger questions during an external inspection.
Company Security Officer — Mixed Fleet
Use this template to compare implementation across multiple vessels and spot recurring non-conformances in access control, drills, or deviation approvals. It creates a consistent audit trail that supports fleet-wide corrective action.

Frequently asked questions

What does this ISPS Ship Security Plan Implementation Audit cover?

This template is built to verify whether the Ship Security Plan is being followed on board, not just whether it exists on paper. It covers inspection details, plan implementation, SSO duties, access control, restricted areas, security equipment, and emergency response sign-off. Use it to capture observable evidence of compliance, deviations, and corrective actions. It is designed for vessel audits under the ISPS framework and SOLAS Chapter XI-2.

When should this audit be run?

Run it during scheduled internal audits, pre-arrival security checks, post-incident reviews, or before a flag, port state, or company security review. It also fits after changes to crew, routes, security level, or security equipment. If the vessel has had repeated access-control issues or a security drill failure, this audit helps confirm whether the Ship Security Plan is still being implemented as written. Many operators use it as part of a recurring compliance cadence rather than only after a problem.

Who should complete this audit?

A qualified auditor, the Ship Security Officer, a company compliance lead, or another authorized representative can complete it, depending on your internal procedure. The person running it should understand the vessel’s security plan, current security level requirements, and how access control and restricted-area controls are supposed to work. The Master or authorized representative should review and acknowledge the results. If the SSO is being audited, the audit should still preserve independence where your process requires it.

How does this relate to SOLAS and ISPS requirements?

This template supports verification of implementation under SOLAS Chapter XI-2 and the ISPS Code framework. It is also useful for checking whether shipboard security measures, drills, records, and reporting practices match the approved Ship Security Plan. The template does not replace the plan or the regulatory text; it helps you document whether the vessel is actually following them. That makes it useful for internal compliance and for preparing for external inspection.

What are the most common mistakes this audit catches?

Common findings include access points left uncontrolled, visitor logs incomplete, credentials not visibly displayed, and restricted areas not clearly marked or physically secured. Auditors also frequently find outdated security records, missed drill frequency, and security equipment that is installed but not tested or maintained on schedule. Another frequent issue is undocumented deviations from the Ship Security Plan. This template helps surface those gaps in a structured way.

Can I customize this template for different vessel types or routes?

Yes. You can tailor the access-control checks, restricted-area list, equipment checks, and evidence fields to match the vessel type, operating area, and company procedures. For example, a passenger vessel may need more emphasis on boarding controls and visitor management, while a cargo vessel may focus more on restricted spaces and watchstanding. You can also add company-specific security level triggers, local port requirements, or additional sign-off fields.

How often should security drills or exercises be checked with this audit?

Use the template to verify that drills or exercises are being conducted at the frequency required by the Ship Security Plan and applicable security procedures. The exact cadence should come from the vessel’s approved plan and company policy, so the audit should confirm both the schedule and the recorded evidence. If a drill was delayed, the audit should capture the reason and any corrective action. That helps distinguish a one-time delay from a recurring non-conformance.

What should I do if I find a deviation from the Ship Security Plan?

Record the deviation clearly, note who approved it, and document any compensating controls or corrective actions. A good audit trail should show whether the deviation was temporary, how long it remained in effect, and whether it affected access control, monitoring, or response readiness. If the deviation creates a security gap, escalate it through the Master and Company Security Officer immediately. This template is designed to make that follow-up easy to track.

Go deeper on the topic

Related concepts
  • 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...
Related guides

Ready to use this template?

Get started with MangoApps and use ISPS Ship Security Plan Implementation Audit with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?