Designing software that says no

Almost all software is designed to say yes — reduce friction, complete the action, keep the user moving. Compliance software has the opposite job. Sometimes the most valuable thing it can do is refuse.

The UNABLE moment

When the crew assigned to a trip can’t legally fly it, we don’t bury a yellow warning three clicks deep. We surface UNABLE — in red, with the exact paragraph that was tripped, and a legal alternative right next to it.

No silent overrides

Operators do sometimes need to make a call the software flagged — that’s their right; operational control stays with the certificate holder under 135.77. So overrides exist. But they’re never silent: an override requires a typed reason and is logged with the user and a timestamp. “We flew anyway” becomes a documented operational-control decision — which is exactly what an auditor or an underwriter wants to see.

Saying no is the feature

Operators told us the part they couldn’t get anywhere else wasn’t the quote — it was the refusal, delivered with the citation and a path forward, before anything left the building.