Updated on 20 October 2026.
An AI monitoring handover should leave the client with working access, an understandable configuration and accepted materials. A PDF report alone does not achieve that. This protocol covers the end of an agency engagement, rather than routine reporting across clients.
Agree the transfer scope
Establish who contracts with the platform, pays for it and may manage access. Project access is not the same as transferring account ownership. Check contractual arrangements before deciding which data and materials may move.
If the project lives in an agency account, do not share that entire account and other clients' information. Confirm a suitable access boundary or transfer method with the provider. Without a transfer feature, a new project and a documented break in history may be necessary.
Prepare the acceptance record
| Material or responsibility | Client receives | Acceptance evidence |
|---|---|---|
| Configuration | Questions and versions, country, language, systems, aliases, competitors | Recipient approves the scope record |
| Access | Personal account and the correct project only | Recipient opens the project independently |
| History | Available, permitted material with scope notes | Files open; gaps are documented |
| Integrations | Connection owner and reauthorisation procedure | Client confirms control |
| Maintenance | Billing, reviews and support contact | Named responsible person |
| Closure | Revoked access and retained copies | Confirmation under agreed rules |
Transfer in this order
Record the end date and acceptance plan. List missing material rather than declaring a complete transfer.
Prepare permitted copies and configuration records. Separate this client's data from other projects; do not transfer everything simply because it is downloadable.
Give the recipient their own access and verify its scope. Do not hand over shared passwords or secrets used for other clients.
Confirm continuity: correct project, active billing, required connections and access to new observations. Use a separate migration protocol if the provider changes.
After acceptance, revoke unnecessary access and authorisations. Agree retained copies, their owner and deletion under applicable arrangements.
Completion criteria
The client should independently open the correct project, understand scope and know who responds to problems. The previously nominated recipient confirms acceptance, including limitations and unresolved issues.
Similar before-and-after scores do not prove a complete handover. Check access and configuration rather than an arbitrary percentage tolerance. Do not promise comparability when questions, method or provider changed.
What to confirm with Semly
Semly's public agency offer describes projects and access management. Confirm available permissions in the relevant plan and how a particular project may move. This protocol does not claim automatic account or full-history transfer.
