ISM Compliance Software: Why a Mapped Clause Is Not Yet Evidence
A system can cross-reference every paragraph of the ISM Code and still leave a company unable to show that its safety management system works.
Search for ISM compliance software or ISM Code software and you will find systems that map clauses, schedule internal audits, distribute controlled documents, track corrective actions and present a compliance score. Each of those functions can be genuinely useful. A well-run document control system saves time, reduces version confusion and makes it easier to find the record an auditor or port State control officer asks for.
The confusion begins when the map is treated as the territory. A clause that has a procedure attached to it is a clause that has been indexed, not a requirement that has been met. The ISM Code does not ask a company to demonstrate that its documents reference the Code. It asks the company to demonstrate that safety and environmental protection are managed in a way that works at sea.
That distinction matters commercially as well as operationally. Companies now spend real money on SMS compliance software and audit platforms. The purchase is sensible only if the system strengthens the evidence a company can produce when someone competent tests the system, rather than simply increasing the volume of material that looks like evidence.
What the ISM Code actually asks a company to do
The ISM Code sets objectives and functional requirements for safe management and pollution prevention. Its scope includes policy, responsibilities and authority, the designated person, the master, personnel, operations, emergency preparedness, reporting, maintenance, documentation and verification. The applicable text is the Code as amended, not an unqualified copy of the original 1993 resolution.
Every one of those areas can be stored in a system. None of them is satisfied by a document that states the activity takes place.
| Code area | What a system can hold | What still has to be demonstrated |
|---|---|---|
| Company responsibilities and authority | Organisation charts, job descriptions, delegations | That the named person had the authority, resources and information to act |
| Designated person ashore | Contact details, a reporting inbox, a log | That concerns reached the person, were escalated and produced a response |
| Shipboard operations | Published procedures and acknowledgement records | That the work is done as described, or that a deviation was identified and controlled |
| Non-conformities and analysis | A CAPA register with owners and dates | That the cause was addressed and the corrective action prevented recurrence |
| Internal audit and review | Schedules, checklists and completed reports | That the audit sampled real work and that management acted on what it found |
None of the right-hand column can be produced by configuration alone. All of it can be undermined by a system that makes the left-hand column easy to populate and the right-hand column easy to ignore.
Why clause mapping feels like progress
A gap analysis is a reasonable starting point. Someone takes the Code, lists its requirements and records where each one is addressed. The output is a matrix with a procedure reference in every row. It is tidy, shareable and satisfying to present to a board or a customer.
A matrix can stop at document references or extend to operating evidence, review status and open questions. The weakness appears when filling the procedure-reference column is treated as completion. A useful map also asks whether the procedure matches what competent people do on this vessel, with this equipment and under the conditions being sampled.
Consider section 7, shipboard operations. A system may hold the enclosed space procedure, permits, training records and distribution history. It can also hold contemporaneous test results and other operating evidence. Merely displaying current documents does not establish whether the permit preceded entry, the atmosphere testing met the applicable procedure, or the standby person understood the rescue arrangements. Those questions require examination of the records and, where appropriate, observation and interviews.
Acknowledgement records illustrate the same gap in a different way. They tell you that a person opened a document, and possibly that they clicked a box. They do not tell you that the person can perform the task when conditions change, that they know why the control exists, or that they would recognise the point at which the procedure no longer fits the situation. Those are questions of competence, not document distribution, and the Code treats them separately for that reason.
A worked evidence chain
Illustrative example, created for this article.
An internal audit samples permit-to-work for enclosed space entry on one vessel. The difference between a register entry and evidence becomes visible when every step records what is known and what is still open.
| Step | What the record shows | What remains open |
|---|---|---|
| Requirement | ISM Code section 7; company procedure for enclosed space entry, revision 4, effective 14 March 2026 | Whether revision 4 reached the vessel before the sampled entry |
| Evidence | Permit number, entry time, atmosphere readings, standby person, training record reference | Whether the atmosphere was tested at the required depth, not only at the entry point |
| Review status | Training record confirms course completion; the sampled company procedure also calls for task authorisation, but that evidence is missing | Partially evidenced. Course attendance alone does not establish the company's additional authorisation requirement was met. |
| Follow-up | Owner named, evidence requested from the technical manager, due date set | Whether the manager can show the person was authorised for this task on this vessel |
| Decision | Auditor records "not verified" and keeps the finding open pending review | Whether the corrective action addresses the cause or only supplies the missing document |
The value is that a second person can follow the chain, see which links are missing and understand why the item is still open. This table is an article example, not an extract from a Meriden product. The Audit And Evidence Readiness Kit is a related guide and workbook for organising evidence. Check the current listing for scope and availability. Sampling, fieldwork and the audit conclusion remain with the auditor.
Where SMS compliance software genuinely helps
The argument is not that the systems are worthless. It is that their value is concentrated in traceability, and traceability is worth having.
- Document control. A system that records when a revision became effective, which ships received it and which superseded versions were withdrawn answers a question that paper systems answer badly.
- Audit and inspection scheduling. Reminders, scopes and completion records make it harder for verification activity to quietly lapse.
- Corrective action tracking. Owners, due dates, evidence and closure decisions create a chain that can be examined later - provided the closure decision is made by a person who checked the evidence rather than by whoever wanted the row to turn green.
- Maintenance and drill records. Planned maintenance and emergency preparedness both depend on recurrence, and recurrence is exactly what software is good at.
- Retrieval under pressure. When a port State control officer asks for a record, the speed and completeness of the answer is itself part of the impression the ship creates.
These are operational improvements. They become compliance evidence only when someone uses them to test whether the control is working.
Four questions that expose documentation without control
A company does not need a new platform to find out whether its SMS is being evidenced or merely described. It needs four questions and the willingness to accept the answers.
- Trace one non-conformity. Take a finding from the last twelve months and follow it from the original report through the cause analysis, the change made, and the later check that the change worked. If the trail stops at "action closed", the system is recording administration rather than learning.
- Ask someone who does the work. Pick a procedure with real risk attached. Ask a crew member to explain its purpose in their own words and to describe what they do when the situation does not match the procedure. Hesitation or a recital of the text is information.
- Check that a change reached the ship. Choose a recent revision and confirm that the old practice stopped, not just that the old PDF was replaced. Document control can be perfect while the working practice on board remains unchanged.
- Read the last internal audit properly. Was it an independent sample of real activity, or a recital of checklist items? Did it find anything? What did management decide, and what changed as a result? A clean audit can be valid. Repeatedly clean reports are a reason to examine scope, sampling and independence, not proof that the audit was weak.
ISM Code software and SMS compliance software are not the same purchase
The ISM Code is the standard. The safety management system is the company's own structure for meeting it. Vendors use the two phrases loosely, and the products behind them differ considerably. Some are document management systems, some are audit tools, some are corrective action trackers, some are training platforms, and some are reporting dashboards that aggregate data from the others. A few now include generative AI features that draft text or summarise findings.
Before buying, it is worth asking questions that map to the evidence you will actually need:
- What is the evidence model? Does the system distinguish between "verified", "not recorded", "not applicable" and "assumed"? Ask the supplier to demonstrate each state rather than assuming a green status means verified.
- Who can change a record, and is the change visible? An audit trail that shows edits, authors and timestamps is worth more than a clean interface.
- Does it work when the ship does not have a connection? A system that assumes continuous connectivity will be worked around at sea, and workarounds become the real process.
- Can you export the evidence? If a dispute, casualty or inspection requires the record, you need it in a form another party can read without your subscription.
- How does it handle a missing entry? A blank treated as zero, or as "compliant", is a false statement waiting to happen. This is a familiar failure in AI-generated summaries and it is just as serious inside a compliance platform.
- What does the AI feature do with the output? Drafting, summarising and source-backed transcription can be legitimate with appropriate checks. Unsupported conformity claims and invented records are not. Ask how the required human verification, attribution and approval remain visible.
Use one open finding as the buying test
Before selecting a platform, bring a redacted or synthetic finding with one missing evidence item. Ask the supplier to show the following without marking the finding complete.
- Requirement to record: follow the clause and company procedure to the sampled evidence, including its date and revision.
- Evidence to uncertainty: identify what is verified, what is missing and what is only an assumption.
- Uncertainty to action: assign a person, due date and specific evidence request without changing the review status.
- Action to closure: show who may approve closure, what effectiveness evidence they considered and how the item can be reopened.
- Export and continuity: retrieve the same trail outside the dashboard and demonstrate the agreed offline process.
Record the observed result for each step, not a vendor yes/no answer. A feature that requires a separate module, integration or manual workaround belongs in the buying decision and implementation plan. This is a suggested evaluation method, not an ISM certification test.
Where AI changes the risk
Generative AI can reduce the effort of drafting. That can help, but it can also increase the amount of material awaiting review. A vessel-specific detail can be missed in fluent text, and an apparently authoritative procedure can remain untested against the operation.
There are legitimate uses. AI can help assemble a first draft of an internal guidance note from primary sources, cluster findings from a series of inspections so that recurring themes become visible, prepare a briefing for a management review, or translate a procedure for a crew whose working language differs from the controlled document. Each of these is a drafting and analysis aid. None of them decides whether the company conforms.
The Code allocates responsibilities to the company and named shipboard and shore roles, not to a model. An AI-generated mapping is a proposal to check against the current text, applicable flag requirements and the vessel's operation. A verified mapping can save time; an unexamined one can conceal the gap between the document and the work.
A defensible way to start
The practical route is to pick one bounded task, define what the output is for, and name the person who will review it. A company might begin with the evidence pack for an internal audit, or the preparation of one vessel's records before a port call, or a structured review of recurring findings. The output stays a draft until a competent reviewer has checked it against source records and signed the decision.
Two current resources support that work without replacing the SMS. ISM SMS AI Workflow covers document revision and review workflows. The SMS and ISM AI System provides guidance and editable tools for integrating AI controls into an existing company SMS; it is not a complete SMS or a substitute for competent approval. These are enquiry listings, not live checkout offers.
If the underlying problem is that records look complete while control is uncertain, the companion analysis on false assurance in maritime compliance examines that pattern directly. If the question is how AI fits into IMO obligations more broadly, read AI for IMO compliance.
Conclusion
An ISM compliance system should make it easier for a company to answer hard questions about its own operation. It should show what changed, who verified it, what evidence exists and where the uncertainty remains. A system that only proves every clause has a document behind it has automated the least informative part of compliance.
The test is not whether the software can find a procedure for section 7. The test is whether the company can show that the procedure is what people do, that they understand why, and that someone independently checked. That evidence is still produced by people doing the work and by reviewers willing to look.
If the system went offline tomorrow, could your team still demonstrate that the safety management system works?
References
- IMO: International Safety Management Code and amendment history. Sections 1.2, 4 to 7, 9, 11 and 12 provide the framework discussed here.
- Resolution A.741(18): original adoption of the ISM Code. This is the original text, not a current consolidated edition; read it with the amendments listed by IMO.
- IMO: SOLAS, 1974, as amended, including chapter IX, Management for the Safe Operation of Ships.