- The shift: from checklist to risk-based assessment
- Anatomy of a SIRE 2.0 inspection
- The four question types — and why you can't predict them
- Three dimensions, four ratings
- The nine Performance Influencing Factors
- Negative observations: SOC, NOC and PIF coding
- The PIQ: your most under-used lever
- Preparing crew for a competency-based inspection
- A 90-day readiness programme
- Six failure patterns that keep recurring
- What this demands of your systems
The Shift: From Checklist to Risk-Based Assessment
The original Ship Inspection Report Programme served the industry for three decades on a simple premise: a standard questionnaire, largely binary answers, and a report that recorded what an inspector saw on the day. Its weakness was equally simple. A fixed question set can be prepared for — and, over time, prepared for instead of being ready.
SIRE 2.0 was built to close that gap. Fully replacing VIQ7 from 2 September 2024, it changes four things at once:
- The question set is generated, not fixed. An algorithm compiles a bespoke questionnaire for every single inspection.
- Assessment is three-dimensional. Hardware, process and human factors are graded separately — the same piece of equipment can pass on condition and fail on how the crew operates it.
- Human performance is formally scored. Crew competence is no longer an inspector's private impression; it is tagged against a defined framework and recorded.
- The record is digital and evidential. Inspectors work on a tablet, capturing photographs and structured observations that become a permanent part of the report.
The practical consequence: you can no longer "prepare for the inspection" in the week before it. You can only be operationally ready — or not — and the inspection samples that readiness at random.
Anatomy of a SIRE 2.0 Inspection
Understanding the pipeline explains where operators gain or lose ground long before the inspector steps aboard.
| Stage | What happens | Where operators lose points |
|---|---|---|
| 1 · Pre-Inspection Questionnaire (PIQ) | The operator submits declarations, vessel data, photographs and certificates — not less than 48 hours, ideally 96 hours, before the inspection. | Stale data and over-claiming. Declarations feed the algorithm. |
| 2 · Algorithmic compilation | The system builds the CVIQ (Compiled Vessel Inspection Questionnaire) from a 12-chapter library, informed by vessel type, history and PIQ declarations. Roughly 100 questions. | Nothing to control here — which is precisely the point. |
| 3 · The inspection | The inspector works through the vessel, often following a risk-organised walk-through sequence, assessing hardware, process and human factors and capturing photographic evidence. | Crew who can locate a document but cannot perform the task. |
| 4 · Report submission | The inspector validates and submits the report with observations coded and PIFs tagged. | — |
| 5 · Operator comment window | The operator has 14 days to add comments before automatic publication (or may release it earlier). | Defensive, unevidenced comments that read worse than the observation. |
| 6 · Publication | The report sits in the database for 12 months. Each charterer and recipient applies its own risk appetite. | Repeat findings across consecutive reports. |
The Four Question Types — and Why You Can't Predict Them
Every CVIQ is drawn from four distinct pools. Knowing the mechanics tells you where predictability ends and genuine readiness begins.
| Type | How it is allocated | What it means for you |
|---|---|---|
| Core | Included in every inspection. Covers risks capable of causing catastrophic or severe consequences. Roughly half the CVIQ. | These are non-negotiable. Continuous excellence here is the baseline. |
| Rotational 1 | Appears roughly every third or fourth inspection. | Rotate your internal verification on a similar cadence — don't let these lapse between appearances. |
| Rotational 2 | Appears at roughly double the interval of Rotational 1 — the long tail. | The classic blind spot. A topic unseen for years still arrives eventually. |
| Campaign | Deployed fleet-wide for a fixed period to probe an emerging industry risk. | Track industry themes; campaign topics are usually visible in the sector's incident conversation. |
| Conditional | Triggered by what you declared in the PIQ. | The self-inflicted category. Declare an activity you cannot evidence and you invite a question you will fail. |
The strategic implication is uncomfortable but clarifying: the only viable preparation strategy is broad, continuous readiness. Attempting to guess the CVIQ is a losing game by design — the programme was built specifically to defeat it.
Three Dimensions, Four Ratings
This is the part most crews under-appreciate. A single question can be examined from three angles:
- Hardware — the physical condition of structure, machinery and equipment.
- Process — whether the company's procedures exist, are appropriate, and are actually followed.
- Human factors — whether the person operating the system genuinely understands and can perform the task.
Each assessment attracts one of four ratings:
| Rating | Meaning | Consequence |
|---|---|---|
| Exceeds expectation | Performance demonstrably better than the standard. | Positive observation; PIFs tagged to explain why it was good. |
| As expected | Meets the required standard. | No finding. |
| Largely as expected | No negative finding, but visible room for improvement. | Not a failure — but reviewers notice, and it can invite follow-up questions. |
| Not as expected | The standard was not met. | A negative observation is raised and coded. |
A well-maintained piece of equipment operated by an officer who cannot explain its function can still produce a negative observation. Immaculate hardware no longer guarantees a clean report. This single change is the biggest cultural adjustment SIRE 2.0 demands.
The Nine Performance Influencing Factors
PIFs are the interpretive heart of SIRE 2.0. When performance is rated Exceeds expectation or Not as expected, the inspector must tag the factors that shaped it — selected from a fixed list, not written freehand. That consistency is what makes the resulting data analysable across the industry.
| Performance Influencing Factor | What it is really asking |
|---|---|
| 1 · Recognition of safety criticality | Does the crew understand why this task matters, not merely how to do it? |
| 2 · Custom and practice surrounding use of procedures | Is the written procedure what actually happens — or has practice quietly drifted? |
| 3 · Procedure accessibility and accuracy | Can the procedure be found quickly, and is it correct for this ship? |
| 4 · Team dynamics and communications | Does information flow across ranks, and will a junior officer challenge a senior? |
| 5 · Stress, workload and fatigue | Is the workload realistic, and are rest hours genuine rather than reconstructed? |
| 6 · Morale and motivation | Does the crew care about the outcome, or are they completing forms? |
| 7 · Workplace ergonomics | Signage, tools, layout, noise, lighting, heat — does the environment help or hinder? |
| 8 · Human-machine interface | Are controls, alarms and displays intelligible under pressure? |
| 9 · Opportunities to learn or practise | Has this person had a genuine chance to rehearse this task before being tested on it? |
Read that list again as a manager rather than as a candidate. Several PIFs — procedure accuracy, workload and fatigue, opportunities to practise, ergonomics — are shore-side responsibilities. When an inspector tags them, the finding is describing your management system, not the individual seafarer standing in front of them.
PIF 5 is the quiet one. If your rest-hour records are reconstructed at the end of the month, fatigue is invisible in your data and highly visible in crew performance. Rest-hour integrity and vetting performance are the same problem viewed from two angles — see our note on work & rest hours compliance.
Negative Observations: SOC, NOC and PIF Coding
A negative observation in SIRE 2.0 is not free text. It is structured data:
- Subject of Concern (SOC) — what the finding relates to.
- Nature of Concern (NOC) — what kind of deficiency it is.
- Performance Influencing Factors — why it happened, in human terms.
This structure has a consequence operators are still adjusting to: findings are now comparable and trendable. A charterer's vetting team can see whether the same subject and nature recur across your fleet and across years. Isolated findings are forgiven; patterns are not.
It also changes what a good response looks like. Closing a finding by replacing a gasket answers the SOC. Closing it properly means addressing the tagged PIF — the procedure that was wrong, the training that never happened, the workload that made the shortcut rational. Your corrective-action process should record that causal link explicitly, because the next inspection's data will show whether it worked.
The PIQ: Your Most Under-Used Lever
Treated as paperwork, the Pre-Inspection Questionnaire is a liability. Treated properly, it is the one part of the process you genuinely control.
Three principles:
- Submit early — ideally 96 hours out. The minimum is 48 hours, but early submission gives you time to correct errors rather than discovering them during the inspection.
- Declare only what you can evidence. Declarations drive conditional questions. If you declare a superintendent inspection or a specialist audit, expect to be asked to produce it — complete, dated and verifiable. An unsupported declaration converts directly into a negative observation.
- Keep photographs and certificates current. The PIQ carries supporting evidence into the inspection. Out-of-date photographs signal an out-of-date management system before anyone boards.
A disciplined habit that costs almost nothing: refresh the standing photograph set and certificate pack on a fixed cycle — for example every six months — so PIQ submission is an export, not a scramble.
Preparing Crew for a Competency-Based Inspection
Under VIQ7, a well-drilled crew could succeed by knowing where documents lived. Under SIRE 2.0, an inspector is as likely to say "show me" as "prove it." The distinction matters enormously:
| The old question | The SIRE 2.0 question |
|---|---|
| "Do you have a calibration certificate for this instrument?" | "Walk me through how you calibrate it — now." |
| "Is there a procedure for enclosed-space entry?" | "Find the procedure, then talk me through your role in the last entry." |
| "Are alarms tested?" | "What does this alarm mean, and what would you do first?" |
Practical implications for training:
- Drills must be genuine, not documented. A drill that exists only as a signed form is exactly what PIF 9 is designed to expose.
- Rotate who demonstrates. If the same competent officer always performs, you have concentrated your capability — and the inspector may ask someone else.
- Teach the "why". PIF 1 rewards a crew that can articulate the consequence a safeguard exists to prevent.
- Fix the procedure when the crew is right. If experienced officers routinely deviate, the procedure is often wrong. Rewriting it is a legitimate — and highly effective — vetting improvement.
- Include joiners. Rotation means the crew on inspection day may not be the crew you trained. Onboarding quality is a vetting control.
A 90-Day Readiness Programme
A structure that works for operators without a large vetting department:
Days 1–30 · Establish the baseline
- Map your last 24 months of vetting and PSC findings by subject and nature; identify repeats.
- Audit PIQ data integrity: vessel particulars, certificates, photographs, standing declarations.
- Review the procedures behind your recurring findings — accuracy first, then accessibility.
Days 31–60 · Close the human gap
- Run "show me" walkthroughs on core-question territory: enclosed spaces, mooring, cargo and ballast operations, machinery spaces, fire-fighting appliances, pollution prevention.
- Rotate demonstrators by rank, and record who has genuinely performed which task.
- Verify rest-hour data reflects reality — then fix the workload driving any breaches, not the record.
Days 61–90 · Rehearse and harden
- Conduct a mock inspection using an unpredictable question sample, including long-tail rotational topics.
- Practise the report response: draft comments that are factual, evidenced and non-defensive.
- Convert every mock finding into a corrective action linked to a PIF, with an owner and a date.
Then repeat it. SIRE 2.0 rewards cadence over crescendo — a modest programme run continuously beats an intensive push before a nominated inspection, because the algorithm decides what it looks at, not you.
Six Failure Patterns That Keep Recurring
- Over-declaration in the PIQ. Claiming completed activities that cannot be produced on demand — the single most avoidable source of findings.
- Documented drills that never happened. Visible immediately when the crew is asked to perform rather than produce.
- Procedure drift. The manual says one thing; the ship has done another for years. PIF 2 exists precisely to surface this.
- Reconstructed rest hours. Records that satisfy the form while fatigue remains real and observable in performance.
- Single-point competence. One outstanding officer masking a thin bench.
- Cosmetic close-out. Findings closed by fixing the artefact without addressing the tagged PIF — which is why the same observation returns next year.
What This Demands of Your Systems
SIRE 2.0 is, in effect, a data-quality audit of your management system conducted through your crew. That places specific demands on the tools behind it — whichever vendor you use:
- Findings that trend. If you cannot group historic observations by subject and nature, you cannot see the patterns a charterer sees.
- Corrective actions with causal linkage. A CAPA record should carry the human factor, not just the repair.
- Controlled, current procedures on board. PIF 3 is a document-control test in disguise — including offline access when connectivity is poor.
- Honest rest-hour data. Recorded as worked, validated automatically, with breaches visible early enough to act on.
- Maintenance evidence that holds up. Overdue critical jobs and thin history are read as management quality — see our PMS guide.
- Training and drill records tied to people. So you can answer "who has actually performed this task?" before an inspector asks.
No software passes an inspection for you — competent, well-supported seafarers do. What good systems do is remove the excuses: they make the procedure findable, the fatigue visible, the history retrievable and the corrective action real. That is the whole of the contribution, and it is worth having.
Make vetting evidence a by-product of daily work
Volaxin Maritime Suite connects SHEQ findings, corrective actions, controlled documents, rest hours and maintenance history on one dataset — with full offline operation on board. Book a demo and we'll walk through your recurring vetting findings together.
Request a DemoFrequently Asked Questions
What is SIRE 2.0?
OCIMF's risk-based tanker inspection programme, which permanently replaced VIQ7 from 2 September 2024. An algorithm compiles a unique questionnaire per inspection, and inspectors assess hardware, process and human factors on a tablet with photographic evidence.
What is a CVIQ?
The Compiled Vessel Inspection Questionnaire — the bespoke set of roughly 100 questions generated for each inspection from a 12-chapter library, informed by vessel type, history and your PIQ declarations.
What are the nine Performance Influencing Factors?
Recognition of safety criticality; custom and practice around procedures; procedure accessibility and accuracy; team dynamics and communications; stress, workload and fatigue; morale and motivation; workplace ergonomics; human-machine interface; and opportunities to learn or practise.
How are questions graded?
Across hardware, process and human factors, with four ratings: Not as expected, Largely as expected, As expected, and Exceeds expectation. "Not as expected" generates a negative observation coded with a Subject of Concern, Nature of Concern and relevant PIFs.
When must the PIQ be submitted?
No less than 48 hours before the planned start, and ideally at least 96 hours. Declarations influence which conditional questions the algorithm selects.
How long do we have to comment on the report?
14 days from submission, after which the report publishes automatically. Published reports remain in the database for 12 months.
Sources & Further Reading
This guide summarises publicly available material on the SIRE 2.0 programme. Operators should always work from the current official documentation, which takes precedence over any summary:
- OCIMF — the SIRE 2.0 programme pages, question library documentation and inspector guidance.
- OCIMF TMSA — the Tanker Management and Self Assessment framework, which underpins many PIQ declarations.
- Your flag State, class society and P&I club circulars, which often carry practical implementation notes.
Nothing here constitutes vetting, legal or classification advice. Requirements evolve; verify against current OCIMF publications before acting.