Cruise Ship Watertight Door Weekly Test Log

This template is for recording the weekly functional test of cruise ship watertight doors. It captures local operation, remote operation, indicator light verification, alarm test completion, and bridge remote closing confirmation. It is meant to document that each door was checked and that the result was clear enough to review later.

Use it weekly, with a recurrence that matches your vessel’s planned maintenance or safety inspection schedule. The log is designed for a recurring compliance task, not an ad-hoc repair note. If a door is repaired, damaged, or fails a test, record that separately as a blocking issue and retest after corrective action.

The test is usually run by qualified shipboard engineering or safety personnel, with the DRI assigned by the vessel’s operating procedure. Bridge staff may need to confirm remote closing, and the result should be visible to the responsible officer. The template works best when one person owns completion and another verifies critical steps where required.

Yes, it is aligned to the weekly testing pattern expected for watertight doors under SOLAS Chapter II-1 Regulation 13. It helps you document the checks that matter for inspection readiness, but it does not replace your company procedures, class requirements, or flag-state instructions. Use it as the record of execution, not as the rulebook itself.

The most common mistake is treating the entry as a single yes/no item instead of separate checklist items for each function. Another pitfall is recording a test as complete without noting a failed indicator, missing alarm, or incomplete bridge confirmation. A third issue is using vague notes instead of independently verifiable results for each door.

Yes. You can add door identifiers, deck locations, and any vessel-specific verification steps such as local control station checks or bridge panel references. Keep each checklist item atomic so a failed function is easy to isolate, and avoid combining multiple doors or multiple actions into one line.

An informal log often misses one of the required checks or makes it hard to prove who completed the test. This template gives you a repeatable structure with clear checklist items, which makes review, audit prep, and follow-up on defects much easier. It also helps standardize the record across shifts and vessels.

Yes. Failed tests can be turned into blocking maintenance tasks, while passed tests remain as compliance records. If your system supports it, link the log to corrective work orders, bridge notifications, or defect reports so the inspection result leads directly to action.