How to Write a Handover Document in English

A handover document that’s just a bullet list of file paths leaves the next person guessing at everything that actually matters — why decisions were made, what’s still broken, who to ask. This guide covers the structure and phrasing for a handover document someone can actually act on without you in the room.

Key Vocabulary

Current state — a factual, as-of-today summary of what’s working, what’s in progress, and what’s known to be broken, distinct from how things were originally planned. “Current state: the migration is about 80% complete. The read path is fully cut over; the write path is still dual-writing to both databases pending one more validation pass.”

Open item — a specific, unresolved piece of work or decision that the next owner needs to pick up, stated with enough context that they don’t need to reconstruct the history themselves. “Open item: we still need to decide whether the fallback behavior on timeout is retry-once or fail-fast. I lean towards fail-fast, but hadn’t gotten sign-off before this handover.”

Tribal knowledge — undocumented context that exists only in someone’s head, the specific thing a handover document exists to capture and transfer before it’s lost. “The reason this service polls instead of using a webhook is tribal knowledge — the original webhook implementation had a subtle bug we never fully diagnosed, so we switched to polling as a workaround. That context isn’t written down anywhere else.”

Point of contact — a named person (not just a team name) who can answer specific questions about a particular area, along with what kind of question they’re best positioned to answer. “Point of contact for the billing integration specifically is Priya — she built the original Stripe webhook handling and knows the edge cases better than anyone else on the team.”

Common Phrases

• “Current state as of today: …”
• “Open item that still needs a decision: …”
• “This next part is tribal knowledge that isn’t written down anywhere else, so I want to make sure it’s captured here.”
• “Point of contact for this specific area is X, not the team’s general channel.”
• “If you get stuck on this, the first thing to check is usually X, based on past experience.”

Example Sentences

Opening a handover document: “This document hands over ownership of the notifications service. Current state: fully live in production, stable, but with two known open items below that I didn’t have time to resolve before this transition.”

Documenting an open item with context: “Open item: the retry logic currently caps at three attempts with no backoff, which occasionally causes a thundering-herd effect during outages. I’d recommend adding exponential backoff before this becomes a bigger problem, but hadn’t prioritized it yet.”

Capturing tribal knowledge explicitly: “One thing that isn’t written down anywhere else: this cron job needs to run before the nightly batch job, not after, even though the dependency isn’t enforced in code. Running it in the wrong order silently produces incorrect reports.”

Professional Tips

• Lead with current state, stated factually and as of today — don’t describe how the system was originally designed to work if that’s diverged from how it actually behaves now.
• List every open item individually with enough context to act on, not just a name — “fix the retry logic” is far less useful than a sentence explaining what’s wrong with it and why it matters.
• Deliberately hunt for tribal knowledge to write down — ask yourself “what do I know about this that isn’t in any doc or comment?” and include all of it, since that’s the exact information a handover exists to preserve.
• Name specific points of contact per area, not just team names — a handover reader with a narrow question needs to know exactly who to ask, not who to broadcast a question to.

Practice Exercise

1. Write a “current state” summary for a hypothetical project you’re handing over.
2. Write an open item entry with enough context for someone unfamiliar with the project to act on it.
3. Write a sentence capturing a piece of tribal knowledge that isn’t documented anywhere else.