MARPOL Compliance Software: What the Record Book Still Has to Prove
A digital record can be legible, searchable and complete, yet still describe something that never happened. Approval, attribution and reconciliation matter before the interface does.
MARPOL compliance software can remove real frustrations: illegible handwriting, missing pages, version confusion and the scramble to retrieve records when an inspector arrives. A chief engineer who can find the right entry in seconds has gained something useful.
But the record is more than an administrative artefact. It describes a specific operation, quantity and time. Software can make that evidence easier to keep and examine. A completed field alone cannot establish that the operation happened as described.
Before buying, separate three questions: which records apply to this ship, whether the electronic book is approved for its intended use, and whether the entries can be reconciled with the operation.
Start with the ship's applicable records
MARPOL addresses oil, noxious liquid substances, harmful substances in packaged form, sewage, garbage and air pollution through six technical annexes. Its record requirements are not identical for every ship. Applicability depends on the annex and regulation, including ship type, tonnage, cargo, persons carried, voyage and equipment. Build a vessel-specific list using the current amended text and flag requirements.
Annex I provides for Oil Record Books Part I and, for applicable oil tankers, Part II; Annex II for the Cargo Record Book; Annex V for garbage records; and Annex VI for specified air-pollution records. As one practical example, the Garbage Record Book threshold was lowered from 400 to 100 gross tonnage from 1 May 2024. The other applicability routes in Annex V regulation 10.3 also matter. An old checklist can miss an obligation before the software is installed.
| Record | What it records | What still needs checking |
|---|---|---|
| Oil record book | The operation, quantity, time and required signatures | Consistency with tank quantities, transfers, equipment status and landing receipts |
| Garbage record book | Waste category, quantity, operation and responsible signatory | Whether the category and handling reflect the actual waste stream and applicable discharge restrictions |
| Fuel and sulphur records | Fuel documentation and recorded changeover information | Whether the records match the fuel used and the operation performed |
| Equipment logs and alarms | Recorded running status, measurements and alarms | Equipment condition, measurement reliability and the response to abnormal indications |
An unexplained mismatch weakens the record as evidence of compliance. It calls for investigation, not an automatic conclusion that an illegal discharge occurred.
An approved record book is different from a supporting tool
A dashboard, spreadsheet or document store is not automatically an approved electronic record book. The MARPOL amendments permitting electronic books under Annexes I, II and V define them as systems approved by the Administration, taking IMO guidance into account. Check the exact book, software version and ship covered before replacing a statutory paper record. Annex VI and the NOx Technical Code have their own corresponding provisions.
IMO resolution MEPC.312(74) provides the supporting guidelines. These cover identifiable users, authenticated signatures, traceable corrections, master verification, backup and recovery, and inspection access. Section 5 calls for written confirmation from the Administration to be carried aboard. A recognised organisation may assess the system and issue that declaration on the Administration's behalf where authorised. A vendor brochure or generic type-approval claim does not replace checking the applicable approval and onboard declaration.
Failure cases worth testing
Confusing the operation signature with master verification
For Oil Record Book Part I, IMO recording guidance distinguishes the officer or officers in charge of the operation, who make and sign its entries, from the master, who signs each completed page. The master need not have personally witnessed every operation. Electronic arrangements must preserve these different responsibilities and meet the Administration's authentication requirements. Shared accounts and signing for another officer without a valid basis undermine accountability. Batch verification is not automatically improper: the applicable process, attribution and actual review matter.
Missing recorded as zero
A blank is a question. A zero is a statement. If an unrecorded sounding or landing becomes zero in a summary, the system has created a fact that was never established. Ask how missing, estimated, corrected and verified values remain distinguishable throughout export and reporting. The same check belongs in the review of AI-generated environmental summaries.
Corrections that erase the original
Legitimate errors need correction. The important distinction is between a visible amendment and an invisible replacement. Ask to see the first value, the correction, who made it, when it changed and whether verification must be repeated. A polished final page without that history can conceal the very issue a reviewer needs to understand.
Records completed in a burst before arrival
Late entries or clustered timestamps deserve examination against the applicable prompt-recording requirements. They can indicate a process problem, but timestamps alone do not prove falsification. Preserve the operation time, entry time and explanation rather than making the history look tidier.
What to require in a supplier demonstration
Ask for these checks using a test record and the ship's actual operating constraints. They are practical procurement questions, not a replacement for the Administration's approval process.
- Show the approval scope. Identify the flag Administration, covered record books, software version and onboard declaration. Establish the route for updates or a change of flag.
- Trace a correction. Demonstrate the original value, amendment, user, time and verification status. Export the same history.
- Test an outage. Demonstrate onboard access, backup restoration and the approved continuity arrangements. Explain how later reconciliation avoids duplicates or invented entries.
- Keep missing data visible. Show the effect of a missing reading on a balance, dashboard and exported report. It should not silently become zero.
- Produce an inspection copy. Test export and printing with amendments and verification details. Establish access for the applicable retention period after a subscription ends.
- Follow the ship's procedures. Identify who makes, signs, reviews and retains each record. Resolve any conflict between the platform workflow and the SMS before implementation.
- Explain the AI boundary. Source-backed transcription or a draft summary needs validation and the applicable signing process. Filling gaps with plausible quantities, times or operations is fabrication.
Under MEPC.312(74), inspection arrangements include access using onboard equipment and the ability to print records. For an investigation, section 6.3 addresses printed copies certified by the master. Test the process before the ship needs it.
A reconciliation to try before buying
Illustrative test data, not a vessel record or a product screenshot. Begin with a sludge tank containing 12.0 m3. Add 3.5 m3 recorded as generated or transferred in, and subtract an 8.5 m3 landing supported by a receipt. The expected balance is 7.0 m3, but the next reported quantity is 7.8 m3.
- Keep the difference visible: 0.8 m3 remains unexplained. Do not invent a transfer or discharge to make the figures agree.
- Check the basis: confirm the same tank, units and time interval. Review the measurement method, calibration, relevant operating conditions and other documented transfers.
- Separate observation from decision: preserve the readings and receipt, name the reviewer and record the next evidence needed. Close the discrepancy only when the explanation is supported.
This demonstrates review logic, not an allowable measurement tolerance. Repeat it with a missing reading, a corrected receipt and an offline entry. A useful system retains the uncertainty and review trail in every case.
Prepare the review before the port call
Inspection preparation should reconcile the environmental records with equipment status, maintenance, receipts and the crew's account. PSC Inspection AI Response supports inspection preparation and deficiency response; it is not a dedicated environmental compliance kit. For checking generated summaries against source information, see the AI Hallucinations Guide And Toolkit. Check each enquiry listing for scope and availability.
These resources do not supply an approved electronic record book, flag approval or a guaranteed inspection outcome. Use the current product descriptions to check the material included and adapt the review to the vessel's procedures.
A MARPOL deficiency may also expose an SMS weakness: an unsuitable procedure, a training gap, an unreviewed deviation or a corrective action that did not work. Review recurring discrepancies alongside maintenance, training and audit evidence. The articles on false assurance and ISM compliance software explore that wider management-system problem.
The purchase decision
A useful MARPOL system makes records more trustworthy and easier to challenge. It preserves authorship, corrections, uncertainty and the evidence behind a review decision. It also has to be approved where it replaces a statutory book and usable under the ship's real operating conditions.
Ask: when this entry is challenged, can the ship show the applicable approval, the responsible signatories, the source evidence and any unresolved difference? That is a stronger buying test than a screen full of completed fields.
References
- IMO: MARPOL overview and six technical annexes. Use the current amended text and applicable flag requirements for vessel-specific duties.
- Resolution MEPC.314(74): electronic-record-book amendments to MARPOL Annexes I, II and V.
- Resolution MEPC.312(74): Guidelines for the Use of Electronic Record Books under MARPOL, particularly sections 2, 4, 5 and 6.
- MEPC.1/Circ.736/Rev.2, hosted by the Netherlands maritime authority: recording operations in Oil Record Book Part I.
- IMO: prevention of pollution by garbage from ships, including the Annex V record-book threshold effective 1 May 2024.
- IMO: ISM Code and amendment history: sections 1.2, 7 and 9 provide the management-system context.