← Navan
First-time day at Navan

Align approval chains after hotel policy changes

You’re the software engineer. Your team is in the room. Printed Oct 17, 2026.

A published hotel rule and its visible approval chain no longer agree.

Travel managers need trustworthy policy changes while active booking approvals must keep moving.

Who you’d be doing this for

“I changed the hotel rule this morning, and the old approver is still getting the requests.”

Christos Lopes · Corporate Travel Manager

Administers traveler groups, hotel limits, and approval routing for an enterprise travel program.

What is at stake

Published hotel rules are sending some travelers through an outdated approval chain. You must weigh a fast correction against keeping active approvals and bookings stable.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • fast correction vs active approval continuity
  • service truth vs portal state
  • administrator confidence vs release scope
  • regression coverage vs pipeline speed

Why Navan

Enterprise travel policies and approval workflows share the same administrator controls for managed travel programs.

Written with these in mind

product-minded backend engineerfull-stack reliability engineerenterprise workflow engineer

Not your kind of problem? 54 more at Navan, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.