Project hand-off brief template
By The Onbo team · Updated
Short answer
A project hand-off brief is a one-page summary that moves a new client from onboarding to delivery: the project in a sentence, goals, scope and exclusions, client inputs with dates, constraints, decision makers, open questions, links to the agreement and files, and the first milestone. Write it once, confirm it with the client and paste it into your project tool.
The moment a project moves from the person who sold it to the people who’ll deliver it is where details get lost. The designer asks a question the client answered two weeks ago. The developer doesn’t know which pages are out of scope. Someone books a review with the wrong approver. A short, consistent hand-off brief stops this by putting everything the delivery team needs on one page.
Why use a hand-off brief?
Without one, delivery teams rebuild the brief from emails, call notes and questionnaire answers, and each person ends up with a slightly different version. A brief gives the whole team the same starting point. It also protects the client from being asked the same questions twice, which is one of the quickest ways to make a new client doubt they chose well. And because it’s written once and confirmed, it becomes the reference point for scope questions later in the project.
The hand-off brief template
Copy this into a document or your project tool and fill it in once onboarding is complete:
Project: [client] - [project name]
In one sentence: [what this project is and why it exists]
Goals (in the client’s words)
- [goal 1]
- [goal 2]
Scope
| Included | Not included |
|---|---|
| [deliverable] | [exclusion] |
| [deliverable] | [exclusion] |
Client inputs
| Input | Owner | Due | Status |
|---|---|---|---|
| [e.g. page content] | [name] | [date] | [received / pending] |
Constraints: [fixed dates, budget limits, systems, legal or brand rules]
Decision makers: [who gives feedback] / [who gives final approval]
Open questions: [anything the client marked “not sure yet”, with a suggested answer]
Links: [accepted agreement] · [invoices and payment status] · [questionnaire answers] · [files folder]
First milestone: [what, and when]
How do you write it well?
Write it from the client’s answers, not from memory. Quote their goals directly; paraphrasing is where meaning drifts. Keep scope and exclusions side by side, because the exclusions are what prevent later disputes. List every client input with an owner and a date, since late inputs are the most common cause of delay. Keep the whole thing to one page. If it grows longer, link to detail rather than copying it in.
For example, a five-person digital agency might have the account manager write the brief the day onboarding completes. The project lead reads it at the internal kickoff, sends a client-friendly version for confirmation, and pastes the final version into the project tool as the first task. When the client asks for an extra page in week three, the team checks the exclusions column and quotes it as a change in one message.
What should you leave out?
Leave out anything the delivery team doesn’t need to start: the sales history, pricing negotiations, internal opinions about the client and long copies of the questionnaire answers. Link to the detail instead. A brief that’s quick to read gets read; one that tries to hold everything becomes another document people skim past.
When does the hand-off happen?
After the agreement is accepted, the deposit is paid and the client has answered your questionnaire and sent files, and before delivery starts. In an agency project kickoff workflow, it sits between the internal kickoff and the first piece of delivery work. For freelancers who are both seller and delivery, the brief is still worth writing: it’s what you confirm with the client, and it’s what you’ll check when scope questions come up.
A hand-off checklist
- Written by the onboarding owner
- Summary fits in one sentence
- Goals quoted in the client’s words
- Scope and exclusions side by side
- Every client input has an owner and a date
- Decision makers named
- Open questions listed with suggested answers
- Links to agreement, payments, answers and files
- Confirmed with the client in writing
- Added to the project tool as the first item
Our guide on how to collect and organize client requirements covers gathering the answers that feed this brief.
Where Onbo fits
When a client finishes onboarding, Onbo produces a plain Markdown hand-off brief of everything collected: the accepted agreement, payment status, every questionnaire answer and the files in your Google Drive. Paste it into your project tool or edit it into your own template, and signed webhook events can notify other tools when onboarding completes. Try it free for 30 days; see pricing.
Questions
What goes in an internal project hand-off?
A one-sentence summary, goals in the client's words, scope and exclusions, client inputs with owners and dates, constraints, decision makers, open questions, links to the agreement and files, and the first milestone.
Who should write the hand-off brief?
The person who owned onboarding, usually the project lead or account manager, before delivery starts.
Should the client see the hand-off brief?
A client version of it, yes. Confirming the summary with the client catches misunderstandings before any work is done.