Voice Note Templates

50 free, copy-paste templates for spoken notes. Each one tells you exactly what to say into your phone or watch in 30–60 seconds — and gives you the AI prompt that turns the transcript into meeting action items, a CRM entry, a session recap, study notes or a first draft.

View on GitHub (MIT)   Try them with a free on-device app

Why templates at all?

Most people abandon voice notes for the same reason: the transcript comes back as one unpunctuated paragraph that is slower to read than the thing would have been to type. That is not a transcription-quality problem. It is a structure problem — nobody said the fields out loud, so nothing downstream can find them.

A template fixes that in the cheapest possible place: the 45 seconds you were already spending. Say the same six things in the same order every time and the transcript becomes parseable by a summariser, by search, and by you in three weeks.

The three-step method behind every template below: (1) state who / what / when in the first sentence, (2) speak the template body, (3) run the matching prompt on the transcript. Step 1 is the one everyone skips and the one that matters most.

The ten categories

  1. Meetings & standups
  2. Sales calls, showings & field visits
  3. Client sessions & private practice
  4. Legal matter recaps
  5. Lectures, seminars & study
  6. Writing & first drafts
  7. Journaling & brain dumps
  8. Travel & multilingual capture
  9. Wrist & hands-free capture
  10. Leaving a subscription transcription tool

1. Meetings & standups

The goal of a post-meeting memo is not a record of the meeting. It is the list of things that changed. Say the decisions and the owners; skip the discussion.

1.1 — Post-meeting decision log

“Meeting recap. [Project], [date], attendees [names]. Three decisions were made. One: [decision], owner [name], by [date]. Two: [decision], owner, date. Three: [decision], owner, date. One thing is still open: [question], and [name] owes us an answer by [date].”

Turn this transcript into two lists: DECISIONS (one line each, no discussion) and OPEN QUESTIONS (question, who owes the answer, by when). Do not invent owners or dates. If one is missing, write UNASSIGNED.

1.2 — Action items only

“Action items from [meeting]. I owe [name] the [deliverable] by [day]. [Name] owes me [deliverable] by [day]. Nobody owns [item] yet — flag it.”

Extract every action item as: owner, deliverable, due date, blocked-by. Output as a checklist. Mark items with no owner as UNASSIGNED at the top of the list.

1.3 — Standup, spoken on the walk in

“Standup for [date]. Yesterday I finished [x] and got stuck on [y]. Today I am doing [z]. My blocker is [blocker] and the person who can unblock it is [name].”

Format as three bullets: Yesterday, Today, Blockers. Under Blockers, name the person who can unblock each item. Keep it under 60 words.

1.4 — The meeting that should have been an email

“Summary for people who were not there. The one thing you need to know is [x]. It affects you if [condition]. If it affects you, do [action] by [date]. Otherwise ignore this.”

Rewrite as a short internal update email. Lead with the one thing that matters. Second paragraph: who is affected and what they must do. No greeting fluff, no recap of the agenda.

1.5 — Interview or 1:1 debrief

“Debrief, [name], [role], [date]. Strongest signal: [evidence]. Weakest signal: [evidence]. One thing I still do not know: [gap]. My recommendation right now is [advance / hold / decline] and my confidence is [low / medium / high].”

Structure as: Signal for, Signal against, Open gap, Recommendation with confidence level. Quote the evidence given, do not add reasoning of your own.

Longer write-up of this workflow: turning meeting voice notes into action items.

2. Sales calls, showings & field visits

The recap you record in the car park is worth more than the one you type at 7pm, because at 7pm you have lost the objection wording. Record before you start the engine.

2.1 — Car-park recap after a client visit

“Visit recap. [Company], [contact name and role], [date]. What they are trying to fix: [problem in their words]. Budget signal: [what they said about money]. Timeline signal: [when]. Objection raised: [objection, quoted]. Next step I committed to: [action] by [date].”

Convert to a CRM entry with fields: Account, Contact, Pain (their words), Budget signal, Timeline, Objection (verbatim), Next step, Due date. Leave a field blank rather than guessing.

2.2 — Property showing recap

“Showing recap. [Address], [date], buyers [names]. They reacted well to [feature] and badly to [feature]. Their real constraint sounded like [constraint]. Competing property they mentioned: [property]. My next action: [action] by [date].”

Summarise as: Positive reactions, Negative reactions, Stated constraint, Competing options mentioned, Next action with date. Then suggest two follow-up properties criteria based only on what was said.

2.3 — Objection capture

“Objection log. [Company]. The objection, in their exact words, was: [quote]. The context was [when in the call it came up]. What I answered: [answer]. Whether it landed: [yes / no / unclear].”

Add this to an objection library entry: Objection (verbatim), Context, Response given, Outcome. Then list two alternative responses, each under 30 words.

2.4 — Pipeline hygiene sweep

“Pipeline check, [date]. [Account] — last contact [date], real next step [step], my honest confidence [percent]. [Account] — same three fields. [Account] — same three fields. The one I am kidding myself about is [account].”

Output a table: Account, Days since last contact, Concrete next step, Stated confidence. Add a final row listing the account the speaker flagged as self-deception, with the reason if given.

2.5 — Handover to a colleague

“Handover, [account], to [colleague]. Relationship status: [status]. Who actually decides: [name and role]. What you must not say: [landmine]. What is promised and when: [promise]. First thing you should do: [action].”

Write a handover note for the incoming rep: Status, Decision maker, Sensitivities to avoid, Outstanding promises with dates, Recommended first action. Flag anything that is a commitment the company must honour.

Longer write-up: voice notes for field sales and realtors.

3. Client sessions & private practice

These templates are recorded after the client has left — they are your recap, not a recording of the session, so no consent question arises. Check your own professional record-keeping obligations before adopting any workflow.

3.1 — Session recap, structured

“Session recap, client [initials or code], [date], session number [n]. Presenting focus today: [topic]. What changed since last time: [change]. What I observed: [observation]. What we agreed for next time: [agreement]. My own note to self: [note].”

Structure as: Focus, Change since last session, Observations, Agreed next steps, Clinician note. Keep the client identifier exactly as spoken. Do not add interpretation that was not stated.

3.2 — Between-session observation

“Observation, client [code], [date]. I noticed [pattern] across the last [n] sessions. The first time I saw it was [when]. What I want to test next session is [approach].”

Write as a single dated progress note: Pattern observed, Evidence across sessions, Planned approach. No diagnosis language unless it was spoken.

3.3 — Referral or coordination note

“Coordination note. Client [code]. I want to refer to [discipline] because [reason]. Relevant history in one sentence: [history]. What I need back from them: [question].”

Draft a short professional referral summary: Reason for referral, Relevant background (one sentence), Specific question being asked. Neutral clinical tone, no speculation.

3.4 — End-of-day caseload sweep

“End of day, [date]. [n] sessions. The one I am still thinking about is [code], because [reason]. Admin I owe: [items]. Supervision topic to raise: [topic].”

Output three lists: Cases needing further thought (with the stated reason), Admin owed, Supervision agenda items. Nothing else.

3.5 — Cancellation and no-show log

“Attendance note. Client [code], [date], [cancelled / no-show], notice given [amount]. Reason stated: [reason]. Pattern so far: [nth occurrence]. Action: [rebook / discuss / policy].”

Log as: Client code, Date, Type, Notice, Stated reason, Occurrence count, Action taken. Flag if the occurrence count is three or higher.

Longer write-up: voice notes for therapists and clinicians.

5. Lectures, seminars & study

Recording the whole lecture creates 50 minutes you will never replay. A 60-second recap recorded while walking out is the artefact you will actually revise from.

5.1 — Walking-out lecture recap

“Lecture recap. [Course], [topic], [date]. The single claim was [claim]. The evidence given was [evidence]. The thing I did not understand is [gap]. What is examinable here is probably [prediction].”

Format as: Central claim, Supporting evidence, Comprehension gap, Likely exam angle. Then generate three recall questions with answers, based only on the transcript.

5.2 — Reading note

“Reading note. [Source], [author], pages [range]. The argument is [argument]. What it disagrees with is [counter-position]. The quote I want is on page [n]: [quote]. How it connects to [other source]: [connection].”

Output a literature note: Source, Argument, Position it opposes, Key quote with page number, Connection to other reading. Preserve the page numbers exactly.

5.3 — Flashcard dump

“Flashcards for [topic]. Term [term], definition [definition]. Term, definition. Term, definition. The one I keep getting wrong is [term].”

Output as a two-column CSV: front, back. Add a third column priority, set to high for the term the speaker said they keep getting wrong, normal for the rest.

5.4 — Pre-exam confidence sweep

“Exam sweep, [subject], [days] days out. Confident on [topics]. Shaky on [topics]. No idea on [topics]. Time available: [hours].”

Build a revision plan allocating the stated hours across the three confidence bands, weighted towards no-idea then shaky. Show the allocation as a table with hours per topic.

5.5 — Seminar contribution prep

“Seminar prep, [topic]. The point I want to make is [point]. The evidence I will cite is [evidence]. The obvious counter is [counter] and my response is [response].”

Write this as speaking notes: one-sentence point, one-sentence evidence, anticipated counter, prepared response. Under 100 words total so it can be read at a glance.

Longer write-up: voice to text for lectures and study notes.

6. Writing & first drafts

Speaking is roughly three times faster than typing, and a spoken draft carries your actual cadence. The trick is to dictate the argument, not the prose.

6.1 — Spoken outline before writing

“Outline for [piece]. The reader is [audience]. After reading it they should [change]. My argument in one sentence: [thesis]. The three moves are: [move one], [move two], [move three]. The thing I must not forget: [detail].”

Turn this into a working outline: audience, desired change, thesis, three sections with a one-line purpose each, and a note list. Do not write any prose yet.

6.2 — Talk-it-out first draft

“First draft, [piece]. Opening: [say the opening as you would say it to a friend]. Middle: [the argument, out loud, unpolished]. Ending: [the point you want to land].”

Clean this transcript into a readable first draft. Keep the speaker's word choice and rhythm. Remove filler words, false starts and repetitions only. Do not add ideas, examples or transitions that were not spoken.

6.3 — Email you are dreading

“Email to [recipient]. What I actually want is [want]. What I am worried about is [worry]. What I am willing to concede is [concession]. Tone should be [tone].”

Draft the email in the stated tone. Lead with the ask, not the apology. Include the concession only if it strengthens the ask. Under 150 words.

6.4 — Idea capture with enough context to survive

“Idea, [date]. The idea is [idea]. It came from [trigger]. Who it would be for: [audience]. The first thing I would have to test is [test]. The reason it might be nothing: [risk].”

Store as: Idea, Trigger, Audience, First test, Stated risk. Then write one sentence I could read in six months that would let me reconstruct why this seemed interesting.

6.5 — Revision pass, spoken

“Revision notes for [piece]. What works: [section]. What does not: [section] because [reason]. What is missing: [gap]. What I should cut even though I like it: [darling].”

Produce a revision checklist ordered by impact: cuts first, then fixes, then additions. Include the stated reason next to each item.

Longer write-up: from voice memo to first draft.

7. Journaling & brain dumps

Written journaling fails on the days it would help most, because on those days you have no patience for a blank page. Speaking has almost no activation cost.

7.1 — Ninety-second brain dump

“Brain dump, [date]. Everything currently in my head: [say it unfiltered until you run out]. The one that is actually urgent is [item]. The one that is loud but not important is [item].”

Split into three lists: Actionable (with a suggested next physical action each), Waiting on someone else, Noise. Put the item the speaker called urgent at the top of Actionable.

7.2 — Evening review

“Evening review, [date]. What actually happened: [events]. What I did well: [thing]. What I would redo: [thing]. Energy level and why: [level, cause]. Tomorrow's single most important thing: [task].”

Write as a dated journal entry in first person, keeping the speaker's phrasing. End with a line: TOMORROW — followed by the single most important task.

7.3 — Decision journal

“Decision, [date]. I decided [decision]. The alternatives were [options]. I chose this because [reasoning]. What I expect to happen: [prediction]. When I will check: [date]. Confidence: [percent].”

Record as a decision-journal entry with fields: Decision, Alternatives, Reasoning, Prediction, Review date, Confidence. Do not evaluate the decision.

7.4 — Emotional first aid

“Right now I feel [feeling]. It started when [trigger]. The story I am telling myself is [story]. What is actually verifiable is [facts]. The smallest useful next action is [action].”

Reflect back four sections: Feeling, Trigger, Interpretation, Verifiable facts, Smallest next action. Do not offer advice, reassurance or diagnosis. Use the speaker's own words wherever possible.

7.5 — Weekly pattern check

“Week of [date]. The pattern I noticed in myself was [pattern]. It showed up on [days]. What preceded it each time: [antecedent]. One experiment for next week: [experiment].”

Summarise as: Pattern, Occurrences, Common antecedent, Experiment. Then propose one measurable success criterion for the experiment.

Longer write-up: voice journaling and brain dump workflows.

8. Travel & multilingual capture

Two constraints stack when travelling: no reliable connection, and thoughts arriving in whichever language you are currently living in. Templates that name the language up front save the transcript.

8.1 — Language-tagged capture

“Note in [language], [date], [place]. [Then say the note entirely in that language, without switching.]”

Transcribe in the original language. Then provide an English summary underneath, marked SUMMARY. Never mix the two in one paragraph.

8.2 — Field observation abroad

“Field note. [Place], [date], [time]. What I am looking at: [description]. What surprised me: [surprise]. What I want to look up later: [question]. Photo reference: [filename or count].”

Format as a dated field note: Location, Observation, Surprise, Follow-up question, Media reference. Keep place names spelled as spoken.

8.3 — Expense capture on the move

“Expense. [Amount] [currency], [date], [merchant], [category]. Business purpose: [purpose]. Receipt: [have it / lost it]. Project code: [code].”

Output one expense row: Date, Amount, Currency, Merchant, Category, Business purpose, Receipt status, Project code. Flag rows where receipt status is lost.

8.4 — Interpreter-free meeting recap

“Meeting recap in [language]. [Name], [company], [date]. Agreed: [points]. Unclear because of language: [points]. Follow up in writing: [items].”

Produce two sections: CONFIRMED (things stated as agreed) and TO CONFIRM IN WRITING (anything the speaker flagged as unclear). Translate to English but keep any quoted phrases in the original.

8.5 — Airplane-mode idea log

“Offline note, [date], flight [number or route]. Idea: [idea]. Why now: [trigger]. What I need to check when I land: [checks].”

Store as: Idea, Trigger, To verify on landing. Output the verification items as a checklist so they can be worked through in order.

Longer write-up: voice to text in any language, offline.

9. Wrist & hands-free capture

The value of wrist capture is not convenience, it is the elimination of the phone. If getting the idea down requires unlocking a device and choosing an app, the idea is gone. Wrist templates must therefore be short enough to say in one breath.

9.1 — One-breath capture

“[Noun phrase for the idea]. Because [one reason]. Next: [one action].”

Expand into a single note: Idea, Rationale, Next action. Do not pad. If the transcript is ambiguous, list the ambiguity instead of resolving it.

9.2 — Mid-walk task capture

“Task. [Task]. For [project]. By [day]. Blocked by [nothing / thing].”

Output one task line: description, project, due date, blocker. If blocker is nothing, omit the field entirely.

9.3 — Driving recap (stationary, engine off)

“Recap. [Who I just met]. [The one thing that changed]. [The one thing I owe them]. [When].”

Four fields only: Person, What changed, Commitment, Deadline. This is a car-park note, keep the output equally short.

9.4 — Workout or run note

“Session [date]. Did [work]. Felt [rating out of ten]. Niggle: [body part or none]. Next session should be [adjustment].”

Log as: Date, Work completed, Perceived effort, Niggle, Adjustment for next session. Track niggles as a separate running list across entries.

9.5 — Shopping and errands

“Errands. Buy [items]. From [shop]. Before [day], because [reason].”

Output a grouped shopping list by shop, with a deadline line at the top. Merge duplicate items.

Longer write-up: the Apple Watch voice memo workflow.

10. Leaving a subscription transcription tool

Most people who cancel a transcription subscription do not miss the transcription — they miss the templates the tool had baked in. These five replace the ones that actually got used.

10.1 — Migration inventory

“Migration note. I am leaving [tool]. What I used it for, honestly: [uses]. What I never used: [features]. What I must not lose: [data]. Export deadline: [date].”

Produce: Actually-used features, Never-used features, Data that must be exported, Export deadline. Then list what a replacement must do, based only on the actually-used list.

10.2 — What it was really costing

“Cost check. [Tool], [amount] per [month or year], [months] used. Times I opened it last month: [number]. Cost per actual use: [say the division out loud or leave it].”

Compute annualised cost, cost per opening, and cost per opening projected over twelve months. Show the arithmetic. Do not recommend anything.

10.3 — Privacy requirements, written down once

“Requirements. Audio must [leave / not leave] the device. Transcripts stored [where]. Retention [duration]. Sharing with third parties: [acceptable / not]. Offline capability: [required / nice to have].”

Turn into a requirements checklist with must-have and nice-to-have columns. Keep the wording literal — these are procurement criteria, not a legal or compliance assessment.

10.4 — Trial evaluation, spoken

“Trial day [n] of [tool]. What worked: [thing]. What annoyed me: [thing]. Did it survive my worst case, which is [worst case]: [yes / no]. Would I pay: [yes / no] and why.”

Log as a dated trial entry: Worked, Annoyed, Worst-case result, Willingness to pay with reason. Across multiple entries, surface any annoyance mentioned more than once.

10.5 — Team rollout note

“Rollout. Replacing [tool] with [tool] for [team]. Who is affected: [names or roles]. What breaks on day one: [things]. Training needed: [amount]. Rollback plan: [plan].”

Write a short rollout plan: Scope, Affected people, Day-one breakage, Training, Rollback trigger and plan. One page maximum.

Longer write-ups: subscription-free alternatives to cloud transcription and free offline voice to text on iPhone and Mac.

Choosing a tool to record these with

Any dictation app works — that is the point of keeping the templates as plain text. The one thing worth deciding deliberately is where the audio goes, because it is the only property you cannot change later.

PropertyCloud transcription servicesOn-device transcription
Works in airplane modeNoYes
Audio uploaded to a third partyYes, by designNo — processing happens locally
Ongoing costUsually a subscriptionDepends on the app
Minutes capCommon on free tiersBounded by device, not by plan

“On-device” here is a technical statement about where processing runs. It is not a legal or compliance claim, and nothing in this pack should be read as one.

The app these templates were written alongside is VoxFlow — free, no account, no cloud, runs the speech model on the device across iPhone, Mac and Apple Watch, 99 languages, works in airplane mode. You do not need it to use anything on this page.

Get VoxFlow free on the App Store   Download page

Licence & contributing

MIT. Copy them, fork them, put them in your own product docs, translate them. If a profession is missing — nurses, surveyors, inspectors, teachers, social workers — open a pull request on the repository with five templates in the same format and it will be merged.