Requests & approvals
Trip requests and approvals
A trip request is a record with dates, purpose, travellers, budget and a status, rather than an email someone has to interpret and forward.
What a request carries
What a request carries
Structured detail
Destination, dates, purpose, travellers and indicative budget, captured up front.
- Consistent fields every time
- Raised by the traveller or on their behalf
- Multiple travellers per request
Policy result attached
The approver sees whether the request is inside policy before deciding.
- Policy verdict alongside the request
- Exception reason visible
- No separate check needed
Notes and discussion
Questions and clarifications stay on the request instead of splitting into a thread.
- Notes retained on the record
- Visible to both sides
- Nothing lost in forwarding
Status history
Who asked, who approved, when it changed, and what it became.
- Full status trail
- Timestamped changes
- Auditable after the fact
Notifications
The people who need to act are told; the people who need to know are kept informed.
- In-portal notifications
- Status changes surfaced
- No chasing required
Becomes the trip
An approved request carries through into bookings, documents and the invoice.
- Bookings attached to the request
- Documents on the same record
- Invoiced against the same trip
One record from request to invoice
A request carries its own history. Who raised it, what the policy engine said, who approved it, what was booked against it and what it was finally invoiced at - all on the same object, months later.
- Structured fields instead of free-text email
- Policy verdict attached before the approver decides
- Notes and clarifications kept on the request
- Timestamped status trail that survives an audit
Ready to see it on your own travel programme?
Walk through the platform with our team, using your routes, your policy and your approval chain.