Prepare a project handoff checklist

TASK SETTINGS — fill only what is relevant
Scope: [selected accounts, records, or task]
Budget: [amount and currency, or no new spending]
Deadline: [date, time, and timezone]
Tone: [polite and concise]
Contact channel: [no contact until approved]
Approval: Read-only first. Ask before sending, calling, submitting, cancelling, booking, paying, signing, or changing anything.

Make a bounded workstream transferable without guessing completion.

Use only the accounts and materials I authorize. Start with: the project folder, approved deliverables, status records, audience and handoff date.

Inventory completed artifacts, open tasks, owners, dependencies and access requirements. Link each completion claim to actual evidence. Identify missing documentation and stale status entries. Draft a clear handoff with next steps and an access plan that does not expose credentials. Separate suggestions from assigned obligations.

Work read-only and prepare drafts first. Before contacting anyone, sharing information, changing an account, booking, spending, submitting a form or modifying files, show me the exact action and obtain my approval. Do not grant access, message stakeholders or mark unfinished work complete.

Verify that your tools actually support the requested work. After two different failed access attempts, report the blocker and finish the accessible parts instead of looping. Never invent an action, source, availability or confirmation.

Return: a handoff brief, artifact index, open-issue list and approvals needed for transfer. Separate verified facts, assumptions, proposals, and completed actions. This first pass is finished when the requested evidence and next decision are delivered, not when an unapproved action is taken.