> ## Documentation Index > Fetch the complete documentation index at: https://docs.thread.app/llms.txt > Use this file to discover all available pages before exploring further. # Handover Briefs > Define the questions every sales-to-post-sales handover must answer, let AI draft the brief, and route it to the AE for review. A **Handover Brief** is the structured context document that travels with an account when it crosses from sales to your activation team: what was sold, to whom, why they bought, what was promised, and what success looks like. Thread drafts the brief with AI from the data that already exists, then routes it to the Account Executive for review — so the person who knows the deal corrects the record instead of writing it from scratch. You define what a brief must contain; Thread handles the drafting, the review loop, and where the result lives. Handover Brief templates are managed by organization admins. The finished briefs are visible to everyone who can see the account. ## Define the brief template Open **Handover Briefs** from the sidebar's Library section to see your organization's brief templates. Each template defines the sections and questions a brief answers, and you can keep more than one — for example a full enterprise brief and a lighter one for self-serve deals. The builder works in sections and blocks: * **Sections** group related content — company snapshot, stakeholders, goals, technical scope, commitments. * **Blocks** are the individual questions and fields inside a section. Add from the palette or create custom blocks with your own fields. * **AI instructions** exist at every level: a template-level prompt that guides the AI's overall drafting, plus per-section and per-block prompts for fine control (e.g. "state the 30/60/90-day milestones as measurable outcomes, not activities"). * **Output style** settings shape the drafted prose — how terse or narrative the answers read. * A **preview panel** shows the brief's shape as you build. Publish the template to make it live; you can unpublish it later without deleting anything. ### Versioning Templates are versioned. Every edit produces a new version, and each generated brief stores a snapshot of the template version it was drafted against — so changing your questions next quarter never rewrites or invalidates the briefs already delivered. Historical briefs render exactly as they were reviewed. ## How a brief gets drafted Briefs are generated by your account-intake [workflow](/workflows/overview): when a closed-won account arrives (from your CRM or a manual upload), the workflow drafts the brief against your published template. The AI drafts from what it can actually see: * **CRM context** — the deal snapshot, account fields, owner, close date, contract values, contacts, and sales notes. * **Call data** — when a call-recording source like [Gong](/integrations/gong) is connected, insights from the deal's call transcripts. * **Connected notes** — meeting and deal notes from sources like Notion and HubSpot. The draft is honest about its own limits: it carries a confidence score, cites its sources (which CRM field a contract value came from, whether it was calculated), and leaves a field blank rather than guessing when the data isn't there. Blanks are exactly what the AE review is for. ## The AE review The AE receives an email with a tokenized review link — no Thread login required. The link opens the drafted brief with the full account picture: snapshot stats, stakeholders, business context, goals, technical scope, commitments made during the sale, and the AI's notes on where each answer came from. The AE can: * **Edit any answer in place.** Edits are kept safe locally while they work, so a closed tab doesn't lose a half-finished review. * **Fill the blanks** the AI couldn't answer — the deal knowledge that only exists in the AE's head. * **Approve** to finalize the brief. Workflows can pair the brief with an owner-assignment step in the same review, so the reviewer also confirms who takes the account on your team. Review links are single-purpose and expire; if a link has expired, a fresh one can be sent. Keep the template focused on what the AI *can't* already read from your CRM. The best questions capture judgment — why they bought, what could derail this, what was promised verbally — and let the AI handle the facts. ## Where the finished brief lives Once approved, the brief is saved to the account: * **On the account page** — a **Handover Brief** tab appears on the account for everyone on your team. This is the working copy your activation team reads. * **Via a tokenized `/brief` link** — a shareable read view of the finished brief for people outside the account page, protected by an email verification gate (a one-time code, no password). Anyone on your team who opens the link while signed in is simply taken to the account's Handover Brief tab. The brief then does real work: it's part of the account context that [Motions](/motions/overview) and [guides](/guides/overview) draw on, so what the AE wrote down is what the resident agent knows. ## Related pages The routing layer that triggers brief drafting on new accounts. Manually created accounts flow through the same intake. Connect call recordings so drafts cite what was actually said. How tokenized review links work across Thread.