Inputs
- Statement of facts event timeline
- NOR tendering and acceptance timing
- Relevant charterparty laytime clauses
- Weather, stoppage, berth, loading, and discharge notes
Laytime calculation turns vessel event history and charterparty terms into an allowed-time position, used-time position, and demurrage or dispatch exposure.
The useful result is not an isolated answer. The team needs to see what Chartera used, what it did, what can still go wrong, and where judgment is required.
Inputs
Chartera
Watch For
Human Review
What the Team Reviews
Inputs
SOF PDF, port-agent recap, fixture/CP terms, relevant email thread
Extracted event
15 Jul 0200-0600, rain stoppage
Clause candidate
Weather exception language flagged for operator review
Calculation row
4.0 hours marked as exception candidate before final treatment
Output state
Draft laytime position with unresolved assumption visible
Next action
Confirm event treatment before sending statement or claim-side position
The usual inputs are the statement of facts, relevant charterparty clauses, NOR timing, loading or discharge event windows, weather and stoppage notes, and the commercial rate assumptions used by the desk.
Teams often reconstruct the same timeline across email, PDFs, spreadsheets, and CP language. The risk is not only arithmetic error; it is missing a source event or applying a term without enough review context.
The useful output is not a black-box answer. It is a reviewable laytime position with allowed time, used time, status, financial impact, and references back to the SOF and terms used.
Yes. Chartera is positioned as a review layer and workflow system, not a replacement for commercial judgment on disputed facts or terms.
The value is source context. A spreadsheet can calculate a number, but the team still needs to know which events, clauses, and assumptions produced that number.
The laytime from SOF + CP case study shows the inputs, process, and result the team reviews.