Reduce avoidable port charges by coordinating shipments sooner.

Read project44 events and timestamps, then confirm terminal availability and carrier terms. Missing coverage is an exception, not a guessed deadline.

1. 1.1Open a shipment from the team’s Import free-time exceptions worklist in project44 (ex: IMP-204). Match its container and bill-of-lading references to Oracle Transportation Management, retaining the terminal and carrier references.
2. 1.2Read the latest release and hold events, including their occurrence and update timestamps. Confirm customs and carrier release without treating an earlier clearance as proof that no newer hold exists.
3. 1.3Check the reported LAST_FREE_DAY event and its description for terminal demurrage. Reconfirm the deadline, local timezone, and pickup availability with the terminal (ex: Wednesday at 17:00 terminal-local).
4. 1.4Attach the confirmation and source timestamps to the shipment record. If release status or free-time coverage is missing, ask the terminal for the missing fact before proposing a pickup.

Record the terminal demurrage deadline and the carrier equipment-return detention deadline separately, including local time and contract terms in Microsoft SharePoint.

1. 2.1Create separate deadline rows in the shipment working record for Import demurrage and Import detention. Use the LAST_FREE_DAY description to distinguish them when project44 supplies both.
2. 2.2Record the pickup deadline in terminal-local time and the empty-return deadline in depot-local time. Retain a source confirmation for each; the dates and timezones may differ.
3. 2.3Open the relevant Microsoft SharePoint rate sheet and free-time terms. Check calendar-day rules, free-time extensions, and the charge trigger before counting chargeable days.
4. 2.4Calculate chargeable days under the applicable terms and rate tiers (ex: two days at $250 per day gives $500). Keep terminal exposure separate from equipment-return charges and recovery premiums.

Check Oracle Transportation Management shipment stops and get actual truck and receiving-slot confirmations through Microsoft Outlook.

1. 3.1Open the shipment stops in Oracle Transportation Management and read the current pickup plan. Check travel time, receiving hours, and unloading requirements before moving a single stop.
2. 3.2Use Microsoft Outlook to obtain a feasible truck, terminal slot, and warehouse appointment. Confirm any premium for the revised movement and retain the carrier’s quote with its expiry.
3. 3.3Confirm unloading capacity and an empty-return slot at the nominated depot before the return deadline. Check that the depot accepts the carrier’s equipment and required return reference.
4. 3.4Compare the full sequence with both deadlines and the transit time between stops. Present an exception if one confirmation is missing rather than treating a proposed time as booked.

The dispatcher reviews the carrier change, premium, and estimated exposure. No additional transport commitment is made before approval.

1. 4.1Prepare the dispatcher’s review with the existing plan, proposed appointments, and source confirmations. Show gross exposure, recovery premium, and potential net benefit separately (ex: $500 less $150 gives $350).
2. 4.2Compare the total additional commitment with the team’s $200 recovery-spend cap. Route amounts within the cap to the dispatcher and larger commitments to the configured higher approver.
3. 4.3Record the approver, time, quote, and authorized amount on the shipment. Confirm that the slots and premium are still available before committing to the revised plan.
4. 4.4If the carrier changes the price or a stop moves beyond its deadline, return the revised plan for a new decision. Do not treat the original approval as an open spending limit.

Write confirmed pickup and delivery appointments into Oracle Transportation Management with the source confirmation numbers. Planned times are not confirmed slots.

1. 5.1After approval, open Shipment Stops in Oracle Transportation Management and use Actions > Set Appointments for the affected pickup and delivery stops.
2. 5.2Enter the confirmed pickup and delivery times in each location’s timezone. Save the source confirmation numbers under the team’s pickup and delivery appointment references (ex: AP-204P and AP-204D).
3. 5.3Record the confirmed empty-return appointment against the return movement with its source reference (ex: ER-204). Preserve the depot’s acceptance instructions for the dispatcher.
4. 5.4Re-read the saved appointments and check feasibility across all stops. Retire the superseded bookings only after the replacement plan is confirmed, retaining cancellation acknowledgments.

Check actual project44 milestones and carrier confirmation; retain invoice-review evidence in Microsoft SharePoint. Close only after the return obligation is resolved.

1. 6.1Check actual gate-out evidence and its timestamp. Do not use project44’s PICKED_UP appointment event as proof that the container physically left the terminal.
2. 6.2Follow warehouse receipt and unloading, then match the carrier’s empty-return receipt to the shipment, container, depot, and return reference. Retain the actual return timestamp and its timezone.
3. 6.3Compare actual gate-out and empty-return times with their separate local deadlines. Keep the carrier and terminal receipts in Microsoft SharePoint alongside rate terms and any approved recovery premium.
4. 6.4Close the movement exception after return is verified, while leaving charge review pending until invoices are checked. Record avoided exposure separately from confirmed savings and deduct actual recovery costs when calculating net benefit.