A clause-by-clause routine for legal text that must survive review

Legal Dictation When Your Words Must Be Exact is a different craft from ordinary speech-to-text, because one swapped article or dropped comma can change an obligation. In most writing a reader can infer what you meant, but in a letter to opposing counsel, a lease clause, or a statement of facts, the reader will hold you to the literal sentence. That is why the useful question is not whether a tool can transcribe speech, but whether the result survives a line-by-line reading against your own intent. Exactness is a habit built from three parts: a clean speaking line, a deliberate way of voicing technical material, and a verification pass you never skip. Each part is simple, and together they decide whether dictation saves an hour or costs you two.
Begin by listing the places where a wrong word is expensive in your own practice. Typical candidates are defined terms, party names, dates, sums, section references, quoted testimony, and standard phrases such as without prejudice or time is of the essence. For each item, note whether the risk comes from sound-alike words, unusual spelling, or spoken punctuation. A name like Catherine may arrive as Katherine, and a figure like fifteen thousand can lose a zero inside a long list. This inventory tells you what to slow down for, what to spell aloud, and what to check by eye. Keep the list on one page beside your screen, because it is the shortest useful guide you will write all week.
Exactness also depends on separating drafting from transcription. When you type, you edit while you compose, so the sentence on screen is already the sentence you approved. When you speak, the first version appears faster than your judgment, and the text can look finished while remaining unverified. Treat the spoken draft as raw material with a short shelf life: speak the substance, then read it against the source before anyone relies on it. That order keeps your attention on the legal question first and the wording second, which is the reverse of how most people type. It also prevents the common trap of polishing a sentence that says the wrong thing.
Finally, decide what exact means for the document in front of you. A client update needs plain, unambiguous sentences, a contract needs consistent defined terms and precise verbs, and a brief needs quotations that match the record word for word. Write that standard at the top of the file as a one-line note, such as defined terms as in the term sheet, or quotes verified against the transcript. The note becomes the instruction you give yourself at the end of the session, and it stops one standard from leaking into a document that needs a different one. The rest of this guide builds a routine around that single line.
Your speaking line is the path from your mouth to the insertion point, and most errors begin there. Before the first sentence, click into the exact field where the text should land and confirm the cursor is visible. In Voiskey the pattern is a shortcut, speech, and text at the insertion point, so an unfocused field is the most common reason for a surprise. Close muted calls, pause music, and move a phone away from the microphone. Sit so your mouth stays a consistent distance from the microphone, because leaning back mid-sentence changes volume and can swallow the ends of words. Two minutes of setup protects an hour of drafting.
Speak in clauses rather than in whole paragraphs, and pause briefly at each boundary. A clause-sized chunk gives the app enough context to place punctuation and resolve a homophone, while a long unbroken run forces it to guess where one idea ends. If you notice a stumble, keep going and correct it in the next few words, for example the notice period is thirty, sorry, forty-five days. Voiskey removes filler words, stutters, false starts, and self-corrections, so a spoken repair usually resolves into the sentence you meant. Resist the urge to stop and retype, because a clean spoken correction is faster and leaves a shorter trail to review.
Set a pace you can sustain for twenty minutes. A comfortable drafting pace is slower than conversation and faster than typing, and it should leave you enough breath to finish each sentence. If your voice rises at the end of every clause, the app may hear a question; if you trail off, it may drop the final word. Record a short sample of your own dictation and listen once, checking for clarity rather than for accent. Most people discover they speak too quickly when reading a defined term they know by heart, which is precisely the material that must not be garbled.
Protect the speaking line for the whole session. Put reference documents on a second screen or in printed form so your eyes are not hunting through open files while you talk. Keep a notepad for items that need a decision later, such as check the notice address, so you do not interrupt the flow to resolve them. When you must look something up, say a marker phrase such as resume after the definition, then jump back to it. A stable line and a single open field are boring advantages, but they are the ones that make a long drafting block feel calm instead of fragile.
Technical material needs a spoken convention, and you should choose it before you start. Say quote and end quote around language that must be reproduced, and say new paragraph only when you actually want a break. For citations, decide whether you will say the full reference or a short placeholder such as cite the deposition at page forty-two and fill it during the check. Placeholders are acceptable when they are obvious, but a vague phrase that looks like finished text is not. Write your conventions on the same page as your risk list so a colleague can draft in your place without inventing a new system.
Defined terms deserve their own rhythm. Say the term once at normal speed, then confirm it the way you would confirm a name on a call. Voiskey learns names, jargon, acronyms, and spelling preferences, so repeated exposure improves the result, but the first use in a new matter still deserves a glance. Keep a short list of deal-specific terms: the parties, the project name, and the defined labels such as Permitted Encumbrances or Closing Date. Read the list aloud once at the start of a session. It warms up your pronunciation, and it reminds you which phrases must be identical everywhere they appear.
Numbers, dates, and money need a fixed spoken format. Choose one pattern for each: forty-five days rather than forty five, March third, twenty twenty-six rather than a string of digits, and one hundred twenty thousand dollars spoken in full. Then read the figure back against the source before moving on. The check is cheap at the moment of speaking and expensive a week later, when the surrounding sentence no longer tells you what you intended. If a number is central to the deal, say it twice and delete the duplicate in the edit. Redundancy on purpose is a mark of care, not of doubt.
Lists and conditions are where spoken structure most often collapses. Say first, second, and third explicitly, and start a new paragraph for each item if the document uses separate lettered clauses. For a conditional sentence, speak the condition first and then the consequence: if the seller does not deliver the certificate by the deadline, the buyer may terminate. That order matches how the clause will be read. After the list, dictate a short closing sentence so the reader knows the enumeration has ended. Then check the count, because three spoken items should produce three written items. If the number is wrong, return to the list before reading the rest of the paragraph.
Verification is a separate task, and it should happen after the draft exists rather than during speech. Read the passage on screen with the source beside it, one clause at a time. Compare defined terms, parties, dates, amounts, and cross-references against the original, and mark anything you cannot confirm. Do not fix as you read; note the problem and keep going, so you finish the pass with a complete list rather than a polished first page and an unread remainder. Voiskey keeps the text inside the drafting app, so the source and the draft can sit side by side without moving the file into another program.
Do a second pass for the things a spell check will not catch: a correct word in the wrong place, a defined term used before it is defined, a shall that should be may, and a cross-reference that points one section too far. Read the sentence as a reader would, and ask what obligation it creates. If you cannot state that obligation in one plain sentence, the clause needs work. Mark the spot and return with a decision. This pass is slower than the first, and it is the one that earns its time on any document another person will rely on.
When you are ready to standardize the routine, download Voiskey and use the same sequence on three real documents before you judge it. Speak one section, run the verification pass, and keep a short note of every correction you made. The note is more useful than an impression, because it shows whether errors cluster around names, numbers, or structure. After three documents you will know which conventions to keep and which to change. Set the shortcut, put your one-page standard beside the screen, and let the habit take less time to build than the argument about whether it works.
Build the check into the deliverable itself. Many teams ask a drafter to confirm that quotations were compared with the record, that defined terms are consistent, and that figures match the source. Turn those expectations into a three-line closing note at the end of your working file, with a date and your initials. The note is not decoration, because it tells the next reader which checks have already happened and which have not. If a check was skipped because a source was unavailable, say so plainly. An honest gap is easier to close than a silent one, and reviewers trust a drafter who marks the boundary of their own work.
Repetition is what turns a procedure into a habit. Choose a fixed opening for every drafting session: open the file, place the cursor, state the standard, and read the term list aloud. Then dictate in clauses, correct in speech, and stop at a natural boundary. The closing is equally fixed: one verification pass, one judgment pass, and one note about gaps. Twenty minutes of this is enough to feel the difference, and a week of it is enough to see which parts still cost you time. Keep the steps short enough that you will actually perform them on a busy afternoon, and write the opening and closing on a card until they become automatic.
Keep a small error log and review it weekly. For each session, record the type of error rather than the whole sentence: a name misspelled, a number transposed, a list item dropped, a defined term varied. After a week, count the categories. A pattern of name errors suggests you should spell names aloud, and a pattern of dropped list items suggests you should dictate the count as you go. This is ordinary process improvement, and it works because you change one habit at a time. A log with three categories is more actionable than a folder of corrected documents. Review it at the end of each week, and change only the habit that produced the most entries.
Share the conventions with anyone who drafts with you. A short written standard, the term list, and the closing note are enough for a colleague to produce a draft you can review without relearning their habits. If your group uses the shared vocabulary and workflows in the team plan, names and acronyms you confirm once can carry across the group, which helps in a matter with many contributors. Whether you work alone or with others, the goal is the same: the next reader should not have to guess which phrases were verified and which were spoken quickly. Say the conventions out loud once when you hand over the file, and leave the list where the next drafter can find it.
Finally, decide when not to dictate. Highly negotiated language, a sentence that has been through six rounds of comments, and anything you would normally type slowly while staring at a clause are poor candidates. Dictation is strongest when the substance is clear and the wording is yours to shape. Reserve typing for the sentences where the choice of a single verb is the work. That division keeps the speed advantage where it helps and keeps your attention where precision is decided. A tool used selectively is easier to trust than one used out of principle. Keep the typed sentences in a short list so the next session starts with a known division of labor.
Voiskey is an AI voice typing app. You press a shortcut, speak, and text appears at the insertion point in the drafting app you already use. It removes filler words, stutters, false starts, self-corrections, and grammar slips, so a spoken repair resolves into the sentence you meant. You still compare defined terms, figures, and quotations with the source before relying on any passage.
Voiskey learns names, jargon, acronyms, and spelling preferences as you use it, which helps repeated defined terms arrive the same way. Read your term list aloud at the start of a session, confirm the first use of each label, and keep the list beside the screen. On the team plan, shared vocabulary can carry confirmed terms across a group of drafters working in the same matter.
Yes. Voiskey is system-level: you press a shortcut, speak, and the text appears at the insertion point in any app or text field. For legal work this means dictation lives inside the drafting app, with no export from a separate suite. You check the passage in the same place you wrote it, beside the source you are comparing against.
Treat the check as a separate pass. Read the passage with the source beside it, one clause at a time, and compare defined terms, parties, dates, amounts, and cross-references. Note problems without fixing them, finish the list, then make corrections. Follow with a judgment pass that asks what obligation each sentence creates before you state that the passage is ready.

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