Buried in Section 1 of RISQ 3.2, right after the vessel’s P&I club details, sits the RISQ DryBMS question — or more precisely, two of them. Q1.29.1 asks whether the vessel manager is a subscriber to the Dry Bulk Centre of Excellence. Q1.29.2 asks whether a DryBMS self-assessment has been completed. Both offer the same three answers: Yes, No, or No Knowledge of This.
Worth being precise about what “consequence” means here, since it’s easy to conflate two different things. Most fleets — including through MarineKPI — apply their own internal risk rating to every RISQ question, weighting some higher than others based on their own risk appetite. That’s a company’s own layer, and it sits entirely outside RightShip’s process. What Q1.29.1 and Q1.29.2 lack isn’t a company’s internal weighting — it’s RightShip’s own mechanism. Almost every other RISQ question, if answered in a way that falls short of what’s expected, generates a finding: a recorded deficiency that becomes part of the inspection report and factors into RightShip’s assessment of the vessel. Annex A, RISQ’s own changelog for the 3.2 revision, states plainly that responses to these two questions are not recorded in the list of findings and do not impact the inspection outcome. No finding. No corrective action tracked by RightShip. Nothing.
It’s Not Just Consequence-Free — It’s Unverified
The detail that matters more than the lack of a finding is sitting in the Guide to Inspection directly beneath the questions: the inspector is not required to request or review any documentation to validate the Master’s response. This isn’t RightShip choosing not to act on the answer yet. It’s RightShip explicitly not checking it. Whatever the Master says — DBCE subscriber, DryBMS assessment completed — goes into the report as stated, with no evidence trail behind it.
That makes these two questions something unusual in a document built almost entirely around verification: a pair of honesty questions rather than compliance questions. For now, at least.
Why the RISQ DryBMS Question Exists at All
RightShip doesn’t add questions to RISQ for decoration. The questionnaire has a formal revision process, and Annex A exists specifically to flag what changed and why fleets should be aware of it. Adding two questions that generate no finding and require no verification, in the same revision that also added a whole new Section 8F for heavy lift vessel inspection, isn’t a filler item — it’s RightShip building the data-collection habit before the accountability follows.
That pattern isn’t unique to RightShip. The tanker sector saw the same sequencing with TMSA itself, and it’s the same direction of travel DryBMS is following more broadly across dry bulk vetting — questions appear with no consequence first, become expected practice next, and only then start generating findings. A manager who’s building the habit of answering Yes to both questions now is in a materially different position twelve or twenty-four months from now than one who’s answering No Knowledge of This today and hoping the questions stay that way indefinitely.
Where This Actually Gets Missed
Here’s the practical problem with the RISQ DryBMS question specifically: because it generates no finding, it doesn’t enter any of the workflows a fleet normally uses to track inspection follow-up.
A “No” against fendering condition gets chased because it’s a finding, with a corrective action attached. A “No” against DBCE subscription generates nothing from RightShip’s side — no ticket, no follow-up, no visibility beyond whatever the Master happened to say in that one inspection. Ask most ship managers today whether their fleet answered Yes or No to Q1.29.2 across their last twelve RISQ inspections, and most won’t know — not because the answer wasn’t given, but because nothing downstream of the questionnaire was built to notice it.
That’s the specific gap a connected inspection record closes — not by making RightShip verify the answer, since that’s RightShip’s decision to make, but by giving a fleet manager visibility into a pattern RightShip currently has no reason to surface: which vessels answered No, which answered Yes, and whether that’s consistent across the fleet or scattered.
The Practical Point
The RISQ DryBMS question carries no finding and no verification today, either way you answer.
That’s exactly why they’re worth taking seriously now rather than later. No consequence is not the same as permanent, and a fleet’s answer to “has a DryBMS self-assessment been completed” is far cheaper to get right while nobody’s checking than after somebody starts.
