The Ship Inspection Report Programme has been the primary vetting mechanism for tanker operators dealing with major oil companies since 1993. For most of that history, the programme worked on a recognisable pattern: inspectors worked through a structured questionnaire, operators answered yes or no, and the outcome was a report that major charterers used to assess fleet risk.
SIRE 2.0, which became the operational standard from August 2024, represents a genuine structural shift — not an incremental update. The binary checklist is gone. In its place is a graduated, evidence-based assessment framework that demands something the old SIRE never did: proof.
From "does the procedure exist" to "was it followed"
The fundamental change in SIRE 2.0 is the introduction of the inspector's discretionary assessment. Under the old framework, if a ship had a procedure for a given operation, that procedure's existence was sufficient to satisfy the relevant question. Under SIRE 2.0, inspectors observe, interview, and verify. They're looking for evidence of implementation, not the existence of documentation.
This changes what ship operators actually need. A safety management system that is comprehensive on paper but inconsistently applied in practice creates a different risk profile than it did before. Inspectors have explicit guidance to probe the gap between policy and practice, and the questions in SIRE 2.0's questionnaire are structured to make that gap visible.
"The question is no longer 'do you have a procedure for enclosed space entry?' It's 'show me the last three times you did an enclosed space entry and walk me through what actually happened on each one.'"
What inspectors are looking for
Three categories of evidence have become consistently important under SIRE 2.0:
Timestamped records of procedural compliance
Not a standing order that says watch conditions should be assessed every 30 minutes — an actual record showing that the assessment happened, when it happened, and what the conditions were at the time. Officers can no longer rely on the assumption that if nothing went wrong, the procedure was followed.
Correlation between sensor data and crew actions
Inspectors can cross-reference vessel logs against AIS data, weather records, and in some cases port state records. Deck log entries that are inconsistent with sensor data — speed over ground that doesn't match logged engine orders, weather entries that don't match the Met record — are detectable and increasingly detected.
Continuous watch records, not batch entries
Watch entries logged at the end of a shift, reconstructed from memory, carry less evidentiary weight than records generated continuously during the watch. The timing of entries is itself evidence of the quality of the watch being kept.
The record-keeping infrastructure gap
Most ship operators who are thinking clearly about SIRE 2.0 have recognised that the gap is not in their procedures — it's in their record-keeping infrastructure. Procedures can be updated overnight. The infrastructure to demonstrate that those procedures were actually followed is a longer-term investment.
Traditional deck logs are not built for this. They were designed to create a narrative record, not to produce evidence. The difference matters: a narrative record tells the story of a voyage; an evidence-grade record creates a tamper-evident, timestamped, sensor-corroborated log that can be interrogated after the fact.
The practical implication for operators preparing for SIRE 2.0 inspections is that the quality of the inspection outcome is increasingly determined by the quality of the record-keeping infrastructure, not just the quality of the procedures. That's a different problem — and a solvable one.
About AIDRIATIC
AIDRIATIC builds AI tools for maritime operations professionals. AIDRIATIC Bridge provides voice-first voyage record and deck logbook capability on the vessel. AIDRIATIC Analyst processes SIRE 2.0 inspection reports into structured, severity-mapped findings. AIDRIATIC Office surfaces findings from all inspection sources in a single signed triage queue for the DPA.
Request a demonstration →