Find where legal drafting time goes and rebuild the order of work

Why Legal Writing Is the Slowest Typing You Do is a question worth answering before you change tools, because the answer decides what to change. Most lawyers assume the delay comes from typing speed, and they look for a faster keyboard or a better shortcut. In practice the delay sits elsewhere: in the pause before a sentence, in the return trip to a source, in the formatting that interrupts the argument, and in the rereading that happens because the first version cannot be trusted. Typing is only the visible part of the work. If you measure the whole loop, you find that the bottleneck is rarely the hands.
Start with a rough audit of one drafting hour. Note when your hands stop moving and why: you are reading a case, deciding a characterization, checking a date, fixing a heading, or searching for the right verb. Do not try to be precise, because four or five categories are enough. Most people find that the largest block is not keystrokes but decisions made between keystrokes. That finding matters because a faster input method only helps the part of the hour it touches. If decisions dominate, the gain from speech is real but limited; if rework dominates, speech plus a better check can change the shape of the hour.
The second slow part is the return trip. Legal writing constantly moves between a source and a sentence: read the record, state the fact, confirm the citation, return to the argument. Each trip costs a little attention, and attention is what you run out of before you run out of time. Anything that keeps the source and the draft in the same visual field reduces those trips. That is why a second screen helps, and why drafting in a separate transcription window hurts: the window becomes another place to visit, and every visit has a cost that never appears on a timesheet.
The third slow part is distrust. When a sentence appears without the physical effort of typing it, it feels provisional, so you reread it more often. When it appears from your own hands, it feels approved, even when it is wrong. Neither feeling is reliable. The useful response is to replace feeling with a fixed check: name what must be verified, then verify it once. A routine check is faster than repeated unease, and it is more accurate than the confidence that comes from typing slowly. The rest of this guide turns that idea into an order of work. That order starts with separating two tasks you are used to doing at once.
Separate drafting from formatting, because switching between them is where many hours disappear. Drafting decides what the sentence says, and formatting decides how the document looks. When you do both at once, every heading change interrupts a legal thought, and every legal thought interrupts a heading change. Choose a plain working format for the drafting block: one heading level, one paragraph style, and no indentation decisions. Speak the substance into that plain frame. Then, in a separate block, apply the real format. The separation protects the part of the work that requires judgment from the part that requires only consistency.
Build the frame before you speak. A template with the caption, headings, numbering, and signature block removes most formatting decisions from the drafting hour. Then the only layout choices left are the ones the substance creates, such as a list inside a clause or an indented quotation. Handle those with a spoken marker and resolve them in the format block. This order also improves the draft, because a document with visible structure is easier to keep on topic. When you can see that a paragraph sits under the wrong heading, you fix an argument rather than a font, and that correction saves more time than any keyboard ever will.
Keep a single working file per document. Multiple copies, one for text and one for layout, create a reconciliation problem at the worst possible moment. If you must work in two files, name them so the relationship is obvious and merge in one pass before review. Better still, work in the file that will be delivered, with the final styles applied early, and let the text grow inside them. The risk of drafting in the delivered file is a stray keystroke in a live document, and the benefit is that nothing has to be moved later. For most legal drafting the benefit wins, provided you save a version before a long block.
Set a boundary for the format block so it does not expand. Give it a short list: heading levels, numbering, quotation indentation, spacing, and the signature block. When the list is done, the block is done. Without a list, formatting becomes a way to avoid the harder work of checking substance, and it can consume an afternoon while the argument stays unverified. A short, finite block also gives you a natural stopping point, which is useful when you are tired. Tired drafters format and rested drafters decide, so decide first, format second, and keep the second block small enough that it never becomes the main event.
Speaking in clauses rather than in sentences is the practical change that makes long drafting blocks possible. A clause is the smallest unit that carries one idea, and it is short enough to say without planning your breath and long enough to give the app context. Speak one clause, pause, and speak the next. The pauses feel unnatural at first, and they become comfortable within a page. They also create natural points to correct a mistake without restarting a paragraph. When you speak a whole sentence in one rush, a stumble at the end forces a decision: repeat everything or trust the repair. The clause boundary removes that decision.
Say the subject and the verb early in each clause. Spoken English tolerates long introductions, but written legal English does not, and the app produces what you said. If you begin with three qualifying phrases, you get a sentence that buries its own point. Practicing short openings also improves your thinking, because you cannot hide an unclear idea behind a graceful preamble. When a clause will not come out straight, that is information: the idea is not settled. Mark the spot and move on, then return with a decision rather than with a thesaurus. A clear clause is short before it is elegant.
Correct in speech rather than at the keyboard. A repair such as the deadline is thirty, no, forty-five days is understood as a self-correction and resolves into the sentence you meant. Voiskey removes filler words, stutters, false starts, self-corrections, and grammar slips, so the spoken repair is usually cleaner than the typed one. The habit to avoid is stopping to fix a single character. Each stop costs the context you were holding, and context is the scarce resource in a drafting block. Keep going, finish the section, and use the check pass for the things that need eyes rather than ears.
Use spoken punctuation sparingly and consistently. Say new paragraph at real breaks, and say quote and end quote around language that must be exact. Do not narrate every comma, because the app adapts punctuation to what you are saying, and a stream of punctuation words breaks the rhythm that makes speech fast. The exception is legal material where a misplaced comma changes meaning. For those sentences, slow down, speak the punctuation you need, and mark the sentence for the check pass. A small set of conventions, used the same way every time, is easier to keep than a long list you consult once and forget.
Measure one week before you decide anything. Keep a simple log for five working days: the document, the block of time, the number of interruptions, and the corrections you made in the check pass. Do not count keystrokes or estimate a percentage from memory. Then download Voiskey and run the same log for a second week with the same kinds of documents. The comparison is more useful than any general claim, because it reflects your documents, your sources, and your habits. If you cannot run two weeks, run three documents on each side, since a small honest comparison beats a large impression.
Read the log for categories, not for a score. Where did the interruptions cluster: sources, decisions, formatting, or corrections? A cluster around sources suggests a layout change rather than a speed problem. A cluster around corrections suggests a convention problem, such as unclear handling of names or numbers. A cluster around formatting suggests the template is incomplete. Each cluster has a different fix, and only one of them is about the input method. Naming the cluster is the point of the exercise, because it stops you from changing the wrong part of the workflow and concluding that nothing works. Keep the note to one page so you can read it at a glance.
Include the check pass in the measurement, because it is part of the work. A method that produces text quickly and leaves a long correction list has not saved time; it has moved the time. When you log, record the minutes spent verifying, and record what kind of item you had to fix. If the list stays short across several documents, the method is working for that kind of draft. If it grows, look at the conventions before you look at the tool, because unclear spoken boundaries and unstated term lists cause more corrections than any other single factor. Fix the convention first, then repeat the same document.
Compare like with like. Dictating a facts section and typing a table of authorities are different tasks, and mixing them in one average tells you nothing. Match document type, section type, and source availability across the two weeks. If a week contains an unusual document, exclude it and say so in the note. The goal is a comparison you would defend to a skeptical colleague, not a number that looks impressive. A defensible comparison usually shows a real gain on prose-heavy sections and little or no gain on highly negotiated sentences, and that pattern is exactly what you need to decide where to use the method.
Keep the gains by keeping the boundaries. The week after the experiment, reserve one block for speaking and one short block for formatting and checking. Do not let the check block expand into a rewrite, and do not let the speaking block drift into layout decisions. Boundaries are what make a faster method stable. When a deadline compresses the schedule, the temptation is to skip the check, and that is the moment to shorten the draft instead. A shorter verified document is worth more than a longer unverified one, and the habit of choosing the first protects the method from the pressure that kills it.
Keep a running list of sentences that resist speech. Every drafter has them: the one-line holding that decides the case, the defined term with a contested history, the sentence with three nested conditions. Type those, and do not apologize for it. The list is a map of where your judgment is concentrated, and it will be similar across matters. Over time it becomes a useful signal about the document: if a section is full of such sentences, it needs more thinking rather than more speed. Speed is for the parts you already understand. Keep the list in the same place as the template so it appears at the start of a session.
Review the method when the documents change. A new court, a new client, or a new template can break conventions that worked for a year. When the format changes, rebuild the frame before the next drafting block rather than repairing it mid-sentence. When the subject matter changes, rebuild the term list. These are small maintenance tasks with a large effect, because they keep the spoken path clear. A method that is never reviewed slowly fills with exceptions until it stops being a method, and ten minutes at the start of a new matter protects the next twenty hours of drafting.
Finally, decide what the saved time is for. Legal writing is slow partly because it is careful, and speed is only worth having if the care survives. Use the recovered hour for the hostile read, the source check, or the client call you would otherwise postpone. That is the honest case for speaking your drafts: not that legal writing becomes easy, but that the mechanical part stops consuming attention that belongs to the judgment. A drafter who can spend an extra hour testing an argument is better off than one who spent it on a keyboard. That is the only measure of speed worth keeping.
Legal writing is slow because the delay sits in decisions, source trips, formatting switches, and rereading, not only in keystrokes. Voiskey is an AI voice typing app: you press a shortcut, speak, and text appears at the insertion point in the app you use. It removes filler words, stutters, false starts, self-corrections, and grammar slips, so the mechanical part stops competing with judgment.
Yes. You speak a clause-sized unit, pause, and continue, which gives the app enough context to place punctuation and resolve a homophone. Voiskey also cleans up filler words and spoken repairs, so an inline correction such as the deadline is thirty, no, forty-five days resolves into the sentence you meant. The clause boundary becomes your natural point to correct without restarting a paragraph.
Log five working days with document type, block length, interruptions, and check-pass corrections. Then run the same log for a second week with Voiskey and the same kinds of documents. Compare like with like, and read the result by category rather than as one score. If corrections cluster around names or numbers, fix your spoken conventions before judging the input method.
Keep one working file, place the insertion point before you speak, and prepare the template so layout is a separate block. Speak clauses rather than long runs, correct in speech, and save punctuation words for sentences where a comma changes meaning. Then run a fixed check pass and note the corrections, because the check is part of the work rather than an interruption of it.

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