← Navan
Complex day at Navan

Fix approval records for role changes before the audit window closes

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

Role changes are colliding with the approval record that regulated bookings must retain.

Travelers need bookings to continue while travel managers need each authorization to remain reconstructable.

Who you’d be doing this for

“Legal asked who approved three trips, and I’m still piecing it together from screenshots.”

Markus Martin · Corporate Travel Manager

Administers a regulated enterprise travel program and must provide authorization evidence for booked travel.

What is at stake

Several confirmed trips cannot be tied to a reconstructable authorization after traveler roles changed. You must weigh booking continuity against an audit record that cannot be recreated later.

Why it isn’t already fixed

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

  • booking continuity vs. authorization traceability
  • role flexibility vs. immutable approval evidence
  • audit deadline vs. cross-service validation
  • least-privilege access vs. operational visibility

Why Navan

Book with AI and enterprise approval workflows place authorization history at the center of corporate travel governance.

Written with these in mind

systems-minded product engineerbackend reliability engineersecurity-conscious full-stack 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.