What a Managed Travel Program Actually Requires And What You Can Build Without a Full TMC
A managed travel program has seven core components, but only four truly need a TMC. See what to build with lighter tools and when a TMC is worth signing.

You already have a corporate travel policy and a preferred airline or two. You're also the one booking flights for the team and fielding Slack messages every time someone's flight gets cancelled. So every quarter, the same question hits about your managed travel program: is it time to bring on a full travel management company (TMC), or can you keep building business travel operations with what you have? It comes down to which parts of your program actually need TMC infrastructure and which ones lighter corporate booking tools can handle.
This guide breaks down the seven components of a managed travel program, shows which four actually require TMC infrastructure, and maps out what you can build with lighter booking and expense tools. You'll get a clear build-vs-buy line so you can avoid a premature TMC contract, keep transaction fees in check, and give finance a defensible answer when they ask why you haven't signed one yet.
The Seven Components That Define a Managed Travel Program
Some components of a managed travel program are process problems you can solve with policy and tooling. Others depend on supplier access and servicing capacity that lighter corporate booking tools usually can't pull off alone.
Travel Policy
Your travel policy covers spending limits, approved fare classes, reimbursement rules, and who signs off before someone books a trip. Those rules only matter if they're enforced at the point of booking, especially when 58% of companies never allow Basic Economy in their corporate travel policies.
Booking Channel
The platform travelers use to book determines what you can see. Frequent business travelers say they always use corporate channels 49% of the time, up from 43% the prior year. The rest book on personal accounts or consumer sites, which creates blind spots in spend tracking and duty of care.
Policy Enforcement
Policy enforcement blocks or flags non-compliant bookings before purchase. Finance review catches the problem only after the money's already spent. That's the difference between stopping an out-of-policy fare at checkout and finding out about it weeks later when receipts and card charges show up.
Expense Management
When booking and expense systems connect, itinerary data groups a trip's receipts and card charges into one expense record, so finance can review the full trip in one place. Without that connection, you're manually pulling expense data from email confirmations and credit card statements.
Data Reporting and Analytics
Spend and compliance data gives you the visibility to control costs. You see where policy breaks down or costs climb. Without it, you're estimating spend instead of measuring it. That makes it harder to tell whether the issue is supplier choice, booking behavior, or a policy that looks clear on paper but breaks down in real bookings.
Duty of Care
When someone on your team gets stranded during a weather event or a security incident, you need to know where they are and how to reach them. Employers have a legal duty to take reasonable safety precautions for business travelers, and OSHA's duty clause rule is part of that US framework.
Growing companies often underestimate this. Three in ten (29 percent) travel managers don't know how long it would take to locate affected employees in a crisis. A documented way to find and contact travelers only works if you know where your people are, and a managed booking channel is what creates that record. A free-and-open booking policy leaves visibility and control gaps during disruptions. For primarily domestic travel, booking tools may cover disruption tracking and phone support, but those capabilities vary by provider and don't replace every TMC function.
Traveler Support
24/7 human access matters for itinerary changes and emergencies. When a flight cancels at 11 PM before a morning client meeting, the traveler needs a person who can rebook across carriers. That support function matters even more when the itinerary is already in motion and a missed connection or cancelled segment ripples through the rest of the trip.
Which Managed Travel Program Components Actually Require a TMC
Four capabilities depend on supplier access and servicing capability that lighter tools usually don't have on their own.
- Access to GDS and NDC channels. Mid-market companies can't independently contract with Sabre, Amadeus, or Travelport at TMC-level terms. GDS providers tie pricing incentives to booking volume that mid-market companies can't hit alone. Meanwhile, airlines are pushing fares through NDC channels, and a standalone OBT can't close those content gaps.
- Post-booking fare monitoring and ticket management. TMCs review reservations for data consistency, continuously re-shop fares after booking, and track unused airline credits. No standalone OBT monitors the full PNR lifecycle after purchase.
- Bulk-negotiated hotel and air rates. TMCs pool spend across multiple clients to access negotiated rate tiers. That includes consortia programs with guaranteed minimum discounts that no individual mid-market company qualifies for.
- Complex rebooking with human agents. OBTs replace phone agents for most bookings. But complex multi-sector itineraries still need human agents who can ticket across carriers, manage fare rule exceptions, and coordinate rebooking during disruptions.
What You Can Build in a Managed Travel Program Without a TMC
A lot of the day-to-day program sits outside those four capabilities. Corporate booking tools and expense platforms already handle policy display and booking-to-expense handoff, and they generate standard reports. That's why many companies use them for the straightforward parts of a corporate travel program.
Online Booking and Policy Enforcement
OBTs and all-in-one platforms can show preferred suppliers, enforce policy at the point of booking, and flag out-of-policy selections without TMC involvement. For companies trying to keep routine trips inside guardrails, that covers a meaningful chunk of the booking workflow before finance has to untangle exceptions later.
Otto the Agent works through an Android + iOS app, the web, and 24/7 human phone support. Its conversational interface ingests your corporate travel policy (budgets, cabin rules, vendor rules) and surfaces policy-compliant options. Travelers see "within policy" vs. "out of policy" indicators with explanations. Otto also auto-attaches stored loyalty numbers and payment information to bookings, which keeps routine trips inside your guardrails.
Expense Management and Financial Integration
All-in-one travel and expense platforms create booking-to-expense pipelines where transactions flow into reconciliation without manual entry. And when the corporate card is mandated, card data captures actual spend, often more completely than what a TMC captures for off-channel bookings.
Basic Spend Reporting
Spend by department and compliance rates are standard OBT and expense platform outputs. TMCs matter more when you need to combine data from several sources or negotiate with suppliers. If your goal is just to understand where money's going and whether people are booking within policy, those standard reports may be enough to start tracking cost per transaction and policy adherence side by side.
Traveler Preference Management and Booking Personalization
Consumer booking sites force travelers to re-enter preferences and loyalty numbers on every trip. A booking tool that stores travel preferences and loyalty numbers, then shows "within policy" vs. "out of policy" indicators with explanations, cuts down on repeated entry and guesswork. Travelers pick from curated options instead of scrolling long lists of results, and they book without starting from scratch each time.
Otto stores traveler preferences, payment methods, and loyalty numbers, then auto-applies them on every booking. It also curates 2-6 top options instead of dumping a long results page on the traveler, which cuts booking time and keeps routine trips inside policy without forcing travelers through a separate portal.
Post-Booking Price Monitoring
Most booking tools stop once the purchase is done. Some keep working after you book by monitoring prices on eligible refundable or changeable hotel rooms. If the booked room's price drops below what the traveler paid, the original booking can be cancelled and rebooked at the lower rate. Travelers may also see policy-compliant upgrade opportunities when a higher room category drops to or below the booked price.
That means the traveler can switch to a better in-policy option with more space to work or a better setup for the next day. Picture a standard king booked at $249 against a $250 policy cap. A week later, the deluxe king drops below $250. The traveler cancels the original booking and rebooks the better room, all within policy, as long as the original booking is refundable or changeable.
Build the Parts That Actually Need a TMC Before You Sign One
A managed travel program can be built in layers. Four capabilities truly need TMC infrastructure: GDS and NDC content, post-booking fare and ticket management, bulk-negotiated supplier rates, and human agents for complex rebooking. Everything else in a managed travel program, including policy enforcement, expense handoff, preference management, and standard reporting, can be handled by lighter tools you already have or can stand up quickly.
Otto sits in the layer that lighter corporate booking tools usually handle. It surfaces policy-compliant options at the point of booking, auto-applies loyalty numbers and payment information, and gives travelers curated choices instead of a portal to fight through. You get the compliance data finance asks for and the traveler experience that drives adoption, without locking yourself into a full TMC contract before your volume justifies one.
Start with Otto to build the routine-booking layer of your program and keep TMC infrastructure on the table for the day your travel complexity actually demands it.
FAQ
What's the difference between a TMC and an OBT?
A TMC is a service provider that pairs software with human agents who handle complex bookings, after-hours support, supplier negotiations, and ticket management. An OBT is software only, used by travelers to self-serve bookings inside policy with corporate guardrails and reporting built in. Most TMCs include an OBT, but an OBT can be purchased on its own. The simplest framing: an OBT handles routine self-serve bookings, while a TMC layers on agent servicing, GDS and NDC content, and negotiated supplier rates.
Does a managed travel program require a dedicated travel manager?
Not necessarily. Mid-market companies often run programs through operations leaders or finance teams instead of a dedicated travel manager. The program needs an owner. Someone needs to own the policy, booking process, reporting, and traveler support decisions, but in smaller organizations that ownership usually sits with whoever already handles vendor management or expense oversight.
How much does a TMC typically charge per booking?
Transaction fees vary by booking type. Unassisted booking fees run around $3–$5, while agent-assisted booking fees cost $18 or more. After-hours fees add roughly $15 on top, so a domestic booking made online but modified by an agent at 10 PM could hit approximately $36 in combined booking fees.
How can I build travel reporting without a TMC?
Mandating a corporate card is the prerequisite. Card data captures actual spend across all vendors, even for bookings made outside your preferred platform. Pair that with an OBT or all-in-one platform that tracks booking-level data, and you can report on total spend, compliance rates, and vendor concentration without TMC-provided reports.
How do I know when a full TMC is worth it?
A full TMC becomes more relevant when your travel includes complex itineraries or enough supplier spend to make negotiated rates meaningful. If your travel is mostly domestic and straightforward, companies often handle much of the program through booking and expense tools, with support coverage layered in as needed. A full TMC usually makes sense when servicing complexity and supplier access matter more than the lighter setup you've already built.
How do I keep routine bookings in policy without forcing travelers through a clunky portal?
Friction is what drives travelers off-platform. When the booking tool takes longer than a consumer site, travelers book outside the system and your visibility disappears. Otto handles routine bookings through a conversational interface that ingests your travel policy and shows "within policy" vs. "out of policy" indicators at the point of selection, so travelers stay inside guardrails without learning a new portal.


