Travel Desk turns one form into the two things every out-of-state trip needs: the Travel Authorization email to your coordinator, and the row in the shared travel planner. Then it keeps track of what happens next β bookings, and money a third party owes you back.
It also works out who else is paying. On invitational or sponsored travel the confirmation usually spells out what the host covers β lodging, airfare, meals, ground transport β and buries the billing contact several paragraphs below it. Travel Desk fills in Third-party reimbursement #1 from that: the payer, their contact address, and which categories they cover. Check it and add the cap in Max reimbursement if the email states one β that's what lets Travel Desk chase the money after the trip.
Links are unwrapped, too. Everything arriving at a state mailbox is rewritten by the
mail filter into a 400-character urldefense.proofpoint.com address; the real
event link is recovered from inside it so the authorization form carries something a
human can read.
Under each filled field it shows where the value came from, down to the line it matched, so you can check it against the email in a glance instead of re-deriving it. It will not overwrite anything you have already typed unless you tick Replace what I've already typed β and what it left alone is listed too.
Where it isn't sure, it leaves the field blank and says why. An unlabelled dollar figure
is ignored on purpose: in a confirmation, $1,240.00 might be the registration,
the hotel total, or last year's price, and a wrong number on a travel authorization is worse
than an empty box. Same for a scanned PDF with no readable text β it tells you it couldn't
read it rather than quietly finding nothing.
Then read down the form and correct anything that looks off. Departure and Return are assumed to be the day either side of the event, which is a guess and is labelled as one.
Jane Doe, MVD, Field Ops, speaker
(only the name is required; blank parts inherit yours). Each person gets their own
planner row, so division totals and any budget report count everybody. Use the
Costs entered above are dropdown to say whether those costs are per person or
for the whole group.| Section | What it does |
|---|---|
| βοΈ My trips | Lists what you've filed. Check for booking emails scans your inbox for confirmations (Concur or whoever your org books through) and links them to the right trip, so you can see at a glance what's still unbooked. |
| π΅ Third-party reimbursements owed | After a trip ends, anything a third party agreed to cover shows up here, aged in days. Workday packet drafts the email finance needs to set up the receivable in Workday. Remind drafts a polite nudge to the third party. Record the Workday number, and mark Received β when the money lands. |
Do this once, then hand every traveler a setup code and you're finished.
The coordinator view opens with the reading, not with work:
| Section | What it is |
|---|---|
| Gauge | Planned versus actual across trips that have been closed out β compared like for like. Money committed on trips still to come is reported separately, so the number isn't flattered by counting estimates against actuals that don't exist yet. |
| Approve travel | The one real queue: requests nobody has authorised yet, soonest departure first. One click records your approval, your name and the date on the planner row. |
| Closed out recently | Trips with costs in, worst overrun first, anything past 20% flagged. Nothing here needs doing unless a number looks wrong β Mark seen just tidies the list. |
Once your planner is connected, a π Coordinator view section appears (travelers who set up with a profile code never see it). Click Load everyone's travel and you get, from the shared planner rather than your own trips:
| Panel | What it answers |
|---|---|
| Still to book | Upcoming trips whose status isn't booked or approved β your follow-up list. |
| Coming up | Everyone's upcoming travel, soonest first. |
| Spend by division | Trips and dollars per division, and per fiscal year β the numbers behind next year's request. |
| Third party owing | Finished trips where somebody agreed to reimburse, so nothing quietly goes uncollected. |
| Authorizations vs planner | Cross-checks the Travel Authorization emails in your inbox against planner rows, and flags both directions: a request you approved that never reached the planner, and a planner row with no authorization behind it. |
SFY27) to scope every panel to one year, or
leave it blank for everything. For charts and trends, use the Power BI recipe below β the
coordinator view is deliberately about what needs doing today.Because the planner is an Excel table on SharePoint, Power BI reads it natively β budget burn per division, a follow-up queue, a destination map. The build recipe is in POWERBI.md in the project repository; hand it to whoever runs Power BI at your agency.
| What you see | What to do |
|---|---|
| The Planner table dropdown is empty | The sheet isn't an Excel Table yet β use Make this sheet a table in the yellow box that appears. (Doing it manually in Excel works too: select the data β Insert > Table β save β Connect workbook again.) |
| Only one row appeared for a group trip | Additional travellers go in Other travelers on this trip, one per line. Names listed in prose elsewhere don't generate rows. |
| "Name, event, and location are required" | Those three fields are blank β they're the ones marked required. |
| The draft didn't open | Some Outlook versions block pop-ups. The draft was still created β check your Drafts folder. |
| Nothing in reimbursements owed | Only trips that have already ended and had a third party entered appear there. Trips filed before this feature existed won't show. |
| A sign-in popup appears | Normal β Travel Desk acts as you, using your own Microsoft 365 permissions. It never sees anything you couldn't already open. |