Compliance & ISM
An SMS that is not a shelf document
The Safety Management System as enforced workflow: state machines the client cannot skip, signatures stamped in the database, and evidence an auditor can verify.
On the safety deck, drills and certificates stay current
Onto the bridge, where the compliance picture reads all green
Objective evidence, by construction
Readiness you can score
Fleet readiness computes from certificates, surveys, drills and open actions. Recording a failure can never raise the score.
Hours of rest, honestly
MLC minimums, ten in twenty-four and seventy-seven in seven days, flag as the slots are painted, not after the month is signed.
Permits that refuse to activate
Thirteen permit-to-work types hold until the last mandatory control is completed. Hot work waits for the fire watch.
Signatures that cannot be forged
Read-and-sign attestations are stamped by a database trigger. Even a direct API write cannot fake a crew acknowledgement.
Drills on the SOLAS cadence
Completing a drill schedules the next occurrence at its required frequency, with muster and response times kept in seconds.
Forms with a legal basis
Statutory PDFs cite the ISM Code, SOLAS regulations and MCA circulars line by line, at the foot of the form.
Certificates, drills and rest hours, current
The compliance cockpit rebuilt in code, down to the certificate expiry heat map a surveyor reads first.
13
ISM registers
16
incident types
11
audit types