If a manager has invited you to contribute, your job is to explain the work as someone else will encounter it. You do not need polished prose. Concrete details are more useful than a long summary of your role.
Open your invitation
Use the invitation or collection link sent by your manager and follow the sign-in or collection steps shown. If you cannot access the case, ask the manager to check the email address and your case participation. Do not forward a personal collection link to other people.
The case also has manager, employee, and colleague chats. Answer from your own perspective: employees can explain routines and exceptions; colleagues can add dependencies, shared decisions, and stakeholder expectations.
Make each answer actionable
For an important responsibility, include:
- When it happens: the trigger, cadence, or deadline.
- How to do it: the practical steps and links to approved source documents.
- Who is involved: the next owner and the person to contact if blocked.
- What goes wrong: common exceptions, warning signs, and escalation paths.
- What happens next: current status and the next concrete action.
Instead of “I handle the weekly report,” write: “Every Monday, update the renewal report from the account dashboard. Check overdue renewals with the account owner before the operations meeting. The runbook explains the filters.” Add the actual approved links in your private case.
Separate facts from unknowns
Say when you do not know something. Flag outdated documentation and decisions that still need an owner. Do not include passwords, API keys, or unrelated personal information; see safe knowledge sharing.
Your context helps Flamekeeper surface missing knowledge before the transition, giving the next person fewer mysteries to solve.