1. Select the operation
How this works
Pick Part I or Part II, then a code letter on the left. The assistant asks for each required item one at a time — exactly the items a Port State Control inspector expects to see. Watch the right-hand page fill in as you go, in the same numbered-item format as the official Oil Record Book. You review and sign at the end; nothing is written to the ledger until you confirm.
📖 Live record preview
This is the actual page your entry is being written onto — updates as you answer.
Vessel particulars
Engine Room Holding Tanks
Configure once per vessel — this is what the AI assistant's tank pickers and the volumetric lockout check draw from. Matches the "Identification of Ship's Tanks" plan view in the official ORB.
Cargo & Slop Tanks
Only needed for tankers carrying oil in bulk (Part II). Leave empty for a non-tanker vessel.
Fuel Types Management
The fuel and lubricant types this vessel is certified/equipped to carry and bunker. This is what the AI assistant offers when logging a Code H bunkering entry — so "type of fuel oil" is always a controlled pick, not free text.
Vessel snapshot
Tank status
🔒 Ledger integrity (tamper-evidence)
Every signed entry is cryptographically chained (SHA-256) to the one before it — the same approach used in the tested backend build. Recomputing the chain here detects any entry whose content was altered after signing, or any entry moved out of sequence.
Data archive
Export writes everything you can see — fleets, vessels, tanks and every Oil Record Book entry — to a single JSON file, generated by the server. Keep it as an offline archive of the record.
Restore reads only the fleets and vessels from such a file, to re-create them on a new installation. Entries are never written back: a signed entry belongs to the hash-chained ledger and can only be created through the Oil Record Book itself.
Audit trail — scoped to what your role can see
| # | Timestamp | Vessel | Role | Action |
|---|