Skip to main content

​
Save a handoff before leaving

A handoff is a short explanation of where the project stands, with references to the evidence. It lets a new conversation start from saved work instead of relying on someone to remember months of discussion. This is a practical coordination procedure. A written handoff is not a complete transcript export or a native PeopleBot Instance backup.

​
1. Ask for the handoff

Keep the handoff compact. Link to supporting records instead of repeating them all. Attachments must actually be retained; a filename or expired link does not preserve the file.

​
2. Start the next conversation

Replace the placeholders. Give the new assistant access through its supported connection; the URL alone does not grant access.

​
3. Check its readback

You should get the current goal, accepted version, unresolved work, and a next action consistent with the handoff. If a newer report supersedes the handoff, the assistant should explain that with a reference.

​
What can travel between platforms?

Saved instructions, selected project knowledge, files, and reports can be read by a compatible assistant elsewhere. Tool access, credentials, provider-specific session formats, and runtime setup must be handled separately. You are preserving accessible project knowledge. You are not transferring hidden model state or guaranteeing that another model behaves identically. Next: verify your backup.