A transportation management system (TMS) is the software a transport operation runs its work through: the shipments customers ask you to move, the trucks and drivers who move them, the progress of each job from pickup to delivery, the paperwork that proves it happened and the figures that show how well it went. For a trucking carrier, or a manufacturer or distributor with its own fleet, a TMS replaces the whiteboard, the spreadsheets and most of the phone calls with one shared record of the day.
This guide explains what a TMS does, the functions most systems include, the signs that a company needs one and the questions to ask before choosing. It ends with what Majestic Intelligence covers today, and what it does not.
What a transportation management system does
Every trucking operation already has a system, even if it is a dispatcher’s memory and a shared spreadsheet. A TMS turns the bookings, assignments, deliveries and paperwork into records that everyone reads the same way.
The term covers two kinds of software. A shipper’s TMS helps a company that sends goods choose carriers and compare prices. A carrier’s TMS, the kind this guide is about, helps the company that owns the trucks plan the work, assign trucks and drivers, follow each job and record the outcome.
At its heart, a carrier’s TMS answers four questions at any moment of the day:
- What work do we have? Every shipment, with its customer, pickup, destination, cargo and deadline.
- Who is doing it? Which truck and driver carries each shipment, and which trucks are still free.
- How is it going? Where each job stands (heading to the pickup, loading, in transit, unloading, delivered) and what is running late.
- How did it go? Whether deliveries arrived on time, whether the paperwork came back, and what each job earned and cost.
The core functions of a TMS
Products differ in depth, but most transportation management software is built from the same set of functions. The table summarises them; the sections below explain each one briefly.
| Function | The question it answers | What it usually looks like |
|---|---|---|
| Shipments and orders | What has the customer asked us to move, and by when? | Order entry and shipment records |
| Planning and dispatch | Which truck and driver should take it? | A dispatch board and assignment rules |
| Execution and visibility | Where does each job stand right now? | A status board, a map and alerts |
| Documents | Can we prove collection and delivery? | Bills of lading and proofs of delivery |
| Fleet, drivers and maintenance | Which trucks and drivers can work, and when? | Truck and driver records, shifts and work orders |
| Analytics and costs | Are we on time, and does the work pay? | Performance figures and cost views |
| Rates, invoicing and integrations | What do we charge, and how does it reach accounting? | Rating, billing and connections to other systems |
Shipments and orders
A shipment records the goods one customer wants moved: what they are, how many pallets and how much they weigh, where they are collected and delivered, the priority and any delivery deadline. Every later step (the job, the documents, the cost) hangs off this one record.
Planning and dispatch
Dispatch matches shipments to trucks and drivers. A good TMS checks what a dispatcher would otherwise check from memory: the truck is in service and has a body that suits the goods, the cargo fits on both pallets and weight, the driver holds the right licence class and has enough of the shift left, and the truck is not booked into the workshop. Some systems also suggest the best truck; the useful ones say why. Our guide to truck dispatching covers that decision in more detail.
Execution and visibility
Once a job is under way, the TMS follows it through its stages and flags exceptions: a truck running late, a truck waiting for a dock, a delivery deadline at risk. Progress can come from drivers updating a status, from telematics devices on the trucks, or both. Each exception should say what happened, why it matters and what to do next.
Documents
A delivery is not finished until the paperwork is. The bill of lading travels with the goods from the pickup; the signed proof of delivery confirms that the consignee received them. A TMS keeps both against the shipment and shows which are still missing, because a missing proof of delivery usually holds up the invoice. Read more in bills of lading and proofs of delivery, explained.
Fleet, drivers and maintenance
Dispatch is only as good as its picture of the fleet. A TMS holds each truck’s type, capacity, home depot and service state; each driver’s licence class, shift and leave; and the maintenance planned for each truck, so work is not offered to a truck due in the workshop.
Analytics and costs
Because every job is recorded, the TMS can report on-time delivery, how much of the fleet’s time goes on delivery work, how far trucks drive empty and which lanes run late. Cost views show where margin is made and where it is lost.
Rates, invoicing and integrations
Many TMS products also handle rating (customer rate tables and quotes), invoicing, driver settlements, and connections to accounting, telematics, electronic logging devices and customer portals. These are valuable, but they are also where implementations grow long and expensive.
Signs your company needs a TMS
A company buys a TMS when its current way of working starts to cost money or customers. Common signs include:
- The day lives in one person’s head. When the lead dispatcher is away, work slows down or goes wrong.
- The spreadsheets disagree. The booking sheet, the driver sheet and the maintenance calendar each tell a different story.
- “Where are my goods?” takes phone calls. A customer asks, the office phones the driver, and the answer arrives long after the question.
- Paperwork goes missing. Proofs of delivery turn up days late or not at all, and invoices wait for them.
- Exceptions are found too late. A missed deadline or a truck stuck waiting for a dock is noticed after the customer complains.
- Wrong assignments slip through. A flatbed is offered for boxed goods, a driver is sent out with too little shift left, or a truck booked for the workshop leaves the yard.
- Nobody can say which work pays. Costs are known for the month, not for the customer, the lane or the job.
One or two can be managed with discipline. When most are true, the workaround usually costs more than a system would.
How to evaluate transportation management software
A sales demonstration shows the best path through a product. These questions show how it behaves on an ordinary day.
- Does it fit the way we haul? Full truckload or less than truckload, one stop or several, live loading or trailer drops, regional or long-haul. A system built for one will strain at another.
- Will a first-time user understand it? Sit a dispatcher in front of it without training. If the screens need a manual, people go back to the spreadsheet.
- Does it explain its suggestions? If the system proposes a truck, can you see why: on time at the pickup, fits the goods, enough shift left? Advice you cannot check is advice nobody trusts.
- What happens when something goes wrong? Ask to see a delay, a missing proof of delivery and a cancelled job, not only a delivery that went to plan.
- Are its figures defined? “On time” can mean against the customer’s deadline or against the plan. Ask how each figure is calculated and whether you can trace it back to the jobs.
- Does it calculate hours of service, or only working windows? US rules limit a driver to 11 hours of driving within a 14-hour window, with a 30-minute break after 8 hours of driving (49 CFR 395.3). Find out whether the system checks these or leaves them to another tool.
- What does it connect to? Ask which connections to telematics, electronic logging devices and accounting exist, which would be built for you, and who maintains them.
- Who holds the data, and where? Hosting, sign-in, access rights and export should be clear before you commit.
What to settle before you choose
Software makes a good process faster and easier to see; it does not create the process. Before choosing a transportation management system, agree a few things inside the company:
- Who books freight, who assigns trucks, and who chases paperwork.
- What counts as late, and which delivery deadlines customers have actually agreed.
- Which records are the master copy: customers, facilities, trucks and drivers.
- Which functions you need on the first day, and which can wait for a second phase.
With these settled, you know exactly what you are asking a system to do, and comparing systems becomes much easier.
How Majestic Intelligence covers the core of a TMS
Majestic Intelligence is logistics management software designed and engineered by METHODSS. It covers six of the seven core functions above, all but rates, invoicing and integrations, around a control tower that shows every truck and facility on a real map:
- Shipments and customers: cargo in pallets and kilograms, a priority (Standard, High or Urgent), an optional delivery deadline and a timeline of every milestone.
- Dispatch: a board by stage (Unassigned, Assigned, Active, Delayed, Completed), suggested trucks with their reasons in words, and planned dispatch by the same readable rules, with no machine learning. See dispatch.
- Execution and visibility: a Dashboard of what needs a decision, and Live Operations, with a satellite map and a schematic 3D view of the same operation. See the control tower.
- Documents: a bill of lading and a proof of delivery for every delivery job, with missing ones flagged first and scans attached in the browser.
- Fleet, drivers and maintenance: trucks with their body types and capacity, drivers with licence classes and shifts, and maintenance work orders that dispatch respects.
- Network and routes: facilities placed on the map and routes calculated along real roads.
- Analytics and costs: On-time delivery, Arrived as planned, Fleet utilisation and Empty distance, plus a Cost Overview of revenue, cost and contribution before overheads from example rates, labelled illustrative.
It matters just as much to say what it does not do. Majestic Intelligence today does not include:
- rating, customer rate tables or invoicing (the Cost Overview is an illustration, not billing);
- hours-of-service compliance (a driver’s shift is a simplified working window);
- multi-stop or less-than-truckload work (each job carries one full-truckload shipment from one pickup to one destination);
- real vehicle tracking, a driver app or customer portals;
- integrations with telematics, electronic logging devices, accounting or other systems.
The Majestic Intelligence demo runs a simulated carrier: every truck, driver, shipment and position is fictional and labelled as simulated, not GPS. Real data, sign-in, hosting and integrations are scoped and built by METHODSS for each client’s operation.
The quickest way to judge whether it fits your operation is to use it. Open the demo in your browser, with no sign-up, or contact METHODSS to talk about your fleet.