Write a complete handover for leave, departure, or role change: live work status, contacts, credentials process, and the tribal knowledge that isn't written anywhere.
Write my handover document. Context: {{context}} (leaving / extended leave / role change; who's taking over; how long I have). My brain-dump: {{braindump}} (projects and their real status, recurring duties, key contacts, systems I touch, things only I know).
Structure: Live work — each item with status, next action, deadline, and where the files live; Recurring duties with frequency and how-to links (or {SOP needed} flags); Key relationships — who, what they care about, current state of play; Access — systems I hold access to (list for IT, never passwords in the doc); and Tribal knowledge — the 'oh, also…' section: quirks, unwritten agreements, the supplier who needs chasing. Mark the 3 things most likely to blow up in my absence, each with a defusing note.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekCompare options against weighted criteria to decide.
Turn 'how we do this around here' into a standard operating procedure anyone can follow on their fir...
Onboard a new supplier properly: the verification file, the terms confirmed in writing, the trial-or...
A sustainability audit that finds real savings: energy, waste, and procurement wins ranked by paybac...
Plan the end-of-year shutdown: customer notice, leave mechanics, skeleton coverage, and the January...
Audit your SaaS stack for overlap and waste: the inventory, the consolidation candidates, and the mi...