Validera sits in your browser quietly until you go to commit a booking. At that point it shows you a coloured badge. This guide explains the three colours and what to do with each one.
When you open a supported source-of-truth platform (your ticket system) and a booking site (Airbnb, Booking.com, etc.), Validera reads the source ticket and watches your booking. Just before you click the commit / book / confirm button, a badge appears. It will be one of three colours.
Everything checks out. The booking matches what the source ticket says: dates, price, location, accessibility, and any other rules your team has set up.
What to do: proceed with the booking as normal. Validera logs that this verification happened so the audit trail shows you didn't blindly book.
Something's off but might be intentional. Maybe the price is slightly above the budget, or the accommodation type matches the request only loosely. Validera will list which specific rules tripped.
What to do: read the warning. If the booking is still right (e.g. you got pre-approval for a small over-budget), click Override, type why, and proceed. If the warning has caught a genuine mistake, fix it before booking.
This booking would breach a hard rule. A blocking rule is one your team has decided cannot be overridden silently — usually involving large dollar amounts, wrong dates, or a location that doesn't match the claim's geography.
What to do: by default, do not proceed. If you genuinely need to override a block (e.g. for a documented exception your manager has approved), click Override and provide a substantive reason. Every override is logged and reviewed by your team admin.
Override reasons appear in your team's audit trail. They're the first thing your manager and your auditor will read. The good ones explain why this booking is correct in this case, with enough specifics that someone reading it three months later still understands.
The bar: if you read your own override reason in three months and have to think hard to remember why you did it, it wasn't specific enough.
Your team has a 10-character minimum on override reasons. That's not a quality bar — it's a typo guard. Aim for one or two complete sentences.
Every time you see a Validera badge, the following is recorded in your team's audit trail:
Your team admin can see this in the dashboard at app.validera.io and export it for compliance reviews. You don't have to do anything special — the logging happens automatically.
To save you wondering: Validera does not capture your password, payment card numbers, MFA codes, files you have open, your browsing history outside the supported platforms, or anything you type that isn't an override reason. The full list is on the security page.
The badge is supposed to be helpful, not annoying. If you think Validera is producing a wrong verdict (passing things it should warn about, or warning on things that are clearly correct), tell us: