BlogTemplates
Client discovery notes template
A client discovery notes template records the client's objective, current constraint and the next step both sides agreed to. It separates evidence from interpretation, marks missing information unknown and keeps suggestions apart from commitments. It is for whoever follows up after a client call while the problem is still being understood; your organisation may also require a formal record.
Short answer
- Use this for client conversations where follow-through depends on understanding the client's goal and present constraint.
- Record what the client said separately from what you think it means.
- Write one next step only when the people in the meeting agreed to it.
- Keep unknowns visible so the next conversation can resolve them.
How do I take notes on a client discovery call that keep evidence, interpretation and agreed next steps apart?
- For
- Whoever follows up after a client discovery call while the problem is still being understood
- What it does
- Records the client's objective, current constraint and one agreed discovery next step, with unknowns left visible.
- Works in
- Plain Markdown; paste into any notes or docs app
Disclosure. Candor is an app that will compete with some products named here. We describe every product, including Candor, from its own documentation, and we'll test them all with the same published method.
Use the Copy button on the blank block, or select it and copy it into your editor. For plain text, remove Markdown heading marks and bold markers; replace table rows with labelled lines. For a Word file you create, Google's desktop instructions are to open it in Drive and choose “Open with Google Docs.” [1]
Template
CLIENT DISCOVERY NOTES
**Client / organisation:** ____________________
**Meeting date and time:** ____________________
**Participants and roles:** ____________________
**Notes owner:** ____________________
Fill only from the source. Write "Unknown" for missing information and
"Not agreed" for an unaccepted action. Add a row for each separate item
in the tables; delete unused blank rows. Label any later confirmation
with its source and date instead of treating it as a meeting agreement.
## Client objective
What outcome did the client say they want? Keep their wording where useful.
## Current constraint
What does the client say is making that outcome hard today?
## Evidence and observations
| What was said or observed | Who or what is the source? | Transcript line, document or example reference | Confirmed or still open? |
|---|---|---|---|
| ____________________ | ____________________ | ____________________ | ____________________ |
## Working interpretation
What might the objective and constraint mean? Label this as your interpretation, not the client's fact.
## Discovery question still to answer
| Question | What we know so far | Evidence reference or person to ask |
|---|---|---|
| ____________________ | ____________________ | ____________________ |
## Suggestions raised, not agreed
- ____________________
## Agreed discovery next step
**Step:** ____________________
**Owner:** ____________________
**Due date (if agreed):** ____________________
**What evidence or result will this produce?** ____________________
**Agreement reference:** ____________________
## Other agreed follow-up
| Action agreed in the meeting | Owner | Due date (if agreed) | Evidence reference |
|---|---|---|---|
| ____________________ | ____________________ | ____________________ | ____________________ |
## Open point that could change the next step
What remains unknown, and why could it change the plan?
## Check-back
**Next conversation (if agreed):** ____________________
**Client confirmation needed from:** ____________________
**Checked by and date:** ____________________
Before sharing the notes:
- Check the objective and constraint against what the client said. Keep a paraphrase faithful; use quotation marks only for exact words.
- Locate the agreement for each action. If nobody accepted it, move it to suggestions (silence is not a recorded acceptance).
- Confirm names and decisions, and every owner and due date. Write “Unknown” where the source does not settle them.
- Ask the client to correct disputed entries. Date later confirmations so they remain separate from what happened in the call.
Filled example
This example is fictional, including all people and meeting details. Its statements and numbers illustrate the fields; the “checked by” entry is fictional too.
CLIENT DISCOVERY NOTES
Client / organisation: Northline Cold Storage (fictional)
Meeting date and time: 21 October 2026, 10:00–10:40
Participants and roles: Leah Ortiz, operations lead; Maya Chen, account lead; Arun Patel, implementation consultant
Notes owner: Maya Chen
Client objective
Leah wants dispatch staff to see which orders need a temperature review before a truck leaves.
Current constraint
Leah says staff check a shared inbox and a spreadsheet, then ask a supervisor when the order status looks old.
Evidence and observations
| What was said or observed | Who or what is the source? | Transcript line, document or example reference | Confirmed or still open? |
|---|---|---|---|
| Leah says delays usually become apparent when the driver is ready. | Leah Ortiz, meeting statement | Recap, 21 Oct, 10:12 | Client report; timing not measured |
| Three handoffs were described for a delayed order. | Leah Ortiz, walkthrough | Notes from 21 Oct, 10:19 | Process description; sample size unknown |
Working interpretation
The handoff may be the main source of delay. This is a hypothesis; the team has not checked order records.
Discovery question still to answer
| Question | What we know so far | Evidence reference or person to ask |
|---|---|---|
| How often does a temperature review delay dispatch? | Leah does not have a count in the meeting. | Ask Leah for a recent anonymised sample; 21 Oct, 10:26 |
Suggestions raised, not agreed
- Maya suggested adding a status flag. Leah did not agree to a design choice.
Agreed discovery next step
Step: Leah will send an anonymised list of ten recent delayed orders with timestamps, if available and permission to share is confirmed.
Owner: Leah Ortiz
Due date (if agreed): 28 October 2026
What evidence or result will this produce? A timeline for each supplied order, showing recorded waits and gaps. A sample of delayed orders cannot establish how often delays occur across all orders.
Agreement reference: Recap, 21 Oct, 10:31; conditional on permission to share the sample
Other agreed follow-up
| Action agreed in the meeting | Owner | Due date (if agreed) | Evidence reference |
|---|---|---|---|
| Maya will review the sample and bring back any gaps in the timeline. | Maya Chen | 30 October 2026 | Meeting notes, 21 Oct, 10:34 |
Open point that could change the next step
The timestamps may be incomplete, and permission to share the sample is not confirmed. Maya proposes discussing a smaller sample if needed; that fallback has not been agreed. The frequency question needs complete counts of delayed orders and total orders for the same defined period.
Check-back
Next conversation (if agreed): 2 November 2026
Client confirmation needed from: Leah Ortiz, on whether the sample can be shared in anonymised form
Checked by and date: Maya Chen, 21 October 2026
The status flag stays in suggestions; moving it into an action list could imply Leah approved it. The delayed-order sample can help locate waits, but cannot answer the frequency question by itself.
When to use this
Use these notes for a discovery call or process walkthrough where someone must investigate before recommending work. If the meeting is chiefly about purchase approval, add the buying process and who can approve the purchase; this template does not qualify a sales opportunity by itself.
Use a different record when your organisation needs formal minutes or a detailed transcript. The minutes vs. notes hub explains the choice. This layout is optional; your organisation's record-keeping rules take priority.
What to customise
Use your team's role names and date format. Add a time zone for cross-border calls or a CRM record link. Delete unused sections, including “Other agreed follow-up” when there is only one commitment. Keep the objective and constraint, plus evidence for any agreed step.
Field-by-field guidance
| Field | What to enter | Where to get it | Common mistake |
|---|---|---|---|
| Client / organisation | Client record name | Calendar or client record | Sending unnecessary identifiers to AI |
| Meeting date and time | When the call happened | Calendar, checked against notes | Using the file's edit date |
| Participants and roles | Names and confirmed roles | Attendee list; ask if unsure | Guessing a job title |
| Notes owner | Person checking the note | Team agreement | Leaving ownership implied |
| Client objective | Outcome the client wants | Client statement | Turning a wish into a commitment |
| Current constraint | Client's stated obstacle | Client account or example | Substituting your diagnosis |
| Evidence and observations | Statement, source, locator and confirmation status | Notes or authorised transcript | Calling an interpretation measured fact |
| Working interpretation | Your hypothesis, labelled | Analysis linked to evidence | Removing the uncertainty |
| Discovery question still to answer | Missing fact that changes the recommendation | Unanswered question | Guessing the answer |
| Suggestions raised, not agreed | Ideas without acceptance | Notes or transcript | Promoting suggestions to actions |
| Agreed discovery next step | Accepted learning action | Explicit agreement | Adding unaccepted work |
| Owner and due date | Agreed person and date | Agreement; ask if unclear | Assigning either by inference |
| What evidence or result will this produce? | Expected evidence and its limits | Proposed method or sample | Treating sampled failures as a failure rate |
| Agreement reference | Acceptance locator and conditions | Recap, transcript or dated confirmation | Dropping a condition |
| Other agreed follow-up | Additional accepted actions | Notes or transcript | Turning topics into tasks |
| Open point | Unknown that could change the step | Unresolved question | Hiding uncertainty |
| Next conversation | Agreed date, otherwise “Not agreed” | Agreement or confirmed invitation | Treating a proposal as booked |
| Client confirmation needed from | Person who can resolve the uncertainty | Conversation or correspondence | Treating a review request as approval |
| Checked by and date | Actual reviewer and review date | Completed human review | Filling it before review |
Voice and AI workflow
After the call, dictate a recap and label it with the date. Number its entries so each claim has a reference. A recap is like a delivery receipt: it can document what you remember receiving, but it cannot prove that everything expected arrived. Keep missing details visible. An authorised transcript can provide another source; check disputed wording with a participant.
Use only material your organisation permits you to send to the chosen AI service. Remove confidential or identifying details before submitting it (removing a name does not establish permission to share the rest). Paste the blank template and that material with this prompt:
Produce client discovery notes in the supplied template's field order, using only the supplied recap or authorised transcript. Before submitting material, the reader must remove confidential or identifying data and confirm permission to use the chosen service.
Use these fields: Client / organisation; Meeting date and time; Participants and roles; Notes owner; Client objective; Current constraint; Evidence and observations; Working interpretation; Discovery question still to answer; Suggestions raised, not agreed; Agreed discovery next step (Step, Owner, Due date if agreed, What evidence or result will this produce?, Agreement reference); Other agreed follow-up; Open point that could change the next step; Check-back (Next conversation if agreed, Client confirmation needed from, Checked by and date).
Preserve supplied source references for statements and actions, including any conditions on agreement. Do not invent locators. Label client reports separately from measured observations and your working interpretation. Put suggestions in their own field. Preserve missing facts as "Unknown" and unaccepted actions as "Not agreed"; never infer a decision, owner or due date. State what the discovery step cannot establish when the source provides a limit. Leave Checked by and date for the human reviewer. A person must confirm every name, decision and due date, and each action owner, against the source before sharing the notes.
What this page can't tell you
This template cannot establish whether the client's account is complete or which formal records your organisation requires. Ask the client to confirm unclear facts, and check whether the proposed evidence will answer the discovery question.
Questions
Do you actually trust AI to take your meeting notes?
Only after checking them against the source. Check the client's objective and constraint against what the client said, and find the agreement behind each action before you share the notes. Ask the client to correct disputed entries, and date later confirmations separately.
Has anyone found an AI tool that pulls action items from meeting notes without adding tasks nobody agreed to?
This template handles that by recording a next step only when the people in the meeting agreed to it. If nobody accepted an action, move it to suggestions, because silence is not a recorded acceptance. Write 'Unknown' where the source doesn't settle an owner or due date.
Anyone else notice the AI meeting notes never make it into the CRM?
This template doesn't connect to a CRM. It records each agreed next step with an owner, due date, expected result and agreement reference, plus a check-back date. Those fields give whoever follows up a record to work from.
About this page
Candor is being built as personal voice intelligence for everyone. You can join the Candor waitlist at candor.inc. Candor's own documentation is at candor.inc/docs.
Candor's docs on this page's topic: What the summary includes.
Last checked: 4 November 2026. To report an error, write to support@candor.inc.
Sources
- Google Docs Editors Help, “Switch from Microsoft Word to Google Docs” — https://support.google.com/docs/answer/9310150?hl=en — checked 2026-11-04