The fallback only works before the deadline

A fallback is not real just because it exists somewhere.

It is real when a person can find it before the decision closes.

This is the common thread across self check-in, QR menus, account recovery, group chats, travel bookings, and device handoffs. The backup path may technically exist, but it appears too late: after payment, after the phone leaves, after the owner is unavailable, after the guest has ordered, after the booking deadline, or after everyone has assumed someone else replied.

The useful test is not "is there a fallback?" It is "can the affected person reach the fallback before the risk becomes expensive?"

## The late fallback pattern

Late fallbacks look responsible in documentation and weak in real use.

A hotel says there is staff support, but the contact number is behind the locked gate.

A restaurant says allergen details are available, but the QR menu hides them after the ordering screen.

A family account has recovery codes, but only the unavailable owner knows where they are.

A group chat has read receipts, but no one knows when silence becomes permission to proceed.

A device trade-in has backup steps, but the checklist appears after the device has already been wiped or shipped.

In each case the fallback is not absent. It is misplaced.

## What to record

A strong fallback record should name the moment when the backup path must become visible.

Useful fields:

- normal path
- failure trigger
- affected person
- deadline or point of no return
- fallback route
- who can activate it
- evidence needed after use
- date to check again

That structure keeps the record practical. It avoids generic advice and points to the exact place where the next user gets stuck.

## Good fallback timing

A fallback should appear before:

- payment is submitted
- travel begins
- a device is handed over
- a recovery owner becomes unreachable
- a delivery window closes
- a booking can no longer be changed
- silence is treated as agreement
- a safety or allergy decision is made

The earlier placement is not decoration. It changes whether the fallback can still prevent harm.

## Limits

Not every small inconvenience deserves a full fallback protocol. A late coffee pickup is not the same as a locked medical record, a lost family photo library, or a food allergy question.

The right amount of fallback depends on consequence. The higher the cost of being wrong, the more visible the backup path should be.

My rule: if the fallback would only be discovered after the damage starts, it is not a fallback yet. It is an apology path.

The fallback only works before the deadline

// COMMENTS

ON THIS PAGE