Intermodal and drayage operations revolve around equipment identity, release conditions, gate events, appointments, customer commitments, and return obligations. A container may be physically present while unavailable for pickup. A completed delivery may leave an empty-return obligation open. A chassis can have a different owner and charge clock from the container. Freight transportation software needs to preserve these distinctions so that dispatch and finance work from the same movement history.
EXSPEEDITE's intermodal evaluation follows the container through availability review, pickup, delivery, chassis use, empty return, supporting documents, and billing. The goal is a coherent operational record with explainable exceptions. It is not a guarantee that every terminal supplies live data, that an alert prevents all charges, or that a calculated amount is automatically legally collectible. The carrier should establish the actual agreements, data sources, and approval responsibilities used in its operation.
Begin with stable container and shipment identities
Capture the container number, relevant booking or bill references, terminal or ramp, customer, equipment requirements, and the parties responsible for each movement. Keep those references distinct. A customer shipment can involve several containers, and a container may appear in different movements over time. A reused equipment number should not cause a new event to attach to an old completed job.
Establish how the TMS identifies the active movement and how duplicate messages are handled. Include revised references and uncertain matches in the demonstration. Operators should be able to investigate the original source rather than trusting an unexplained automatic match. The integrity of the identifier mapping affects every later milestone, document, charge, and customer update. Cleaning those mappings before enabling automation is usually more valuable than adding another status color to an unreliable record.
Availability is a state with dependencies
Distinguish physical arrival from availability, release, appointment eligibility, and an authorized pickup plan. The source of a status may be a terminal system, a railroad interface, an agent update, or a reviewed manual entry. Record when the source was checked and whether the observation is current enough for the operational decision. A stale available flag should not appear equivalent to a recently confirmed pickup condition.
In the EXSPEEDITE demonstration, use a container that arrives but remains on hold, followed by a later release. Ask how dispatch sees the change and which downstream actions are allowed. If a data source is unavailable, the workflow should identify the missing evidence and assign a follow-up. Software can organize the review and communication; it should not invent release authority or imply that every facility offers the same real-time integration.
Model Last Free Day with rule ownership
Last Free Day information should retain its source, effective time, equipment scope, and relevant calendar assumptions. A displayed date may come from an external party or a configured calculation. Those are different evidence types. Identify who maintains the applicable rule, how updates are approved, and how a changed date affects active work. Avoid treating one universal free-time formula as valid for every terminal, contract, or equipment type.
Test a changed availability date, a holiday calendar exception, and a conflicting Last Free Day value. The system should expose the conflict and preserve the earlier observation. Dispatchers need a prioritized action list, while finance needs enough history to investigate a charge later. An alert is useful when it triggers accountable work. It is not a promise that a pickup can always be arranged before the deadline or that every assessed charge is valid.
Separate container, chassis, and movement clocks
Container tracking should produce an equipment-specific timeline across port or rail availability, pickup, customer delivery, and empty return. Where an agreement uses per diem equipment charges, configure its actual daily rate tiers, free-time terms, start and stop events, calendar treatment, and approved exceptions. Retain the agreement version used in the calculation. Test a charge crossing a rate-tier boundary and a disputed return date; a generic day count should not silently become an approved customer invoice or carrier payable.
Container detention, terminal storage or demurrage, chassis usage, and truck waiting time may involve different parties and agreements. The carrier should define those categories explicitly instead of collecting them in one generic detention field. Record the start and end events relevant to each rule, plus any uncertain interval. A return of one equipment component does not necessarily close another component's obligation.
Use a demonstration where a container is delivered, the chassis remains in use, and the empty is returned later to a changed location. Ask EXSPEEDITE to show which obligations remain open after each milestone. Then inspect the proposed charges and supporting evidence. The system should distinguish observed duration from approved commercial treatment. These distinctions help operators act and help finance explain the outcome without reconstructing the entire movement from email.
Gate moves need receipts and discrepancy history
Terminal interchange records and equipment interchange receipts or reports establish useful evidence around gate activity and equipment condition. Terminology varies among operators; a label such as TIR should be defined in the carrier's workflow and not confused with an international customs transit document. Keep the relevant receipt, equipment details, event time, location, and reported damage attached to the movement. Maersk's EIR material illustrates the capture of container, damage, and trucker information. Maersk EIR
Test an unreadable receipt, a corrected equipment number, and damage identified at return. The workflow should preserve the original document and the reviewed correction. A gate observation should not erase a previously recorded discrepancy. Assign responsibility for obtaining missing evidence and resolving conflicting documents. The strongest operational record explains what was reported, by whom, and when, without presenting every imported field as an independently verified fact.
Dispatch appointments as constrained commitments
A driver needs the correct equipment, facility instructions, appointment, and expected movement sequence. A dual transaction or changed return location can affect the next assignment. Dispatchers should be able to distinguish a requested slot from a confirmed slot and see whether the current plan depends on an unresolved release or equipment issue. A calendar entry without that context can create a false sense of readiness.
Run a day with a late release, an unavailable return location, and a driver whose next assignment must change. Ask the operator to recover the plan while preserving completed movement history. Include stale telematics data so that the system's uncertainty handling is visible. Route planning and HOS observations support judgment, but they do not replace facility confirmation or a complete legal driving analysis. The carrier remains responsible for the approved operating plan.
Empty return is a distinct completion gate
Customer delivery does not necessarily complete the drayage job. The empty may need return authorization, an accepted location, an appointment, and a final gate receipt. Track those requirements separately. A delivered container should remain visible where an equipment obligation is still open. Define who monitors that queue and what event is sufficient to close it.
Test a return location change communicated after delivery. The workflow should retain the prior instruction and identify the approved current instruction. Confirm that a driver or dispatcher can attach the final receipt and that billing sees unresolved evidence. This is also a useful correction test: if the wrong empty was associated with the job, the system should preserve the correction history rather than silently rewriting the event. Operational completion should be explainable to both the customer and finance.
Rate the service, then review accessorials
A drayage rate can combine a base movement, fuel adjustment, chassis treatment, additional stops, waiting, storage, or other agreed items. Establish which items are included, which are conditional, and which require approval. Store the relevant agreement version and effective date. A fee observed on an external invoice does not automatically become an authorized pass-through charge to the customer.
In EXSPEEDITE, request a demonstration that links the operational event, supporting document, proposed charge, reviewer, and final invoice line. Reject one proposed charge and amend another. Inspect whether the system retains both decisions and prevents duplicate billing after an integration retry. Reproducibility matters more than a large accessorial menu. Finance should be able to explain why an amount was billed without relying on the memory of the dispatcher who handled the container.
Keep regulatory references current and scoped
A software rule should identify whether it comes from a contract, an operating policy, or an applicable legal requirement. These sources change on different schedules. Do not encode a regulatory summary from an old marketing article as an unquestioned invoice rule. Maintain an effective date, source reference, owner, and review process for any compliance-sensitive configuration, with specialist review where the decision requires it.
For example, the FMC reported that a court set aside the invoice-recipient provision in 46 CFR 541.4 while other parts of the billing rule remained. That history illustrates why an old rule summary needs verification before implementation. It does not establish the legal treatment of a particular carrier's charge. The TMS should preserve evidence and route decisions through the responsible process. FMC decision notice
Integrate customer and financial visibility
Customers may need milestones, documents, and exception updates without seeing internal buy rates, driver information, or unrelated shipments. Define a publication boundary for each portal or outbound message. An imported raw status should become a customer-facing fact only through the approved operational interpretation. Explain when a status was last confirmed and how a customer can resolve a discrepancy.
Accounting integration should carry approved charges and references to the correct ledger entity. Define credit, payment-status, and unknown-outcome handling at the object level. Reconcile source and destination totals before treating an export as complete. A delayed response must not produce a duplicate invoice. Review accounting integration controls alongside the intermodal demonstration so that operational milestones and financial authorization remain connected without becoming interchangeable.
Implement around representative container cycles
Pilot import, export, rail-ramp, and empty-return patterns that reflect the business. Include disputed dates, missing receipts, changed return instructions, and data-source outages. Assign owners for status review, free-time configuration, equipment exceptions, document completion, and invoice approval. Train all shifts on the degraded workflow, since terminal and connector availability may vary during the operating day.
Reconcile active containers and open equipment obligations before cutover. Preserve historical documents and the ability to explain old charges. Define rollback conditions and an authoritative source for in-flight movements. Success means the team can identify what is open, what evidence is missing, and what action comes next. Use the broader freight transportation software guide and truckload carrier workflow to frame a complete EXSPEEDITE operating evaluation rather than a narrow container-status demonstration.