Keep critical knowledge working when roles change.
Capture the work, decisions, and context your team depends on. Flamekeeper helps you review gaps and prepare a useful handover when someone leaves, takes extended leave, or changes roles.
- Up in 10 minutes
- GDPR & CCPA compliant
- The leaver just gets a link
Good morning, Emma.
A little clarity for your day. Here’s what needs your attention.
Handovers in progress
People, progress, and a clear next step
Your HR platform closes the departure. It can't capture what's in their head.
Payroll, access, equipment, paperwork, and exit interviews all need to happen. Your HR platform is built to make sure they do.
But knowledge transfer usually becomes one more checkbox: write a handover, transfer some files, schedule a meeting. That confirms the task was completed. It doesn't confirm the right knowledge was captured.
Flamekeeper fills that gap.
Flamekeeper integrates with the HR software you already use, so it’s easy to kick off offboarding and manage employee changes in one flow. Personio, HiBob, and Workday are available now, with more integrations on the way.
Turn “complete the offboarding” into a process you can trust.
From identifying what matters to approving the final documents, every step is visible before the employee leaves.
Start a case in two minutes.
Drop in the employee's role, last day, and a sentence of context. Or talk it through with the AI assistant. Flamekeeper turns that context into a role-specific knowledge-transfer plan, not a generic offboarding template.
- A short form, or a quick chat with the AI
- Sections drafted from the role and your real context
- Yours to edit before anyone else gets pulled in
Pull out what they'd never write down.
AI-guided interviews with the manager, the departing employee, and the team members who rely on them uncover tacit knowledge a blank document misses. They can respond in the app, through a single email link, or by bringing in relevant Slack and Microsoft Teams messages. You see progress as it lands.
Handover case: Erik Stewart
What does Erik handle that would quietly break next month if nobody picked it up?
The quarterly Snowflake billing reconciliation. It is a notebook on his laptop, he runs it manually, and nobody else has seen the inputs.
What is the consequence if it is missed, and who should take ownership?
Last quarter it caught a €14k overcharge. Priya should own it, but Erik needs to walk her through the notebook first.
Got it. I've added Priya as the next owner. After she runs it for the first time, what should she verify, and who should she contact if the numbers don't match?
Knowledge extracted
Ownership starts after Erik completes the walkthrough.
No backup currently knows the inputs or workflow.
Manual notebook workflow; inputs still need documenting.
Currently stored on Erik's laptop.
Assign Priya as the new owner before the last day.
Documents that actually reflect the role.
When the knowledge transfer feels complete, Flamekeeper drafts the handover documents from everything you captured. The leaver refines them by chatting with the AI, dropping in files, notes, or meeting transcripts. Action items spawn alongside, so nothing slips.
- Documents drafted from the case, not a blank page
- Leaver refines via chat, files, notes, transcripts
- Action items tracked beside the docs they belong to
Recurring Responsibilities Map
This document maps the recurring work needed to keep billing operations healthy, including normal ownership, timing, systems, and escalation paths.
Weekly responsibilities
- Review failed payment retries every Monday in Stripe and the billing dashboard.
- Reconcile enterprise invoices by comparing Snowflake usage totals against issued invoices.
- Check unresolved billing support tickets before Wednesday's finance sync.
- Confirm usage imports completed successfully before invoice generation.
- Share the payment retry and collections summary with Finance.
Monthly responsibilities
- Close the billing period by running the reconciliation notebook and confirming manual adjustments.
- Share material revenue exceptions with Finance and Customer Success.
- Audit plan changes, credits, and manual adjustments before close.
- Refresh the billing ownership and escalation contact list.
What usually causes the reconciliation to fail, and who can approve a manual correction when the totals don't match? You can reply here, or send a source file or meeting transcript and I'll extract the relevant details.
Sign it off, then put it where work lives.
A reviewer approves each document. Action items close out one by one. Download the full pack as PDF, Word, or Markdown, or push it to Google Docs, ready for the knowledge base, wiki, LMS, or shared drive your organization already uses.
- Review and approvalSo you know what's been signed off, and by whom.
- Action items closedSpawned from the case, tracked to done.
- Knowledge base-ready exportChoose from a wide range of formats that work with your existing knowledge base—with no migration or lock-in.
Flamekeeper does one thing.
Keep your existing HR offboarding process for payroll, access, equipment, and exit interviews. Flamekeeper handles knowledge retention: capturing what the person leaving knows, including the parts that are not in any document, and preparing it for your existing knowledge base.
What we do
- +Open a case from a role and short context
- +AI interviews that uncover tacit knowledge from the leaver, manager, and team
- +Drafted documents the leaver refines with chat, files, notes
- +Reviewed pack exported as PDF, Word, Google Docs, or Markdown
What we do not do
- −HRIS and employee records
- −Payroll, benefits, PTO
- −Exit interviews and surveys
- −Asset return and IT deprovisioning
From knowledge to a handover people can use.
Flamekeeper draws on knowledge-management research, including Roudiere and Lento's ASK framework, to turn tacit knowledge into structured, usable handovers through guided elicitation, adaptive follow-ups, and quality checking. Find out more
The employee offboarding you wish you had on the way in.
The last two weeks of a job are usually a slog of half-finished docs, awkward calendar invites, and the quiet feeling that you are leaving things undone, even though you have worked hard to leave well.
Flamekeeper gives you a clear structure instead of a blank Google Doc, guided interviews instead of memory dumps, and targeted validation instead of endless back-and-forth. Your replacement gets a practical head start, and you can close the chapter properly.
“The onboarding document was actionable from day one. It captured the decisions behind the work and the right people to contact—even details my manager didn’t have.” Maria, new team member
Start free. Add handovers when you need them.
Your first handover is free, then choose the pack that fits your team.
One handover
Try the full handover workflow.
Free
1 handover during beta
Beta offerThree handovers
A pack for your next transitions.
€129
€43 per handover
3 handoversFive handovers
More handovers, a lower unit price.
€199
€39.80 per handover
5 handoversEnterprise
Planning a wider rollout?
Let's talk
- Discuss handover volume
- Review procurement needs
- Talk through data requirements
Your first handover is free. After that: €49 for one handover, €129 for three, or €199 for five. Prices shown in EUR.
Make this a team thing.
Individual handovers are useful. A standard knowledge-transfer process across the company is transformational, and it is usually something HR teams are ready to fund because institutional knowledge loss from employee departures lands in their world.
We wrote them an email. Yellow placeholders are yours to fill in. Edit anything else.
Hi [HR contact],
I want to suggest we standardize knowledge transfer for role changes and employee departures. I think Flamekeeper is a practical option.
Why now. Handover quality is inconsistent across teams, so tacit and institutional knowledge gets lost during offboarding. That creates avoidable disruption for incoming employees and their managers.
What this gives us. A repeatable process with clear ownership, practical documentation, visibility on open risks before transition day, and an approved pack for our existing knowledge base.
Can we run a short pilot for the next transition and review results with HR and team leads? If outcomes are strong, we can make it our default handover standard.
Thanks,
[Your name]
Real questions, honest answers.
Practical notes for handovers that hold up.
Knowledge Base Basics for Organizational Knowledge Transfer
Learn what a knowledge base is, how organizational knowledge differs by type, and how sharing knowledge keeps handovers, onboarding, and ops steady.
Read article10 Best Employee Onboarding Tools: A Guide to Software Selection
Find the best onboarding software for your team. This guide compares 10 employee onboarding tools by use case, from HR admin to training.
Read articleSomeone on your team will leave this quarter.
Be ready before they give notice.

