Which trips need approval?
Only the ones outside your rules. If every trip waits for a yes, people book late, prices rise, and the approver becomes the bottleneck.
- A fare or hotel above the limit for that route or city.
- A cabin class above the one set for that flight length.
- A trip booked later than your advance-booking rule allows.
Who should approve?
One person per team, usually the traveller's manager. In a small company, a second level of approval rarely adds anything except delay.
Name a stand-in for every approver, so trips don't wait while they're on leave or travelling themselves. And make sure nobody approves their own trip.
How fast should approvals be?
Same day, ideally within a few hours. Fares and hotel rates move, and some bookings are held only for a short time, so a slow yes can cost more than the trip it approves.
If the price changes before the trip is booked, it should go back to the approver. They said yes to a number, not to whatever the fare becomes.
How do you set it up?
Five lines are enough to start. Write them down, tell everyone who travels, and adjust after a month.
- Rules
- [fare limit by route], [hotel limit by city], [cabin by flight length], booked [days] ahead.
- Inside the rules
- Books straight away, no approval needed.
- Outside the rules
- Approved by [role] for [team].
- Stand-in
- [name or role] while the approver is away.
- Answer within
- [hours], before the fare or the hold runs out.
How do approvals work in Explura?
Trips inside your rules book straight away; trips outside them go to an approver first, then the traveller pays and books. Approvers are chosen per department during set-up. Approvers can choose someone to cover their approvals while they're away.
If the price changes before booking, the trip goes back to the approver. Some bookings are held for a limited time, so approve before the hold runs out.
Book a 15-minute call, then bring a real trip to a 45-minute one and we price it live.
