Give Every Automation an Owner and a Maintenance Card

The person who built the workflow is away. A form field changes, requests stop appearing, and everyone assumes someone else is watching it. Avoid that gap with a one-page maintenance card. It should help the next person understand and operate the system—not serve as a technical trophy.

Write the essentials Purpose and expected result. Business owner and backup. Connected tools and account owners. Where failures appear and who responds. How to pause processing safely. How to perform the task manually. Last successful test, next review, and change notes. Use the workflow map as the starting point. Keep passwords and secret keys out of this document; consult the FTC’s security guide and your access checklist.

Define a check that proves something “The workflow is switched on” is weak evidence. For an inquiry process, compare source submissions with the tracker, inspect failures, and review sample outputs. Set review frequency according to volume and consequences. An occasional low-risk report and a busy customer intake process do not need identical routines. If failed runs can be replayed, check the tool’s behavior first. Zapier’s replay documentation helps explain why recovery needs more thought than clicking Run again.

Plan for ordinary changes A renamed field, departed employee, revised policy, or edited prompt can change the result. Record what changed and rerun the saved tests. For documentation, Google’s version-history guidance can help track revisions. Keep the actual workflow’s configuration history separately where your tool supports it; a document revision is not the running configuration.

Practice the fallback Ask the owner to explain how to pause the workflow, identify pending items, complete one manually, and restart without processing it twice. Use the debugging guide if the recovery path is unclear. Document the routine as an operating procedure someone else can follow.

Account for the upkeep Maintenance time belongs in the benefit calculation. If the owner does not have time or access to act, the name on the card is not enough. Your finish line is a short document plus one successful fallback rehearsal. A reliable small workflow with clear ownership is easier to build on than a complex system nobody can safely stop.