Source: [Original HTML page](https://stolenorbit.com/en/templates/automation-handover/)

Language: English

FREE TEMPLATE · FILL IN, DOWNLOAD, REUSE

# Automation handover worksheet

Verify that the assigned team can operate the service when its original builder is unavailable. Handover is an operational exercise, not merely a list of files.

[By Stolen Orbit](https://stolenorbit.com/en/about/) Revision 2026-09-24

## When to use it and what to produce

[Source for this section](https://stolenorbit.com/en/templates/automation-handover/#template-purpose)

At the end of a pilot, when managed support starts or when partners and internal owners change.

A handover record with accessible materials, accepted responsibilities, an operating exercise and assigned outstanding work.

Fill in the fields below and download your document. The website does not send or save answers: closing the page may lose them. Examples are illustrative and should be replaced with your process data.

[Download the complete blank template (.md)](https://stolenorbit.com/downloads/ownership-handover-en.md)

Without JavaScript, download the full template above and complete it in your editor.

## 1\. Assign accountability

[Source for this section](https://stolenorbit.com/en/templates/automation-handover/#ownership)

Distinguish the owner of the business outcome from the people managing infrastructure and configuration. Also record who decides changes, costs and suspensions.

**See a worked example**

Illustrative example: operations decides whether to add document categories; the partner implements the change after approval and testing. IT manages access to connected systems.

**Roles, backups and contacts**

Identify process owner, technical contact, support and backups with monitored contact channels.

**Service and support boundaries**

List workflows, environments, agreed coverage and activities requiring a separate engagement.

**Decisions and approvals**

Specify who authorises new access, functional changes, additional spending and workflow suspension.

## 2\. Check materials and access

[Source for this section](https://stolenorbit.com/en/templates/automation-handover/#materials)

Open the materials using the recipient’s identity. A documentation link is insufficient when its intended reader lacks the necessary permissions.

**See a worked example**

Illustrative example: the recipient opens workflow controls and logs with their own account. Personal credentials used during the trial are replaced or revoked.

**Materials and location**

Link configuration, agreed code, diagrams, versions, evaluation cases and dependency documentation.

**Accounts and credential management**

Record account ownership, references to managed secret storage and how access is changed or revoked.

**Licences, renewals and costs**

Specify who receives invoices and notices, monitors usage and approves renewals or increases.

## 3\. Run a guided handover

[Source for this section](https://stolenorbit.com/en/templates/automation-handover/#acceptance)

Have the recipient perform essential tasks. Record difficulties as outstanding work instead of automatically treating the handover as complete.

**See a worked example**

Illustrative example: the new owner finds a paused case but cannot access its recovery instructions. Missing access remains a blocker for accepting that responsibility.

**Recipient operating exercise**

Ask them to find a case, recognise an error, stop the flow and follow recovery in a suitable environment.

**Outstanding work and dates**

Assign impact, owner and due date to each unfinished item; state temporary operating limitations.

**Acceptance and first review**

Record who accepts which scope, with what reservations and when the first operating period is reviewed.

## Pitfalls to avoid

[Source for this section](https://stolenorbit.com/en/templates/automation-handover/#template-pitfalls)

-   Delivering files without checking that recipients can open and use them.
-   Depending on a single personal account to operate the service.
-   Closing a project while leaving outstanding work without an owner.

[Connect your ERP with a clear account of every record.](https://stolenorbit.com/en/services/erp-integration-automation/)

[Keep your automation manageable after the launch.](https://stolenorbit.com/en/services/automation-ai-maintenance/)

[Move from the first enquiry to a complete client handover.](https://stolenorbit.com/en/resources/professional-services-workflow-automation/)

[Build or buy AI: compare the complete business process.](https://stolenorbit.com/en/resources/build-or-buy-ai/)

[From AI pilot to production: increase exposure with concrete evidence.](https://stolenorbit.com/en/resources/rolling-out-ai-safely/)

[A useful AI brief describes the work to improve and the tests to pass.](https://stolenorbit.com/en/resources/ai-project-vendor-brief/)

[All templates and tools](https://stolenorbit.com/en/tools/)

[All guides](https://stolenorbit.com/en/resources/)

## Take the next step together.

Use this document to start a discussion about scope, evaluation and project ownership.

Review the text before sending. Only your email is needed alongside the message; other details are optional.

[Contact us](/en/contact/)

## Turn the question into a next step.

-   [Rolling out AI](https://stolenorbit.com/en/resources/rolling-out-ai-safely/)
-   [AI rollout plan](https://stolenorbit.com/en/templates/ai-rollout-plan/)
-   [AI operations runbook](https://stolenorbit.com/en/templates/ai-monitoring-runbook/)