Most construction companies end up with a travel platform that “kind of works.” A generic corporate travel tool their TMC recommended, configured for construction the best they could. It fails quietly. Field workers book outside it. Project codes land in overhead instead of the right job. Hotels sell out while the approval email sits unread in a PM’s inbox.
Global business travel spend hit $1.57 trillion in 2025. But 91% of out-of-policy bookings trace to workflow friction. For construction, that friction is structural. Three approvers instead of one. Eight hundred project codes instead of a handful of cost centers. A field workforce where 40% of workers don’t use the internet.
This checklist is built from conversations with travel managers at construction companies managing $500K to $12M in annual crew travel. It’s also a direct response to what we hear most from finance and operations teams evaluating a corporate travel management platform for construction for the first time: they don’t know what questions to ask.
It covers the 2 disqualifier questions, the 9-point evaluation framework, the demo methodology, and honest commentary on where each major platform falls short for construction.
Use it as a copy-paste document for your next vendor RFP.
What Are The 2 Questions That Disqualify A Travel Platform Instantly?
Two questions decide whether a travel platform can actually serve a construction company. If the vendor can’t demonstrate both during the demo, the platform isn’t built for construction. Everything else on the checklist matters only if these two pass.
Disqualifier 1: Does The Platform Trigger Pre-Trip Permission Before The Booking Search?
Most platforms trigger approval after the employee has searched, selected flights, and priced the trip. For construction, that sequence is backwards.
The first approval isn’t about cost. It’s about manpower. Can the worker leave their current site? Is the receiving site ready for them? That’s an operations manager decision.
Ask the vendor: “Show me how a pre-trip request triggers an approval from the operations manager before the employee sees flight or hotel options.” If they walk you through a standard approval-after-booking flow, they’ve failed disqualifier 1.
Disqualifier 2: Does Approval Routing Follow The Job Code When Crews Rotate?
Construction crews rotate. A worker on Project A this week is on Project B next week. The approver for Project A is a different PM from the approver for Project B.
If the platform routes to a static “manager of record” pulled from the HRIS, the approval goes to someone at headquarters with no visibility into the field crew’s current schedule or budget.
Ask the vendor: “If I enter Job Code 1585 on my booking, does the approval route to the PM assigned to Job 1585 automatically? What happens when that PM changes?”
If the answer involves manual re-mapping or a static org chart, they’ve failed disqualifier 2.
On a Concur Community thread titled “How is this program this bad?” One user summarized a sentiment echoed across construction forums: “Most travel management software is built for consultants flying business class, not construction crews needing 15 rooms near a job site.”
If a platform clears both disqualifiers, the remaining 7 criteria decide whether it fits your specific operating model.
The 9-Point Construction Travel Platform Checklist
1. Pre-trip permission workflow – manpower coordination before booking search
Ask: “Can I trigger approval before the worker sees any options?”
2. Dynamic project-code routing – approvals follow the job when crews rotate
Ask: “When crews rotate, does routing follow the code or the person?”
3. Construction ERP integration (Vista, Viewpoint, NetSuite, Sage, CMiC) – sync 800+ codes as jobs open and close
Ask: “Show me a live sync with 500+ codes from a customer’s ERP.”
4. Mobile-first booking – field crews are mobile-only, often offline
Ask: “Can a worker book a hotel in 60 seconds on a phone, one-handed?”
5. Remote area inventory – wind farms, pipelines, rural sites
Ask: “What happens when the nearest hotel is 90 minutes from the site?”
6. Virtual cards and credit card authorization automation – field workers often lack personal credit
Ask: “One-time cards per booking, tagged to project, auto-close after checkout?”
7. Group booking capacity (30–50 rooms) – crew mobilizations
Ask: “Can I book 40 rooms in one transaction?”
8. 24/7 support and same-day modifications – last-minute is structural in construction
Ask: “Project extends Friday 4pm – can crews rebook by 5pm?”
9. No penalties for last-minute bookings – policy should accommodate urgency
Ask: “Will same-day bookings auto-flag as violations?”
Most tools for traveling construction managers were designed for the wrong kind of traveler, a consultant with a corporate card, not a superintendent moving a crew of 40 to a remote site on 24 hours’ notice. That’s what the checklist is designed to expose
Where Do SAP Concur, Navan, TravelPerk, And Engine Fall Short For Construction?
Each major platform has a specific construction gap. It’s a factual accounting of where each category breaks down, based on conversations with 20+ construction companies and public practitioner feedback.
SAP Concur – the incumbent enterprise option
Consistently described as “clunky” and “outdated” on SAP’s own community forum. Its pre-trip approval model requires employees to search and price the trip before approval triggers – the wrong sequence for construction’s 3-role split.
Navan – the modern all-in-one
Strong consumer-style mobile UX. But dynamic policies are based on average market rates, not configurable by specific job location or role. The T&E engine struggles to match complex project codes – it’s designed for cost centers, not the 5-layer job/phase/GL/task/WCB hierarchies construction uses.
TravelPerk – the European-built option
Group booking cap of 8 users. That’s a disqualifier for construction mobilizations of 30–50. Military time and international date formats confuse US-based field crews, one specialty contractor flagged this as a primary reason for migration.
Engine – the construction-focused specialist
Core strength is lodging. But it’s hotel-only, construction companies need unified management for flights, hotels, and specialized vehicle rentals in one workflow. Good mobile experience for field crews, but limited ERP integration depth compared to enterprise platforms.
Platform Construction-Fit: 9-Point Checklist Summary
| Capability | Concur | Navan | TravelPerk | Engine |
|---|---|---|---|---|
| Pre-trip permission | Partial | No | No | Partial |
| Dynamic job-code routing | Limited | Partial | Limited | Yes |
| ERP integration depth | Strong | Medium | Medium | Weak |
| Mobile-first UX | Weak | Strong | Medium | Strong |
| Remote inventory | Medium | Medium | Weak | Strong |
| Virtual cards | Broken | Partial | Weak | Partial |
| Group booking (30+ rooms) | 30+ | Medium | 8-cap | Strong |
| 24/7 + same-day changes | Via TMC | Yes | Medium | Yes |
| Last-minute friendly | Flags | Market | Policy | Native |
How ITILITE Is Different and Built for Construction
ITILITE travel management for construction is built around the two things that disqualify every other platform on this list.
Pre-trip permission is a native workflow and not a configuration workaround. Before a worker sees a single flight or hotel option, the operations manager gets a manpower check request. The superintendent confirms site readiness. Only after both approve does the booking search open.
Approval routing follows the job code, not the org chart. When a crew rotates from Project A to Project B, the approval notification routes to the PM assigned to that job code, pulled from a nightly ERP sync. When the PM changes, the routing updates automatically.
On virtual cards: each booking generates a one-time card, auto-tagged to the job number, phase code, and GL code at the moment of creation, sent directly to the hotel, and auto-closed seven days post-checkout. Field workers check in with an ID. Finance gets 90%+ automatic reconciliation into Vista, Viewpoint, NetSuite, Sage, or CMiC.
Group bookings go up to 50 rooms in a single transaction, across multiple check-in dates and job codes. Same-day bookings don’t trigger policy violations, they route through a dedicated exception path that logs, tags, and audits without blocking.
What Are The Red Flags During A Travel Platform Demo?
- Red flags fall into three categories: vague answers, generic feature claims, and demo-environment shortcuts.
- “Our construction customers love it” – with no specific feature the vendor can demo.
- Static dropdown menus for project codes that aren’t searchable or alphabetized, especially with 200+ codes. Free-text fields don’t scale (some firms manage 800+ codes).
- Non-US date/time formats (military time, DD/MM/YYYY) without a toggle lead to booking errors for field crews.
- No drive-type filters (4WD, AWD, crew cab) for rental vehicles indicates poor understanding of construction needs.
- Vague group booking claims like “we support large groups” without a defined room cap.
- Ghost card/central card failures that default to employee personal cards instead of corporate cards.
How Do You Pilot A Travel Platform At One Construction Site First?
Pilot with one superintendent, one site, one crew of 10–20 field workers, over 30 days. Measure booking rate, bypass rate, and time-to-book. If adoption is below 70% at day 30, the platform will fail at scale too.
- Week 1: Config and training. Set up codes, approvers, and virtual cards. Run a “booking blitz” on site, a 15-minute group session where every worker downloads the app and makes their first booking together.
- Week 2: Live bookings. Track every booking, every modification, every support call. Flag anything that took more than two attempts.
- Week 3: Intentional stress tests. Run a same-day mobilization. Run a group booking of 20 or more. Run a project extension that requires 1–2 weeks of modifications across the crew.
- Week 4: Measure and decide.
The right platform reduces the manual coordination load entirely. How technology reduces construction managers’ travel needs isn’t about booking fewer trips. It’s about eliminating the group texts, the approval delays, and the month-end reconciliation that consume hours every week
The 3 Metrics That Decide Rollout
- Booking rate: Target 85%+. Percentage of trips booked through the platform vs. direct.
- Bypass rate: Target under 15%. Percentage of workers who booked outside the system at least once.
- Time-to-book: Target under 90 seconds on mobile. Median from “opens app” to “booking confirmed.”
If any metric misses target at day 30, the root cause is either platform fit, move on to another vendor or change management, which is fixable.
How To Use The Checklist
Copy the 9-point checklist into your vendor RFP. Send it to any vendor you’re evaluating. If they can’t answer items 1 and 2 with live demonstrations, they weren’t built for construction.
The goal isn’t a perfect platform. It’s one built for how construction actually operates, project-coded, crew-rotating, last-minute, mobile-first – validated on a real jobsite before you sign the annual contract.
See how ITILITE approaches travel and expense management for construction companies.
