Create intermediate Works with: Any AI

Asana Handover Task List for a Departing Team Member

Structured brief Has example

• ✅ Asana

Make sure work, access and knowledge are transferred.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Build a handover task list in Asana for a colleague who is leaving or changing role. Their responsibilities: [RESPONSIBILITIES]. Open tasks and projects: [OPEN_WORK]. Recipients: [RECIPIENTS]. Last day: [LAST_DAY].

Create sections for Active work, Recurring duties, Relationships and contacts, Access and accounts (reminders only, handled through the proper process), Documents and where they live, and Knowledge sessions. For each task give the name, the new owner, a due date counted back from the last day, and what done means. Order tasks so the highest-risk items come first, and check that every open task has a named new owner by the last day.

Do not put passwords or personal data in tasks. Add two short knowledge sessions with a topic list for each, and a task to record decisions the person made on their own that others may not know about. Add a task to review shared inboxes, calendars and scheduled items, and a short message for each group of customers or partners saying who their new contact is. Add a check one month after departure to catch anything missed.

Keep the tone neutral and factual, because the person may be leaving unhappily.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Last day: 28 March (so tasks are dated from that day).
Sections and sample tasks. Active work: list open tasks and agree the new owner for each (due 14 March); handover meeting for the three main projects (due 18 March). Relationships: introduce successors to the five key contacts (due 21 March). Access: transfer shared files and request removal of accounts through IT (due 28 March). Knowledge: record a 30-minute walkthrough of the monthly report (due 24 March). Check: on 4 April confirm that no open task is still assigned to the leaver and that nothing was missed.

• structured
• asana