Short answer: Dictate performance reviews by talking through each section out loud in one pass, describing specific things the person actually did, then editing what you said. Speak the narrative, type the ratings and figures, and always reread critical feedback before submitting.
Review season has a shape that every manager recognises. The first review is thoughtful. The fourth is decent. The eighth is a paragraph of adjectives that could apply to anyone on the team, written at eleven at night because the form is due tomorrow.
That decay is not a character flaw. It is a throughput problem. A manager with eight reports is being asked to produce something like six thousand words of careful, specific, defensible prose inside a two-week window, on top of a normal job. Typing at an average adult rate of roughly 40 words per minute, the writing alone is hours of keyboard time, and every hour of it competes with the actual work of managing.
Speech runs at 130 to 150 words per minute. That gap is why dictating reviews is worth the small amount of setup it takes, and it is also why the resulting reviews tend to be better rather than merely faster. This guide covers the workflow: what to speak, what to type, how to structure each section out loud, the tone trap that catches people the first time, and what voice cannot fix.
The real problem is not writing speed. It is the blank box.
Be honest about the failure mode. A vague review is rarely the product of a manager who has nothing to say. It is the product of a manager who has plenty to say, has it in a loose unstructured form in their head, and is looking at an empty text box that demands polished sentences.
Typing forces you to compose and transcribe at the same time. Under that load, most people reach for the safe generic sentence, because it is easier to type "consistently delivers high-quality work" than to reconstruct the specific quarter where that was true and why it mattered.
Talking does not have that problem. Ask a manager to describe someone's year out loud and you get detail immediately: the project that slipped and how they handled it, the moment they took over a stalled thread, the conversation where they changed their mind. The information was always there. The keyboard was the bottleneck.
Thin reviews are an input problem, not a discipline problem. Fix the input and the specificity arrives on its own.
This is the core argument for dictating reviews, and it is worth being precise about what it does and does not claim. Voice will not invent evidence you never gathered. If you did not pay attention all year, dictating will produce fluent vagueness instead of terse vagueness. What voice does is remove the friction between what you know and what lands on the page.
Where the raw material comes from
The best review is assembled, not composed. If you have been capturing notes all year, review writing becomes an editing job that takes twenty minutes per person instead of ninety.
The highest-value habit is a running note per report, updated after every one-on-one. Two or three sentences, dictated in the ninety seconds after the meeting ends while it is still fresh: what they raised, what you agreed, what you noticed. Nobody types those notes consistently, because typing them competes with the next meeting. Almost everyone can speak them, because ninety seconds of talking costs nothing. We wrote about the meeting side of this in how to run better one-on-ones, and the same capture principle applies to meeting notes generally.
On Mac, Meeting Mode records the conversation with speaker detection and produces AI notes afterward, which is useful for the meetings where you genuinely cannot take notes and talk at the same time, such as skip-levels, calibration sessions and project retros. Tell people when you are capturing a conversation; that is basic courtesy and, in many workplaces, policy. For one-on-ones specifically, most managers find a short dictated note afterward is a better fit than recording, because a one-on-one is exactly the meeting where people need to feel unobserved.
A five-part spoken structure for every section
The reason dictated reviews sometimes come out rambling is that people press the hotkey with no plan. Give yourself a structure and speak to it. This one works for a strengths section, a growth section, a goal assessment or a competency box, and it takes about ninety seconds per section:
- The claim. One sentence stating what you are assessing. "Her strongest area this year was cross-team communication."
- The evidence. Two or three specific things that happened. Name the project, the situation, the quarter. This is the part that makes a review real, and it is the part that generic reviews skip.
- The impact. What changed because of it. Who was unblocked, what shipped, what stopped being a problem.
- The pattern. Whether this was a one-off or a consistent trait, and whether it changed over the year.
- The forward look. What good looks like next, stated as a behaviour rather than a personality trait.
Speak all five in one held press without stopping to fix wording. Resist the urge to edit mid-flow; that is what drags a ninety-second section into a fifteen-minute one. You will produce a rough, slightly over-long block, and over-long is exactly what you want, because cutting is fast and expanding is slow.
The same structure, for the growth section
Development feedback is where managers hedge hardest, and hedging is what makes it useless. Speaking helps, because the plain spoken version of a concern is usually clearer than the written one. Say the thing the way you would say it to a peer, then edit for tone. The order matters: get it accurate first, make it kind second. Doing it in the other order produces feedback so softened that the person never realises there was a problem.
Speak the sentences, type the values
This is the boundary that keeps dictated reviews clean. Voice belongs in every field that holds prose. Keep your hands on everything that is a value.
Dictate: narrative summaries, competency evidence boxes, strengths, development areas, goal commentary, promotion justifications, manager comments on a self-review, the one-on-one note that feeds all of it.
Type: numeric ratings, rating scale selections, dropdowns, compensation figures, percentages, dates, employee IDs, level and title strings, anything with a strict format. Numbers are the one category where a dictation error looks completely normal on the page, which makes it the one category never worth the risk in a document this consequential.
The batching version of this rule is faster than it sounds: do one pass through the whole form speaking every prose box, then a second pass clicking every rating and typing every figure. Switching input modes ten times per form is what makes people give up on dictation in structured tools.
Where you actually dictate it
Performance reviews almost always live in a browser: an HR platform, a performance tool, an internal form. That is normally the death of dictation features, because those platforms have no microphone of their own, browser extensions need approval, and nobody is getting IT to install anything during review week.
Voice Keyboard Pro sidesteps that entirely. It sits in the Mac menu bar and types at your cursor, system-wide. You click into the text box in whatever tool your company uses, hold the hotkey, talk, release, and the text appears where the cursor is. Nothing is installed into the HR system, no admin has to approve anything, and the workflow is identical whether the box is in a browser tab, a document, or an email to your skip-level.
Two practical notes. Pick a hotkey that does not collide with a browser shortcut. And check that the text field commits the way you expect before you speak six paragraphs into it, because some form fields autosave on blur and some do not; losing a dictated block to a form reset is a bad way to learn that.
The tone trap
Here is the failure mode nobody warns you about. Spoken feedback is more direct than written feedback, because speech carries tone that text does not. When you say "I don't think that landed" out loud, your voice does most of the softening. On the page, stripped of that, the same sentence reads considerably colder than you meant.
Two rules handle it:
- Never submit a critical paragraph in the same sitting you dictated it. Even ten minutes of distance is enough to catch the sentence that reads sharper than intended.
- Read the development section aloud before submitting. If you would not say it in that phrasing to the person's face, rewrite it. This is a thirty-second check that prevents most of the review conversations that go badly.
On iPhone, Voice Edit is genuinely useful for this pass: you speak the change you want rather than placing a cursor and retyping. "Change the second sentence to say the deadline was missed once, not repeatedly" is faster than doing it by hand, and it makes tone editing something you will actually bother to do.
Writing reviews that hold up
Performance reviews are records. They get read by HR, by the next manager, sometimes by people you did not anticipate, occasionally in a dispute. Dictation makes you faster, which means it also makes you faster at writing something you would rather not have written. A few habits, all of which are just good review practice, matter more once you are producing text at speaking speed:
- Describe the work, not the person. "The design doc went out without the migration section" rather than "she is careless."
- Stay with observations, not diagnoses. You saw behaviour and outcomes. You did not see motivation, attitude or what was happening in someone's life.
- Avoid anything touching protected characteristics, health, family circumstances or personal life. This is not a dictation rule, it is a review rule, but talking makes it easier to drift there.
- Keep the specifics checkable. If you cite a date, a project or a metric, be sure it is right. Reread every figure.
- Reread before you submit. Every time, without exception.
Your HR and legal teams own the policy on what belongs in a review and how it is retained. We build dictation software; we cannot rule on your company's rules, and this is not legal advice. If you are unsure whether something belongs in the written record, ask them before you write it, not after.
The names problem
Every review is dense with proper nouns: the names of the people you manage, the internal project code names, the systems, the customer accounts, the team names. These are exactly the words a general transcription engine has no reason to know, so they come back wrong, and stock dictation never learns from your corrections. Fixing the same surname eight times in one evening is the thing that makes people abandon voice halfway through review season.
Smart Vocabulary is the fix. It is a personal dictionary with replacement rules: you teach it your team's names, your internal project names, your acronyms and your product vocabulary once, and they stop being errors. Fifteen minutes of setup before review week pays for itself in the first two reviews. It is the same technique that makes voice workable in an applicant tracking system, which we covered in how to dictate in Greenhouse, and in HR work generally, covered in voice dictation for HR professionals.
Self-reviews and upward feedback
Two adjacent documents benefit from the same approach.
Your own self-review is the one people procrastinate on hardest, because writing about yourself in the third-person institutional register is deeply unpleasant. Dictating it works well precisely because you are allowed to be loose in the first pass. Talk through the year chronologically, quarter by quarter, saying what you worked on and what came of it, without any attempt at polish. You will produce twice the material you need in about ten minutes, and cutting a long honest draft is far easier than staring at an empty box trying to sound accomplished.
Peer and upward feedback is usually short-form, which means people write two sentences and move on. Voice raises the floor here more than anywhere else: ninety seconds of talking produces a genuinely useful paragraph, and the marginal cost over the useless two-sentence version is almost nothing.
The review-season workflow
Put together, here is the shape of a review week that does not consume your evenings:
- Gather first, write second. Before you open any form, pull up your running notes, one-on-one records, project docs and any peer feedback for that person. Read them. Do not write yet.
- One person per sitting. Reviews written back to back start borrowing each other's language, which is where generic phrasing comes from.
- Talk the whole draft in one pass. Every prose section, five-part structure each, no editing mid-flow. Aim for twenty to thirty percent more words than you need.
- Second pass: values. Ratings, dropdowns, figures, dates. Hands only.
- Third pass: cut and cool. Trim the overshoot, check every proper noun and number, read the development section aloud.
- Leave it overnight if the review is difficult. The ones that need the extra day are obvious while you are writing them.
A manager who has kept notes can move through this in twenty to thirty minutes per person. The difference is not the typing speed. It is that steps one and three stop competing with each other.
On iPhone: the notes that make reviews possible
Most of the raw material for a review is generated away from a desk, in the ninety seconds after a meeting, walking between rooms, or on the way home when you remember something worth writing down.
The Voice Keyboard Pro keyboard has a mic button built into it, so it works inside any iOS app: your notes app, your task manager, an email to yourself, the HR tool's mobile view. Dictate the observation while it is fresh and it will still be there in November.
Voice Edit handles the corrections without the cursor-hunting that makes phone editing miserable. And for managers with distributed teams, the two-way translation while dictating across 24 languages means you can capture a thought in one language and produce it in another, which matters when the person reading the review is not reading in their first language.
What voice does not fix
Three honest limits.
It does not fix an absent evidence base. If you have not been paying attention, dictation gives you longer vague sentences rather than shorter ones. The notes habit is the actual intervention; voice just makes the habit sustainable.
It does not fix a bad review process. If the form asks the wrong questions or the calibration is arbitrary, faster writing produces the same outcome sooner.
It does not do the thinking. The hard part of a review is deciding what is true about someone's year and how to say it usefully. That happens in your head, before you press the hotkey. Voice removes the transcription tax on that judgement. It does not supply the judgement.
Frequently asked questions
Will a dictated review sound less professional?
It will sound more conversational and less compressed. In a review that is generally an advantage, because the register that makes reviews unreadable is exactly the compressed institutional one. A short editing pass closes the gap, and the specificity you gain is worth far more than the polish you spend ten minutes restoring.
Does my HR platform support dictation?
It does not need to. Voice Keyboard Pro types at your cursor at the system level on Mac, so it works in any text field in any browser or app. Nothing is installed into the HR system and no admin approval is required.
Is it safe to dictate employee information?
Voice Keyboard Pro's servers store only operational pings. No audio and no transcript content is retained. That said, employee records are among the most sensitive data most managers handle, and your employer's policy governs which tools are approved for it. Check with your IT and HR teams; that call is theirs, not ours. Also mind your surroundings, since dictating a difficult review in an open office is a confidentiality problem no software can solve.
How much time does this actually save?
The mechanical part is arithmetic: producing prose at 130 to 150 words per minute instead of around 40. The larger saving is the staring time that never shows up in a word count, and that varies enormously by person. Most managers find the first draft is the part that collapses, from an hour to something closer to fifteen minutes, with editing time roughly unchanged.
Should I dictate the review meeting itself?
Dictate your notes afterward. Recording a review conversation raises consent and policy questions that vary by jurisdiction and employer, and it changes how the conversation goes. A five-minute dictated summary immediately after, while you still remember what the person said, is more useful than a transcript anyway.
The short version
Reviews get generic because typing forces you to compose and transcribe simultaneously, and under that load everyone reaches for the safe adjective. Talk through each section with a five-part structure, overshoot, then cut. Speak the prose and type the values. Teach your team's names to a personal dictionary once. Read the hard paragraphs aloud before you submit. Voice Keyboard Pro has a free tier if you want to try it on the next review you owe.