Free tool
SIRE 2.0 inspection preparation checklist
The strongest response to a SIRE 2.0 observation is not to receive it. Walk the ship before the inspector arrives — by area, and across the three things a SIRE 2.0 inspection weighs together: the hardware, the process behind it, and the crew’s familiarity with both. An item can be in perfect order and still draw an observation if the record or the familiarity is missing. Runs in your browser; nothing you tick is sent anywhere.
Showing all 33 checks. Filter by focus to run a hardware walk, then a process check, then a familiarity round.
Certification, documentation & records
Bridge & navigation
Mooring & deck operations
Cargo, ballast & tank operations
Engine room & machinery
Safety management & drills (ISM)
Fire, life-saving & emergency systems
Pollution prevention
Structure, hull & enclosed spaces
Crew, manning & rest hours
If an observation is still raised
Preparation reduces findings; it does not guarantee none. If one is raised, a strong written response answers five separate questions — keep them apart, the common failure is collapsing them into one paragraph:
- Immediate cause — the condition itself, one sentence, not why.
- Root cause — the gap in the system, not a person. Walk the four checks above to reach it.
- Corrective action — what closed this finding now; dated and verifiable.
- Preventive action — the change to procedure, PMS or checklist that stops recurrence across the fleet and leaves a record.
- Objective evidence — the record that proves it: a certificate, a PMS entry, a photograph, an amended procedure. Not “the defect has been rectified” on its own.
Free report
Four worked examples
The SIRE 2.0 Observation Response Pack fills these five fields in end-to-end with four engine-room examples, and shows what tends to be accepted as objective evidence and what tends to come back. See also the SIRE 2.0 transition guide.
This is an independent preparation aid. It is not an OCIMF publication, carries no OCIMF endorsement, and reproduces no part of the SIRE 2.0 question library. It is built on generic operational areas and the publicly described hardware/process/human assessment approach — see OCIMF’s SIRE programme. How an inspection assesses your ship is OCIMF’s and the inspector’s alone; confirm current requirements with the source.
Questions
What is this SIRE 2.0 checklist?
It is a preparation checklist to walk the ship before a SIRE 2.0 inspection — the point being to prevent the observation, not just answer it afterwards. It is organised by operational area and, within each area, by the three things a SIRE 2.0 inspection weighs: the hardware, the process behind it, and the human familiarity with both. It runs entirely in your browser.
Does it contain the SIRE 2.0 question library?
No. The SIRE 2.0 question set (the CVIQ) is OCIMF’s and is not reproduced here. This checklist is built from generic operational areas and good-practice preparation, not from OCIMF’s questions.
What do Hardware, Process and Human mean here?
SIRE 2.0 assesses a finding across three dimensions: the physical condition of the equipment (hardware), the procedures and records behind it (process), and the crew’s familiarity and competence (human). A good preparation walk checks all three — a piece of equipment can be in perfect order and still draw an observation if the record or the familiarity is missing.
Is this only for tankers?
Yes. SIRE is OCIMF’s tanker inspection programme, so the ship-type filter covers oil, chemical and gas carriers. For Port State Control across all ship types, use the PSC deficiency checklist tool.
Does this tool send my data anywhere?
No. Nothing you tick or select is transmitted, logged or stored, and there is no sign-in. Use the print button to keep a copy.
Stay Ahead of Important Maritime Developments
Leave your email to receive selected maritime developments and updates from Apeks Tech. No spam — only what matters.