Last reviewed Sep 6, 2026
In Preflight, no one manually checks a box to mark a requirement as passed. Every result is calculated by Launch itself, based on what it can observe in your connected systems.
Why this is deliberate
The gap between a ticked box and a true condition
A checklist that a person can tick by hand only records that someone clicked a box, not that the underlying condition is actually true. Launch is built to remove that gap. If a requirement checks pricing consistency, Preflight reads the actual prices from your connected systems and compares them; it doesn't ask anyone to confirm they're consistent.
What this means day to day
You can't resolve a failed requirement by marking it passed. You resolve it by fixing the underlying condition, for example correcting a mismatched price, and then re-running the preflight so Launch can verify the fix.