Maritime Compliance Intelligence: What the Dashboard Cannot Tell You
Connect the applicable requirement, the supporting record and the decision. Keep missing evidence visible throughout that chain.
A fleet dashboard shows an action as closed. The repair record exists, the deadline was met and the monthly report is green. Ask what demonstrated that the equipment worked afterwards, and the answer may be harder to find. That gap is a useful place to begin when assessing maritime compliance intelligence.
Certificates, inspection findings, training records and maintenance data can all contribute to the picture. Their value depends on the question being asked. A completion date may establish that a task was recorded as finished. It does not, by itself, establish that the required control was effective.
The practical test is traceability: can a reviewer move from an applicable requirement to the evidence and then to the decision, without silently filling the gaps? A platform can support that chain well. The following diagnostic can help establish whether yours does.
Three layers that must stay visible
A useful compliance intelligence system keeps three layers distinct. Each needs its own evidence and review.
| Layer | The question it answers | Failure to test for |
|---|---|---|
| Obligation | What applies to this ship, flag, trade and date? | A generic checklist overlooks vessel-specific conditions or amendments |
| Evidence | What record exists, where did it come from and what does it establish? | Missing or self-reported information is treated as verified |
| Judgement | What conclusion does the evidence support and what should happen next? | The decision has no identifiable basis or accountable owner |
Applicability needs a basis. A requirement may depend on gross tonnage, construction date, voyage type, cargo, flag and the amendments in force. Record the source version and the vessel facts used to decide whether it applies. A justified exemption or equivalent arrangement needs its own authority and scope.
Evidence needs a status. Keep "not received", "received but not reviewed", "reviewed with an unresolved question" and "verified for this purpose" distinct. Missing data can indicate a failed transfer, a missing record or an unperformed activity. Those possibilities require different follow-up.
The decision needs an accountable author. Automated rules can flag exceptions and support conclusions. Preserve the rule version, source evidence and any human review or override. Responsibility for approving the method and acting on the result remains with the relevant people and organisation.
Follow one requirement through to a decision
Illustrative diagnostic only: the record below is fictional and is not a product screenshot or a finding about a real vessel. It examines a repair to a standby pump. The regulatory starting point is ISM Code sections 10.2 and 10.3, covering maintenance checks and records, and reliability measures including tests of standby arrangements. Use the applicable amended Code and the vessel-specific SMS procedures to determine the actual task.
| Link in the chain | Recorded position | Question still to resolve |
|---|---|---|
| Requirement and applicability | ISM 10.2/10.3 linked to the vessel-specific maintenance instruction and identified equipment | Has the reviewer checked the current instruction and required verification method? |
| Source evidence | Repair job card dated 2 November 2026; maintenance export received 4 November | Does the job-card reference match this pump and the reported defect? |
| Missing evidence | No post-repair test result is attached to the review file | Was the test done but not transferred, or is the activity outstanding? |
| Decision and owner | QHSE reviewer leaves verification open; technical superintendent coordinates with the chief engineer | What immediate operating controls or escalation are needed under the SMS while the condition is established? |
| Closure and follow-up | Closure depends on review of suitable evidence and a recorded decision | Who checks the result, and does the defect warrant a later effectiveness check? |
The honest status is "repair reported complete; verification unresolved". It is neither a confirmed equipment failure nor a verified success. If a missing record masks a safety-critical uncertainty, escalate immediately through the SMS rather than waiting for the next dashboard cycle.
This discipline also prevents inaccurate obligation labels. In the MLC's flag-State provisions, Regulation 5.1.1 concerns general principles, 5.1.3 certification, and 5.1.4 inspection and enforcement. Regulation 5.2.1 addresses port-State inspections. Record the particular provision and national implementation relevant to the evidence, rather than attaching a broad "MLC compliant" label.
The aggregation trap
A fleet percentage can hide the unresolved items underneath it. If a system excludes missing evidence from the denominator, a high verification rate may describe only the records that were easy to obtain. Report the number assessed, the number outstanding and the age and significance of those gaps alongside the percentage.
As a simple illustration, eight verified records out of eight reviewed is a different position from eight verified records out of ten expected, with two still missing. Neither figure explains the consequence of the missing records. The reviewer needs their identity and operational significance before drawing a conclusion.
Keep the reason for each classification, its author and its date. "Not applicable" should have a recorded basis; "verified" should state what was verified and for which period or activity. When definitions change, retain enough history to explain the effect on the trend.
Signals worth tracking
Overdue actions, certificate dates and audit completion are useful controls. Add a few diagnostic questions that test what those indicators mean.
- Repeated findings across different ships. Is there a common procedure, supplier, maintenance practice or training gap? Recurrence warrants investigation; it does not prove one system-level cause.
- Actions closed without evidence. Sample closed actions and ask whether the linked records demonstrate the required correction. Count unsupported closures separately from records awaiting review.
- Changes in reporting patterns. A decline in near-miss reports could reflect safer work, less activity, different definitions or reduced reporting. Compare exposure, reporting access and vessel feedback before calling it an improvement.
- Time between detection and escalation. Measure against the urgency of the issue. A short average can conceal a serious case that remained unresolved.
- Divergence between ship and office records. Compare timestamps, controlled versions and the original record. Either side may be stale or incomplete; establish which source supports the fact in question.
- Applicability exceptions. Sample "not applicable" entries and check their reasons against the vessel facts and governing requirements.
For a closer examination of corrective effectiveness, see why the same safety findings keep coming back.
What to ask before buying a maritime compliance platform
- Where does the obligation content come from? Can you see the source, version, amendment status and update process?
- Can it represent vessel-specific applicability and retain the reason for an exception?
- Can the supplier demonstrate missing, conflicting, unreviewed and verified evidence without turning any of them into an automatic green result?
- Who changed a record, when, and is the previous state preserved? Can you export the review trail?
- What does the score include or exclude, and can you inspect the underlying records and denominator?
- What happens when the vessel is offline, the source is unavailable or two records conflict?
- Does the AI layer suggest material for review or trigger a decision? How are its outputs checked and its data access controlled?
Keep AI suggestions separate from verified facts
AI can assist with reading at scale. A model can suggest themes across inspection reports, audit findings and incident narratives. Retain the source passages and record IDs so a reviewer can test the grouping, inspect exceptions and reject unsupported conclusions.
It can also assist with consistency checking, flagging differences between a procedure and its source or between two versions of a record. It may miss a contradiction or invent one, so treat the output as a review queue. In the pump example, it could flag the absent test attachment; it could not establish whether the test occurred.
These AI review steps are recommended working controls, not additional statutory certification. Use the company's authorised tools and existing document-control and approval arrangements. The AI Hallucinations Guide And Toolkit supports checking source information in AI-assisted drafts. Teams considering policy and pilot controls can review the AI Governance And Confidentiality Kit. These are enquiry listings, not live checkout offers.
A one-hour test on your current system
Pick one finding from the last year. Ask the platform, or the team, to show you:
- The applicable requirement, with its source version and date.
- The evidence that established the finding, and who reviewed it.
- The change made in response and the evidence of implementation.
- The check of effectiveness, or the reason and plan for a later check.
- The closure decision, its basis and its author, or the question keeping it open.
Note where the chain breaks and whether the problem is retrieval, a missing activity or an unsupported decision. One complete sample does not establish fleet-wide compliance, but an incomplete sample gives you a concrete improvement task. The same approach helps examine the file behind a maritime due diligence result.
If mapping questions to evidence and tracking unresolved review is the difficulty, the Audit And Evidence Readiness Kit provides a guide and editable audit tools for that supporting task. Start with one scope and assess whether another reviewer can follow the references. For inspection preparation and deficiency response, consider PSC Inspection AI Response. Confirm the current scope and delivery arrangements before ordering.
Conclusion
Choose one important decision and trace it backwards: who made it, what evidence supported it and which requirement or company control was being tested? Then trace the missing information forwards to an owner and an action. That is a practical test of the value your compliance intelligence provides.
Meriden's resources support that work as editable documents and review routines. They are not a compliance platform, certification service or substitute for operational evidence. The useful buying question is whether the material addresses the particular gap your diagnostic found.
A useful dashboard leaves the unanswered question visible until someone has evidence to resolve it.
References
- IMO: ISM Code and amendment history. Relevant sections: 9, reports and analysis; 10, maintenance; 11, documentation; 12, company verification, review and evaluation. The page also identifies MSC-MEPC.7/Circ.7, Guidance on near-miss reporting.
- IMO resolution A.741(18), original Code sections 10.2 and 10.3, maintenance checks, records and reliability measures. Read with the subsequent amendments listed by IMO, not as a standalone current consolidated text.
- ILO: Maritime Labour Convention, 2006, consolidated text including the 2022 amendments, Regulations 5.1.1, 5.1.3, 5.1.4 and 5.2.1 and the corresponding Standards A5.1.1, A5.1.3, A5.1.4 and A5.2.1. Confirm applicable national implementation and the ILO's amendment status.