Short answer: Clio has no built-in dictation, but any system-wide voice-to-text tool works inside it. On Mac, click into a time entry description or matter note, hold your dictation hotkey, speak, and release. On iPhone, switch to a voice keyboard in the Clio app and tap the mic.
Clio runs in a browser tab and on your phone, and neither place gives you a dictation button. That is not an oversight in the product so much as a boundary: practice management software manages the record, and text input is the operating system's job. Which means the fix is not a Clio setting or an integration you need to buy. It is a dictation tool that types wherever your cursor already is.
The reason this matters more in Clio than in most software is arithmetic. A practice management system is a text-entry machine wearing a database costume. Every matter you touch generates a description, a note, a task, an email, an activity. Most of those entries are short. All of them are typed. And a meaningful share of them get written badly or not at all, not because lawyers do not know what happened, but because typing a two-line summary at 5:40 PM after a full docket is the last thing anyone wants to do.
Where dictation actually helps inside Clio
Not every field in Clio wants your voice. Sorting the surfaces first saves you from the frustration of trying to speak a dollar amount into a rate field. Here are the places where speaking beats typing, roughly in order of how much time they give back.
1. Time entry descriptions
This is the whole game. Time entry descriptions are the single highest-frequency writing surface in any billing-based practice, and they are also the surface where quality has direct financial consequences. A vague entry gets written down by a billing partner or challenged by a client. A specific entry survives review.
The trouble is that specificity costs keystrokes, and keystrokes at the end of the day are expensive in willpower. So entries compress: "Call w/ client." "Review docs." "Email re: matter." Everyone knows those are weak. Everyone writes them anyway, because the good version is four times as long to type.
Speaking removes that tradeoff. The good version and the weak version take the same effort out loud. Click into the description field, hold your hotkey, and say what you actually did:
Telephone conference with client regarding the proposed settlement figure, discussed the tax treatment of the structured payments and the timeline for responding to opposing counsel, confirmed authority to counter at the number we discussed Monday.
That took about eleven seconds to say. Typed, it is closer to forty-five, and most people would not have bothered. Multiply across the entries in a week and the difference is not a rounding error.
2. Matter notes and activity descriptions
Matter notes are where the reasoning lives: why you took a position, what the client said they wanted, what the other side signaled off the record. That context is what makes a file usable when someone picks it up six months later, and it is exactly the kind of content that dies when typing is the bottleneck.
Dictating a matter note right after the call, while the detail is intact, produces a note two or three times longer than the one you would have typed an hour later. Length is not the point; recall is. You capture the qualifier the client added at the end, the concern they mentioned in passing, the date they said was hard.
3. Client emails from inside Clio
Communications sent through Clio are still just a compose box. Same workflow: click in, hold, speak. Client updates, scheduling confirmations, document requests, and "here is where we stand" messages are all natural speech shaped like email, and they read better dictated than typed, because dictating produces the sentences you would say to the client's face rather than the clipped shorthand you type when you are trying to clear an inbox.
One caution particular to legal email: dictated text lands in the field raw. Read it before you send. That is true of typed email too, but the speed of dictation makes it tempting to fire off a reply you have not actually looked at.
4. Tasks, and the description nobody fills in
Clio tasks have a name field and a description field. The name gets filled in. The description gets skipped, almost universally, because typing a second block of text to explain a task you just named feels redundant in the moment and is invaluable two weeks later.
Speaking the description costs you six seconds. "Draft the response to the motion to compel, focus on the proportionality argument, the prior production log is in the documents tab under the March folder." Now the task is actionable by someone other than the person who created it, which is the entire point of a task in a shared system.
5. Document and workflow notes
Version notes, intake summaries, and the running commentary that keeps a matter legible all benefit from the same treatment. If it is prose and it lives in a text box, you can speak it.
The fields to skip
Speak the prose, type the data. This is the rule that keeps voice input from becoming a net loss, and it applies to every practice management system, not just Clio.
- Rates, amounts, and quantities. Numeric fields want exact digits. Type them.
- Time durations. Same reason. Entering 0.4 by voice into a field with strict formatting is slower than typing two characters.
- Dropdowns and matter selectors. These are selections, not text. Voice does not help.
- Matter numbers, file numbers, invoice numbers. Anything with a fixed format and no tolerance for error should come from your fingers or from paste.
- Email addresses and phone numbers. Structural characters, no natural spoken form.
Everything that is a sentence, speak. Everything that is a value, type. Once that split is habit, you stop fighting the tool.
Setting it up on Mac
Because Clio is browser-based on the desktop, you need dictation that works at the system level rather than inside a specific app. Anything that only works in one editor is useless here.
Voice Keyboard Pro works this way on Mac: it lives in the menu bar, you hold a hotkey, you speak, you release, and the text appears at your cursor in whatever app or browser tab is focused. Clio in Chrome, Clio in Safari, an email compose window, a task modal, a note field. No extension, no per-site setup, nothing that breaks when Clio ships a UI update.
The practical setup is three steps:
- Install the Mac app and grant it microphone and accessibility permission when prompted. Accessibility is what lets text land at the cursor system-wide.
- Pick a hotkey you can hold without thinking. Something your hand rests near, and something that does not collide with a browser or Clio shortcut you already use.
- Test it in a scratch field before you use it on a live matter. Open a note, hold, say a sentence, release. Confirm the text lands where you expect.
If you have been looking at legal-specific dictation software, it is worth understanding what the category difference actually is. Traditional legal dictation suites are built around a document-first workflow and often want to own the application you write in. A system-wide tool inverts that: it does not care what you are writing in, which is precisely what you need when your day is split across a practice management browser tab, an email client, a PDF, and a word processor. We covered that distinction in more depth in our guide to legal dictation software for Mac, and in a direct comparison for firms evaluating a Dragon Legal alternative.
Setting it up on iPhone
Clio's mobile app is where the time entry problem is most acute, because mobile is where you are when the billable moment happens. You finish a call in a parking lot, or between hearings, and the entry either gets made in the next ninety seconds or gets reconstructed from memory that evening.
Typing a real description on a phone keyboard is miserable enough that most people log a placeholder and promise to fix it later. They do not fix it later.
The iPhone approach uses a keyboard rather than an app. Voice Keyboard Pro installs as a third-party keyboard with a mic button built in, so inside the Clio mobile app you tap into the description field, switch keyboards with the globe key, tap the mic, and speak. The text goes into the field like any other typed input.
Two setup details matter on iOS:
- You have to add the keyboard in Settings → General → Keyboard → Keyboards before it will appear in the globe menu.
- You have to enable Allow Full Access for the keyboard, because a third-party keyboard cannot reach the microphone without it. If the mic button does nothing, this is nearly always why.
The payoff is that the parking-lot entry becomes a real entry. Fifteen seconds of speech, done before you have started the car, with the detail intact.
The vocabulary problem, and why it is the whole story
Here is the thing that decides whether dictation sticks in a law practice or gets abandoned in week two: proper nouns.
General transcription handles ordinary English very well. It handles your client's surname, your opposing counsel's firm name, the case you cite six times a day, and the defined terms in the agreement you are living inside considerably less well. And the correction cost is asymmetric. If a tool gets ninety-eight percent of a paragraph right but mangles the client name every single time, you will experience it as broken, because the two percent it misses is the two percent that appears in every entry.
This is not a microphone problem and it is not solved by speaking more clearly. No general model has ever seen your matter list. The fix is telling the tool your vocabulary.
Voice Keyboard Pro's Smart Vocabulary is a personal dictionary with replacement rules for exactly this. You add the terms your practice actually uses, and they come out right from then on:
- Client and matter names, including the ones with unusual spellings
- Opposing counsel and firm names you write repeatedly
- Case names and citations you reference across filings
- Defined terms from the agreements you are working in
- Practice-area terminology and any local court or procedural shorthand
Load it once, during a quiet twenty minutes, with the thirty or forty terms that show up in your writing every week. That single investment is the difference between a tool you use daily and a tool you uninstall. Our post on voice-to-text for lawyers goes deeper on building that list, and the companion piece for paralegals covers the shared-vocabulary case when a whole team is entering into the same matters.
A realistic daily workflow
The version of this that survives contact with an actual practice is not "dictate everything." It is a small number of specific habits.
Enter time at the end of the event, not the end of the day
The strongest argument for dictation in Clio is not raw speed. It is that speaking is fast enough to do contemporaneously. Reconstructed time is always understated because you forget the short tasks, and it is always vaguer because you are describing a memory rather than a thing that just happened. If entering time costs fifteen seconds of talking, you will do it while it is still true.
Talk long, then cut
Dictate more than you need and trim. Cutting a sentence takes two seconds; remembering a detail you did not capture takes a phone call. This is the reverse of typing discipline, where you write minimally because writing is expensive, and it takes a week to feel natural.
Speak your punctuation early on
Say "period" and "comma" until the rhythm is automatic. Most people find that within a few days they stop thinking about it. Speaking punctuation is also what makes dictated entries scan like written text rather than a transcript.
Use the phone for capture, the desktop for cleanup
Mobile is for getting it into the system. Desktop is for making it right. If you dictate a rough note into the Clio app between meetings, you can tidy it at your desk in a fraction of the time it would have taken to write from scratch.
What to do about the recording, ethically
Two boundaries are worth stating plainly, because legal work carries obligations that generic productivity advice ignores.
First, confidentiality. Dictating client information means client information passes through a transcription service. Voice Keyboard Pro's servers store only operational pings, not audio and not transcript content, which is the property you want here. But your obligations run to your firm and your bar, not to a vendor's privacy page, so check your firm's policy on cloud-processed client data before you dictate matter-specific detail. We can describe how our system handles data; we cannot make a compliance determination for your practice.
Second, environment. Dictation is spoken aloud. That is fine in a closed office and not fine in a shared workspace, a courthouse hallway, or a coffee shop. The privilege risk in speaking a client name in a public corridor has nothing to do with software.
Common questions
Does Clio have built-in dictation?
No. Clio does not ship a dictation feature in either the web app or the mobile app. Text entry is handled by whatever input method your operating system provides, which is why a system-wide tool works everywhere in Clio without an integration.
Will this work in Clio Manage and Clio Grow?
Yes. Both are browser-based on desktop, and system-wide dictation is indifferent to which one is on screen. Anywhere there is a text field and a cursor, you can speak into it. The same is true of any other web-based practice management tool you happen to run alongside.
Will a Clio interface update break it?
No, and this is the main advantage of the system-level approach over a browser extension. Extensions target page elements and break when those elements change. Typing at the cursor is an operating system function; Clio cannot break it by redesigning a form.
Can I dictate a whole demand letter this way?
You can dictate the prose of it. Long-form legal drafting still wants a real document editor and a careful editing pass, and the structural pieces, citations, defined terms, numbered paragraphs, benefit from typing and templates. Dictation is at its best for the first pass and for the hundreds of short entries around the drafting, not as a replacement for the drafting discipline itself.
What about accuracy with legal terminology?
Common legal vocabulary transcribes well. Party names, firm names, unusual case citations, and matter-specific defined terms are where the errors concentrate, and that is what Smart Vocabulary is for. Budget the setup time honestly: twenty minutes of adding terms is the difference between a tool that mostly works and a tool that works.
The real argument
Practice management systems are sold on organization, but they run on text entry. The gap between a well-kept Clio instance and a thin one is not effort or intelligence. It is how much friction sits between knowing something and recording it.
Typing at roughly forty words per minute, which is the adult average, puts real friction there. Speech runs at 130 to 150 words per minute for most people with no practice at all. When the entry is a two-line description you have to write forty times a week, that ratio decides whether the description is specific or whether it says "review docs."
Voice Keyboard Pro has a free tier with daily limits, and Pro is $4.99 a month or $34.99 a year if you use it constantly. The reasonable way to evaluate it is to dictate one day of time entries and compare them to last week's. If this week's entries are longer, more specific, and were entered while the work was still fresh, you already have your answer.
Add client and matter names to your vocabulary, and on iPhone tap Speak in the Clio app to log a call before you forget the details.
3-day free trial on the monthly plan · Apple Silicon & Intel