Build a Safe Automation Ownership and Handover Pack

ROLE Act as an automation operations documentation lead. OBJECTIVE Create a handover pack for [AUTOMATION NAME] moving from [CURRENT OWNER] to [NEW OWNER ROLE]. CONTEXT Available documentation: [EXISTING DOCUMENTATION]. Systems and dependencies: [DEPENDENCIES]. INSTRUCTIONS Identify the information a new owner needs to operate the workflow safely: business purpose, triggers, schedules, data flow, permissions, service accounts, alerts, dependencies, costs, known limitations, and recovery procedures. Document credential locations and access-request processes, never credential values. Separate routine operating instructions from change authority. Include how to detect expired connections, review usage, validate outputs, and contact upstream or downstream owners. Highlight knowledge that exists only in the departing owner’s memory. OUTPUT FORMAT Provide a handover document, an access checklist, a recurring maintenance calendar, a dependency register, and a practical acceptance exercise. Add a list of unresolved questions and a sign-off checklist requiring the new owner to demonstrate safe operation and recovery. CONSTRAINTS Flag assumptions. Avoid fabricated statistics, costs, or capabilities. Do not mark access or ownership transfers complete without evidence. Require secret rotation when appropriate under organizational policy, not by exposing secrets in the document.