A four-block day that keeps checkpoints in a one-person law practice

A Dictation Workflow for a solo practice has to survive the fact that nobody else is there to catch the gaps. In a firm, a draft moves to an assistant, then to a reviewer, then to a filing clerk, and each handoff is a chance to notice a missing date or an unverified name. A solo lawyer has one pair of eyes and one calendar, so the workflow must build those checks into the work itself rather than into other people. Speech helps because it compresses the mechanical part of drafting, and it raises the stakes because the same person must verify the result. The answer is a fixed daily structure with explicit checkpoints.
Start by mapping a normal week. List the recurring outputs: client letters, engagement letters, demand letters, motions, discovery responses, file notes, and billing narratives. For each, note the average length, the source material it draws on, and the deadline pattern. Most solo practices have four or five repeat outputs that account for most of the writing, and those are the ones worth designing around. A workflow tuned to the repeat work frees attention for the unusual matter, which is where judgment is most needed. Do not design for the exception; design for the Tuesday afternoon that happens every week. Rewrite the list each quarter, because a solo practice changes shape faster than it notices.
Choose one input method and one place to draft. Switching between tools costs more than any single tool's shortcomings, because each switch forces you to reorient. If you speak your drafts, keep the same shortcut, the same microphone position, and the same template for a month before evaluating. A solo practice has no one to enforce consistency, so the calendar must do it: put the drafting blocks in the week and protect them. Consistency is the only way a one-person practice accumulates process, because process lives in habits rather than in colleagues. Put the block in the calendar with the same start time each week, and treat it like a client appointment.
Decide what you will never dictate. For most solo lawyers the list includes anything with a negotiated number, a sentence that has been through several rounds with opposing counsel, and language that a client has already approved. Typing those is not a failure of the method; it is a division of labor between speed and care. Write the list down and revisit it monthly. A workflow that claims to cover everything will be abandoned in a busy week, while a workflow with honest limits will survive. The goal is a practice that drafts faster without becoming a practice that checks less.
Build the day in four blocks: intake, drafting, review, and close. The intake block captures the facts while they are fresh, including names, dates, and documents. The drafting block speaks the repeat outputs into prepared templates. The review block runs the check passes with no other task open. The close block saves versions, names files, and writes the next actions. Four blocks are easier to protect than a dozen good intentions, and they match the way legal work actually arrives: a fact, a draft, a check, a handoff. A solo lawyer who names the blocks can tell at four in the afternoon which one was lost.
Put drafting before review, and never mix them. When you review inside the drafting block, you read for typos while the argument is still forming, and you miss both. The separation also protects against the most common solo failure, which is finishing a draft and sending it in the same motion. A review block with a start time is a small commitment that produces a real pause. If a deadline forces the blocks together, shorten the draft rather than the review, because a shorter letter that has been checked is worth more than a longer one that has not. Name the review block in the calendar so the pause has a place to happen.
Batch similar work inside the drafting block. Three client status letters dictated in one sitting share vocabulary and tone, and the second and third go faster than the first. Batching also reduces the cost of setup: one microphone check, one template, one term list. The risk of batching is monotony, which produces flat prose, so alternate the batching with a short break and read each output as if it were the only one. A solo practice runs on attention, and attention is managed by rhythm rather than by willpower. Batch by document type rather than by client, because the shared vocabulary is what saves the time.
Leave a margin at the end of each block. A block that runs to the minute will be colonized by the next urgent call, and the review will be the part that disappears. Fifteen minutes of margin lets you finish the check pass and write the next action. It also gives you a place to put the interruption without abandoning the method. The margin is not slack, because it is the part of the schedule that makes the schedule believable. Solo practitioners who plan every minute are planning for a week that never happens. Write the next action in the close block, so the margin is not spent deciding what comes next.
Intake is where voice drafting pays for itself, because intake is mostly repetition with small variations. A new matter needs an engagement letter with the same structure every time: scope, fees, responsibilities, and next steps. Speak the structure into a template, then speak the matter-specific facts. Voiskey learns names, jargon, acronyms, and spelling preferences, so client and matter names improve with use, and the first use in a new matter still deserves a check. The gain is not only speed, because every engagement letter receives the same sections, which is exactly the consistency a solo practice struggles to maintain.
Build an intake note template with the fields you always need. Party names exactly as they will appear in the letter, the matter description, the scope boundaries, the fee arrangement, and the client's stated goal. Speak into the fields rather than into prose, and the note becomes reusable across the matter. A structured note also improves the letter, because you can see which field is empty before you start writing. Empty fields are the source of most follow-up calls, and a solo lawyer has no assistant to notice them. When a field does not apply, write not applicable rather than leaving it blank, so a later reader knows it was considered.
Speak the scope section slowly, because scope is where engagement letters fail. Say what is included, what is not, and what would require a separate agreement. Use a short list, spoken as a list. Then read the scope back against the intake note and confirm that every excluded item is named. A vague scope is worse than a short one, because it invites the client to expect work you did not price. This is one place where dictation speed should be deliberately slowed, since the sentence carries the commercial relationship. If the client asks for work outside the scope, the letter should already say what happens next.
Finish the letter with a clear next step and a date. Clients read the closing more than the middle, and a solo practice benefits when the closing is unambiguous: what you will do, what they must send, and when you will speak again. Speak the closing as a list, then verify that each item appears in the body. Keep the approved letter as a pattern for the next similar matter, with the client-specific facts removed. Over a year, this produces a small library of engagement letters that are consistent, complete, and fast to produce. Keep the library short, because a folder of twenty variations will not be used under deadline.
Protect the review pass as the one block that cannot be moved. Speak the draft in the morning and review it after lunch if the schedule allows, because a gap makes errors easier to see. Read with a checklist that matches the document: names and defined terms, dates and figures, obligations and deadlines, and the next-step list. Voiskey keeps the text in the drafting app, so the checklist can sit beside the document without moving anything. The review is the only part of the workflow that catches the mistakes speed creates, and a solo practice cannot outsource it to a colleague.
Read the document once for what it says and once for what it omits. Omission is the failure mode of fast drafting: the sentence that was never spoken, the exception that was assumed, the deadline that was in your head. Compare the draft against the intake note and the source documents, and mark every required element that is missing. Keep a standard list of required elements for each document type, and tick it. The list is the closest thing a solo practice has to a second reader, and it works because it does not get tired. A missing element is easier to guard against when the list names it before the draft begins.
Make the review visible in the file. A short note at the end of the draft stating which checks were run and which were skipped is evidence for you and information for the client. Date it and keep it with the version. When a matter later goes wrong, that note is the difference between a clear account and a reconstruction. It also disciplines the review, because writing down which checks you skipped is uncomfortable in a useful way. Write the note before you send, not after, because the note is part of the check. A note written from memory a day later records an intention rather than a fact.
When you are ready to make the review routine, download Voiskey and run the same checklist on five documents drawn from different matter types. Keep the corrections in a single list and read it at the end of the week. The list will show whether errors cluster around names, figures, or structure, and each cluster has a different fix. After five documents you will know which checks to keep, which to shorten, and which to add. Download Voiskey once, set the shortcut, and let the checklist carry the discipline that a solo practice cannot delegate. Keep the five documents in one folder so the comparison is easy to repeat.
Run a weekly reset of twenty minutes. Open the drafts that were sent, list the corrections you made after sending, and note the cause of each. Count the templates you used and the ones you rebuilt from scratch. Check the term list against the current matters and remove names that no longer apply. A reset is short because it is a review of a review, not a new project. What it produces is a small set of changes for the coming week, which is more useful than a general intention to be more careful. Put the reset in the calendar on the same afternoon each week, because it will not happen otherwise.
Keep the changes to one or two per week. A solo practice cannot absorb a new process every Monday, and a workflow with ten new rules will collapse by Wednesday. Choose the change that addresses the most frequent correction, apply it for a week, and measure again. If the correction disappears, keep the change; if it does not, the diagnosis was wrong and the next reset should say so. This is the same discipline as a case: form a hypothesis, test it, and record the result. Write the change at the top of the next week's page, so it is visible when the work starts.
Review the commercial side of the workflow once a month. Track how long each repeat output takes, how often a client asks for clarification, and how many drafts are returned for revision. These are ordinary practice measures, and they tell you whether the method is producing usable work. If a document type remains slow after several weeks, the problem may be the template rather than the drafting method. If clients keep asking the same question, the letter pattern needs a clearer section. Numbers about your own work are more useful than impressions. Review the numbers with the same skepticism you would apply to an opposing party's figures.
Finally, decide what the practice does with the recovered time. A solo lawyer who drafts faster can take one more matter, finish earlier, or spend the saved hour on the review that protects the file. The third choice is usually the best investment, because it converts speed into quality rather than into volume. That is the only defensible reason to change a legal workflow: not that it is faster in a demonstration, but that it makes the work you send out more reliable. A practice that drafts by voice and checks carefully can grow without adding risk. Write down which use you chose, so the next month's review can test whether it happened.
Voiskey is an AI voice typing app: you press a shortcut, speak, and text appears at the insertion point in the app you already use. For a solo practice that means drafts land in the same file you will check and send, with no copying between apps. It removes filler words, stutters, false starts, self-corrections, and grammar slips, so the repeat outputs take less of the day.
Yes. Template the structure once, then speak the matter-specific facts into it. Voiskey adapts punctuation, formatting, tone, and wording to what you are trying to do, and it learns names, jargon, acronyms, and spelling preferences, so client and matter names settle with use. Read the scope section back against the intake note before the letter goes out.
Check names and defined terms, dates and figures, obligations and deadlines, and the next-step list. Read once for what the draft says and once for what it omits, comparing it with the intake note and the source documents. Write a short note at the end stating which checks were run and which were skipped, then keep it with the version you send.
Voiskey learns names, jargon, acronyms, and spelling preferences as you use it, which reduces variation across documents. Read the matter term list aloud before a drafting block and confirm the first use of each party name after it appears. On the team plan, shared vocabulary and workflows can carry confirmed labels across a group, which helps when a solo practice brings in contract help.

Download Voiskey for Mac and Windows and start drafting by voice today.
Use it across macOS, Windows, iOS, and Android