For AI service providers · Template
AI service handoff checklist
Use this handoff checklist when a managed AI service changes owner or ends. Confirm delivered artifacts, stopped schedules and revoked access separately. The template does not transfer ownership or delete data automatically; record the actual checks and any unresolved retention or support obligations.
By Agentic Workers Team · Published · Updated
Download the checklistPrepare
Client; account owners; final deliverable; open work; retained files; agreed retention; support end date. Fill each field with an owner and a verification reference. Leave unknown items open rather than marking them complete.
Remove access
Stopped schedules; revoked upload links; revoked app invitations; disconnected accounts; reviewed provider consent; removed membership. Fill each field with an owner and a verification reference. Leave unknown items open rather than marking them complete.
Confirm
Client receipt; denied-access checks; source-account access; unresolved exceptions; responsible owner; final acknowledgement. Fill each field with an owner and a verification reference. Leave unknown items open rather than marking them complete.
Example provider workflow. Adapt it to the client’s agreed scope.
- 01
Prepare
Complete this part with the responsible client or provider owner.
- 02
Remove access
Complete this part with the responsible client or provider owner.
- 03
Confirm
Complete this part with the responsible client or provider owner.
Fit and limitations
- Good fit
- Providers documenting a real client setup, review or exit.
- Poor fit
- Treating a completed form as proof that a control exists or a result was verified.
- Known limits
- Keep secrets out of the document. Examples and blank fields are not evidence of completed work. Adapt the checklist to the client’s actual agreement and tools.
Sources and evidence
Documentation establishes the scope of a claim. It does not replace an acceptance test in your client’s environment.
| Source | What it supports | Checked |
|---|---|---|
| Customer portal operating notesProduct documentation | Upload and app-connection invitations are scoped to a selected agent. Revoking an invitation is separate from disconnecting an account. | |
| Agent tools and review guidanceProduct documentation | Supported tool actions can require approval. Test the exact tool and runtime; coverage is not universal. | |
| Read an agent run recordProduct documentation | Inspect available tool calls and execution details within the relevant workspace. A completed run is not proof of an accepted result. |
Questions providers ask
Can I download and adapt this?
Yes. Download the plain-text template and complete it for your service.
Should I include passwords or API keys?
No. Record the account owner and approved secret-storage reference, never secret values.
When is a check complete?
When the named owner has verified the result and recorded a safe evidence reference.
Set up one client service
Set up the client workspace, connect its tools and review the first deliverable. Use a tested delivery path, such as Telegram, so the client can receive work in chat. Track operating costs and review effort before pricing a recurring service.
Sign up now