Here is how a TMS renewal can easily happen. The reminder lands when the operation is already busy, the notice deadline is approaching, and there is barely enough time to evaluate alternatives properly. The Transport Manager is mid-peak, the FD wants a recommendation by Friday, and the only vendor who can demo inside the window is the incumbent. So the contract rolls over for another term, the workarounds everyone has stopped noticing roll over with it, and the stack of tools around the transport management system (TMS) keeps quietly growing.
Nobody chose that outcome. The calendar chose it. A renewal handled against a 90-day deadline can easily become a rollover; starting 12 months out gives you time to make a proper decision, and the difference between the two is not effort but sequencing. This is the quarter-by-quarter plan.
Why the TMS contract renewal clock starts at 12 months
Count backwards from your renewal date. Notice periods vary by contract and often run to 90 days, so confirm yours first: the real deadline usually sits well before the date on the paper. A proper evaluation takes a quarter of its own: demos scripted on your own jobs, references taken, security questionnaires answered, an internal case made to the board. A migration, if you switch, wants its slot chosen rather than forced. And before any of that is useful, you need to know what you are actually paying for today, which almost no operation does off the top of its head.
Twelve months gives you enough runway to keep every option open, including the option to stay with your current supplier on better terms.
Months 12 to 9: audit the stack you actually run
Twelve months out from a TMS contract renewal, the first job is not comparing vendors. It is establishing what “today” costs. Not the TMS line alone: the whole operational stack. Yours may include the TMS plus telematics, an ePOD or driver app, a separate walkaround-checks app, the accounts package, a fuel card system and sometimes a route optimiser, each with its own login, its own contract and its own renewal date. The aggregate is the number the FD needs, and it is often larger than expected. Total it and see.
Build one sheet, one row per tool:
The stack audit sheet — one row per tool: copy into your spreadsheet and fill in
| Tool | Annual cost | Renewal date | Notice period | Who owns it | Talks to the TMS? |
|---|---|---|---|---|---|
| 01 Current TMS planning, jobs, invoicing | £ | n/a | |||
| 02 Telematics vehicle positions, tacho | £ | yes / partial / no | |||
| 03 ePOD / driver app PODs, job updates | £ | yes / partial / no | |||
| 04 Checks app daily checks, defects | £ | yes / partial / no | |||
| 05 Accounts package invoicing, ledger | £ | yes / partial / no | |||
| 06 Other fuel cards, optimiser | £ | yes / partial / no |
Two more columns worth adding as you go: whether each contract auto-renews, and what data-export rights it grants on exit. Both become load-bearing in the final quarter, and both are easier to find now than under deadline.
Then add the column no invoice shows: the hours your office spends re-keying and reconciling between the tools that do not talk. Someone types tracker mileage into a spreadsheet; someone chases PODs from one app to invoice in another; someone reassembles compliance evidence from three systems before an audit. Estimate honestly, price the hours at office rates, and add it to the total. Our piece on the real cost of running without a proper TMS shows the method on a worked example; the same arithmetic applies to a fragmented stack.
While the sheet is open, log the workarounds. Every “we export it to Excel because the report doesn’t”, every double entry, every screen the newest planner needed weeks to learn. In month one these feel like complaints; in month nine they become your demo script.
Months 9 to 6: requirements, exit terms and the market scan
Write requirements from the workaround log, not a feature checklist. Vendor feature lists all read the same. “Plan this multi-collection run with a subbed middle leg, and show me the invoice it produces” does not. Ten scenarios drawn from your own awkward jobs will tell you more than a hundred tick-boxes, and our guide on the warning signs your current setup has been outgrown is a useful prompt for which scenarios matter.
Put compliance evidence on the requirements list explicitly. Ask every vendor, including your incumbent, to show walkaround checks, defect reports and inspection records being produced for an examiner. If DVSA Earned Recognition is on your roadmap, a voluntary scheme in which operators with at least two years’ licence history share performance data with DVSA in return for fewer roadside stops, check whether your drivers’ hours and maintenance systems can support the required KPIs and reporting. Then ask each TMS vendor exactly how its system integrates with that compliance stack, and verify the answer rather than relying on broad compliance claims.
Read your own exit terms now. Notice period, data export rights, and what happens to your archived records after the contract ends. You will negotiate better in month three if you found the answers in month nine. Remember the retention rules do not pause for a system change: safety inspection records, and defect reports relating to faults and their rectification, must remain available for at least 15 months whoever holds your contract.
Scan the market lightly. This quarter is for building the long list, not sitting demos. Category searches, peer recommendations at the usual industry events, and each vendor’s published material will get you to four or five names. Get comparable pricing from every shortlisted supplier early, including implementation, integrations and additional modules, so you can compare total cost rather than headline licence fees. HaulierMagic’s rates are published per office user and per driver device on the pricing page, with integration one-offs listed alongside, which is the level of detail worth requesting from every vendor on the list.
Months 6 to 3: shortlist, scripted demos, references
Cut the long list to two or three plus the incumbent, and run the same process on all of them.
Scripted demos, on your jobs. Send every vendor the same ten scenarios in advance and make the demo follow them. Watch who drives: a system a vendor’s own salesperson navigates hesitantly is a system your planners will fight. Put your most sceptical senior planner in the room with a scorecard; they will see what the buying committee cannot.
References your size and shape. Ask each finalist for two or three operators in your fleet-size band and sector, and ask every reference the same question: what went wrong in the first 90 days and how was it handled? The vendor whose customers answer that question warmly is the one with a real implementation process.
The incumbent gets the same paper. Same scenarios, same written questions, same scorecard. Sometimes the incumbent wins the evaluation honestly, and that is a fine outcome, because now it is an outcome rather than a default.
Months 3 to 0: decide, negotiate, and book the slot
This is where the TMS contract renewal becomes a decision. With the notice deadline still ahead of you, every path is open, and each one is stronger for the work behind it.
If you switch: serve notice inside the window, secure the full data export and continued access to your compliance history in writing, and choose the migration slot deliberately, a quieter operational period, not whichever month the contract forces. The mechanics of a safe move, including what migrates, parallel running and cutover, are covered step by step in our guide to switching TMS without stopping the trucks. On HaulierMagic, implementation typically runs two to four weeks alongside day-to-day operations.
If you stay: stay on your terms. You now hold a documented stack cost, a workaround log, competing quotes and a scored evaluation. That is negotiating material: for pricing, for support commitments, and for fixes to the specific frictions your planners logged in month one. A renewal signed with leverage looks nothing like one signed against a deadline.
Either way, the operation wins, because the decision was made by the people who run it rather than by the calendar. That is the whole argument for the 12-month TMS contract renewal plan: not that switching is always right, but that rolling over blind never is.
TMS contract renewal: what operators ask
Our renewal is only six months away. Is it too late to run this?
No, but compress rather than skip. Run the stack audit and the requirements work in parallel over the first month, go straight to a shortlist of two plus the incumbent, and protect the scripted demos and reference calls above everything else; they are the steps that change decisions. What you should not compress is the notice period: confirm the exact date in week one, because every other deadline hangs off it.
What notice period and exit terms should we check in the current contract?
Four things: the notice date and required format (some contracts demand written notice by a specific method), any auto-renewal term length, your data export rights on exit, and how long you retain access to historic records after termination. The last one matters most in haulage, because safety inspection records and defect reports relating to faults and rectification must remain available for at least 15 months regardless of which system created them.
Is it worth evaluating alternatives if we will probably stay?
Yes, and probably more so. A documented evaluation converts “we would rather not move” into negotiating leverage on price, support and roadmap commitments, and it leaves a ready-made plan on file for the next renewal. The most expensive sentence in software procurement is “we didn’t have time to look at anything else.”
Who inside the business should own the renewal process?
A practical split is for the Transport Manager to lead the operational evaluation, finance to own the cost model, and an experienced planner to score the demos. The important thing is to name one person accountable for keeping the renewal process on schedule; renewal-by-committee with no owner is what lets the decision default to whoever replies to the vendor’s email. Name that owner at T-12 and put the four quarterly milestones in their diary the same day.
