LOG

Logbooks

Features

All 18 Features

Every feature in Logbooks is built for daily maritime work — simple to use, fast to navigate, and fully integrated with the rest of Navatom.

01

One Entry, Every Record Book

Each event on board is logged once, as an entry of its type: a Departure, a Noon report, a Fuel Changeover or a GMDSS Call. The type sets the form, the fields it needs and whether a position is required, and puts the entry in every record book it belongs to. A fuel changeover, for example, is in both the Deck Log and the Engine Log.

Entries are grouped by activity, from navigation and watchkeeping to cargo, engineering, environmental and radio, and each carries the voyage it belongs to. Favorites and suggestions put the types a crew uses most at the top.

  • 13 record books from one entry
  • 250+ entry types
  • Form set by the entry type
  • Grouped by 9 activities
  • Favorites & suggested types

02

Signed Logbook Days

Entries start as drafts and are completed, and a completed entry can still be corrected, with each change kept in its history. When the day's entries are done, an officer whose rank holds the right signs the day. Signing locks every entry of that day and discards any unfinished draft.

A signed day can be unsigned only by a rank that holds that right, with a reason on record. The day is counted in UTC, and each entry shows UTC and the vessel's local time side by side.

  • Draft, completed & corrected
  • Every change kept in history
  • Signing locks the whole day
  • Unsigning needs a right & a reason
  • UTC and ship's time together

03

The Logbook Drives Your Other Apps

A drill or safety committee meeting entry starts the drill or meeting in its app. An entry for authorities or inspectors on board starts the audit and takes its findings. Ending an engine breakdown or a navigation equipment defect records the downtime in PMS, on the equipment the entry names.

It works the other way too: drills, safety meetings, third-party audits, voyages, equipment downtime and deficiencies on critical equipment add draft entries for the officer to complete. The office chooses which of these links each vessel uses.

  • Drill & meeting entries start them
  • Inspection entries start the audit
  • Breakdowns record PMS downtime
  • Other apps add draft entries
  • Links chosen per vessel

04

Works Offline on Board

The ship app keeps the logbook working when the vessel loses its connection. Entries are created, completed, corrected and ended offline, with comments and attachments, and are sent in the order they were made once the connection returns. A change that clashes with the server, such as one to a day signed meanwhile, waits for a decision on board.

Signing a day needs the connection, and only once the device has sent every change for that day.

  • Log, complete & correct offline
  • Changes sent in order
  • Clashes shown, never lost silently
  • Signing waits for every change

05

Tasks That Run Until They End

Some events run for a while: a pilot on board, a sea passage, an ECA transit, a fuel changeover, a breakdown. The start entry stays ongoing until End Task logs its paired end entry, often with the subject already filled in, and deleting the end entry reopens the task.

  • 22 start and end pairs
  • Ongoing until ended
  • End entry prefilled from the start
  • Reopened if the end is deleted

06

Deck Log: Watch, Navigation & Maneuvers

The bridge records watch handovers with the watch team, position fixes, noon reports, weather observations, course changes, anchoring, mooring and pilots. The master's standing, night and company orders are logged, and each officer's acknowledgement is an entry of its own. Weather observations can be filled in with the current weather at the position, then corrected.

  • Watch handovers with the team
  • Position fixes & noon reports
  • Weather autofill at the position
  • Anchoring, mooring & pilots
  • Orders acknowledged by each officer

07

Engine Log: Readings, Soundings & Fuel

The engine room records machinery readings, tank soundings, bunkering, fuel changeovers and breakdowns. The daily fuel consumption is logged per consumer with the fuel remaining on board, checked against the previous entry and what was bunkered since, and it is the source of Voyage's emissions figures.

  • Instrument readings & tank soundings
  • Daily fuel by consumer
  • Checked against the last entry & bunkers
  • Bunkering & fuel changeovers
  • Feeds EU MRV, CII & IMO DCS in Voyage

08

Oil Record Book Parts I & II

Part I records the oil and oily-water operations of the machinery spaces: bilge water discharged overboard or automatically, oil residue (sludge) disposed of or incinerated, fuel tanks ballasted or cleaned, overboard valves sealed, and the oil filtering equipment's failures. Part II records an oil tanker's cargo and ballast operations, from loading, unloading and crude oil washing to slop discharge and the oil discharge monitoring equipment.

  • Bilge, sludge & oil residue
  • Overboard valves sealed & unsealed
  • Oil filtering equipment failures
  • Tanker loading, unloading & COW
  • ODME failures recorded

09

Garbage, Sewage & Ballast Water Record Books

The Garbage Record Book keeps Part I for garbage and Part II for cargo residues that count as garbage: discharged into the sea, landed to a reception facility, incinerated or lost by accident, by category. Sewage and graywater discharges are logged too. The Ballast Water Record Book records each uptake, treatment, exchange and discharge, and the ballast water management system's failures.

  • Garbage Parts I & II by category
  • Sewage & graywater discharges
  • Ballast uptake, exchange & discharge
  • BWMS failures recorded

10

Cargo Record Book for Noxious Liquids

For ships carrying noxious liquid substances in bulk, the Cargo Record Book records loading, unloading, internal transfers, mandatory prewashes, tank washings and their discharge, and the surveyor's control.

  • NLS loading & unloading
  • Mandatory prewash
  • Tank washings discharged
  • Surveyor control recorded

11

EGCS, ECA & Shore Power Records

The EGCS Record Book records when the scrubber starts and stops, its malfunctions and its residue. ECA entry and exit open and close the vessel's transit of an emission control area, and shore power connections are logged, as is a port call at berth without shore power, with the FuelEU exception that applies and the fuel burned instead.

  • Scrubber runs & malfunctions
  • ECA transits as tasks
  • Shore power, or the exception & fuel used

12

GMDSS Log

The radio log records the daily, weekly and monthly tests of the GMDSS equipment, battery capacity tests and surveys, distress, urgency and safety calls, work on the equipment, and the radio operators who join and leave.

  • Daily, weekly & monthly tests
  • Distress, urgency & safety calls
  • Operators joining & leaving

13

Ozone-Depleting Substances & Biofouling Record Books

The ODS Record Book records refrigerants and halons recharged, repaired, released, landed or supplied. The Biofouling Record Book records hull and niche area inspections, in-water cleaning and risk monitoring under the IMO biofouling guidelines.

  • Refrigerants & halons tracked
  • Hull & niche area inspections
  • Cleaning & risk monitoring

14

Fleet Positions Map

In the office, a map shows each vessel at its latest logged position, heading the way it was going, faded when that position is over 24 hours old. Choose one vessel or several to see their tracks over the last 24 hours to 14 days, with arrivals, departures, anchorages and bunkerings marked, and open any point's entry from the map.

  • Latest position of every vessel
  • Tracks over 24 hours to 14 days
  • Several vessels at once
  • Open the entry behind any point

15

KPIs on How the Logs Are Kept

More than 110 KPIs in the Logbooks menu measure the logs in 11 sections, from record integrity and bridge watchkeeping to drills, the oil record book, ballast water, the engine room, GMDSS and port calls. They show the days signed within 24 hours, entries changed after a day was signed, bilge water discharged or ballast handled while the oil filter or the ballast water system was failed, ECA entries with the changeover finished in time and the CO2 from the daily fuel reports.

  • 110+ KPIs in 11 sections
  • Days signed within 24 hours
  • Changes after a day was signed
  • Discharges while equipment was failed
  • Fleet or one vessel, by month or quarter

16

Fuel & Emissions Analytics

Four analytics pages read the daily fuel reports, bunkering records and tank soundings. Fuel on board shows the days of fuel left and sets the book against the tanks, Bunkering checks each delivery against its delivery note and sulphur limit, Consumption breaks the burn down by consumer, grade and state, and Emissions and compliance shows attained against required CII, EEOI per voyage and estimates for EU ETS and FuelEU.

  • Fuel on board & days left
  • Bunkers against the delivery note
  • Burn by consumer, grade & state
  • CII, EEOI, EU ETS & FuelEU

17

Office Review, Comments & Attachments

The office reads each vessel's logbook day by day, grouped by event, activity, record book or status, and adds comments and files to any entry. No office screen creates or changes an entry: the log stays the ship's.

  • Each vessel's day in one list
  • Group by record book or activity
  • Comments & attachments from the office
  • The log stays the ship's

18

Access by Rank on Every Vessel

Each rank on each vessel gets view or edit access to the logbook, and the rights to sign or unsign a day are given separately, so the company decides which ranks keep the log and which sign it.

  • View or edit per rank
  • Sign & unsign rights apart
  • Set for each vessel

Technical

Under the Hood

Architecture and engineering behind Logbooks — data handling, real-time sync, and interface design.

One Record, Many Books

An entry is stored once and listed in each record book its type belongs to, so the deck log and the engine log never hold two versions of one event.

Locked Days, Audited Unsigning

Signing a day locks every entry in it; unsigning needs its own right and a reason, and is recorded.

Changes Kept in Order

Changes made offline are sent in the order they were made, and a change the server refuses waits for a decision instead of being dropped.

UTC Days with Local Time

Logbook days are UTC dates, and every entry also shows the vessel's local time and offset.

Complete Event History

Every change to an entry is recorded with who made it, when and what changed, with comments and attachments on every entry.

Same Category

Related Modules

Other Operation modules that integrate with Logbooks.

Record every voyage from departure to arrival, and report its emissions for EU MRV, IMO DCS and CII.

Run shipboard operations step by step and control hazardous work with digital permits to work.

Solutions

Explore Solutions

Compliance and operational solutions powered by Logbooks.

CII & EEXI Compliance

Navatom builds each vessel's yearly CII dataset, with its attained annual efficiency ratio, from the fuel the engine room logs, so the figures you report are the ones the ship recorded.

Maritime Data Integrity & Retention

Navatom has never lost customer data. Years of maintenance records, voyage reports, crew documents and compliance evidence stay in one place, accessible instantly and preserved with complete integrity.

EU ETS for Shipping

Navatom keeps the per-voyage CO2 and EU MRV figures that EU ETS obligations are based on, built from the fuel each ship logs, so your ETS reporting starts from one record of what the fleet burned.

EU MRV Reporting

Navatom builds each voyage's EU MRV figures, from CO2 to transport work, from the fuel the engine room logs, for ships calling at EU/EEA ports under Regulation (EU) 2015/757.

Fleet Scalability & Rapid Onboarding

Add vessels to Navatom in minutes, not months. As a maritime cloud platform, Navatom requires no installation, no infrastructure scaling, and no IT projects — whether you are onboarding your second vessel or your two-hundredth.

FuelEU Maritime Compliance

Navatom records the fuel each ship burns, its shore power connections and the FuelEU exceptions that apply, giving you the data that FuelEU Maritime reporting under Regulation (EU) 2023/1805 needs.

IMO DCS Reporting

Navatom collects fuel consumption, distance and hours underway from daily operations and builds each vessel's IMO DCS dataset, in line with MARPOL Annex VI Regulation 22A.

Ship Management for Large Fleets

Navatom is an integrated ship management platform that manages large fleets with the same ease as small ones: 40+ modules, instant vessel onboarding, and years of operational data kept without performance loss.

Ship Management for Small Fleets

Navatom gives small fleet operators the same 40+ integrated ship management modules used by large fleets, with nothing to install and the ability to start from just one vessel.

Ready to try Logbooks?

Start your free trial today and see how Logbooks fits into your fleet operations.