Free Engineering Handoff Template

An engineering handoff is the document one engineer hands to the next when work changes hands — at end of day across time zones, before vacation, when a project transfers owners, or when on-call rotates. Most handoffs in practice are a Slack message, a "see thread above" link, and a hope. This template replaces the hope with structure.

The version below is the result of watching teams iterate on the format for a long time. The sections are not arbitrary; each one corresponds to a question the next engineer asks within their first ten minutes of picking the work up. If a section is missing, the next engineer either guesses or interrupts the previous engineer. Both are expensive.

When to use it

• End of day on any work that another engineer will continue tomorrow.
• Before a vacation, sabbatical, or extended off-call window.
• When ownership of a feature or service formally transfers.
• When on-call rotates and an open incident is still warm.
• Any time you would otherwise write "@someone, can you pick this up?" with no other context.

The template structure

This is the structure of the template. Copy it into a Notion page, a Linear doc, or a markdown file in your repo — it works in any of them.

ENGINEERING HANDOFF — [short title]
From: [name]   To: [name or "whoever is on tomorrow"]   Date: [date]

WHAT THIS WORK IS
  One sentence. The user-facing or system-facing outcome.
  Link: [PR / issue / design doc]

CURRENT STATE
  [ ] In progress — branch: [branch name]
  [ ] Blocked — see Blockers below
  [ ] Ready for review — PR: [link]
  [ ] Merged, awaiting deploy
  Last meaningful commit: [sha / message]

WHAT I JUST DID
  - bullet
  - bullet
  - bullet

WHAT I WAS ABOUT TO DO
  Next concrete step (not a goal — a step). E.g.:
  "Run the migration locally, confirm row count, then push."

DECISIONS MADE
  - Decision: [...]   Why: [...]   Reversible? [yes/no]
  - Decision: [...]   Why: [...]   Reversible? [yes/no]

OPEN QUESTIONS
  - Question:  [...]   Asked of: [name or "nobody yet"]
  - Question:  [...]   Asked of: [name or "nobody yet"]

BLOCKERS
  - Blocker: [...]   Owner: [name]   Since: [date]

HOW TO PICK IT UP
  1. [step]
  2. [step]
  3. [step]
  Local setup gotchas: [...]
  Tests to run first:   [...]

CONTACT
  If urgent and you cannot proceed: [name / channel]
  Otherwise: leave a comment on the PR.

How to use it well

• Write it as the last act of the day, not the first act of the next. A handoff written in the morning by the receiving engineer is not a handoff, it is reconstruction. The whole point is to capture the working state while it is still in the writer's head.
• "What I was about to do" must be a concrete next step. "Continue the migration" is not a step. "Run npm run migrate:dev, confirm row count is 14302, then push to main" is.
• List decisions with their reversibility. The next engineer needs to know which choices are load-bearing and which are placeholders. Reversibility is the cheap proxy.
• Open questions go in the handoff even if you have not asked them yet. Asked-of-nobody is a valid value. The point is that the question exists; the next engineer can ask it.
• One sentence on "what this work is" — no more. Long context belongs in the linked design doc. The handoff is for resuming, not for explaining.

What to skip

Skip the daily standup framing. The classic three questions (what I did, what I'll do, blockers) are written for a manager's audience. A handoff is written for the next engineer's audience. The two documents look similar and serve completely different purposes; conflating them is why handoffs are bad on teams that use Geekbot.

Skip the urge to include a full project status. The handoff is about the slice of work changing hands, not the project. Status reports are a different document and they have their own audience.

Frequently asked questions

Is this template free?

Yes. Copy the ASCII block above, paste it into wherever your team writes — Notion, Linear, a markdown file in the repo, the description of a draft PR. It works in any of them.

Can I edit it?

Yes, and you should. Teams that use this template heavily often drop the Decisions section (because they log decisions elsewhere) or add a Deploy state row (because their pipeline takes long enough that 'awaiting deploy' is a real status). Adapt to your reality.

Do I need to give my email?

Not for the template itself. The structure on this page is the whole thing. The download is a polished Notion version with a few extra examples; it is gated only because we use it to keep in touch about the rest of the engineering pack.