First week
Request billing admin access. Meet Priya from Security. Review the renewal decision history.
Answers: What should I do before I understand anything else?Roles change hands. The work should not skip a beat.
Handov is employee handover software that turns what one person carries, from in-flight work and decisions to relationships and access, into a reviewable handover. A manager approves it before someone else takes over, for a week or for good.
For People Operations teams and managers handling departures, internal moves, parental leave and other coverage, and succession.
The parts of a role that never make it into the document
A folder and a task list show what exists. They rarely explain what is fragile, who holds influence, why an exception exists, or what the next owner should do first, whether the role is changing hands for good, for a season, or just for a week.
Handov asks for this context explicitly, and a manager signs it off before the role changes hands.
Written downLeft out
The decision
Why it was made, what constrained it, and which options were rejected.
The contact
How much influence they have, what they expect, and how they prefer to work.
The workaround
The undocumented exception that keeps a process from breaking.
Every open handover, its readiness, and what is blocking it
Managers see which transitions are on track, which items are unowned, and what needs a decision before the handover date. No chasing for "the handover doc".
How a handover runs in Handov
Four stages, each with a named owner. The manager sets it up, the employee captures, both review the gaps, and the successor receives an approved, read-only pack.
ManagerTransition brief
In progress01
Define the transition.
Name who is handing over, who takes over, the target date, and the accountable manager.
Current ownerAlex Morgan · Product Operations
Transition ownerRachel Osei · Manager
SuccessorNot assigned · action required
The pack Jordan Kim opens on day one
Prepared by Alex Morgan and approved by their manager. Immediate actions come first, then the context behind them. Each area answers one question the successor would otherwise have to go and ask.
Active work
The billing migration is in testing. Finance sign-off is due on 18 September.
Answers: What is in flight, and when is the next deadline?People
Priya owns the security review. Karim controls the client budget and expects early notice of changes.
Answers: Who do I depend on, and what do they expect from me?Systems and access
Billing admin access is approved by Finance Operations and normally takes five working days.
Answers: What do I need access to, and how long will it take?Decisions and exceptions
The renewal date stays unconfirmed until security signs off. The reason and the source email are attached.
Answers: Why is it done this way, and where is the evidence?What happens to a forwarded email?
Handov pulls the people, actions, decisions, and risks out of it and proposes where they belong. Nothing reaches the successor pack until a person says so.
- The employee confirms accuracy. Suggested context stays in review until they keep or discard it.
- The source stays attached. A reviewer can always see which email an item came from.
- The manager controls release. The successor sees the pack only after approval.
Organization boundariesDatabase-level policies keep each organization's records separate by role.
AI drafts, people decideAI prepares reviewable drafts and checks. Nothing is applied to a handover without a person's review.
No-training AI requestsRequests sent through OpenRouter carry no-training, zero-retention terms. Our DPA lists every AI provider and what reaches it.
No secrets storedThe pack records who grants access, never the credential itself.
Security questions for your team? Write to us 
Give the next person the full picture.
A renewal date matters. So does why it changed, who agreed to it, and what still needs a decision. Handov brings that context into the handover so the next person can pick up the work, for a week or for good.
Let’s talk about your handoverThings people ask before they try it
The objections we hear most, answered as plainly as we can.
Ask a different question
How is Handov different from a shared document?
A shared document stores whatever someone remembers to write. Handov establishes ownership, guides capture across the critical parts of a role, exposes gaps, requires manager approval, and presents the successor with a structured pack.
What if the current owner does not fill it in?
Handov cannot make anyone write. What it does is make the gap visible while the current owner is still available. The manager sees which areas are empty and which items are blocking, and can chase specific questions instead of asking for "the handover doc". An empty area on the target date is a known gap, not a surprise three weeks later.
Does Handov publish AI-generated content automatically?
No. Automated extraction can prepare a reviewable draft from a forwarded email. The employee decides what to keep, the source remains attached, and the manager approves the handover before release.
What does the readiness score mean?
Readiness reflects the required context captured for each responsibility and whether a successor has been assigned. The gap report shows the missing areas behind the score. It helps a manager focus attention; it does not claim that every possible risk has been discovered.
When can a successor access the handover?
Only after approval. The successor receives a stable, read-only pack. If changes are required, an authorized manager can reopen the handover and return it to review.
Does Handov replace our wiki or password manager?
No. Handov holds the context around one role for the weeks of a transition, then hands the successor a read-only pack. Permanent documentation stays in your wiki. Handov is not designed to store credentials: AI-generated questions never ask for a password, and the pack is meant to record which system is needed, who grants access, and how long it takes, not the credential itself.
Is Handov only for people leaving?
No. Roles change hands for many reasons: someone leaves, moves to a different team, goes on parental leave or a sabbatical, hands off a specific responsibility, or a backup needs to be ready before the fact. Handov works the same way in each case: capture, review, approve, hand over.
Run the next transition properly
Tell us about the role, the timing, and what your team cannot afford to lose. We are opening access to a small number of organizations ahead of launch and reply personally within two working days.