Track the last free day with the tariff and event evidence beside it

The spreadsheet says Friday is the last free day. The carrier portal shows Thursday. The person who entered the date is off shift, and nobody can identify whether it refers to terminal storage, carrier demurrage or empty return.

A useful last-free-day record is an explainable calculation, not a date copied into a dashboard. It needs a named clock, governing rule, source event, counting convention, local time context and an owner who can act before the deadline.

Name the deadline the team is managing

A container can have more than one relevant free-time period. Use separate records for separate charge clocks rather than one ambiguous “LFD” column. Link each to the appropriate carrier, terminal, movement direction and equipment scope.

Carrier information itself can contain multiple applicable periods and exceptions. OOCL's India page is one example of why the relevant tariff section and validity date must accompany the calculation. OOCL India — Demurrage and detention free time and charges.

A minimal deadline record should include:

Calculate the boundary explicitly

Use this illustrative rule: five calendar days of free time, with the trigger date included as day one. The confirmed trigger occurs on 10 June in the agreed local timezone.

The last free date is 14 June. Under a different rule that excludes the trigger date, it would be 15 June. A one-day difference can therefore be a rule-definition issue rather than a data-entry mistake.

Do not add business-day exclusions or a midnight deadline unless the actual terms define them. A carrier's free-day calendar and the opening hours of an empty-return depot are also different constraints. Even when a contractual last free date is Sunday, an operation may need to act earlier because the available service window is narrower.

Preserve what is known and what is estimated

If the trigger event is predicted, the deadline is provisional. A later actual event should lead to a new calculation with a recorded reason. Keep the earlier value for audit and communication history; do not leave an old alert circulating without its changed context.

DCSA's Track and Trace standards provide shared container-journey event definitions. Using a standard helps align meaning, but the implementation still has to establish which authorised source supplies the event and whether it is current. DCSA — Track and Trace standards.

A source timestamp can also be corrected. Store event time and when the system received it. If the source moves a trigger back one day, the previously calculated deadline may already have passed. That should create a high-priority review, not merely update a cell.

Route conflicting dates instead of selecting the convenient one

Suppose the portal and the calculated record disagree. Compare clock type, free-time agreement, event status, timezone, calendar and amendments before treating either date as authoritative. The account owner should obtain clarification where the governing terms or source interpretation remain uncertain.

A manual override needs the same discipline. Capture the authority, reason, evidence and expiry or scope. A date changed “to stop the alert” is not a resolved deadline.

Connect the deadline to an achievable action

Working backwards from a verified last free date, identify booking, documentation, release, truck availability and depot appointment dependencies. The planned action time should allow for the actual operating windows and approved contingency, not simply equal the last free timestamp.

Extend the illustrative example to 14 June 2026, a Sunday. Suppose the designated depot is closed that day and its last Saturday acceptance window ends at 16:00 on 13 June. With two hours of travel and 30 minutes of gate processing, a departure at 13:30 on Saturday consumes all available time. Any agreed queue or traffic contingency requires an earlier departure. The commercial last free date remains Sunday; the operational action target is earlier.

Record both dates and the reason for the difference. A depot closure does not itself change free time. If two credible sources conflict, the planner should escalate and consider protective action within their authority while the account owner resolves the terms; selecting the later date to remove urgency leaves the risk unexplained.

Give each case an on-duty owner. Record the intended action, current blocker and next confirmation point. Acknowledging an alert means someone has seen it; closing the case should require the relevant completion evidence or another authorised resolution.

Deadline workflow: confirm clock and rule → obtain trigger evidence → calculate provisional or verified date → assign feasible action → monitor changes → close on evidenced completion. Missing or conflicting inputs route to a review queue while the operational risk remains visible.

For a small volume, a controlled register with a named shift reviewer may be sufficient. A carrier portal supplies useful source evidence but may not manage local transport dependencies. An integration is justified when repeated changes, several clocks or shift handovers exceed what the register can reliably track. Test each approach with a backward correction and a closed-facility case, and require it to show both the contractual date and the next feasible action.

Make a deadline reproducible and actionable

A reliable last free day explains both why the date is correct and what must happen before it. That combination is more useful than a coloured date field, especially when events, rules or operating windows change.

Next actions

1. Separate the deadline types currently stored in one container list.
2. Recalculate a sample using explicit trigger, calendar and inclusion rules.
3. Attach evidence and mark provisional or conflicting cases.
4. Assign actions using real transport and facility windows.
5. Test how a corrected event or amended free-time agreement changes the plan.

A deadline-control assessment should trace one completed container journey from the governing clock to the action taken too late.