Port State Control Pre-Arrival Readiness Checklist
Use this pre-arrival checklist to verify certificates, fire safety, life-saving appliances, and record books before port state control inspection. It helps the master and DRI catch PSC deficiencies early and reduce detention risk.
Trusted by frontline teams 15 years of frontline software
Built for: Maritime Shipping · Port Operations · Ship Management · Offshore Operations
Overview
This template is a Port State Control pre-arrival readiness checklist for the 24–48 hours before a vessel reaches port. It is built to help the master and designated crew verify the items PSC officers commonly inspect first: statutory certificates, fire safety equipment, life-saving appliances, record books, and other readiness points that can trigger a deficiency or detention if they are missing, expired, or not serviceable.
Use it when you need a structured final review before arrival, after maintenance, after crew changes, or before entering a port known for close inspection. It works best as a simple, repeatable gate with clear verification steps, so each checklist item can be answered yes, no, or N/A without ambiguity. If a check fails, the item should be marked blocking and assigned to the right DRI for correction or escalation.
Do not use this template as a substitute for routine onboard safety rounds, class surveys, or the vessel’s full SMS procedures. It is also not the right tool for broad voyage planning or cargo operations. Its purpose is narrower: confirm that the vessel is inspection-ready before arrival and capture the common gaps that lead to PSC findings. If you need a post-inspection corrective action tracker, pair this checklist with a remediation task list so findings do not get lost after the pre-arrival review.
Standards & compliance context
- This template supports PSC readiness aligned with flag-state, class, and port inspection expectations, but it does not replace the vessel’s required statutory procedures.
- Checklist items should be written so each verification step can be answered clearly and evidenced during an inspection record review.
- Use critical priority only where a failed item could affect safety or compliance, such as expired certificates or unserviceable emergency equipment.
- If the vessel operates under an SMS or ISM-based workflow, keep the checklist linked to the corrective action process so deficiencies are tracked to closure.
- When local port guidance or regional inspection focus differs, customize the checklist to match the vessel’s actual regulatory exposure.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Create the checklist 24–48 hours before ETA and assign a single DRI for the overall review, with item-level owners for deck, engine, safety, and documents.
- Add checklist items for the vessel’s current PSC risk areas, including certificates, fire safety, life-saving appliances, record books, alarms, and any recent maintenance work.
- Run each checklist item as an independently verifiable yes/no/N/A check and attach evidence such as a document reference, test result, or photo when a defect is found.
- Mark any failed item as blocking, assign the corrective action to the responsible crew member or shore contact, and set a clear follow-up verification step before arrival.
- Review the completed checklist with the master, confirm all critical items are closed or formally risk-accepted, and keep the record available for the inspection team.
- After arrival, update the template with any PSC findings so the next voyage starts with the latest deficiency patterns and recurring issues already captured.
Best practices
- Keep each checklist item atomic, such as verifying one certificate or one appliance condition, so a failed answer points to a single fix.
- Use normal priority for routine readiness checks and reserve critical only for items with direct safety or compliance impact.
- Record the exact document name, expiry date, or equipment location in the verification step so the next reviewer can confirm the same item quickly.
- Treat missing evidence as a failed check, not a pass based on verbal confirmation from another watchstander.
- Escalate any expired statutory certificate or inoperable lifesaving equipment immediately, because those findings can become blocking at the berth.
- Separate non-blocking housekeeping issues from blocking compliance gaps so the crew focuses first on detention-risk items.
- Review recent PSC deficiency trends for the vessel class and port region before customizing the checklist for the next voyage.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this Port State Control Pre-Arrival Readiness Checklist cover?
This template covers the 24–48 hour pre-arrival review a vessel uses to prepare for a port state control inspection. It focuses on certificates, fire safety equipment, life-saving appliances, record books, and other common deficiency areas that PSC officers check first. It is meant to surface issues before arrival so the crew can correct them or escalate them to shore support.
How often should this checklist be run?
Run it once before each port arrival, typically within 24–48 hours of ETA. If the vessel is entering a higher-scrutiny port, has had recent maintenance, or is carrying out a crew change, it is worth repeating after any major status change. The checklist is not meant to replace routine onboard inspections; it is a pre-arrival readiness gate.
Who should own and complete this checklist?
The master usually owns the final review, with the chief officer, chief engineer, or designated DRI completing the relevant checklist items. The right owner depends on the vessel and the item type: deck, engine, safety, or document control. The key is to assign one accountable person for follow-up so findings do not stay blocking without action.
Is this template useful for regulatory compliance?
Yes, it is designed around the kind of evidence PSC officers expect to see during an inspection. It supports a compliance workflow by prompting verification of valid certificates, maintained safety equipment, and complete records. It does not replace the applicable flag-state, class, or company procedures, but it helps the crew prepare against them in a structured way.
What are the most common mistakes this checklist helps prevent?
Common misses include expired or unavailable certificates, missing entries in logbooks, unserviceable fire extinguishers, defective emergency lighting, and life-saving appliances that are not ready for immediate use. Another frequent issue is assuming a task is complete without a verification step, such as checking the actual document or equipment rather than relying on memory. This template helps turn those checks into independently verifiable checklist items.
Can I customize the checklist for different vessel types or ports?
Yes, and you should. A tanker, bulk carrier, container ship, or passenger vessel may need different focus areas, and some ports or regions emphasize specific deficiency patterns. You can add or remove checklist items, adjust the recurrence, and map items to the vessel’s actual PSC exposure without changing the overall pre-arrival structure.
How does this compare with an ad-hoc pre-arrival review?
An ad-hoc review depends on memory and informal handoffs, which makes it easy to miss a document, a test status, or a follow-up action. This template creates a repeatable checklist with clear yes/no/N/A verification steps, so the crew can track what was checked and what still needs attention. That makes the review easier to assign, audit, and repeat voyage after voyage.
Can this template connect to other operational workflows?
Yes. It works well alongside maintenance, corrective action, and document-control workflows, especially when a failed item needs a blocking follow-up before arrival. Teams often link it to a Kanban board for remediation, or to an ITIL-style runbook for escalation when a deficiency needs shore-side support. The checklist itself is the readiness gate; the linked workflow handles the fix.
Related templates
Go deeper on the topic
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
Compliance is the practice of ensuring employee behavior meets regulatory, contractual, and internal-policy requirements — and of producing the evidence to...
-
Compliance training automation is the software-driven process for assigning, tracking, and evidencing required training (HIPAA, harassment prevention,...
-
HR case management is a structured system for handling employee questions, requests, and issues — with routing, SLAs, an audit trail, and a knowledge base...
Ready to use this template?
Get started with MangoApps and use Port State Control Pre-Arrival Readiness Checklist with your team — pricing built for small business.
