The Oil Record Book is one of the documents a Port State Control officer reaches for early in an inspection. It is required on board under MARPOL Annex I, it is supposed to be current and signed, and it can be checked against the physical evidence in the engine room. When the entries, the equipment counters, and the tank soundings do not line up, the book is where the discrepancy shows. That is why the ORB has long been a focus of PSC, and why falsified Oil Record Books have been the basis of pollution prosecutions, including cases brought under the United States Act to Prevent Pollution from Ships.
An electronic ORB changes how the inspection runs, not what it checks. The officer is still confirming that the record is complete, signed, untampered, and consistent with the machinery. This article walks through what a PSC officer actually does with the book, where paper makes that hard, and how an offline electronic system answers each check on the vessel.
What the officer is checking
A PSC inspection of the Oil Record Book is a check on four things. First, completeness: every operation MARPOL Annex I lists, from bilge transfers to oily-water separator use to sludge landings, has to be recorded, with no gaps over the period under review. Second, signatures: each completed operation is signed by the officer in charge, and each completed page is signed by the Master, under Annex I Reg.17 for Part I and Reg.36 for Part II on a tanker. Third, integrity: entries should not show signs of alteration, erasure, or back-dating. Fourth, consistency: the ORB has to match the oil content meter readings, the oily-water separator running hours, the sludge tank levels, and the bunker delivery notes.
The authority for this sits in MARPOL and in the regional Port State Control regimes, the Paris MoU, the Tokyo MoU, and the others, which coordinate inspections and share results. An ORB deficiency can be recorded as a finding, and in serious cases, a book that is clearly false or grossly incomplete, it can contribute to a detention. The point is not that the book is read for its own sake; it is read because it is the written account of operations that have a direct pollution consequence.
Where paper books fail the check
Paper Oil Record Books fail the four checks in predictable ways. A missing signature is invisible until someone pages through every completed page looking for one. An altered entry is hard to prove and hard to disprove, because a single struck-through line can be a legitimate correction or a cover-up, and the paper does not say which. Back-dating leaves no trace at all if the handwriting matches. And checking months of handwritten entries against equipment counters is slow manual cross-referencing, done under time pressure while the officer also has the rest of the inspection to run.
These are not failures of diligence; they are failures of the medium. Paper records what was written, not when it was written or whether it was changed afterward. The integrity of a paper ORB rests on the inspector’s eye and the crew’s honesty, which is exactly the weakness that the documented falsification cases exploited. An electronic system that records the same operations can also record the things paper cannot: the time each entry was made, the identity behind it, and a cryptographic proof that nothing changed since.
The inspection, run on the vessel and offline
A vessel at a berth often has no usable internet, and the officer will not wait for a satellite pass. So the controlling requirement, stated in the MEPC.312(74) guidelines and treated as a hard constraint in ShipORB, is that the entire inspection works offline on the ship. The authoritative record lives in an encrypted database on the vessel, in SQLite with SQLCipher, and the inspection reads from there with no shore connection.
The officer works on a LAN device, in a browser on the vessel network. The dashboard shows the entry count, the verification status, and which operations are recorded over the period in question. Opening any entry shows its full workflow trail, Created, Reviewed, Verified, with the officer behind each step and the time it happened. Filtering to a date range or an operation code takes seconds, which replaces the manual page-turning that eats the most inspection time on paper.
Proving integrity instead of asserting it
The check a paper book cannot answer is the integrity check, and it is the one an electronic system answers best. Each ShipORB entry includes the SHA-256 hash of the entry before it, so the entries form a chain. The officer can run the verification independently from the integrity view: the system recomputes the chain and reports either that every entry matches or exactly where the first mismatch is. Changing a single byte of a stored entry breaks every hash after it, so a quiet alteration is not a matter of opinion; it is a failed check at a named entry.
Corrections are handled without hiding anything. A wrong entry is not overwritten; a linked amendment entry is created, and the original and the amendment are shown together, which is the digital form of the struck-through-and-initialled paper correction. Signatures are bound the same way: each state transition carries an ECDSA P-256 signature tied to the officer, only the Master can verify, and a book cannot be closed while any page that holds entries is still unsigned by the Master. So the signature check the officer runs by hand on paper is a property the system already guarantees.
The export the officer takes away
A PSC officer routinely wants a copy of the record. On paper that means a photocopy of the relevant pages. ShipORB generates an IMO-format PDF for any date range the officer asks for, matching the traditional ORB layout, with the vessel particulars, the entries in chronological order, the operation codes and item numbers, the officer, reviewer, and Master signatures, and a hash-verification stamp in each page footer. The export goes to a USB drive on the vessel, again with no shore connection.
The verification stamp is the part that matters for the record after the inspection. It lets the exported document be checked against the same hash chain later, so the copy the officer takes is not just a printout; it is a copy whose integrity can be re-confirmed. That is a property a photocopy of a paper page has never had.
What changes, and what does not
The regulation behind the inspection does not move. The ORB is still required under MARPOL Annex I, the retention period is still three years after the last entry, the signing duties under Reg.17 and Reg.36 still apply, and the officer is still checking completeness, signatures, integrity, and consistency with the machinery. An electronic ORB does not ask for a lighter inspection.
What changes is that the checks paper made slow or impossible become fast and definite. The signature check is guaranteed by the close logic. The integrity check is a recomputation, not a judgment call. The completeness and consistency review is a filter and a sort rather than a page-by-page read. For the crew, it means an inspection that is shorter and less adversarial; for the officer, it means a record that proves its own integrity. The PSC readiness checklist sets out the on-board steps a vessel runs before arrival, and the contact team can walk a fleet through a mock inspection.