What is a manual fallback?

Definition

A manual fallback preserves a workable path when an automated system fails, produces uncertain output, or encounters an exception. It can involve returning to the former procedure, routing the case to a person, or using a simpler verified tool.

Fallbacks should be designed before failure and tested periodically. The responsible person needs the required access, source information, and instructions, while the automation must fail visibly enough to trigger the alternate path.

Frequently asked questions

Why keep a manual fallback after automation?

It prevents one tool failure or incorrect result from stopping important work and supports recovery while the underlying problem is investigated.

What makes a manual fallback practical?

It needs clear triggers, an available owner, accessible inputs, current instructions, manageable workload, and a way to reconcile later results.

Videos explaining manual fallback