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 entry. 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 · Marine Compliance
Overview
This template is a Port State Control pre-arrival readiness checklist for the master and shipboard team to run 24–48 hours before reaching port. It focuses on the items PSC inspectors commonly ask for first: statutory certificates, fire safety equipment, life-saving appliances, navigation and pollution-prevention records, and any known deficiencies that could trigger detention or a follow-up inspection.
Use it when you want a repeatable pre-arrival verification step instead of relying on memory, email chains, or a last-minute walk-through. It is especially useful after maintenance periods, crew changes, document renewals, or any voyage where a prior deficiency has not yet been fully closed. The checklist helps separate blocking issues, which must be fixed or escalated before arrival, from non-blocking items that can be monitored or documented.
Do not use this template as a substitute for class surveys, flag-state compliance programs, or a full safety management system audit. It is also not the right tool for cargo operations, customs clearance, or berth readiness unless you intentionally add those items. The value of the template is its narrow scope: a clear, port-entry-focused review that produces an auditable list of what was checked, what passed, what needs action, and who owns the next step.
Standards & compliance context
- This template supports evidence gathering for PSC reviews but does not replace the underlying obligations in SOLAS, MARPOL, STCW, MLC, flag-state rules, or class requirements.
- Use the checklist to confirm that statutory certificates are current and available for inspection, with any renewal gaps escalated before arrival.
- Fire safety and life-saving appliance checks should follow the vessel’s approved maintenance and inspection procedures, not informal visual-only review.
- Record-book verification should preserve the integrity of ship logs and pollution-prevention records without backfilling or altering entries outside normal correction procedures.
- If a deficiency affects seaworthiness, safety, or pollution control, treat it as critical and document the corrective action path before port entry.
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
- 1. Set the checklist to run 24–48 hours before arrival and assign the master as the final reviewer with the relevant department heads as DRIs for their sections.
- 2. Add the vessel-specific certificates, equipment checks, and record books that PSC inspectors most often request for your flag, trade lane, and vessel type.
- 3. Mark each checklist item as simple or checklist task type so every entry can be answered yes, no, or N/A with one clear verification step.
- 4. Complete the physical and document review, flag any blocking deficiency immediately, and create follow-up tasks for repairs, rechecks, or document retrieval.
- 5. Review the full result before port entry, confirm what is ready, and record any unresolved non-blocking items with their owner and next action.
- 6. After arrival, update the checklist with any PSC feedback so the next recurrence reflects actual deficiency patterns and inspection findings.
Best practices
- Write each checklist item as a single, independently verifiable action, such as verifying one certificate or one piece of safety equipment.
- Keep the review window tight at 24–48 hours before arrival so there is still time to correct a blocking deficiency.
- Assign the DRI by department, not by convenience, so deck, engine, and documentation items each have a clear owner.
- Treat expired, missing, or unserviceable statutory items as blocking until they are corrected or formally escalated.
- Photograph or attach evidence for any defect, seal issue, missing label, or out-of-date record at the time of inspection.
- Map recurring PSC findings to the checklist so the same deficiency does not reappear on the next port call.
- Avoid compound checklist items that mix certificates, equipment, and records in one line because they are hard to verify cleanly.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this checklist cover?
This checklist covers the shipboard items most often reviewed during Port State Control pre-arrival screening: statutory certificates, fire safety equipment, life-saving appliances, navigation and pollution-prevention records, and common deficiency-prone documents. It is designed for the 24–48 hour window before arrival so the master can confirm readiness while there is still time to correct blocking issues. It is not a cargo, customs, or berth planning checklist.
How often should this checklist run?
Use it for every port call, ideally 24–48 hours before arrival, and again if the voyage plan changes or a critical defect is found. If your operation has longer coastal legs or multiple intermediate ports, you can set a recurrence for each arrival rather than using a weekly cadence. The goal is to make it a pre-arrival verification step, not an after-the-fact audit.
Who should run the checklist?
The master should own the review, with the chief officer, chief engineer, or another designated DRI completing the item checks as assigned. On larger vessels, the checklist can be split into simple and checklist task types so each department verifies its own area before the master signs off. The final review should stay with the person responsible for port readiness.
Is this checklist tied to a specific regulation or PSC regime?
It is aligned to the way PSC inspectors typically assess ship condition, records, and statutory compliance, but it is not a substitute for the applicable flag, class, SOLAS, MARPOL, STCW, or MLC requirements. Use the checklist to confirm that the ship can evidence compliance on arrival and that any known deficiency is documented and controlled. Local PSC focus areas can be mapped into the checklist items as needed.
What are the most common mistakes when using a pre-arrival PSC checklist?
The most common mistake is treating the checklist as a paperwork exercise and skipping physical verification of equipment. Another frequent issue is combining multiple checks into one item, which makes it hard to answer yes, no, or N/A cleanly. Teams also miss the chance to assign blocking items early, so a defect is discovered only after the vessel is already committed to port entry.
Can I customize the deficiency codes and inspection focus?
Yes. This template is meant to be adapted to the vessel type, flag, trading area, and the PSC deficiency patterns you see most often. You can add local port focus items, map checklist items to internal deficiency codes, and remove sections that do not apply to the ship class. Keep each checklist item independently verifiable so the review stays fast and unambiguous.
How does this compare with an ad hoc pre-arrival review?
An ad hoc review depends on memory, email threads, and last-minute calls, which makes it easy to miss a certificate expiry or a non-working safety item. This template gives the crew a repeatable sequence, clear ownership, and a consistent verification step before arrival. It also creates a record of what was checked, what was blocked, and what was escalated.
Can this checklist integrate with other shipboard workflows?
Yes. It works well alongside maintenance, defect reporting, document control, and voyage planning workflows because each finding can become a follow-up task with a DRI and priority. You can also link it to recurring inspections, corrective action tracking, and handover notes so unresolved issues do not disappear between voyages. The checklist is especially useful when your team wants one place to capture readiness and escalation.
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.