Maritime Guides

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.

How the Work Holds Together

Inputs, checks, exceptions, and human review.

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

  • Statement of facts event timeline
  • NOR tendering and acceptance timing
  • Relevant charterparty laytime clauses
  • Weather, stoppage, berth, loading, and discharge notes

Chartera

  • Brings SOF events, CP terms, and operational notes into one review view.
  • Keeps extracted timeline rows tied to the source event, clause, message, or document.
  • Separates calculated exposure from assumptions that still need commercial confirmation.
  • Prepares the result for review, claims work, or an assigned follow-up.

Watch For

  • 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.

Human Review

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

What the Team Reviews

Laytime Position

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 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.

Common Questions

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 case study shows the inputs, process, and result the team reviews.