Chartera
Maritime answers

How chartering teams track NOR, SOF, demurrage, and claims

Chartering and operations teams need a shared timeline where NOR, SOF events, CP terms, open actions, and claim-side exposure stay connected.

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

Source-linked output anatomy

Chartering and operations teams need a shared timeline where NOR, SOF events, CP terms, open actions, and claim-side exposure stay connected.

4 source inputs

Source packet

Inputs captured before any output is trusted

1

Fixture recap and CP terms

2

NOR, SOF, port-agent, and master updates

3

Claims correspondence and deadline notes

4

Invoices, hire payments, bunker updates, and noon reports when relevant

Evidence Review item

How chartering teams track NOR, SOF, demurrage, and claims

Reviewable

Input

Forwarded port-agent email with SOF attachment

Classification

Laytime evidence / operational update

Matched context

TC operation and voyage record

Safe next action

Confirm SOF event treatment, then update laytime context

Source trail

Email, attachment, event row, CP clause, review state

Source trailReview stateHuman checkpoint

Failure modes avoided

What review catches

A summary looks plausible but is detached from the email, clause, document, or report behind it.

A task appears in a generic dashboard without who owns it, why it matters, or by when it needs action.

A source record is summarized once but does not become reusable operational context.

Desk checkpoint

Where the desk call stays visible

Desk review remains explicit for commercial decisions, disputed facts, role-specific interpretation, and material 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

    Capture the incoming record from email, forwarding, or document intake.

  2. 02

    Classify the record and match it to the relevant TC, voyage, counterparty, or operational context.

  3. 03

    Create a review item with source count, confidence, missing context, and the desk action to check.

  4. 04

    Route the reviewed item into cockpit work, contract context, claims context, or a source-linked record.

What stays under control

Preserves the evidence object: raw email, attachment, document, report, or source reference.

Shows review state before an extracted record is treated as operational truth.

Routes source-linked outputs into cockpit, contract, voyage, finance, laytime, and claims context.

Why these records drift

NOR, SOF, recap, fixture, port-agent updates, and claims correspondence often live in separate threads. By the time a claim is disputed, the team may be reconstructing events from scattered source material.

What good tracking looks like

A useful workflow keeps each event tied to vessel, voyage, counterparty, source message, owner, due date, and downstream financial relevance.

Where AI helps

AI is most useful when it extracts and routes facts from communication into a reviewable execution view. The important control is that source references stay attached.

Questions teams ask

Is this a replacement for claims teams?

No. The goal is earlier visibility, cleaner handoff, and better source trails before a dispute becomes expensive.

What should be tracked first?

Start with high-risk events: NOR timing, stoppages, completion events, claims deadlines, and owner-assigned follow-ups.

Can this start from email?

Yes. Chartera proof pages show operations communication becoming source-linked task and status records.