# AI Client Handoff Document: Files, Access and Limits

A delivery link is not a complete handoff. The client needs to know which files are final, who owns each service and what remains to be checked. Use Brainbaby to create a handoff from a verified inventory, then open the files and test the instructions as the recipient would.

## Your brief

1. List final artifact names, versions, allowed share links and delivery status. Distinguish editable source, exported copy, preview and deployed service.

   ____________________

2. Record account owners, renewal responsibilities and secure access-transfer steps. Do not put passwords, secret API keys or recovery codes in the document.

   ____________________

3. Document known limitations, accepted exclusions and the support window you actually agreed. Assign unresolved items and link relevant operating instructions.

   ____________________

## Prompt

Create a project handoff from [verified inventory]. Include final files and versions, how to open or operate each deliverable, ownership, secure access-transfer checklist, known limitations and support scope. Separate verified checks from pending checks. Do not include credentials or claim a service is live without evidence. Add a recipient acceptance checklist and a section for unanswered questions.

## Illustrative example

Illustrative delivery: a PDF proposal, editable slide deck and a website preview. The inventory labels the preview as pending domain deployment. It identifies the client’s account as the future hosting owner and includes instructions to review form delivery. A handoff that calls all three ‘production complete’ would hide a material unfinished step.

## Acceptance checks

- [ ] Can the recipient open the delivered files and distinguish source, export, preview and live service?
- [ ] Are account ownership, renewals and access transfer clear without embedding secrets?
- [ ] Do unresolved checks have an owner and do support dates match the agreement?

Do not replace the client’s existing access with your own account for convenience. The document should describe a secure transfer and explicit ownership, not create dependency on a freelancer’s personal login.

---

Brainbaby · https://brainbaby.ai/blog/ai-client-project-handoff

CC BY 4.0 — https://creativecommons.org/licenses/by/4.0/