
By Forecepts Team
19 June 2026

By Forecepts Team
19 June 2026
Choosing a travel management company is rarely won or lost on price. Most TMCs competing for the same account quote within a similar range, and most demos look impressive. What actually separates a partnership that works for years from one that triggers a frustrated re-tender within eighteen months is harder to see in a sales pitch: how the TMC enforces policy day to day, how it handles disruption, how clearly it can prove the value it delivers, and how seriously it takes implementation rather than treating go-live as the finish line.
This article is for corporate travel managers, procurement teams, and finance leads evaluating a TMC — whether for the first time or after a frustrating experience with an incumbent. It sets out what to actually check, beyond the proposal and the demo.
Before evaluating any TMC, get clear internally on the shape of your own travel programme — because this determines which capabilities actually matter for your evaluation and which are irrelevant.
• Traveller volume and profile — How many travellers, how frequently, and what kind of trips (domestic, regional, international, high-value executive travel)?
• Markets and entities — Do you need coverage in one market or several? Do subsidiaries or related entities need their own self-service booking, with their own policy and reporting?
• Policy complexity — How many approval levels, how many policy variations by grade or department, and how much exception handling do you expect to need?
• Internal resourcing — Will you have a dedicated travel manager engaging with the TMC, or does the programme need to run with minimal internal oversight?
A TMC that is an excellent fit for a single-entity, single-market company with simple policy may be a poor fit for a multi-entity regional group, and vice versa. Getting this internal picture clear first means the rest of the evaluation can be specific rather than generic.
content is included and from which airlines, and whether low-cost carriers are covered through an aggregator. This matters because a gap in content coverage shows up as travellers being unable to find the fares or airlines they expect — which quietly drives bookings outside the managed channel. A TMC that has thought carefully about its own content sourcing will have clear, specific answers rather than generic assurances; for the procurement questions a well-run TMC asks when sourcing its booking technology, see Travel Booking Engine: A Buyer's Framework — a TMC that can speak fluently to that framework is one that has done its own homework on content coverage.
Almost every TMC will say they support a corporate booking tool with policy enforcement. The more useful question is how the enforcement actually works: is policy checked at the point of booking, or only flagged afterwards in a report? Real-time, point-of-booking enforcement prevents out-of-policy spend before it happens; after-the-fact reporting only documents it. For the mechanics of why this distinction matters, see Why Travel Policy Compliance Fails And How to Fix It. It is also worth asking how approval is configured — active, passive, or hybrid — and whether the TMC can adjust approval rules per entity if you have subsidiaries with different needs. For the underlying booking tool capability this depends on, see Corporate Booking Tool: A TMC's Guide for 2026.
How a TMC handles the period between signing and go-live is one of the strongest predictors of how the relationship will run afterwards. A TMC that treats implementation as a formality — a quick configuration call and a login — is signalling how it will treat support requests later.
Questions worth asking directly:
• Will configuration be tested against our real booking data before go-live, or only against demo data?
• What does onboarding look like if we have subsidiaries or multiple markets?
• Who handles GDS-level configuration issues, and how quickly?
• What training is provided for travellers, approvers, and administrators — and is it tailored to each role?
A TMC that responds to these questions with a clear, staged plan — rather than a vague assurance that "it will be smooth" — is a TMC that has actually thought about implementation as a discipline. For the implementation process from the TMC's own side, which shows what a properly run implementation should look like, see Implementing a Corporate Booking Tool: How TMCs Go From Tender to Live.
Ask, before you sign, what reporting the TMC will provide and how often — and ask to see a sample. A TMC that cannot produce a clear example of a savings or compliance report at the proposal stage is unlikely to produce one unprompted a year into the contract. The reporting that actually matters at renewal time covers savings delivered against a baseline, policy compliance rate and trend, the percentage of spend booked outside the managed channel, and cost per trip by relevant segment. For the full breakdown of what this reporting should contain and why it matters at renewal, see Why Corporate Clients Leave Their TMC — and How to Prevent It, which sets out the same reporting requirements from the TMC's side — a TMC that has read and internalised that framework is one that is prepared to be evaluated against it. The underlying data infrastructure that makes this reporting possible is covered in What Is a Mid-Back Office System for Travel Agencies?.
Some signals are visible during the sales process itself, before you have committed to anything.
| Red Flag | What It Usually Means |
|---|---|
| Cannot produce a sample savings or compliance report | Reporting will likely be an afterthought once you are a live client |
| Vague answers about GDS or content coverage | Gaps will surface as traveller complaints about missing fares or airlines |
| No clear implementation plan, or implementation treated as a formality | Configuration is likely to be tested against demo data only, not your real data |
| Approval and policy described only in generic terms | Policy enforcement may be reporting-only rather than point-of-booking |
| No proactive communication plan beyond "call us if you need anything" | Service responsiveness during disruption is likely to be reactive, not proactive |
These are the buyer-side mirror of the reasons corporate clients end up leaving their TMC after the fact — the patterns are visible earlier than most buyers expect, if you know what to look for. See Why Corporate Clients Leave Their TMC — and How to Prevent It for the fuller picture of how these issues develop over the life of a contract.
A few questions matter more for buyers operating in or across Asia-Pacific.
• Regional coverage consistency: If you operate in multiple APAC markets, ask whether service quality and content coverage are consistent across them, or whether the TMC is strong in its home market and weaker elsewhere.
• Local low-cost carrier content: Ask specifically whether regional LCCs relevant to your travel patterns are covered, since this is a common content gap that surfaces as off-tool booking.
• Multi-currency reporting: If your operation spans currencies, ask whether savings and compliance reporting consolidates meaningfully across them, or requires manual reconciliation.
• Subsidiary self-service: If you have or expect subsidiaries needing their own booking access, ask explicitly how onboarding and policy configuration scale per entity.
For context, Forecepts builds the technology layer (SWIFT IBE, CBT, and Mid-Back Office) that many TMCs in Asia-Pacific use to deliver the capabilities described above: point-of-booking policy enforcement, structured savings and compliance reporting, and implementation support including GDS configuration. If you are evaluating a TMC and want to understand what is technically possible behind the proposal you have received, the team is glad to walk through it.
Frequently Asked Questions
For a programme of any complexity, allowing several months from initial outreach to signed contract is realistic — enough time for demos, a detailed walk-through, and ideally a reference conversation with an existing client of comparable size. Rushing the evaluation to meet an internal deadline is one of the more common causes of a poor TMC fit.
Price matters, but a TMC that is meaningfully cheaper than the alternatives is usually cheaper somewhere specific — content coverage, service responsiveness, reporting depth, or implementation support. The total cost of a TMC relationship includes the cost of off-tool booking, missed savings, and internal time spent chasing reports that should have been provided automatically. Evaluating on total value rather than headline price avoids most of the common regret patterns.
Asking to see a real, anonymised example of the savings and compliance report a current client receives is unusually revealing. It tests whether the TMC actually produces this reporting as a matter of course, and it shows you directly what you would be working with a year into the relationship — rather than a description of what is theoretically possible.
Asking to see a real, anonymised example of the savings and compliance report a current client receives is unusually revealing. It tests whether the TMC actually produces this reporting as a matter of course, and it shows you directly what you would be working with a year into the relationship — rather than a description of what is theoretically possible.