No single commercial travel site is "DHS-authorized" for all three booking types. Department of Homeland Security employees book flights, hotels, and car rentals through their agency's official travel management system under the E-Gov Travel Service program, and the hotel piece runs through FedRooms. What travelers actually see on screen depends on which of the three E-Gov Travel Service vendors their component uses, so the short answer is your agency's ETS booking engine, not Expedia, Booking.com, or any consumer site.
The authorization question behind DHS traveler reservations
The word "authorized" is doing heavy lifting in this query. For DHS travelers, it does not mean "a site that accepts a government credit card" or "a site with a government rate filter." Authorization means the reservation flows through a system covered by the Federal Travel Regulation and the agency's own travel policy, with an approved travel authorization on file first.
Under the Federal Travel Regulation, specifically 41 CFR Part 301, federal employees on official business must use the methods their agency designates for common carrier transportation and lodging. DHS components designate their E-Gov Travel Service instance, and the General Services Administration administers that contract centrally. Consumer travel sites sit outside that chain of authorization entirely.
That distinction matters because a reservation made outside the authorized system can be denied reimbursement even when the price was lower. Agencies have some discretion to approve non-contract accommodations when nothing contract-compliant is available, but the exception requires documentation and prior approval rather than a receipt submitted afterward. The practical result is that "authorized" is a reimbursement status, not a website feature.
The system traces back to the E-Government Act of 2002, which pushed agencies toward shared, web-based travel services. GSA built the E-Gov Travel Service around three awarded vendors, and the program has since moved into its second generation, called ETS2, with a follow-on contract known as ETSNext underway. Every DHS traveler's booking path runs through one of those vendor platforms.
Why flights and cars follow one rule but hotels follow another
Flight and car rental reservations go through the ETS booking engine alongside the travel authorization itself. The hotel layer is different because the federal lodging program carries its own inventory and its own compliance requirement, so the booking screen a DHS traveler sees for lodging is a nightly-rate search against the FedRooms program rather than an open market search.
FedRooms is GSA's government-wide hotel program. Properties that join agree to publish rates at or below the per diem ceiling for their location and to hold inventory for federal travelers, and those rates carry no cancellation penalty when a trip changes. That last term is the operational reason the program exists: a federal traveler whose authorization gets pulled at 4 p.m. can cancel a FedRooms booking without a fee, which most commercial rates will not allow.
DHS travelers reach FedRooms through the lodging module inside their ETS platform, not by browsing fedrooms.com and booking there as a consumer. The site is useful for research and for finding properties, but the reservation itself belongs in the authorized system so that it links to the travel authorization and the voucher. A FedRooms rate booked through a consumer channel can create a reconciliation problem at voucher time.
The hotel rule has a geographic exception worth knowing. Contract lodging requirements apply where FedRooms or another approved program has inventory, and federal travelers staying outside those areas may book other accommodations with documentation. Confirm the specific exception language with your component's travel policy office before relying on it, because the thresholds vary.
The three ETS platforms DHS components actually run
DHS does not operate one travel system. Components run different ETS vendors, so two DHS employees on the same trip may see entirely different screens. The table below compares the practical booking surfaces rather than scoring them.
| Booking layer | System or program | Who controls it | What it covers | DHS traveler action |
|---|---|---|---|---|
| Authorization | Component's ETS platform (DTS, E2 Solutions, or GetThere-connected instance) | Agency travel office under GSA's ETS contract | Trip approval, flight, rail, rental car | Create authorization before booking |
| Lodging inventory | FedRooms program | GSA | Per diem-compliant hotel rates, no cancellation penalty | Search inside the ETS lodging module |
| Flight and rail | ETS vendor content plus GSA city-pair contracts | ETS vendor; GSA sets contract fares | Coach class contract fares where available | Book in ETS; contract fare applies first |
| Rental car | ETS rental car module | ETS vendor; GSA sets government rates | Compact and mid-size government rates | Book in ETS; decline personal insurance |
| Voucher and reimbursement | Component's ETS platform | Agency finance office | Expense reconciliation after travel | Complete voucher in ETS after trip |
The three vendor platforms in the current ETS2 generation are Concur Government Edition, E2 Solutions from CWTSatoTravel, and the GetThere-based system operated by AdTrav. DHS components are split across them: U.S. Customs and Border Protection has run Concur Government Edition, while other components use E2 Solutions or the AdTrav instance. The right answer for any individual DHS employee is whatever their travel office issued credentials for.
Do not assume the platform transfers with the job. A DHS employee moving from one component to another may lose access to their old ETS instance and receive credentials for a different vendor entirely, with different screen names for the same functions. The travel authorization module in one platform may be called "Authorizations" and in another "Trip Requests," which is why training material rarely transfers cleanly between components.
How a DHS traveler books flights, hotel, and car in the authorized system
The sequence below follows the order the systems enforce. Steps 1 through 3 happen before any reservation exists, and the system will typically block booking without an approved authorization number.
1: Log in to your component's ETS platform with the credentials issued by your travel office. Confirm the trip's fund cite and approver are correct before starting the authorization. 2: Create the travel authorization: purpose of travel, dates, destinations, and estimated costs. Submit it to your approving official and wait for approval to post back into the system. 3: Open the flight module and search city-pair contract fares first. If a GSA contract fare exists for your route, the system generally surfaces it ahead of commercial content, and you select coach class unless a justified exception is documented. 4: Move to the lodging module and search FedRooms inventory at your destination. Filter by the per diem rate for that location and confirm the property's cancellation terms display as penalty-free before you hold the room. 5: Book the rental car in the rental car module at the government rate for a compact or mid-size class. Decline the collision damage waiver, because federal travelers are covered under the agency's program rather than a commercial policy. 6: Review the itinerary as a single trip record, confirm all three reservations link to the same authorization number, and ticket or confirm. Save the confirmation numbers into the authorization record. 7: After travel, complete the voucher in the same platform, attach receipts, and route it to your approver. The voucher matches against the authorization, so changes made outside the system will surface as discrepancies.
Failure handling matters more than most guides admit. If approval does not post before your departure date, the system may let you hold an itinerary but not ticket it, and held segments expire. If a FedRooms property shows no availability, the lodging module usually prompts for a documented exception rather than blocking the booking; capture the search result as evidence. If a flight cancels en route, call the ETS vendor's after-hours line rather than rebooking on a consumer site, because an out-of-system rebooking requires a later amendment and can complicate the voucher.
What "DHS-authorized" rules out, and the sites travelers wrongly assume qualify
Consumer booking sites are not authorized for DHS official travel regardless of the government rate filters they display. Expedia, Booking.com, Hotels.com, and similar platforms sell inventory under commercial terms, and their "government rate" tags are property-set discounts rather than FedRooms contract rates. A DHS traveler who books there creates an out-of-policy transaction that needs a documented exception to survive the voucher stage.
The same applies to airline websites and rental car company direct bookings. Even when the fare matches what the ETS platform would show, the reservation lacks the authorization linkage the voucher process requires, and the agency cannot apply its contract terms to a booking it never controlled. The traveler carries the reconciliation burden.
Government rate portals run by the rental car companies deserve a specific note. Avis, Enterprise, and Hertz each publish government rates, and those rates are legitimate for federal travelers, but the rate eligibility is a pricing question while authorization is a system question. Booking a government rate directly still means booking outside ETS, so the rate being valid does not make the channel compliant.
Third-party trip planners and expense apps are a separate trap. An app that imports itinerary emails and produces a tidy travel timeline is not connected to the authorization record and cannot substitute for the ETS voucher. DHS travelers who use personal tools for convenience still have to key the same information into the official system.
FedRooms versus open-market lodging: a same-dimension comparison
The comparison below isolates the dimensions that decide whether a hotel booking survives voucher review. Rates vary by city and date, so the table states the mechanism rather than quoting figures that change nightly.
| Dimension | FedRooms booking in ETS | Open-market or consumer booking |
|---|---|---|
| Rate ceiling | At or below the location's per diem rate | Set by property; may exceed per diem |
| Cancellation | No penalty under program terms | Property policy; penalties common inside 24β48 hours |
| Authorization linkage | Ties to the trip authorization record | Manual entry; exception documentation required |
| Per diem compliance | Built into the search filter | Traveler must verify and justify any overage |
| Reimbursement risk | Low when booked per policy | Denied or reduced without approved exception |
| Inventory | Held for federal travelers at member properties | Open market; no federal hold |
| Loyalty points | Earned per property program terms | Earned per property program terms |
FedRooms wins on cancellation flexibility and compliance documentation; the open market wins on choice and occasionally on location convenience where no member property exists. Neither wins on price in every case, which is why the agency exception process exists rather than an absolute ban.
The most common failure case is a traveler who books a conference hotel outside FedRooms because the event is there, arrives, and discovers the nightly rate exceeds per diem by a wide margin. Reimbursement then depends on an approved exception tied to the conference location, and approval is not guaranteed after the fact. Asking the travel office before booking takes ten minutes and removes the risk.
Rental car rules that trip up experienced travelers
The rental car module enforces a class restriction that catches frequent travelers: compact or mid-size unless a documented need supports an upgrade, and the government rate applies to those classes. Booking an SUV because it was the only car on the lot produces a rate the voucher may not fully cover.
Insurance is the second trap. Federal travelers on official business are covered under the agency's rental program rather than a commercial collision policy, so the counter agent's offer of damage coverage is a personal expense that reimbursement will not honor. Decline it at the counter and confirm the government rate code carried through to the contract.
Fuel and toll handling vary by component policy rather than by system. Some agencies reimburse fuel purchases on return of the vehicle with a receipt, others require refueling before return, so confirm the rule in your component's travel policy rather than assuming the system will correct you. The ETS platform records the rental but does not adjudicate the fuel line.
If the rental counter cannot find the government rate at pickup, call the ETS vendor's travel line before signing anything at a higher rate. Signing first converts a rate dispute into a reimbursement exception, and the traveler absorbs the documentation work either way.
When the authorized system isn't available: exceptions, group travel, and local vouchers
The system occasionally cannot serve the trip. Group travel for a conference or a large inspection team sometimes needs block bookings that the ETS module cannot hold, and components handle those through a group travel request routed to the travel office rather than through the standard screen. The same office issues the documentation that makes the later voucher clean.
Local travel below the threshold for a full authorization is another gap. Some components allow meals and incidental expenses without a formal authorization, and some allow local lodging booked outside the system within a stated dollar limit, but those thresholds are component-specific. Never assume the DHS-wide rule matches your component's rule; ask the travel office for the current threshold in writing.
Emergency travel is the case where the rule bends rather than breaks. When a traveler must move before an authorization can post, the standard practice is to book through the ETS vendor's after-hours travel line, which can create the record retroactively, rather than through a consumer site. The traveler then files the authorization amendment on return. Booking on a personal account during an emergency is the version of this that produces the worst voucher outcomes.
The voucher itself is the final check. It reconciles actual expenses against the authorization, and every out-of-system purchase becomes a line the approver has to justify. Travelers who treat the voucher as paperwork rather than as the audit it is tend to be the ones surprised by denials.
How the ETSNext transition changes the booking screen
GSA has been moving the E-Gov Travel Service into a successor contract called ETSNext, and the transition is the single most likely reason a DHS traveler's booking screen will look unfamiliar in the next few years. Because GSA administers the program, the vendor lineup and platform interfaces change on GSA's schedule rather than on any component's preference.
The practical consequence is that platform-specific instructions age quickly. A guide that names exact menu paths in one vendor's interface may be obsolete after a component migrates, while the underlying policy sequence, authorization first, then flight, lodging, and car within the system, stays constant. Learn the sequence and treat the screen names as temporary.
Travelers should watch for migration notices from their component travel office rather than assuming the old login persists. Access credentials are typically reissued during a platform change, and pending authorizations may need to be recreated in the new system. Confirm the migration date with the travel office if a trip straddles it.
The stable facts across any transition are these: booking happens in the agency's designated system, lodging runs through FedRooms inventory where available, contract fares and government car rates apply first, and reimbursement depends on the authorization linkage. Those four facts survive vendor changes because they come from the Federal Travel Regulation and GSA program design, not from any interface.
FAQ
Can a DHS employee book official travel on Expedia if the rate is lower?
No. A lower commercial rate does not make a consumer site authorized, and the booking lacks the authorization linkage the voucher process requires. Reimbursement then depends on a documented exception approved through your component's travel office, which is not guaranteed after the fact. Book in your ETS platform even when a consumer site shows a cheaper fare.
Does every DHS component use the same travel reservation system?
No. Components are split across the ETS2 vendor platforms, including Concur Government Edition, E2 Solutions from CWTSatoTravel, and the GetThere-based AdTrav instance. The platform name on your login screen tells you which one you have. Your travel office issues the credentials, and they do not transfer automatically if you change components.
Is FedRooms a booking website or a rate program?
It is a rate program administered by GSA with inventory held at member hotels, not a consumer booking engine for federal travelers. DHS travelers reach the rates through the lodging module inside their ETS platform. Booking a FedRooms rate through a consumer channel can create a reconciliation problem at voucher time.
What happens if I book a rental car outside the system during an emergency?
You can still be reimbursed, but the purchase becomes an exception the approver has to justify against your authorization. The cleaner path is the ETS vendor's after-hours travel line, which creates a record the amendment can attach to. Booking on a personal account is the version that produces the worst voucher outcomes.
Why does the rental car counter sometimes not have my government rate?
Rate codes occasionally fail to carry from the booking to the counter contract, usually because the reservation was modified outside the system or the class changed at pickup. Call the ETS vendor's travel line before signing at a higher rate. Signing first converts a rate dispute into a reimbursement exception.
Do I have to stay at a FedRooms property every night?
Contract lodging requirements apply where FedRooms or another approved program has inventory, and federal travelers staying outside those areas may book other accommodations with documentation. The geographic exception language varies, so confirm the current threshold with your component's travel policy office before relying on it.
How does the ETSNext transition affect reservations I already have?
Pending authorizations may need to be recreated in the new platform if a trip straddles a migration date, and credentials are typically reissued. Watch for migration notices from your travel office rather than assuming the old login persists. The policy sequence stays the same even when the screen changes.
Can I use a personal expense app to track my official trip?
You can track expenses however you like, but the app is not connected to the authorization record and cannot substitute for the ETS voucher. The same information has to be keyed into the official system for reimbursement. Treat personal tools as convenience, not compliance.
This article is general educational information about federal travel reservation channels, not a legal opinion or an official statement of DHS or GSA policy. Travel rules, per diem ceilings, exception thresholds, and platform assignments change, and component policies differ, so confirm current requirements with your component's travel office or a qualified federal travel professional before booking.