Electronic ship logbook
Deck and engine entries that survive the voyage — and become your compliance numbers.
A ship logbook is written where there is no internet. Most digital logbooks assume otherwise, which is why crews go back to paper and the office rekeys everything weeks later. This one is built the other way round: the entry is written and kept on the device, then reconciled with the server when a connection returns.
What it does
- Separate deck and engine journals, matching how the two departments actually record
- Works with no connection — entries are queued on the device and sent when signal returns, without duplicating
- Each entry carries who wrote it and when, and corrections are recorded rather than overwritten
- Export a voyage or a date range as PDF for a verifier, inspector or charterer
- The same entries feed EU MRV, IMO DCS and CII figures — no second data entry for compliance
- Web and mobile, so the office and the vessel work from one record
Who it is for
Small and mid-size fleets that keep real logbooks and do not have a class-society ERP behind them — typically coasters, general cargo and short-sea operators.
Why offline is the whole problem
Bunkering, departure, arrival, weather and consumption entries are made at the moment they happen. At sea that moment usually has no connection. A logbook that silently loses an entry, or silently writes it twice when the signal returns, is worse than paper because nobody notices.
Entries here are stamped with an identifier before the first send attempt. If the send fails they stay queued; if it succeeds twice, the second is recognised as the same entry rather than a new one. A failed send is visible to the crew, not swallowed.
From the logbook to the report
Consumption, distance and time recorded in the journal are the same figures a monitoring plan requires. Instead of asking the crew to write them twice, the reporting layer derives EU MRV, IMO DCS and CII from what was already logged.
Where a figure cannot be derived it is left blank rather than estimated. An empty field is a question you can answer; an invented one is a finding waiting to happen.
What this is not
This is an operational logbook, not a type-approved electronic record book. Statutory record books — the Oil Record Book and its equivalents — carry flag-state type approval requirements that this does not claim. Keep those as your flag administration requires.
Common questions
Does it work without an internet connection?
Yes. Entries are written on the device and queued; they are sent when a connection returns. The crew sees what is still waiting to be sent, and an entry that reaches the server twice is stored once.
Is this a type-approved electronic record book?
No. It is an operational deck and engine logbook. Statutory record books such as the Oil Record Book have flag-state type approval requirements that this does not claim to meet.
Can a verifier be given the logbook?
Yes. A voyage or a date range can be exported as a PDF, and the underlying entries carry the author and the time they were recorded.
Do the logbook entries have to be retyped for EU MRV?
No. The reporting layer reads the same entries. Consumption, distance and time recorded once become the MRV, IMO DCS and CII figures.
Free for shipowners
Bunker procurement is free for shipowners — suppliers pay the commission. The compliance layer comes with it.