“The superintendent texts me and I have to start a group message on my phone with the superintendent, operations manager, and my agent.”
That’s how a travel coordinator at a mid-size foundation contractor described her approval process. Her phone, not a platform, not a form, not an approval chain – is the workflow.
After speaking with travel managers at general contractors, specialty firms, and engineering companies across $500K to $12M in annual crew travel, we found the same pattern everywhere. Construction travel approval doesn’t fail because people ignore the rules. It fails because the rules were designed for corporate travel – one traveler, one manager, one approval and construction doesn’t work that way.
Three people with different authority need to coordinate before a single hotel gets booked. The superintendent controls what happens on the ground. The project manager owns the budget. The operations manager controls manpower across sites. When your approval tool only knows about one of them, the default workflow becomes a group text on someone’s personal phone.
Meanwhile, 91% of out-of-policy bookings trace to workflow friction , inconvenience (36%), last-minute timing (30%), or slow approved channels (25%) – not employee misbehavior.
This guide covers why the approval problem in construction is structural, not behavioral, and how to build a workflow that matches how the industry actually operates.
Why Construction Travel Approval Breaks When Other Industries Doesn’t
This is exactly the question we need to figure out!
McKinsey’s capital projects research found that 98% of megaprojects experience cost overruns or delays, averaging 79% over budget. KPMG found only 31% of projects came within 10% of budget over a three-year window. Travel is a small slice of that overrun, but it’s a slice finance teams actually control.
The problem isn’t that construction companies lack travel policies. It’s that they inherited policies designed for corporate travel and applied them to an entirely different operating model.
The 3 Role Structural Split
In corporate travel, one manager approves. In construction, three people with different authority must coordinate and they rarely sit in the same room.
| Role | Authority Type | Key Question | Typical Location/Availability |
|---|---|---|---|
| Superintendent | Operational authority | “Is this person needed at the receiving site?” | On the job site daily |
| Project Manager | Financial authority | “Does the budget allow this on my job code?” | In the field or in client meetings, often unreachable |
| Operations Manager | Manpower authority | “Can this person leave their current site without leaving us short?” | Office-based, managing multiple sites |
When your platform only routes to a single manager of record, the approval goes to someone at headquarters with no visibility into the field crew’s schedule or budget. The superintendent texts the coordinator. The coordinator starts a group thread. The PM – who’s in a trench with notifications off, never sees it. By the time he does, the hotel has sold out.
“Mike’s in a meeting and he never got notified. In that time period, a guy in the field – the hotel sold out.”
ITILITE’s approval workflow is built around this 3-role structure – [see how it works ]
The other 6 Failure Points
- Last-minute, permit-driven trips. Policy says “approve 7 days out.” Reality says “the inspector failed the pour, get on the 6 a.m. flight.” This isn’t a violation – it’s how construction works.
- Multi-site, multi-cost-code trips. A PM visits three sites in two days. Without project-code tagging at booking, the charge lands in overhead instead of the right WIP bucket.
- Crew rotations of 20–120 people. Approval tools built for one traveler choke on a Monday morning crew movement of 50 workers.
- Remote sites with no preferred vendors. Pipeline, wind, and infrastructure jobs are in places corporate hotel programs have never heard of. Crews book directly and those bookings go invisible.
- Field-to-office receipt gap. Superintendents don’t carry laptops. Receipts pile up in glove boxes for weeks. At one specialty contractor, 40% of field employees don’t use the internet at all.
- Per diem vs. actuals confusion. Travel pay, subsistence, and reimbursables follow different rules under union contracts and Davis-Bacon. Approvers often can’t tell which bucket a charge belongs to.
The result: leakage, late reimbursements, angry foremen, and a finance team reconciling shoeboxes at month-end.
What’s the Difference Between Pre-Trip and Permission and Booking Approval?
This is the concept that no generic travel platform supports natively and the single most important workflow distinction in construction travel. After talking with travel coordinators across specialty contractors and general contractors, we found that every company needs two separate approval steps. Almost all of them collapse both into one, or skip the first entirely.
Pre-trip permission is a manpower and scheduling check that fires before any booking search begins. Booking approval is a cost and itinerary check that fires after the worker selects specific flights and hotels. Conflating the two is why hotels sell out before PMs respond.
Pre-trip permission asks one question: should this person travel at all?
- Can this worker leave their current site without leaving it short-staffed? (Operations Manager)
- Is this worker needed at the receiving site? (Superintendent)
- Is the company paying, or is this personal? (Basic filter)
It captures only the basics – employee name, job number, dates, destination, travel type. No itinerary, no pricing, no hotel selection. It’s a gate, not a booking.
Booking approval asks a different question: is this specific itinerary acceptable?
- Does the budget allow this cost on this job code? (PM)
- Is the hotel within policy? Is the flight reasonable? (Policy engine)
The Correct Sequence
- Superintendent requests crew move → “Send Eddie Rivera to Nashville on December 2nd”
- Operations Manager confirms coverage → “Eddie can leave the Birmingham site”
- Worker or coordinator searches and books
- PM approves cost against the job budget
When companies skip steps 1 and 2 and jump straight to booking, the PM gets an approval request for a trip they didn’t know was happening, on a project they may not be tracking today. That’s when the system breaks. That’s when the PM in the meeting never sees the notification, and the hotel sells out.
Three Ways To Implement Pre-Trip Permission
- Native platform form. Built-in pre-trip request that captures job number, dates, and travel type before the booking search unlocks. Best for companies whose platforms support custom pre-booking workflows.
- Trigger form via Google Forms or Slack. Routes to the ops manager for a yes/no, then unlocks booking access. Best for companies on platforms without native pre-trip support.
- Sequential approval chain. Ops manager approves first (manpower), then PM approves second (cost) – triggered on “travel request,” not “booking confirmation.” Best for companies that want a single system but need two-stage routing.
One mid-size foundation contractor built a custom digital form that routes to a shared group email for a simple yes/no from either of two operations managers. It replaced the personal group texts and created an audit trail that didn’t exist before. The reason that matters: a superintendent once verbally approved a worker driving instead of flying, then forgot he’d said yes when the expense report arrived a month later. “I’ve got to go through my text messages” to prove it happened.
Why Routing By ORG Chart Fails in Construction
Standard travel platforms route approvals to a worker’s manager of record – a static relationship pulled from the HRIS. In corporate travel, that works. In construction, it doesn’t. A field worker’s supervisor changes every time they rotate to a new project.
When a worker selects Job Code 1585 for their booking, the approval should route to the superintendent or PM assigned to Job 1585, not to a director at headquarters who hasn’t been on that site in months. Static org chart routing sends the approval to someone without context, without budget visibility, and without urgency.
The Fix: Route by Job Code
When an employee selects a project code at booking, the approval routes dynamically to the PM or superintendent assigned to that specific project. When crews rotate and in construction, they rotate constantly – the routing follows the job, not the person.
Two things make this work, and most generic platforms support neither:
- Dynamic code-to-approver mapping. Your ERP or HRIS syncs nightly to map each active job number to its current PM and superintendent. When a job opens or a PM changes, the routing updates automatically.
- Project-code selection before search. The worker picks their job code before they see flight or hotel options – so the system knows where to route before the booking is priced.
One geotechnical firm managing 800+ project codes, about 60 active at any time – runs exactly this structure. Their previous platform used static routing. PMs who’d rotated off a project were still receiving approval notifications they couldn’t action. Hotels sold out. Crews booked direct. The approved channel became a bottleneck instead of a tool.
How Much Is Approval Leakage Actually Costing You?
Leakage ie, bookings made outside approved channels is the most measurable form of approval chaos. GBTA’s Achieving the Perfect Business Trip study found that 67% of travel managers say air travel leakage has grown or stayed flat year over year, and 81% say the same about hotels. Cross-industry benchmarks put hotel out-of-policy bookings near 37% and flights near 15%.
Why Employees Book Outside The System
Inconvenience of the approved channel: 36% Last-minute decisions: 30% Preferred channel too slow: 25% Other: 9%
91% is a workflow problem, not a people problem. In construction, the causes run deeper: the approved channel requires a laptop that field crews don’t carry; the preferred channel takes 14 clicks to book a Best Western in Odessa; and last-minute isn’t a failure of planning – it’s a structural feature of an industry where weather, inspections, and permits move on 24-hour notice.
The benchmark for T&E reimbursement cycle time is 3 days or less for top-quartile organizations, 5 days for the median. In construction, the pre-trip approval clock matters more than the reimbursement clock. A policy that requires 7-day advance approval is structurally incompatible with an industry where a failed inspection means someone’s on a 6 a.m. flight tomorrow. If approval takes longer than a foreman’s patience, the trip happens anyway.
The 7 Step Approval Workflow That Matches How Construction Actually Operates
Built around the finance KPIs – cycle time, leakage rate, cost-code accuracy, that actually move project margin.
Step 1. Separate pre-trip permission from booking approval
Before any booking search begins, require a manpower check: can this worker leave their current site, and is the receiving site confirmed? Route to the operations manager (manpower) and superintendent (operational need). Only after both confirm does the worker or central booker search for flights and hotels.
Step 2. Set tiered approval thresholds
Not every trip deserves the same scrutiny. Define three tiers:
Auto-approve: in-region day trips under $500. No human touches it. Single approver (PM): site visits under $2,000, domestic, single traveler. Dual approver (PM + finance): international, multi-day, crew movements of 20+ workers, or any trip over $5,000.
Stop burning finance cycles on $38 mileage claims so they have capacity to catch the $12,000 crew mobilizations.
Step 3. Force project code selection before search
Require a job or cost code before a trip request can be submitted and use that code to route the approval dynamically. The charge maps to the correct WIP from day one. No month-end reclass, no “which project was Tuesday again?” conversations. One geotechnical firm managing 800+ codes runs this exact system, syncing nightly from NetSuite.
Step 4. Build a mobile-first approval path
Approvals must work from a phone, in under 60 seconds, with one thumb. Push notification → trip summary → approve or reject → done. If a PM has to open a laptop to approve a $400 hotel, the trip is going to happen without them. At one specialty contractor, 40% of field employees don’t use the internet at all – mobile-first isn’t a preference, it’s a requirement.
Step 5. Create an explicit same-day exception path
This is the step every generic template skips and the single largest source of leakage in construction. Build a formal same-day or emergency mobilization exception with a one-tap PM override and configurable approval expiry. The trip still gets logged, tagged to a project, and audited. Exceptions become data. Blocked trips become shoebox receipts.
Step 6. Enable central booker delegation
Many field workers don’t use computers, don’t know their company email, and won’t create a platform account. The workaround at most companies is a central booker, one coordinator managing travel for entire crews. One specialty contractor runs a single coordinator for 102 field workers. Another environmental firm routes the entire company’s travel through one person.
Give coordinators official delegated access, accounts that let them book, modify, and cancel on behalf of assigned workers without sharing credentials. Without it, managers share executive logins. As one contractor described their pre-platform state: “the wild, wild west.”
Step 7. Reconcile in two stages, review KPIs monthly
Stage 1: PM verification. The PM confirms the cost code matches actual work scope. Catches miscoding before it hits the GL.
Stage 2: Finance verification. Finance verifies policy compliance and posts.
Two stages sounds slower. It prevents the biggest rework trigger: a correctly approved trip posted to the wrong job.
Track three KPIs monthly:
- Out-of-policy booking % – target: under 20%
- Average pre-trip approval cycle in hours – target: under 24 hours
- % of trips tagged to a valid job code at booking – target: 95%+
If leakage stays above 30% after deploying mobile approval and an exception path, the problem is your booking UX, not your people.
What About Subcontractors, Union Crews, And Davis Bacon?
Most construction travel approval workflows are silent on the two trickiest cases and both are where margin quietly disappears.
Subcontractors. If your contract reimburses sub travel, put subs in the same booking tool with a separate cost center. Treat their trips as single-approaches (PM) by default. Sub travel left as an unmanaged invoice line is where reimbursable spend erodes project margin with no audit trail.
Union and Davis-Bacon crews. Travel pay, subsistence, and reimbursable expenses follow different rules by collective bargaining agreement and by state. With IIJA driving a surge in federal work, more contractors are hitting prevailing-wage requirements for the first time. Any trip involving a prevailing-wage project should flag automatically and route to a finance reviewer trained on the applicable rules. Don’t ask the PM to make that call – they won’t know the CBA details, and a mistake becomes a compliance issue.
Making Approval Work For How Construction Actually Operates
Construction travel approval doesn’t need more rules. It needs rules that match the operating model, three roles instead of one, permission before booking, routing by job code instead of org chart, and a same-day exception path that turns off-book trips into auditable data.
The companies that get this right do a few things consistently. They separate pre-trip permission from booking approval – two steps, two different questions, often two different approvers. They route by job code so approvals follow the project when crews rotate. They give central bookers delegated access instead of shared credentials. They build for same-day travel because in construction, it’s structural, not exceptional. And they track leakage monthly and treat it as a UX signal, not a compliance failure.
Start with the pre-trip permission form. Even a Google Form that routes to an ops manager for yes/no, before any booking search begins, replaces the group text workflow and creates an audit trail that didn’t exist before. That single change addresses the structural gap that no generic travel platform was built to handle.
Start with the pre-trip permission form. Even a Google Form that routes to an ops manager for yes/no – before any booking search begins, replaces the group text workflow and creates an audit trail that didn’t exist before. That single change addresses the structural gap that no generic travel platform was built to handle. See how ITILITE handles travel and expense management for construction companies.
