Plan coverage for a key person's leave: what actually needs covering vs what can wait, who picks up what, and the handover that prevents the return-to-chaos.
Plan coverage for: {{person}}'s leave ({{dates}}). Their responsibilities: {{duties}} (recurring work, live projects, decision authorities, relationships they own). Available coverage: {{team}}.
Triage their load: must-be-covered (customer-facing, deadline-bound, decision authorities — assign each to a named person with the authority explicitly delegated), can-pause (park with a restart note), and can-batch-for-return (the queue they'll process back). Build: the delegation announcement (internal + the external note to customers/suppliers naming their temporary contact), the handover meeting agenda, the emergency-contact rule (what genuinely justifies interrupting leave — decided now, not at 9pm mid-crisis), and the return-week plan: a catch-up day before the calendar refills. Flag: if one person's leave takes this much planning, that's a key-person-risk finding — note it.
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 WeekWrite a clear, inclusive job description from key details.
Role-specific interview questions with scoring guidance: behavioural, technical, and situational — p...
Frame difficult feedback clearly and kindly (SBI model).
Draft a balanced performance review from notes.
Run a probation review properly — pass, extend, or exit: the evidence assessment, the conversation s...
Design an internal move or secondment: the three-way agreement, backfill reality, success criteria,...