Magellan
TMS Workflows: Software Does Not Fix a Broken Process
Define load statuses, document ownership and exception handoffs before relying on a TMS to control the operation.
A carrier can enter every load into a transportation management system and still depend on phone calls to understand the operation. The gap often appears when different employees give the same field different meanings. One dispatcher marks a load delivered when the driver calls. Another waits for a signed receipt. Billing sees the same status and assumes the file is complete.
Begin with the business event each status is meant to represent. Write a short definition, the evidence required, the person responsible and the next handoff. A company might distinguish physical delivery from document completion and billing readiness. Those are workflow choices to define for the operation, not claims that every TMS includes those exact features.
Map one ordinary load before redesigning the whole company. Follow booking, assignment, pickup, delivery, document review and billing. Note where people leave the system to resolve uncertainty. A repeated phone call can reveal a missing rule, an unclear responsibility or information that the receiving team cannot see. Establish the rule before deciding whether software configuration or another controlled process should support it.
The load file should contain enough reliable information for the next person to act. At booking, that may include the customer, agreed rate, locations, appointments, equipment requirements and instructions. At assignment, the relevant driver and equipment information must be checked through the company's authorized processes. At billing, the required delivery and charge evidence needs review.
Avoid requiring every possible field at every stage. A mandatory field filled with a placeholder can create false confidence. Identify which facts are known, which are pending and which prevent the next step. Give unresolved items an owner and an escalation route rather than forcing staff to enter an invented value.
For example, a hypothetical load is booked with a delivery appointment awaiting confirmation. Record the uncertainty, responsible person and next check. The system should not imply that the customer confirmed a time merely because a scheduling field cannot be blank. If the software cannot express the needed distinction, use an approved supporting control and make its location clear. The operational truth should determine the record, rather than the form determining what staff claim happened.
A document is useful when the reviewer can identify the load, version, source and purpose. Keep the original rate confirmation and subsequent authorized changes. Connect delivery records, receipts and charge approvals to the appropriate movement. A folder of unnamed scans forces the next person to repeat work that should have been resolved at intake.
Some load-related records can also serve compliance purposes. 49 CFR 395.11 (49 CFR 395.11) defines supporting-document requirements for covered hours-of-service records. That does not mean every document belongs in an unrestricted TMS attachment area or that the TMS automatically satisfies the rule. Confirm applicability, retention, access and retrieval through the responsible compliance process.
Use a document index or consistent naming approach that preserves the load reference and document type. Separate customer-facing records from restricted personnel or sensitive information. Define how incorrect uploads are corrected while maintaining appropriate history. A person should be able to explain why a record supports the load, not simply point to the fact that a file was uploaded. Where a document is missing, state what is missing and who is obtaining it.
Normal status progression is not enough for a breakdown, rejected shipment, missing delivery record, rate dispute or temperature concern. An exception needs its own facts, owner, next action and escalation. It should remain visible until the appropriate person has resolved it or made a documented decision about what happens next.
Use specific language. “Delivery complete; signed receipt pending” communicates more than “done” when billing cannot yet proceed. A note should distinguish what the driver reported, what the office verified and what the customer authorized. Keep later instructions linked to the original event so staff can follow the sequence.
A hypothetical detention claim illustrates the handoff. Dispatch records arrival and departure information and preserves the available evidence. The responsible person checks the contract and requests approval through the agreed channel. Billing receives the approved amount and supporting record, or an explicit unresolved status. An internal note that detention was requested is not proof that the customer accepted the charge. Defining this distinction before configuring fields reduces the chance that a confident status hides an unverified assumption.
Test the proposed rules on a small set of representative loads, including at least one exception. Ask dispatch, document review and billing staff to follow the same definitions. Observe where they disagree, need duplicate entry or cannot retrieve the evidence. A successful demonstration by the administrator alone does not establish that the daily handoff works.
Write the operating procedure in terms of actions and decisions, with screenshots only where they help users find the relevant control. Give the procedure an owner and version. Training should include an actual task, such as completing a document handoff, rather than only confirmation that someone opened a file.
Record what the pilot proves and what remains untested. If an integration or feature is unavailable, identify the approved manual route and its review responsibility. Do not claim that data synchronizes, access is enforced or a hold is automatic unless that behavior has been demonstrated. A workflow proposal describes intended work; a tested process establishes evidence that the people and tools can perform it under the conditions examined.
Measure issues that expose process friction: loads with missing evidence at billing, unresolved exceptions, repeated corrections and handoffs that depend on one employee. Interpret those measures with the team's actual workload and definitions. A lower exception count could mean better work or simply less complete recording.
Choose one recurring failure and trace it backwards. If invoices wait for delivery records, examine collection instructions, document intake, ownership and review timing before assuming the answer is another software feature. If a field is routinely wrong, determine whether its source and meaning are clear. Make the authorized change and check a later sample.
The TMS should help people execute an agreed process and retrieve its evidence. It cannot decide the company's responsibilities by itself. A clear workflow tells staff what happened, what remains open and who acts next. Once those rules are established, configuration can support them. Buying a new screen or adding more required fields has limited value when the handoff underneath remains undefined.