From nine minutes of typing to ninety seconds of talking: voice notes in the field

Voice notes for technicians solve a problem every service manager knows: the job note that says "replaced part, system running" and nothing else. The tech isn't lazy. They're standing in a driveway in July with sweat in their eyes, typing on a phone with thumbs that just spent an hour on a condenser, and the next job is already late. A useful note takes too long to type, so they type a useless one.

Talking is faster. Lab research puts speech at roughly three times the speed of typing on a phone. This post looks at what that research says, works out what it's worth in a 10-tech shop, gives you a five-part spoken template that turns rambling into a usable record, and covers the one thing that makes or breaks voice notes: a confirm step before anything is saved.

What the research says about talking vs typing

The best-known study was led by researchers at Stanford, with a co-author from the University of Washington. Participants entered short phrases on an iPhone 6 Plus, once with the keyboard and once by speech recognition, in English and in Mandarin. Speech was 2.93 times faster in English (153 words per minute versus 52) and 2.87 times faster in Mandarin. The error rate while entering text was lower with speech too: 5.30% versus 11.22%. The final text after corrections had slightly more errors with speech, 1.30% versus 0.79%.¹

That keyboard number came from people sitting at a table typing short phrases. Real-world typing is slower. A 2019 study led by researchers at Aalto University analyzed typing by 37,370 volunteers on their own phones and found an average of 36.2 words per minute.²

Neither study was done in a driveway with a compressor running or in gloves. Field conditions slow both methods. But they slow typing more: gloves, sweat, sun glare on the screen and cold fingers all hit the keyboard, while speech mostly needs a quiet spot, which the inside of a truck cab provides.

The nine-minute note: a worked example

What does a good job note contain? For a repair visit: what the tech found, what they did, the parts and materials used, what they recommend, and any safety concerns. Written properly, that's about 150 to 250 words. Here's the math for a 200-word note, using the research speeds as a guide and adding the parts the studies don't measure.

Every number here is an estimate. The talking speed is deliberately slower than the lab figure, because people pause and think when describing real work.

At 6.5 minutes saved per note, 4 notes a day, 10 techs and 250 working days, that's 65,000 minutes, or about 1,080 hours a year. Even if you cut that in half for real-world friction, it's most of the capacity of a part-time employee, recovered from paperwork that the techs disliked anyway.

The bigger payoff is the note itself. A tech who will type 12 words will often say 150. Those 150 words are the ones the office uses to sell the replacement, the next tech uses to avoid a misdiagnosis, and the warranty claim uses to prove what happened.

What a structured voice note sounds like

Here is an example, invented for illustration, of what a tech might say in the cab after a no-cool call, and what a usable record looks like after it's organized and confirmed.

What the tech said (about 70 seconds): "OK so, Johnson job, customer said no cool since last night. Got there, outdoor fan wasn't spinning, compressor humming. Checked the cap, it's a 5 microfarad, reading like 3. Swapped it with a 5 440, fan came up, let it run twenty minutes, split was 19 degrees. Contactor's pretty pitted, didn't change it, told her it should get done next time. Coil's dirty too. Unit's a 2011, so, you know, worth mentioning replacement. Nothing unsafe."

The tech's job is to check that list, untick anything wrong, and confirm. The rambling stays in the audio and the original transcript; the record is clean.

Why the note matters more than the minutes

A thin job note costs you in four places:

• The next visit. The tech who comes back in March needs to know what was found in August. Notes are one of the cheapest ways to protect your first-time fix rate.
• The sale. "Heat exchanger shows rust at the burner inlet, recommend replacement within the year" is a lead. "Furnace old" isn't.
• The invoice. Parts used but not billed are pure margin lost. A spoken list of what was used is easier to check against the invoice than a memory at 6 p.m.
• The dispute. When a customer says the tech never mentioned the leak, a dated note saying he did is worth more than anyone's recollection.

A five-part spoken note template

People ramble when they talk. The fix is not to ask techs to talk less, but to give them an order to talk in. Teach this script and put it on a card in every truck.

1. 1

   Found

   What the customer reported and what you found, with the measurements behind it. 'No cool. Outdoor fan not running, capacitor reading 3 microfarads on a 5 rating.'

2. 2

   Did

   What you did and the result. 'Replaced the fan capacitor, fan running, system cooling with a 19-degree split.'

3. 3

   Used

   Every part and material, with quantities. 'One 5 microfarad 440-volt run capacitor.' Name parts the way your price book does.

4. 4

   Recommend

   What the system needs next and how urgent it is. 'Contactor pitted, recommend replacing at next visit. Coil dirty, recommend cleaning.'

5. 5

   Safety

   Anything unsafe now or soon. 'No safety concerns.' Saying it out loud matters: it proves you checked.

A note recorded this way takes 60 to 90 seconds. It also maps cleanly onto the parts of a job record: the note, the findings, the invoice lines and the options for the customer.

Spanish-speaking techs and one-language records

The trades rely heavily on Hispanic and Latino workers. In the BLS Current Population Survey for 2025, they made up 26.7% of employed HVAC mechanics and installers, 30.3% of plumbers, pipefitters and steamfitters, and 25.0% of electricians, against 20.0% of all employed people.³

Ethnicity is not language, and many of these techs are fully bilingual. But most shops have at least one excellent tech who explains a diagnosis far better in Spanish than they write it in English. Typing forces them to do the hardest part, writing in his second language on a small screen, at the worst moment of the day. Voice notes that accept any language and produce the office's language remove that tax. Keep the original words with the record, so a bilingual manager can check the translation when it matters.

The catch: speech-to-text makes mistakes

Voice notes go through two automated steps: speech-to-text, then a model that organizes the words. Both can be wrong.

Speech recognition mishears model numbers, part sizes and brand names, especially with background noise. Worse, it can add words. A 2024 study of OpenAI's Whisper found that about 1% of transcriptions contained entire phrases or sentences that weren't in the audio, and 38% of those included harmful content such as false statements or implied authority.⁴ One percent sounds small until it's the sentence "no gas leak detected" in a note where nobody said it.

The answer is not to avoid voice notes. It is to never save them blind.

What the confirm step should look like

• Every item is separate. The note, each finding, each part and each option has its own checkbox. The tech unticks what's wrong instead of retyping the whole thing.
• Parts come from your price book only. Anything the system can't match is listed as unmatched, never guessed. A list of unmatched mentions each month is also a list of what your price book is missing.
• Safety findings are the tech's call. Software can label a finding "high" because the tech said "cracked," but the tech confirms the severity before it's saved.
• Nothing is written until the tech taps confirm. Draft until then.

Getting techs to actually use it

Most rollouts stall on habits, not technology. Three objections come up in almost every shop.

"I'm not talking to my phone in front of the customer." Fair. Record in the truck cab after the job, with the door shut. It's quieter, which helps accuracy, and it keeps the note a private summary rather than a performance.

"Is this recording the customer?" It shouldn't be. A voice note is the tech's own summary of the visit, recorded only when the tech taps record. Recording conversations with customers is a different thing with its own rules: federal law allows recording with one party's consent, but several states, including California, Florida, Illinois, Maryland, Massachusetts, Pennsylvania and Washington, generally require everyone's consent.⁵ Keep the two separate, and tell your techs which is which.

"It got my part wrong, so I stopped." That's the confirm step doing its job, and the fix is usually in the price book. If techs say "dual run cap" and your price book says "CAPACITOR-DUAL-45/5-440V," matching will struggle. Rename your most-used items so they read the way techs say them.

One more habit worth building: the service manager listens to one voice note per tech per week and replies with one specific comment. Nothing improves notes faster than knowing someone reads them.

Rolling out voice notes in a week

Track three numbers before and after: share of completed jobs with a real note, findings logged per visit, and parts on invoices that match what techs said they used.

How voice notes work in TradesWork

In TradesWork, a technician taps Record on the job and talks for up to five minutes, or types or dictates with the keyboard instead. Voice notes turn the recording into a clean English job note in any spoken language, findings rated by severity, parts matched to your price book with anything unmatched listed separately, and up to three draft good/better/best options. Nothing is saved until the tech ticks what's right and confirms. A recording made with no signal is kept on the phone and processed when signal returns. It needs a speech-to-text service connected and AI turned on for your company. See how it fits with the other AI helpers on the AI overview.