Contents
At a glance
- Category
- Business and buying
- Test of completeness
- You could run and change the system without the builder
- Ownership
- Platform account, API keys, OAuth connections and code repository all in your name
- Documentation
- Plain-language purpose, triggers, connections, failure behaviour, how to change common things
- Never skip
- A recorded live walkthrough where the owner makes a real change
- Agree in writing
- Included maintenance period, who fixes API breakages, change rate and response time
What a real handover includes
Handover is the transfer of a working automation from whoever built it to whoever will own it. It is complete when you could, in principle, run and change the system without the builder - not because you want to, but because you can. Anything short of that is a dependency dressed up as a delivery.
The reason to be precise about this is that automation projects are unusually easy to hand over badly. A workflow running in someone else's account, built with their API keys, documented nowhere, is technically delivered and practically theirs. That situation is uncomfortably common and it is entirely avoidable by agreeing the handover contents before the build starts.
The checklist
Ownership: the platform account is in your name and billed to you, all API keys and OAuth connections are on your accounts, and any code lives in a repository you control. Access: you hold admin, and the builder's access can be revoked without breaking anything.
Documentation: what each workflow does in plain language, the trigger and the schedule, what it connects to, what happens when it fails, and how to change the things most likely to need changing - message wording, timings, recipients. Operations: where to see runs, how to spot a failure, who to call, and what the monitoring and alerting is. Continuity: a working export of every workflow and a note of the exact platform version.
The part everyone skips
A live walkthrough with the person who will actually own it, in which they make a real change while the builder watches. Not a demo - a change. Editing a message, adding a recipient, pausing a workflow. Fifteen minutes of that reveals more gaps than any document, and it is the difference between documentation that is accurate and documentation that was written from memory.
Record it. The person who attends the walkthrough will leave the business eventually, and a recording plus written documentation is what makes the second handover survivable.
What happens after
Agree the ongoing arrangement explicitly, because this is where most disputes begin. Three questions: what maintenance is included and for how long; what happens when an API changes and breaks something six months later; and what the rate and response time are for changes - see SLA.
None of those need to be generous. They need to be written down. "Included for thirty days, then billed hourly with a two-working-day response" is a perfectly good answer; the absence of an answer is not.
What you should know
Ask what the handover contains in the first conversation, not the last. A builder who cannot describe it is telling you something useful about how the project will end. This is also the practical test of vendor lock-in at the supplier level rather than the platform level - the question "what happens if we stop working together" should have a boring answer.
A8gent's own position is that you own what we build: the accounts are yours, the documentation is written for the owner rather than for a developer, and handover includes a recurring plain-language report of what ran and what it saved. If you want to see how that is scoped, start with the free automation audit or read the automation services page.
Handover FAQ
What should a proper automation handover include?
Ownership of the platform account and all credentials, admin access, plain-language documentation of what each workflow does and how to change it, operational guidance on monitoring and failures, and a working export of every workflow with the platform version noted.
How do I know the handover was complete?
You could revoke the builder's access today and still run and change the system. If revoking their access would break something, or if nobody in your business knows how to edit a message, the handover was a demonstration rather than a transfer.
Whose accounts should the automation run on?
Yours, billed to you. A workflow living in the builder's account with their API keys is a dependency regardless of how well it works, and unwinding it later costs more than setting it up correctly at the start.
What is the most useful part of a handover?
A recorded live walkthrough in which the person who will own it makes a real change while the builder watches - editing a message, adding a recipient, pausing a workflow. Fifteen minutes of that exposes more documentation gaps than any review.
Who fixes it when something breaks after handover?
Whoever your written agreement says. Agree three things up front: what maintenance is included and for how long, what happens when a third-party API changes six months later, and the rate and response time for changes. The answers need not be generous, only explicit.
When should I ask about handover?
In the first conversation. A builder who cannot describe what you will receive at the end is telling you something useful about how the project will finish, and it is far cheaper to learn that before the work starts than after.
Primary source
NIST AI Risk Management Framework - governance and documentation practices
Checked August 2026. Anything priced or rate-limited moves, so verify against the source before you budget.
Want this built rather than explained?
Knowing what handover means is one thing; having it running in your business is another. We scope one workflow at a time, quote a fixed price in writing after a free consult, build it, and hand it over with documentation you own.
