Step 1
Sanitized source packet
Email subject
MV PACIFIC SIGNAL - SOF update and rain stoppage
Attachment
Statement of facts PDF, port agent recap
Operational note
Rain stoppage reported 15 Jul 0200-0600; receiver asking for updated laytime position.
Operations desk examples
Inspect a sanitized TC operations flow. Start with a forwarded email and attached SOF, then follow how Chartera classifies it, links it to the right TC file, keeps the source trail, and turns it into a desk item to check.
This is an illustrative walkthrough using sanitized sample material. It is not a customer record or a measured proof claim.
Step 2
Evidence Review item
Classification
SOF / laytime evidence
Matched record
TC operation: Santos -> Qingdao grain voyage
Confidence
High match, one event needs operator confirmation
Missing context
Confirm weather exception language against CP clause
1. Evidence intake
A forwarded email and attached SOF enter Chartera as source material. The original message and attachment remain available for review.
2. Classification and match
The packet is classified as laytime evidence and matched to the relevant TC operation, with confidence and missing context surfaced.
3. Review actions
The operator can confirm the match, open the TC, request follow-up, mark reviewed, or leave the item in the review queue.
4. Cockpit action
Once reviewed, the item becomes source-linked work: a cockpit action, laytime context, or contract record update with evidence attached.
Desk call
What the chartering desk checks
A chartering desk does not need another loose summary. It needs to know whether this SOF belongs to the right TC file, whether the rain period changes laytime, and what can safely move forward.
Confirm the file
Right vessel, voyage, counterparty, TC operation, and source packet?
Check the clause
Does the CP weather language put this rain period on or off the clock?
Make the desk call
Update the laytime file, ask the agent for clarification, escalate, or hold.
Step 3
Review actions
Confirm matchOpen in TCRequest follow-upMark reviewedNo action needed
The desk keeps the call. Chartera shows the inferred match, source material, and next desk action so a manager can check it before the laytime position moves.
Step 4
Cockpit queue and source trail
Critical
Confirm rain stoppage treatment before laytime statement is sent.
Today
Review SOF event window and CP weather exception language.
Watch
Receiver has requested updated laytime position; source packet attached.
Source trail
- Email: SOF update from port agent
- Attachment: statement of facts PDF
- Clause context: weather exception review required
- Review state: operator confirmation needed