Question 1

SIRE 2.0 Q10.1.2 and SOLAS Ch.V Reg.26 require steering gear to be "checked and tested by the ship's crew" within 12 hours before departure, and engine/steering function fully confirmed before entering restricted or coastal waters. Why does this testing requirement specifically target points just before critical manoeuvring phases, rather than relying on routine periodic testing during the voyage at sea?

Accepted Answer

Machinery that has been idle or in a different operating mode for some time can fail on transition to active use in a way that periodic testing during steady-state sea passage would not necessarily reveal — testing immediately before the phase where full manoeuvring capability is actually needed (departure, restricted waters) catches a fault at the one point where discovering it in advance still allows time to respond, rather than discovering it only when the capability is suddenly required This is the same "test it right before you actually need it" logic that applies to many pre-critical-phase checks across the industry — a system that tested fine during routine sea passage can still fail on the specific transition to active manoeuvring mode, and testing immediately beforehand is what actually confirms readiness for the upcoming high-consequence phase, rather than relying on an earlier, less relevant test.

Question 2

SIRE 2.0 Q10.1.1 requires the Chief Engineer to issue written Standing Orders (signed by all engineer officers) supplemented by Daily Orders, mirroring the Master's Standing Orders/Bridge Order Book structure covered elsewhere in this content library. Why does the Chief Engineer need a parallel, separate set of orders rather than simply operating under the Master's standing orders alone?

Accepted Answer

The Master's standing orders address bridge/navigational command and control, but engine room management has its own distinct technical decision points (UMS entry procedures, critical alarm response, defect handling, bilge/sludge/incinerator supervision) that fall within the Chief Engineer's specific area of responsibility and require department-specific guidance the Master's orders are not structured to cover in that depth This mirrors the same command-and-control logic as the Master's standing orders, applied to a genuinely distinct technical domain — engine room management has its own specific decision points (UMS entry, critical alarm response, defect handling) that the Master's bridge-focused orders are not designed to address in the necessary engineering detail, so a parallel, department-specific order structure exists rather than being collapsed into one document.

Question 3

SIRE 2.0's guidance explicitly states a negative observation "should not be raised where a change in circumstances, such as a delay in mooring/unmooring, had occurred" even if Engine Room Log Book records show a deviation from the Chief Engineer's Daily Orders. Why does the inspection deliberately build in this exception, rather than treating any deviation from the written orders as a finding?

Accepted Answer

Daily Orders are written based on the anticipated timing of operations, but real port/voyage circumstances genuinely change after the orders are written — penalising the crew for sensibly adapting to a real operational change (rather than ignoring the orders through poor planning or carelessness) would punish good judgement and could create an incentive to rigidly follow outdated instructions even when conditions have clearly changed This is a carefully calibrated distinction worth understanding precisely: the inspection is checking whether the crew followed sound engineering management, not whether they rigidly executed a plan that real circumstances had already overtaken. Treating every deviation as a failure regardless of cause would actually incentivise worse decision-making — following outdated written orders over the actual situation in front of them.