Bulk Cargo Voyage Tracker

Follow the voyage: vessel nomination against the laycan, AIS position (free trackers cover it) for the sea leg, NOR tendered at arrival, then loading/discharge progress in daily tonnage. The commercial clock is laytime — demurrage here is a charter-party calculation, not a tariff — so the dates this board records are exactly the ones a laytime statement will need.

The cost-bearing and decision-bearing ones — for this mode, watch in transit (where dwell starts costing) and the transition into completed (where the record closes). Rows that stall between those two stages are the ones worth a phone call today rather than a report next month.

No — that's the design choice. API visibility platforms are excellent and expensive; this board costs nothing and runs on the notifications you already receive. Start here, learn which lanes genuinely need real-time feeds, and buy integration only where the manual cadence actually fails you.

Via export/import workflow rather than live sync: the data is deliberately local-only for privacy. The pragmatic team pattern is one owner per board (dispatch owns it, everyone reads the morning CSV), or per-person boards split by client or lane. For true multi-user sync you'd graduate to a shared system — this is the zero-cost on-ramp.