Track laytime, capture NOR and SOF data at every port, and resolve disputes with timestamped evidence instead of email threads.
✕NOR reports arrive by email in different formats
✕Laytime calculated manually in spreadsheets
✕Disputes take weeks with evidence scattered across emails
✕No fleet-wide visibility into delay patterns
✕Agent performance is unmeasurable
✓Every port call event captured in structured fields
✓Status workflows enforce data completion at each stage
✓Laytime statements generated from recorded data
✓Fleet delay dashboard shows exposure across ports
✓Agent documentation quality is measurable
Custom fields capture NOR tendered, SOF details, berth and departure times, crew counts, draft readings, and voyage data as each event occurs.
Each stage requires specific fields before the job advances. The data exists because the workflow demands it.
Fleet-wide view of port call timelines, with filters by vessel, port, agent, and date range. Delay clusters surface before they become recurring losses.
Merge tags pull NOR, SOF, berth times, and exception periods into branded laytime statement templates via document generation.
Base captures the full port call timeline through custom fields that your agents fill as events happen. Arrival date, ETA and ETD, anchor drop and up, gangway down and up, first and last line ashore, free practice, clearance, officials on and off.
The level of detail scales to your operation. Some organizations track a dozen fields per port call. Others track closer to forty. The custom field system adapts to what your demurrage calculations require.
The job dashboard shows delay patterns across your fleet in real time. Filter by vessel, port, agent, or date range to see where demurrage exposure is building.
Vessel arrival analytics from government port call data add historical context. Compare documentation completeness across your port agents to identify where process gaps cost you money.
Port call timeline captured
Median charge-to-invoice
Government arrival data
Enforced field completion
A VMS tracks the voyage. Base tracks what happens at the port, which is the stage where demurrage actually accrues. Your VMS says the vessel sailed from Houston to Rotterdam. Base says it waited 14 hours for a berth and the laytime clock started at 1300 after free practice.
Adoption works when the tool is faster than the current process. Agents at one organization hit 80% activation because Base replaced their spreadsheet and email workflow with structured fields that auto-populate from previous jobs.
Bring a port call that turned into a demurrage dispute: the NOR timestamps, the SOF, the laytime clock, the exceptions. We will rebuild it inside Base together. See every delay tagged to the hour, every exception documented, and the audit trail you would hand a principal or a charterer. Operators running laytime tracking in Base typically resolve demurrage disputes in days instead of weeks once evidence lives beside the port call.
The same timeline feeds your disbursement documents, your QuickBooks and Xero charge lines, and vessel compliance history, all keyed to the same port call.
Every port call generates a timeline of events. The only question is whether that timeline lives in scattered emails, or in a structured record your team can act on.