Travel Agency and Corporate Travel Management

01Purpose and scope

• This manual supports the course Travel Agency and Corporate Travel Management. It describes how day-to-day travel work is actually done in two related settings: a travel agency that sells and services trips for many clients, and an in-house or outsourced corporate travel program that manages trips for one organization's employees and guests. The two share most tools and vocabulary, but they differ in who sets the rules, who pays, and who answers when something goes wrong.
• The scope covers trip requests, search and booking, changes and cancellations, ticketing and fare rules, supplier relationships, traveler communication, invoicing and reconciliation, and reporting. It does not cover tour operation at destination, wholesale package design, or the detailed accounting treatment of travel expenses, which belong to specialists in those fields. Readers working in a country with its own consumer protection, data privacy or tax rules should confirm local requirements with the current authoritative source, since these rules vary by jurisdiction and change over time.
• This guidance does not replace qualified professional judgment, approved internal procedures, or any license or authorization needed to sell travel or handle client money in your area.

02Core principles

• The traveler's needs and the organization's rules both matter, and a good program treats them as a design problem rather than a choice between control and service. A policy that nobody can follow will be bypassed, and bypassed bookings are the hardest to manage for cost, safety and data quality.
• Every booking should be traceable. A reservation needs a named traveler, an approver where policy requires one, a cost center or client account, a fare or rate basis, and a record of who made the decision. When something changes, the history should show the change, not overwrite it.
• Duty of care is a core obligation. The organization or agency must know where travelers are, have a way to reach them, and have a plan for disruptions such as weather events, political unrest, illness or a cancelled flight. Knowing location depends on accurate itineraries, which is why itinerary accuracy is treated as a safety matter as well as a service matter.
• Supplier relationships are long term. Preferred airlines, hotels, car companies and rail operators are chosen for price, reliability, service and data exchange, and they should be reviewed on a regular schedule rather than only when a problem arises.
• Decisions should be explainable to the traveler, the client and the auditor. If a fare was chosen because it was the lowest compliant option, the booking record should show that. If an exception was approved, the reason should be written down.

03Planning and preparation

• Start by defining the client or organization profile. For a corporate program, gather the travel policy, approval thresholds, preferred suppliers, negotiated rates, traveler profiles including loyalty numbers and seat or meal needs, and the list of cost centers. For an agency, confirm the service agreement, payment terms, markup or fee structure, and the client's escalation contacts. Missing information at this stage usually becomes an expensive problem later.
• Confirm the technology stack. Most bookings pass through a global distribution system, a direct connection to a supplier, or a travel management platform that connects to several sources. Decide which system is the system of record for bookings, which is used for expense data, and how traveler profiles are stored. Where personal data is involved, document who may access it and where it is stored, and check the applicable data privacy requirements for each country the travelers visit or the data crosses.
• Set up the approval chain before the first trip. Identify approvers by name or role, define what they must see before approving, and agree on response times. A common arrangement is that trips below a set cost go straight to booking while higher-cost or out-of-policy trips route to a manager or budget owner. The threshold is a business decision, so record who made it.
• Prepare traveler information packs. These usually include the itinerary, hotel details, emergency contact numbers, check-in rules, visa or entry requirements where relevant, and any mandatory health or insurance notices. Entry and health requirements change frequently, so point travelers to the official government or health authority source for the destination and make clear that the pack is a summary.
• Trade-offs begin here. A tightly controlled program with few approved fares lowers cost but can frustrate senior staff and increase leakage through off-channel bookings. A loose program gives travelers more freedom but makes duty of care and reporting harder. Most organizations land between these, and the balance shifts with trip risk, traveler seniority and destination.

04Recommended workflow

1. 1
   : Capture the request in full. Record the traveler name exactly as it appears on the passport or identity document, the purpose, origin, destination, dates or flexibility, budget or cost center, any special requirements, and the approver. Ask for missing items immediately rather than booking on assumptions, because a wrong name or date can make a ticket non-refundable or non-transferable.
2. 2
   : Check policy and approval. Compare the request against the travel policy and the approval matrix. If the request is compliant, move to booking. If it is out of policy, record the reason the traveler gives, route it for approval, and do not confirm a fare until approval is on file, unless the client has agreed that the agency may proceed and accept the risk.
3. 3
   : Search and select options. Look at a range of options across suppliers and fare types. Note fare rules for changes, refunds, baggage, minimum connection times and advance purchase. Compare total cost, including taxes, fees, and the cost of likely changes, rather than the headline fare. Where a lower fare carries restrictions the traveler is unlikely to meet, say so in the options summary.
4. 4
   : Book and ticket. Create the reservation in the system of record, confirm names and dates against the traveler's identity document, and issue tickets or confirmations in the required form. Confirm that loyalty numbers, seat requests and special meal requests were transmitted and check the supplier confirmation rather than assuming it was accepted.
5. 5
   : Confirm and distribute the itinerary. Send the itinerary to the traveler, the approver and, where the policy requires it, the traveler's assistant or the client's travel contact. Include the record locator or reference, supplier contact numbers, check-in windows and any rules for changes. Store a copy in the file so the trip can be found during a disruption.
6. 6
   : Manage changes and disruptions. When a flight is cancelled or a meeting moves, act on the reservation rather than creating a new one alongside the old one. Check fare rules, rebook using the same supplier where possible, and notify the traveler and approver of the change and its cost. Record the reason for the change, since patterns in changes are useful for supplier reviews.
7. 7
   : Reconcile and close. After travel, match tickets, invoices and card charges against the booking record. Check for unused tickets that can be refunded within the supplier's time limits, flag disputed charges, and send the corporate or client report. Close the file only when all charges are matched or an exception is recorded with an owner.

05Quality checks, risk controls and compliance

• Build a check at each stage where errors are most costly. The most common and expensive errors are name mismatches, wrong dates or airports, missing visas or entry documents, duplicate bookings, and fares booked without understanding their rules. A second person reviewing the itinerary against the identity document catches many of these before the traveler is affected.
• Control access to personal and payment data. Travel files often hold passport numbers, dates of birth, loyalty numbers and payment card details. Payment card handling is governed by the Payment Card Industry Data Security Standard for organizations that store, process or transmit card data, and many agencies prefer to use tokenized or virtual card payments to reduce scope. Personal data rules such as those in the European Union's General Data Protection Regulation or US state privacy laws apply depending on where people and data are located, so confirm obligations with your legal or privacy function.
• Manage duty of care with a traveler tracking method. This can be a travel management platform that shows active trips, a regularly updated list, or a process that uses the itinerary and a traveler's check-in notice. Set a plan for alerts about a destination, such as who gets notified, how fast, and what options the traveler has. Any such plan should be reviewed with security or risk specialists, and it should not be assumed to replace local emergency services.
• Keep records of advisories and restrictions. Government travel advisories, sanctions lists and health notices change. Set a routine to check the official source for each destination before a trip is ticketed and again before departure for high-risk trips. Where a destination is restricted by law or sanctions, booking may be prohibited, and that decision belongs with qualified legal or compliance staff.
• Watch for tax and invoicing requirements. Value added tax, sales tax, tourism levies and withholding rules vary by jurisdiction and by the way the supplier and client are registered. Do not assume that a tax treatment applies across borders. Ask the finance or tax function, and where rules are uncertain, rely on the current authoritative source or a qualified tax adviser.
• Recognize the limits of this guidance. Travel involves medicine, insurance, immigration and financial obligations. Decisions in those areas need qualified professional judgment, approved procedures, and where required, formal authorization.

06Collaboration and documentation

• Good travel work depends on clear handoffs. The traveler provides needs and constraints, the approver provides the business decision, the agent or program coordinator provides booking expertise, and the supplier provides inventory and service. Name a single owner for each trip file so the traveler is not receiving conflicting answers from different people.
• Document the standard operating procedures that every agent follows. A short written procedure for each common task, such as changing a ticket, handling a visa question or reporting an incident, reduces variation between staff and makes training faster. Keep procedures under version control and record the date of each revision in the document control system, not in the procedure text.
• Maintain a supplier file for each preferred partner. It should include negotiated rates and their expiry, contact points for account managers and service desks, rules on changes and refunds, performance notes and any service issues. This file is the basis for supplier review meetings.
• Define escalation paths. For example, a missed connection during working hours may go to the desk on duty, while an incident involving a traveler's safety may go to the duty of care lead and the client's security contact. Put the contacts in the procedures and test them periodically.
• Keep the client informed in a way they can use. Monthly or quarterly reports should show spend by traveler group or cost center, advance booking rates, policy compliance, exceptions with reasons, and changes with costs. Reports that are not used should be simplified, not expanded.

07Measures and continuous improvement

• Measure what the program can influence. Common indicators include policy compliance rate, share of bookings made through the approved channel, average cost per trip compared with a negotiated benchmark, advance booking rate, number and cost of changes, unused ticket value, and time from request to confirmed booking. Choose a small set that matches the client's goals, and define each one in writing so that two people calculate it the same way.
• Use traveler feedback alongside financial data. A program that saves money by forcing unsuitable flights may lose staff satisfaction, and a satisfaction score alone does not show whether costs are controlled. Short post-trip surveys and a standing channel for complaints help balance the picture.
• Review supplier performance at a set interval. Look at on-time performance, service recovery, rate competitiveness and data quality such as schedule changes or missing loyalty credits. Use the review to renegotiate, add a supplier, or move volume.
• Run improvement cycles. Pick one problem, such as a high rate of out-of-policy hotel bookings, make a specific change such as adding a preferred property near the client site, and measure the result over a defined period. Keep changes small enough to evaluate, and drop changes that do not work.
• Be honest about limits. Some measures respond slowly, and some cost savings reduce traveler convenience or resilience. Any figure you report should have a note about how it was calculated and what it does not capture.

08Common mistakes and how to prevent them

• Name errors are the most common expensive mistake. Check each traveler name against the identity document exactly as printed, including middle names where the supplier requires them, and watch for transliteration differences on names from other scripts. Correcting a name after ticketing may be impossible or costly, so the check belongs before the booking is finalized.
• Booking on the wrong date or in the wrong time zone causes missed flights and hotel no-shows. Confirm local time at the destination and the departure airport, and read the itinerary back to the traveler in plain language.
• Relying on the lowest headline fare without checking restrictions leads to surprise charges when plans change. Show the total cost and the change rules together, so the traveler and approver can judge the real trade-off.
• Failing to cancel or update old reservations creates duplicate charges and no-show penalties. Make cancelling the superseded booking part of every change procedure, and check the record for an open reservation before closing the file.
• Leaving traveler contact details out of date weakens duty of care. Ask travelers to confirm mobile numbers and emergency contacts before each trip, and recheck them for frequent travelers at fixed intervals.
• Allowing off-channel bookings to go unreported hides spend and risk. Track what is booked outside the program through expense claims, card data and traveler surveys, and use the findings to improve the approved channel rather than only tightening rules.

09Practical checklist

• Confirm the client profile, service agreement, travel policy and approval matrix are current and on file.
• Verify each traveler's name, identity document, loyalty numbers and special requirements before searching.
• Check entry, visa and health requirements against the official source for every destination and transit point.
• Compare total cost including taxes, fees and change rules, and record the reason for the selected option.
• Obtain required approval before confirming any out-of-policy booking, or record client agreement to proceed.
• Issue the itinerary to the traveler and approver with supplier contacts, reference numbers and check-in rules.
• Confirm that tracking or duty of care information reflects the current itinerary and emergency contacts.
• Cancel or update superseded reservations when a trip changes, and note the reason in the file.
• Reconcile tickets, invoices and card charges after travel and close exceptions with a named owner.
• Review compliance, advance booking, change cost and supplier performance measures on the agreed schedule.

★Learning sources

• Micro Degree: Travel Agency and Corporate Travel Management
• Micro Degree: Customer Service Excellence
• Micro Degree: Corporate Travel Management
• Micro Degree: Hotel Technology Management