Use case

Project handoff

A handoff document is a snapshot of what the outgoing owner remembered on the day they wrote it. The incoming owner's first week is spent discovering everything it left out.

How do you hand off a project without writing a long document?

Collect the material that already exists — the plan, the decision emails, the status notes, the current budget — into a Brief. Brieflin extracts who is involved, what was decided, what is open and what is next. You correct it, then hand the new owner one link they can question as issues come up over their first month.

How handoffs go wrong today

  • The doc is written under deadline pressure on the last day.
  • It records conclusions but not why they were reached, so the new owner re-opens settled decisions.
  • Half the real context is in a Slack thread the new owner cannot see.
  • The outgoing owner keeps getting pinged for three months anyway.

The handoff, done as a Brief

  1. Step 1

    Dump the material

    Plan, budget, status updates, the email threads where things were agreed. Do not curate yet.

  2. Step 2

    Review the extraction

    Fix roles, confirm which decisions are current, delete anything superseded.

  3. Step 3

    Add the things only you know

    Paste a short note about the politics, the fragile dependency, the client's real priority. That is the part no document captures.

  4. Step 4

    Hand over the link

    The new owner asks their own questions on their own schedule, instead of booking time with you.

What the new owner gets

People

  • Who to go to for what
  • Who signs off
  • Who is external

Decisions

  • What was settled
  • When
  • What was rejected and why

In flight

  • Open items and owners
  • Blocked work
  • Upcoming dates

See the shape

The example Briefs show the same structure applied to different kinds of work.

Open an example Brief

What a new owner asks in week one

Test your Brief against these before you hand it over.

  • What is the single most urgent thing right now?
  • Who actually approves changes here?
  • What has already been tried and rejected?
  • What is the client or stakeholder most sensitive about?
  • What is going to break if nobody touches it?

Why the answers hold up

  • Each answer cites the source it came from, so the new owner can read the original wording.
  • Where your notes and the plan disagree, both are shown.
  • Questions the material cannot answer come back as 'unknown' — which is itself useful, because it tells the new owner what to ask you.

Handoff checklist

  • Current plan and current budget, not last quarter's.
  • The decision thread for anything contentious.
  • A pasted note on the unwritten context.
  • Named owners for every open item.
  • One question you know is unanswerable, so the gap is visible.

Common questions

What information belongs in a Brief?
Include the material that answers the questions the recipient will actually ask: who decides what, what has been agreed, what is still open, what the timeline is, and where the numbers came from. Source documents, decision emails, status notes and the current financial model matter more than polished summaries.
How is Brieflin different from a document?
A document answers the questions its author thought of. A Brief answers the questions the recipient actually has, because they can ask. The document is still useful as a source — Brieflin reads it and keeps it as evidence — but the recipient no longer has to find the one paragraph that matters to them.
How does a Brief work?
You add sources, Brieflin extracts the structure, you review and correct what it understood, then you publish one link. Recipients open the link without an account and ask questions in plain language. Each answer is generated only from your sources and cites the passage behind it. You can revoke the link at any time.

Ask Brief

The handoff keeps working because the new owner can keep asking.

How Ask Brief works

Hand over context, not homework

Build the Brief while you still remember the details.