The company now books travel through a travel desk, and the travel policy has a cap: the desk approves trips up to its limit and refuses anything over it, which has to be rebooked; no line approver may approve travel over the cap. Every travel report must reach the desk first. The desk appears in a team’s HR roster with the role travel, wherever someone added it; everyone else has the role approver. When the desk is away, travel goes to the line approvers like any other report.
Small trips are approved by team leads who don’t check the policy, and trips over the cap are approved by finance and paid. The travel team finds out from the card statement.
Reproduce
The platform roster lists the travel desk last. A 60 travel report comes back EX-11: approved by Sam; checked Sam; a 2,500 trip comes back approved by finance.
Acceptance criteria
- A travel report goes to the travel desk before anyone else, wherever the roster lists it: up to the desk’s limit it is approved, over it refused, and nobody after the desk sees it.
- Any other report passes the travel desk and goes to the line approvers as before; the checked list shows it passed the desk.
- When the travel desk is away, or the team has none, travel goes to the line approvers like any other report.
- CHAIN-101’s rules still hold: roster order, limits, people who are away.
Notes
- Each case gives one roster, then submits each report in turn; the lines print joined by “ | ”.
- A refusal prints as EX-12: refused by travel desk; checked travel desk.
- Keep the names and signatures of submit, routeExpense and report.