Since 1 October 2020, when the MARPOL amendments in IMO resolution MEPC.314(74) entered into force, a ship can keep its Oil Record Book electronically instead of on paper. For a single vessel the change is about how the book is kept. For a fleet, it changes something larger: the company gets a live view of compliance across every ship, the kind of view paper has never allowed. This article looks at what actually changes when a fleet makes the move, past the obvious point that there is less paperwork.
Three things shift in practice: how a fleet sees its own compliance, how integrity is established, and how an inspection runs at the berth. None of them is a marketing abstraction; each maps to a specific MARPOL requirement and a specific mechanism.
Compliance visible across the fleet
A paper Oil Record Book records one ship, and only for whoever has the book in hand. For a company managing dozens of vessels, the compliance picture is always weeks behind: the office learns that a book has a gap when the vessel reaches port and the book is reviewed, or when a Port State Control officer finds it first. Aggregating the state of the records across a fleet in anything close to real time is not possible on paper.
An electronic system that syncs to shore changes the timing. Each vessel keeps its authoritative record locally, and when the satellite link is up the entries reach the shore side, where a superintendent sees entry counts, verification status, and pending items per ship. The record stays the ship’s, kept under MARPOL on the vessel; what shore gets is visibility. A gap or an unsigned page becomes something the office can see and act on while there is still time, instead of a finding read back to them after an inspection.
Integrity that is computed, not trusted
The requirement under MEPC.312(74) is that a confirmed entry cannot be altered or deleted without the change being detectable. On paper that property rests on the inspector’s eye and the crew’s honesty, and the limits of that are documented: falsified Oil Record Books have been the basis of pollution prosecutions, including cases under the United States Act to Prevent Pollution from Ships.
ShipORB establishes the same property by computation. Each entry includes the SHA-256 hash of the entry before it, so the entries form a chain in which any change to a stored entry breaks every hash that follows. A correction is a linked amendment, never an overwrite, and both records are kept. The verification check recomputes the chain and reports the first entry where the stored bytes no longer match. Integrity stops being something a fleet asserts and becomes something anyone can recompute and confirm, which is the same shift the paper-versus-electronic comparison treats as the strongest single argument for the electronic form.
Offline by necessity, not as a feature
Anything built for ships has to work without the internet, because satellite connectivity at sea is intermittent and a vessel can be out of contact for weeks. This is not a convenience; it is the operating condition. So every operation in ShipORB, creating an entry, reviewing it, verifying it, signing it, works against an encrypted on-vessel database with no network connection, and sync happens on its own when the link returns.
The same constraint governs inspections. MEPC.312(74) requires that an authorized officer can inspect and copy the entries, and on a ship that has to be possible with no shore connection. A Port State Control officer reads and filters entries on a LAN device, sees the full Created, Reviewed, Verified trail on any entry, re-runs the integrity check, and exports an IMO-format PDF with a per-page verification stamp, all on the vessel. The detail of how that inspection runs is covered in the PSC inspection walkthrough.
The signing duties do not relax
It is worth being clear that going electronic does not lighten the regulatory duties. MARPOL Annex I still requires the officer in charge to sign each completed operation and the Master to sign each completed page, under Reg.17 for Part I and Reg.36 for Part II. The retention period is unchanged: the book stays available for inspection and is kept for three years after the last entry.
What the electronic form does is enforce these rather than rely on them. ShipORB binds an ECDSA P-256 signature to each entry, treats a page as a fixed 25-entry block matching the paper form, and refuses to close a book while any page that holds entries is still unsigned by the Master. The continuity hash that links each closed book to the next keeps the three-year record provable across book changes, not just within one book. The duties are the same; the system makes them hard to miss.
What the move actually buys
Set against the paperwork it removes, the substantive gain from an electronic Oil Record Book is threefold. A fleet sees its compliance state while it can still act on it. Integrity becomes a computation an inspector can re-run, not a judgment about handwriting. And the inspection at the berth is faster and more definite, with an export whose integrity can be checked again later. Each rests on a MARPOL Annex I requirement and a named mechanism, not on a claim about modernization.
The approval step is real and runs through the flag Administration, which the flag-state acceptance article covers, and the paper book remains the fallback if a system is ever down. Inside those boundaries, the electronic ORB meets the regulation more reliably than paper on the requirements that matter most. The features page sets out the system in detail, and the compliance page maps each capability to the rule it satisfies.