A worked audit, line by line
MV NORDIC DAWN — how one messy SoF becomes a $16,312.50 settlement
This is a complete laytime audit on a sample voyage, published so you can judge the engine without sending us anything. The inputs are below; the computation is the engine’s verbatim output; and the same voyage is pre-loaded in the live worksheet — change any event and watch every figure recompute.
1 · The charter terms
A discharge call at Rotterdam under a non-reversible fixture. These seven values are the entire contractual configuration the engine needs:
- Laytime allowed
- 72h 00m (3 days)
- Demurrage rate
- $18,000.00 / day
- Despatch rate
- $9,000.00 / day
- Weekend rule
- SHEX — Sundays & holidays excepted
- Laytime type
- Non-reversible
- NOR gates
- WIBON · WCCON · WIFPON
- Turn-time
- None (0h)
2 · The Statement of Facts
Nine events. In a live audit these are AI-extracted from the scanned SoF and verified by a human in the worksheet; whether each interval counts is then a matter of the charter terms, not opinion.
| ID | Timestamp | Event | Counting |
|---|---|---|---|
| E1 | Sat 08 Jun 2024 · 12:24 UTC | NOR tendered | counts |
| E2 | Sat 08 Jun 2024 · 16:00 UTC | NOR accepted | counts |
| E3 | Sun 09 Jun 2024 · 04:30 UTC | Shifting to berth | excluded |
| E4 | Sun 09 Jun 2024 · 06:00 UTC | All fast | counts |
| E5 | Sun 09 Jun 2024 · 07:00 UTC | Cargo commenced | counts |
| E6 | Mon 10 Jun 2024 · 11:00 UTC | Weather delay — rain | excluded |
| E7 | Mon 10 Jun 2024 · 14:00 UTC | Weather cleared | counts |
| E8 | Tue 11 Jun 2024 · 15:30 UTC | Cargo completed | counts |
| E9 | Tue 11 Jun 2024 · 16:30 UTC | Hoses disconnected | counts |
3 · Where the time goes
This is the part that quietly goes wrong in spreadsheets. Laytime commences with the valid NOR at 12:24 on Saturday under WIBON — but the fixture is SHEX, so Sunday hours are excepted from counting. The shifting interval (E3→E4) is excluded. The rain stoppage (E6→E7) is excepted in full — three hours that never touch the clock. Each exception is a window with a start, an end, and a factor; the engine intersects every window against the counting timeline in exact decimal minutes. No interval is approximated, and running the same inputs twice produces the same answer to the cent.
- Laytime commenced
- 2024-06-08 · 12:24 UTC
- Laytime would expire
- 2024-06-13 · 08:00 UTC
- Laytime allowed
- 3d 00h 00m
- Laytime used
- 1d 04h 30m
- Balance (time saved)
- 1d 19h 30m under allowance
4 · The settlement
The vessel finished 1d 19h 30m inside her allowance — 43.5 hours saved. Despatch at $9,000/day:
43.5h saved ÷ 24 × $9,000.00 / day
$16,312.50 despatch — owner owes charterer
Get the direction of one weather window wrong, or let a spreadsheet count Sunday under SHEX, and this number moves by thousands of dollars — in either direction. That is the entire case for computing it deterministically.
See it for yourself
- Download the statement (PDF) — the exact document a counterparty receives, rendered from this computation.
- Open the live worksheet — this voyage is pre-loaded. Move the rain window, flip SHEX to SHINC, and watch the settlement recompute. Nothing to install, nothing to send.
Illustrative sample voyage — not a client document. A live audit runs the same engine on your own Statement of Facts and is verified against the source. Method per the BIMCO Laytime Definitions 2013; all arithmetic exact-decimal, all timestamps UTC-native.