Question 1

RISQ Q2.13 instructs the inspector not to record a non-conformity for an inaccurate officer matrix if a crew change occurred within seven days of the inspection, but otherwise requires the matrix to accurately reflect officers and engineers actually onboard. What does this seven-day allowance reveal about how the questionnaire balances administrative lag against genuine record-keeping failure?

Accepted Answer

The allowance distinguishes between an honest, short administrative delay in updating records after a routine crew change and a matrix that is wrong because it has not been properly maintained — the underlying concern is whether the company's record-keeping process functions at all, not whether it is instantaneously perfect at every moment This is a deliberately calibrated rule, not an oversight — it stops the inspection from penalising a company for the unavoidable lag between a crew change and updating shore-based records, while still catching matrices that are wrong because nobody bothered to maintain them. The inspector is still expected to verify random junior officer/engineer records against actual crew lists and certificates regardless of this allowance.

Question 2

RISQ Q4.4 asks whether the Master "periodically review[s] the effectiveness of the onboard Safety Management System, report[s] the findings to shore based management and receive[s] feedback from them," at least once every 12 months. Why is the feedback loop back from shore management treated as part of the requirement, not just the Master's review itself?

Accepted Answer

A Master's review that goes unanswered by the company is a one-way report, not a functioning management loop — the ISM Code's purpose is to ensure shore management actively engages with and acts on shipboard safety findings, so evidence of a response from the company is what distinguishes a genuine SMS from one that exists only on the ship This is the same systemic-versus-isolated logic seen in the SIRE/PSC content: a safety management system that only flows one direction (ship to shore, with no documented response) is not actually managing anything — it is filing. RISQ's explicit requirement for "evidence of the company's response" turns this from a paperwork exercise into a real test of whether shore management is engaged.

Question 3

RISQ Q4.5 requires enclosed space entry procedures to be defined in the SMS, with RightShip specifically recommending that an enclosed independent compartment housing a ballast water treatment system be identified as an enclosed space. Why call this specific example out, rather than leaving "enclosed space" to be interpreted generically?

Accepted Answer

Ballast water treatment systems are a relatively recent addition to many vessels' machinery and may not have been captured when the ship's original enclosed-space list was compiled — RightShip's guidance closes a real gap where a genuinely hazardous space could be missed simply because it postdates the vessel's original space-identification exercise This question tests the same "normalisation of deviance via omission" pattern flagged elsewhere in this library's enclosed-space content — a space can be hazardous and yet absent from the official list simply because nobody updated the list when the equipment was retrofitted. BWM systems, often added under retrofit compliance deadlines, are a concrete, real-world example of exactly this gap.