7 Ways to Use AI With Your Hands Full

Using AI with your hands full is a different problem from using AI at a desk, and almost nothing written about AI goes near it. Your hands are inside a panel, on a mixing bowl, holding a stud plumb, wrist-deep in a sink trap, or on a steering wheel. The keyboard isn't an option. Neither is stopping.

Here's what changed, and it's bigger than a features list. Deskless workers make up 70% to 80% of the global workforce, roughly 2.7 billion people, according to Boston Consulting Group. For most of the last decade those people were structurally excluded from AI, because AI shipped as a text box, and a text box demands two clean hands and eyes on a screen. That barrier came down quietly. Voice input got reliable enough for a loud room, models learned to look at whatever your camera sees, and the exchange stopped requiring your attention on a rectangle.

Every idea below assumes your hands stay where they are. Each one ends with something you can start today.

1. Narrate the Job While You're Inside It, Not From the Truck Afterward

Marisol services commercial rooftop units around Tucson. Her old routine was the one everybody has: do the work, drive to the next call, and write it all up somewhere between 7 and 9pm from memory. By then the serial number is a guess, the reason she swapped to the odd fitting is gone, and the note reads "replaced contactor, tested OK."

Now she talks through the job while she's doing it. Phone in her shirt pocket, recorder running, saying out loud what she'd otherwise be forgetting: the model plate, the reading before and after, why the manufacturer's spec didn't fit the actual duct run. It costs her zero extra minutes because she's not adding a step, she's moving one.

What comes out the other end is the thing techs never have when they need it. A record written at the moment of the decision, with the reasoning attached, which is exactly what saves you eight months later when the customer calls back and swears nobody touched that valve. One warning worth taking seriously: transcription in noisy real-world audio is much rougher than the clean-audio benchmarks imply, as AssemblyAI's accuracy review lays out. Say part numbers digit by digit and spell the codes.

Start today: Record one whole job on your phone's built-in voice recorder. Then hand the audio over with this: "Turn this into a service record with four sections: what I found, what I did, parts and serial numbers, and what the next person should watch." Read it once before it goes in the file.

2. Ask for the One Page of the Manual You're Stuck On

You're halfway into a job and the answer lives on page 63 of a 200-page PDF. The old options were both bad: climb out, degrease your hands, and scroll on a phone, or guess. Most people guess.

The move is to load the specific document first, then ask out loud. That word "specific" is doing all the work here. A general question to a general model gives you an answer for a machine like yours, which is a machine that isn't yours. Point it at the manual for your exact model and part number, and the answer comes back with the page it came from, which is the only kind of answer worth having when a torque value is involved.

For a shop or a crew with fifty manuals, this stops being a per-job task and becomes a shared library problem. That's what turning scattered documentation into something searchable is for, and the payoff is that the newest person on the crew asks the same question and gets the same answer as the person with twenty years.

Start today: Download the PDF manual for the one piece of equipment you touch most. Upload it into your assistant of choice, then ask it a question you already know the answer to. If it gets that one right and cites the page, you can trust the workflow. If it doesn't, you've learned that cheaply.

3. Show It the Part Instead of Trying to Describe It

Naming things is the real bottleneck, and nobody talks about it. There's an unlabeled valve on a wall, a bolt with a head shape you've never seen, a connector with the wrong number of pins, a status light blinking in a pattern that means something to somebody. You can't search for a thing you can't name. So you don't search. You improvise, or you call someone and describe it badly for four minutes.

Point the camera at it instead. Ask what it is, what it threads into, and what it's usually called in the trade. The genuinely useful output isn't the identification. It's the vocabulary. Once you have the words "quarter-turn ball valve, sweat by FIP," you can search like someone who already knew, and every result gets better.

Treat it as a search-term generator, not an authority. It will confidently misidentify things in bad light and with anything proprietary. The test is whether the term it hands you leads to a real manufacturer page.

Start today: Photograph three things in your work area you've never known the proper name for. Ask for the name, the common trade slang, and the exact phrase to search for a replacement. Save the answers somewhere you'll find them.

4. Turn a Day of Voice Notes Into the Paperwork That Has to Exist Anyway

Here's the tax nobody prices into the job. You finish the work at 2pm. You type it up at 8pm. Job logs, service reports, timesheets, inventory adjustments, invoice lines, the mileage. Every one of those facts existed at 2pm, in your mouth, in the exact moment you were standing in front of the evidence. The information was never the missing piece. The transfer was.

The fix is consistency first, then handoff. If your end-of-job voice note contains the same facts in the same order every time, the trip from spoken words to filled fields becomes a rule instead of a judgment call. And a rule is something you describe once and stop doing. This is where the retyping stops being your job: you say the five things, the workflow files them where they belong, and your evening comes back.

Consistency is the part people skip and it's the whole trick. A rambling note produces a rambling record. Five facts, same order, thirty seconds.

Start today: Pick your five facts (job, what was done, parts, time, next step) and record them the same way after every job for one week. At the end of the week you'll have both a habit and a pattern clear enough to hand off.

5. Make the Checklist Talk Back

In a kitchen, a lab, a clean room, or anywhere gloves and contamination rules apply, touching a screen isn't a small cost. It's a glove change. So the checklist lives on a laminated card, and the laminated card gets skimmed, and step four gets skipped on the days you're behind.

A spoken checklist fixes the part paper can't. It reads one step, waits, and refuses to advance until you say the step is done. That refusal is the entire value. Paper lets your eyes jump ahead and your memory fill in the rest, which is how experienced people skip steps and inexperienced people skip them without noticing. Aviation figured this out generations ago and the discipline transfers cleanly to anyone working alone with nobody watching.

You also get timestamps for free. Each confirmation lands with a time on it, which turns "I did the sanitizing cycle" into a record instead of a claim. If you work anywhere with an inspector, that record is the difference between a good day and a bad one, and keeping the log without keeping the log is the whole game.

Start today: Write out your most-skipped procedure as numbered steps. Paste it in and say: "Read me one step at a time. Wait for me to say done before you read the next one. If I ask for a step out of order, tell me which one I skipped." Run it once with gloves on.

6. Give Yourself a Real Button

Wake words fail in loud rooms and feel absurd on a job site. Half the reason voice input doesn't stick is the awkward two seconds of getting the thing to listen. Fix the input path and the rest follows.

The hardware is probably already on you. A long press on an earbud stem. A five-dollar Bluetooth camera remote clipped to a shirt pocket, which is a button your phone thinks is a shutter. A steering wheel control. A watch face you can hit through a glove.

Worth being honest about: most of this idea isn't AI at all. It's a cheap remote plus the dictation already built into your operating system, which costs nothing and runs on the device. The AI part happens later, to the text. That distinction matters underground, in freezers, and on rural sites where the signal dies, because capture has to work offline even when processing can't. Open models like Whisper run locally on ordinary hardware if you want the transcription offline too.

Start today: Map one physical button on something you already wear or carry to voice capture. Then test it with your gloves on, in the noisiest place you work. If it fails that test it will fail every day.

7. Set It Up Before the Day Your Hands Are Full for Good

Devon keeps the books for three restaurants in Cleveland and spent four months last year unable to type without pain after a wrist injury. The tools that got him through weren't specialty purchases. They were sitting in his settings the whole time, switched off.

Full voice control of a computer is a different thing from dictation, and most people have never tried it. Voice Control on macOS and voice access on Windows 11 both drive the whole machine: clicking, scrolling, switching apps, selecting text, no mouse required. Apple's runs its audio processing on the device, so nothing leaves your machine.

The thing that changed recently is correction. Old speech recognition made you repair errors word by word, which was slower than typing and killed the habit for most people who tried it. Now you say "replace the second sentence with..." in plain language and it works. That single improvement is what moved voice from a demo to a real input method.

Learn it while you don't need it. The week you break a wrist, sprain a thumb, or end up with a hand in a cast is the worst possible week to be reading a setup guide.

Start today: Turn on Voice Control in Accessibility settings on a Mac, or voice access on Windows 11 version 22H2 or later. Run the built-in tutorial, then spend fifteen minutes doing one ordinary task without touching the keyboard. It feels strange for ten minutes and then it doesn't.

Pick One

Seven ideas, one week. If you write up jobs at night, do the voice note habit in idea four, because a week of it will show you exactly how much of your evening was pure transfer. If you keep hitting things you can't name, spend five minutes on idea three today and watch how much faster your searching gets.

Sundays we report what shipped, Wednesdays we take one workflow apart on the bench, and Mondays are for ideas. When one of these turns out to be something you do every single day, that's the signal to move it into the agent workflow directory and stop carrying it yourself.

Frequently Asked Questions

• Does any of this work when I have no signal?+
  The capture half does. Dictation on modern phones and laptops runs on the device itself, so a basement, a walk-in freezer, or a rural site is fine for recording. The processing half usually needs a connection, so the practical pattern is capture now and process later. Record the voice note offline, and let the assistant turn it into a job log when your phone gets a bar back.
• How accurate is voice input in a loud environment?+
  Worse than the benchmark numbers suggest. Published accuracy is measured on clean audio, and real production audio degrades that meaningfully once you add machinery, echo, and accents. Three things fix most of it: a boom mic or bone-conduction headset instead of the phone's built-in mic, saying digits one at a time, and spelling part codes phonetically. Read the transcript once before it goes anywhere that matters. If the output feeds a shared record, the same discipline that turns spoken notes into tasks applies here.
• What should I never do hands-free?+
  Anything that competes for your attention while you're driving or operating machinery. Hands-free is not attention-free, and holding a conversation with an assistant takes real focus. Verify anything safety-critical against the source too: torque values, dosages, electrical ratings, load limits. A model states a wrong number with total confidence, and a wrong torque spec is a failure in the physical world, not a typo.
• I work at a desk. Is any of this for me?+
  Yes, because your hands are full more often than you think. Walking between buildings, standing in a warehouse aisle, carrying a box, driving to a site visit. Those are the moments when the thought arrives and the keyboard doesn't exist. Voice capture turns them into input, and if what you're capturing is a conversation, the notes can file themselves rather than sitting in an audio file nobody opens.