Blog Post 06: ISM Code Compliance for Mid-Size Fleets
Title: ISM Code Compliance for Mid-Size Fleets: Practical Maintenance Documentation That Works
Target Audience: DPA / Compliance, Fleet Managers, Technical Superintendents, Shipowner Directors.
Core Keywords: ISM Code, Compliance, Maintenance Documentation, Audit Trail, IMO, DPA, Port State Control, Class Survey, Non-Conformity, Safety Management System, SMS.
The Documentation Burden on Mid-Size Fleets
For a shipowner managing 3 to 30 vessels, ISM Code compliance presents a structural challenge. The regulatory requirement is clear: the company must establish and maintain documented procedures for maintenance (ISM Code, Section 10). The practical reality is that producing audit-ready evidence for every maintenance intervention — across multiple vessels, jurisdictions, and suppliers — requires a discipline that many mid-size technical departments struggle to sustain.
The consequence is not theoretical. When a Port State Control officer or Class surveyor asks for the maintenance record of a critical system, the response should be a documented work order with evidence, not an email thread. When a DPA conducts an internal audit, the maintenance files should support the Safety Management System (SMS), not contradict it.
This article outlines what ISM Section 10 requires in practice, where mid-size fleets commonly fall short, and how an integrated maintenance operator addresses these gaps.
What ISM Section 10 Actually Requires
ISM Code Section 10 — Maintenance of the Ship and Equipment — establishes four obligations for the company:
10.1: Procedures for maintenance. The company must establish procedures to ensure that the ship is maintained in conformity with the rules and regulations of the flag State, Class society, and any additional company requirements.
10.2: Scheduled inspections. Inspections must be scheduled and documented at intervals consistent with statutory and Class requirements.
10.3: Non-conformities and corrective action. Any non-conformity identified during maintenance, inspection, or operation must be reported, analysed, and corrected. The company must document the corrective action and verify its effectiveness.
10.4: Equipment and technical systems. The company must identify equipment and technical systems whose sudden failure could cause hazardous situations. These systems must be subject to periodic testing and documented verification.
The critical detail is that ISM Section 10 does not prescribe a specific system or software. It requires documented evidence that maintenance is planned, executed, and verified. The form of that evidence is left to the company — but the audit trail must exist and must be demonstrable.
Common Gaps in Mid-Size Fleet Compliance
| Gap | Manifestation | ISM Risk |
|---|---|---|
| Fragmented evidence | Work orders with different suppliers in different formats, no central repository | Inability to demonstrate a coordinated maintenance system |
| Incomplete corrective action tracking | Non-conformities logged but corrective actions not verified as effective | Non-compliance with 10.3 |
| Missing risk-based identification | Critical equipment not formally identified; testing schedules not documented | Non-compliance with 10.4 |
| Vendor documentation not integrated | Supplier reports stored separately from the vessel's maintenance history | Audit trail discontinuity between external work and internal records |
| Language gaps | Critical maintenance documentation only in one language while crew speaks another | Safety communication risk; potential ISM finding |
A DPA conducting an internal audit should be able to trace any maintenance intervention — from planned preventive work to emergency repair — through its complete lifecycle: request, authorisation, execution, evidence, verification, and close-out. When the evidence chain is broken, the ISM audit trail is broken.
The Audit Trail as a Compliance Deliverable
The concept of an audit trail is central to ISM compliance. It is not an administrative overhead; it is the documented proof that the company's SMS is being followed in practice.
For each maintenance case, the audit trail should include:
- Initiation. How was the need identified? Planned schedule, crew report, survey finding, Class requirement?
- Work order. What was the scope? Who authorised it? What permit or isolation was required?
- Execution. Who performed the work? What method statement was followed? What evidence was captured (photos, test reports, NDT results)?
- Verification. Who verified that the work was completed correctly? Was Class or surveyor attendance required?
- Close-out. What documentation was filed? Is the SMS record updated? Is the next inspection date scheduled?
When this chain is maintained consistently, the DPA can present the complete evidence package for any maintenance item at an internal audit, external audit, or Port State inspection.
Practical Compliance for the 3–30 Vessel Fleet
For a technical department managing a mid-size fleet, ISM Section 10 compliance is achievable through structured processes rather than a large compliance team:
1. Standardise the work order format. Every maintenance intervention — whether executed by ship crew, a local workshop, or an external operator — should follow the same work order template with consistent fields: scope, permits, evidence, verification, close-out.
2. Centralise the evidence repository. All maintenance documentation should be stored in a single structure organised by vessel and by system. Spreadsheets and shared folders are acceptable at this scale; the requirement is consistency, not software sophistication.
3. Implement a non-conformity loop. Every non-conformity identified during maintenance must be recorded, assigned for corrective action, verified upon completion, and closed. The DPA must be able to demonstrate that this loop is functioning.
4. Identify and schedule critical equipment testing. For each vessel, identify the equipment and systems whose failure could create a hazardous situation (ISM 10.4). Schedule their periodic testing and document the results.
5. Integrate external supplier documentation. When a third party executes maintenance — dry dock, afloat repair, underwater inspection — their documentation must meet the same standard as the company's internal records. The DPA should not have to reconcile external reports manually.
How an Integrated Operator Supports the DPA
When a mid-size shipowner contracts maintenance execution to an integrated operator, the compliance benefit extends beyond the technical outcome. Each case delivered by Atlantech Marine produces a documented audit trail aligned with ISM Section 10 requirements:
- Work orders with scope, permits, and evidence.
- Non-conformity reporting and corrective action records.
- Critical equipment testing documentation.
- Close-out reports ready for Class, DPA, or PSC inspection.
The DPA does not need to reconstruct the evidence chain from multiple supplier invoices and emails. The case file — from request to close-out — is the audit trail.
Need to strengthen your fleet's maintenance compliance? Submit a service request or contact our team to discuss your ISM documentation requirements.
Atlantech Marine — Integrated maintenance with auditable compliance for mid-size shipowners. Based in Malta. Operating across the Mediterranean and West Africa.