Cruise Ship Watertight Door Weekly Test Log
Weekly test log for watertight doors on a cruise ship, with fields to record local and remote operation, indicator lights, alarms, and bridge closing confirmation. Use it to prove each door was tested and any defect was assigned for follow-up.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Cruise Lines · Passenger Shipping · Maritime Operations
Overview
This template is a weekly test log for cruise ship watertight doors. It is built to record the specific checks that matter for compliance and operational readiness: local door operation, remote operation, indicator light verification, alarm test completion, and bridge remote closing confirmation. Each entry should identify the door being tested, the result, and any defect or follow-up action.
Use this template when you need a repeatable record of routine watertight door testing across a passenger vessel. It works well for bridge, deck, and engineering teams that need a consistent way to show the test was completed and that any failure was escalated. The log is especially useful before audits, after maintenance work, or during periods when multiple doors must be verified on a fixed cadence.
Do not use this template as a replacement for corrective maintenance, lockout procedures, or a broader safety management system. It is not meant for ad hoc troubleshooting alone, and it should not be used to hide a failed test behind a generic pass mark. If a door does not respond correctly, the record should show the failure, the blocking impact if any, and the next action owner. The value of the template is in making each weekly check independently verifiable and easy to review later.
Standards & compliance context
- This template supports recordkeeping aligned with SOLAS Chapter II-1 Regulation 13 by documenting routine watertight door testing.
- If a failed test affects safety or watertight integrity, treat it as a critical issue and escalate according to the vessel’s safety management procedures.
- The log should preserve evidence of who performed the test, when it was done, and what verification step was completed for each door.
- Any maintenance follow-up created from this log should be tracked separately so the inspection record and corrective action record remain distinct.
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. Add each watertight door that must be tested, along with its door ID, location, and the weekly recurrence day that matches the vessel’s operating schedule.
- 2. Assign a DRI for the inspection and define who records bridge confirmation, who performs the local test, and who closes out any defects.
- 3. Run each checklist item in order by verifying local operation, remote operation, indicator lights, alarm response, and bridge remote closing for every door on the list.
- 4. Record a yes, no, or N/A result for each checklist item and add a note whenever a test fails, is blocked, or requires follow-up maintenance.
- 5. Review the completed log at the end of the run, create any linked maintenance or safety tasks for failures, and confirm the record is stored with the weekly compliance file.
Best practices
- Test each door as its own checklist item so a single failure does not hide behind a ship-wide pass.
- Record the exact door identifier and location every time to avoid confusion between similar doors on different decks.
- Use a clear blocking versus non-blocking decision when a defect affects watertight integrity or remote control.
- Verify indicator lights and alarm behavior during the same test cycle instead of assuming they match the door movement result.
- Capture bridge remote closing confirmation as a separate verification step rather than folding it into the general door test.
- Assign follow-up work immediately when a door fails so the weekly log does not become a passive record of unresolved defects.
- Keep checklist items atomic and verb-based, such as verifying operation or confirming alarm response, to preserve audit clarity.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this watertight door weekly test log cover?
This template is for weekly verification of cruise ship watertight doors. It captures local operation, remote operation, indicator light status, alarm test completion, and bridge remote closing confirmation. It is meant to create a clear audit trail for each door, not to replace the ship’s maintenance or defect management process.
How often should this log be used?
Use it weekly, with the recurrence set to a specific day of the week that matches your vessel’s operating routine. The log is designed for repeated inspection cycles, so each run should stand on its own with dated entries and a clear DRI. If a door is out of service, record the blocking issue and the corrective action separately.
Who should complete the test log?
The log is usually completed by a deck officer, engineering officer, or another assigned crew member who can verify the door’s operation and record the result. The DRI should be someone authorized to test the door and escalate defects. Bridge confirmation should be recorded by the person who can verify the remote closing response.
Does this template help with SOLAS compliance?
Yes, it is structured to support weekly watertight door testing records aligned with SOLAS Chapter II-1 Regulation 13. It helps document that required checks were performed and that failures were tracked. It does not replace the vessel’s formal compliance program, but it makes the evidence easier to review during audits or inspections.
What are the most common mistakes when using this log?
A common mistake is recording a single pass/fail for the whole ship instead of one checklist item per door or per required function. Another is using vague entries like "OK" without noting which operation was verified. Teams also sometimes forget to log a failed indicator light or alarm as a blocking issue with follow-up ownership.
Can I customize the template for different ship layouts?
Yes, you can tailor the checklist item list to match the number of doors, deck locations, and control stations on your vessel. You can also add fields for door ID, location, test time, and defect reference number. Keep each checklist item independently verifiable so the log stays easy to audit.
How does this compare with an ad hoc paper log?
An ad hoc paper log often misses repeatability, consistent wording, and clear ownership for defects. This template gives you a standard task type with the same verification steps every week, which makes trends easier to spot and reviews faster to complete. It also reduces the chance that a required check is skipped because the form was improvised.
Can this log be integrated with maintenance or safety workflows?
Yes, the log works well when linked to a maintenance task, defect ticket, or safety report for any failed door. A failed verification step should create a follow-up task with a clear priority and DRI. That keeps the weekly test from becoming a dead-end record and helps ensure corrective action is tracked to closure.
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 Cruise Ship Watertight Door Weekly Test Log with your team — pricing built for small business.
