Prepare for your next client call with a one-page brief
Gather what changed, check outstanding commitments, and arrive with the decisions you need. Includes a worked example and a copyable template.
On this page
Marlow Studio, its people and the records in the worked example are fictional.
Your next client call starts in twenty minutes. Last week’s notes say the pilot is Friday. A newer email asks for two extra fields. Somewhere in the thread is a file you promised to send.
You open the notes, then the email, then the folder. The calendar reminder joins in, apparently concerned you haven’t opened enough things.
A short client meeting brief gives you somewhere to put the pieces that affect today’s conversation. Start with the outcome you need from the call. Bring forward the changes and unfinished commitments that could affect it, with links to the records you’ll want to check.
Keep it to a page you can scan while someone is talking. Leave the supporting documents a click away.
Start with the decision the call needs
Write one sentence explaining what you want to resolve. “Weekly catch-up” gives you little help deciding what belongs on the page. “Agree what can go into Friday’s pilot and what must wait” gives the preparation a direction.
Atlassian’s page-led meeting guidance recommends putting the purpose, intended outcome and key discussion points near the top of a written meeting page. For a consultant’s private prep brief, use that structure to identify the questions you need answered.
Then check who can answer them. A conversation about scope may need the person who approves the work. If they can’t attend, make the goal a recommendation for their review. Leave the decision open until they respond.
Pull forward what changed
Begin with the last agreed position and the commitments still open. Read the relevant messages and work records since that point. An older unresolved dependency still belongs on the page even if nobody mentioned it this week.
For each item, keep the date and a source link. Distinguish a proposed change from an accepted one. If two records disagree, preserve both long enough to resolve the conflict.
Include your own unfinished work. A brief that carefully tracks everything the client owes while overlooking your late deliverable will make for an awkward opening.
Keep observations precise. “I couldn’t find the sample in the shared folder” leaves room to discover it arrived by email. “The client hasn’t sent it” assumes you’ve checked every place it could be.
A worked client meeting brief
Imagine you’re Nora, an operations consultant helping Marlow Studio improve how it takes on new projects. Your next call is November 17.
You have four relevant records:
| Record | What it establishes |
|---|---|
| November 10 call notes | Maya approved a five-project intake pilot for November 20, subject to receiving sample data. Eli agreed to send the sample by November 12. Nora agreed to send a field map by November 13. |
| November 13 email from Maya | She asks whether budget and lead source can be added before the pilot. Nora hasn’t agreed to the extra work. |
| November 16 sent email | Nora sent the original field map, three days after the agreed date. |
| November 17 folder check | Nora couldn’t find the sample in the agreed shared folder. Delivery through another channel hasn’t been checked. |
The original Friday date stays visible without becoming a fresh promise. The extra fields remain a request. You also have a reminder to own the late field map before asking about the missing sample.
In your actual brief, turn the record names into links. Keep any private assessments on your own copy; review the contents before sharing a version with the client.
Use AI to assemble the first pass
If you use an assistant, provide the relevant client records through a tool and account approved for that information. Keep each record’s date and source label attached. Ask it to fill the brief from those materials and leave unsupported fields marked “not confirmed.”
For this example, a useful instruction would be:
Check each date against the original record, including who agreed to what. In this case, “Maya approved the extra fields” would be wrong. So would a confident statement that the expanded pilot is ready for Friday. A source label helps you find the record to check; read the passage it points to.
Copy this client meeting prep template
Use it in the document where you already keep client notes. Delete empty sections when they’re irrelevant and keep the full history in the linked records.
Before joining, check for any new message that changes the brief. After the call, fill in what was actually agreed while the details are fresh. If Maya needs another day to decide, leave the pilot date unresolved and record when you’ll ask again.
Source reviewed
Reviewed November 17, 2026. The consultant brief, worked example and AI instructions are editorial recommendations, not a reported customer result or a measured time saving.
- Atlassian Team Playbook, Page-Led Meetings: supports placing written context, meeting purpose, desired outcomes and key discussion points near the top.
Before the call
Keep the one-page brief open beside the source records you may need. Use it to guide the discussion, not to turn an unresolved request into a decision.
After the call, record what was actually agreed, who owns the next action and the date attached to it.
Product screens show a sample workspace. Client names in examples are fictional.