Chartera
Maritime answers

What is laytime calculation from SOF and CP terms?

Laytime calculation turns vessel event history and charterparty terms into an allowed-time position, used-time position, and demurrage or dispatch exposure.

Answer path

From explanation to reviewable work

Inspect example

Source packet

Email, attachments, and operational documents

Evidence Review item

Classified output with source links

Cockpit action

Owned task for the operating desk

Desk decision

Confirm, correct, ask for clarification, or escalate

01Start with the canonical explainerUse the source-linked output page as the baseline for evaluating any Chartera workflow output.Read source-linked standard02Inspect the desk surfaceSee a sanitized source packet become an Evidence Review item, source trail, and cockpit action.Open operations desk example03Check control pointsReview email access, AI usage, source retention, desk review, deletion, and procurement questions.Review trust controls

Evidence object

Laytime review artifact

Laytime calculation turns vessel event history and charterparty terms into an allowed-time position, used-time position, and demurrage or dispatch exposure.

5 source inputs

Source packet

Inputs captured before any output is trusted

1

Statement of facts event timeline

2

NOR tendering and acceptance timing

3

Relevant charterparty laytime clauses

4

Weather, stoppage, berth, loading, and discharge notes

5

Demurrage or dispatch rate assumptions

Evidence Review item

What is laytime calculation from SOF and CP terms?

Reviewable

Source packet

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

Source trailReview stateHuman checkpoint

Failure modes avoided

What review catches

A weather stoppage is counted or excluded without checking the CP clause.

NOR timing is accepted from one message while the SOF shows a different operational sequence.

A spreadsheet result survives, but the team cannot reconstruct which events produced it.

Desk checkpoint

Where the desk call stays visible

Commercial review remains required for disputed facts, clause interpretation, exception treatment, and any claim-side position sent outside the team.

Chartera prepares

Matched TC or voyage context, missing evidence, source trail, and the desk item to check.

The desk decides

Confirm, correct, ask the agent for clarification, escalate, approve, or hold it back.

The file carries forward

The reviewed call stays attached to the task, record, laytime file, or claims pack.

Workflow trace

  1. 01

    Normalize the SOF event timeline into reviewable time windows.

  2. 02

    Attach each material event to the source line, message, or document it came from.

  3. 03

    Apply the relevant CP assumptions and mark exceptions that need human confirmation.

  4. 04

    Calculate used time, allowed time, and exposure with the source trail still visible.

What stays under control

Builds a review packet from SOF events, CP terms, and operational notes.

Keeps extracted timeline rows tied to the source event, clause, message, or document.

Separates calculated exposure from assumptions that still need commercial confirmation.

Turns the result into a workflow artifact that can move into review, claims context, or cockpit follow-up.

The source material

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.

The operational problem

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.

What Chartera should produce

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.

Questions teams ask

Does laytime calculation require human review?

Yes. Chartera is positioned as a review layer and workflow system, not a replacement for commercial judgment on disputed facts or terms.

What makes this different from a spreadsheet?

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.

Where can I see an example?

The laytime from SOF + CP proof page shows the input, process, and resulting artifact pattern.