Audit habits, define voice rules, and test on real documents.

Building a Legal Dictation style guide starts with evidence from the team's own drafts, not with a list of preferences. Collect recent documents that were dictated and later edited, and mark the corrections that recur. Look for patterns: names that are repeatedly respelled, numbers that are converted to digits inconsistently, citations that are spoken one way and written another, and punctuation that is added by hand. Group the corrections by type. Write a short audit note with the counts and two examples for each pattern. A guide built from recurring corrections is adopted because it solves a problem the team already recognizes.
Interview the people who dictate and the people who edit. Ask the drafters which phrases cause the most retyping and which documents they avoid dictating. Ask the editors which defects they fix most often and which ones matter most to clients. Record the answers without merging them, because a drafter's frustration and an editor's quality concern often point to different rules. If a partner has a house style that differs from the team's habit, record the difference and the reason. A style guide that ignores the people who will use it becomes a document nobody opens after the first week.
Review the existing written standards before writing a new one. Collect the firm's formatting manual, the court's formatting rules, the client's outside counsel guidelines, and any prior style note. Note the rules that already cover dictation and the rules that only cover written drafting. A dictation guide should not repeat a formatting manual; it should translate the formatting rules into voice instructions. If a court requires a specific citation format, the guide should say how to speak the citation so the written result matches. Reference the source rule rather than restating it from memory. Keep a dated copy of each source rule in the project folder, so a later reviewer can see which version the guide relied on.
Scope the guide to the work the team actually dictates. List the document types: client letters, demand letters, motions, briefs, contracts, discovery responses, and internal memos. Decide which types the first version covers and which wait for a later revision. Name the language or languages the team uses, since a bilingual practice needs rules for each. Decide who owns the guide and who approves a change. A narrow first version that covers the most common documents is more useful than a comprehensive guide that is never finished. Write the covered document types on the first page and note the types that are out of scope for now, so a drafter knows when to fall back to typing. Review that list at the first quarterly revision, because the mix of work changes.
Write the voice rules as instructions a person can follow while speaking. Start with sentence structure: speak in complete sentences, state the subject and the verb, and avoid nested clauses. Next, punctuation: say period, comma, and new paragraph, or explain how the app handles punctuation automatically. Next, numbers: say whether to speak a number as words or digits and how to handle dates, amounts, and section numbers. Next, citations: say how to speak a case name, a statute, and a page reference. Each rule should show a spoken example and the written result. Keep each rule on its own line and number the rules, so a drafter can cite a rule by number when a question comes up during a review.
Write the rules for names and defined terms. Record how to speak a party name for the first time and how to refer to it afterward. Record how to dictate a defined term and where the definition belongs. Record how to correct a name that came out wrong, since a correction spoken at the insertion point is faster than retyping the sentence. If the team uses acronyms, record the expansion and the short form. A short list of names and terms, kept with the guide, prevents the same spelling debate from recurring in every document. Store that list next to the document template, so it is open while the drafter speaks.
Write the rules for editing and correction. Explain the Speak-Polish-Type-Edit routine in plain terms: speak the draft, review the polished text, type or dictate the corrections, and edit the final passage. Record how to mark a place that needs a citation or a figure that must be confirmed. Record how to handle a sentence that needs to be moved, since a spoken instruction to move text may be slower than a quick edit. The correction rules matter because most dictation time is lost in fixing, not in speaking. Add one worked example that shows a spoken sentence, the polished text, and the correction, so the routine is concrete rather than abstract.
Write the rules for document structure. Record how to dictate a heading, a numbered list, a block quote, and a signature block. Record how to start a new section and how to mark an exhibit reference. Record the order in which the sections of a common document should be dictated, since a fixed order reduces reordering later. If the team uses templates, record how the dictated text fits into the template. Structure rules turn a free-form transcript into a document that is close to its final form before the first edit. Keep a sample document that follows the structure, and use that sample in training so the rules are shown rather than described.
Build the vocabulary list from the audit and the document set. Include party names, client names, expert names, institution names, statutory terms, and recurring phrases. For each entry, record the correct spelling, the short form, and a note on how to speak it. Mark the entries the app should learn, since Voiskey learns names, jargon, acronyms, and spelling preferences. Keep the list in a format the team can update, with a date and an owner for each change. A vocabulary list is the most-used part of a dictation guide, because it fixes the errors that cost the most time.
Group the vocabulary by practice area and by document type. A litigation team needs case names and procedural terms; a corporate team needs entity names and closing terms; a regulatory team needs statutory and agency terms. Grouping lets a drafter load only the list that applies to the current matter. Note the terms that appear across areas so they are not duplicated with different spellings. A grouped list is easier to maintain and easier to teach than one long alphabetical list. Add a short header to each group that names the matters it covers and the date it was last reviewed. When a matter closes, move its terms to an archive group instead of deleting them, because a later matter may reuse the same names.
Record the phrases that the team says often and writes rarely. Legal drafting has stock phrases, and a dictation guide should say which ones to speak in full and which to abbreviate. Record the preferred phrasing for common transitions, such as therefore, however, and accordingly. Record the phrases the team wants to avoid, such as filler openings and redundant pairs. Keep the phrase list short, because a long list of preferred phrases is hard to remember and easy to ignore. The goal is consistency, not a new dialect. Review the phrase list at the same time as the vocabulary list, since the two are edited together in practice and a phrase often turns into an entry.
Record the exceptions and the matter-specific terms. Some matters have a defined term that conflicts with the general list, and some clients have a preferred spelling that differs from the firm's. Record the exception, the matter, and the reason. If a term is used only in one matter, keep it in the matter file rather than in the general list. If a client's preference should apply to all of that client's work, add it to the client section. Exceptions recorded in the right place keep the general list clean and still give the drafter the right answer. Note who approved each exception, so a drafter can confirm it without a new debate.
Test the guide on real documents before publishing it. Choose three documents of different types, dictate each one using only the guide, and record the time spent and the corrections needed. Compare the result with the team's current output. Ask a drafter who did not write the guide to run the same test, and note where they hesitated or misread a rule. Voiskey helps here because it learns names, jargon, acronyms, and spelling preferences, so the vocabulary list can be tested directly in the drafting app. Download Voiskey before the test and dictate the sample documents at the insertion point.
Review the test results rule by rule. For each rule, note whether it was followed, whether it helped, and whether it caused confusion. A rule that nobody follows is either unclear or unnecessary; decide which and revise or remove it. A rule that produced a consistent result should stay, even if it feels unusual. Keep the spoken examples that worked and replace the ones that did not. A guide tested on real documents is shorter than a guide written from theory, and it is far more likely to be used. Keep the revised rules in the same order as the test log, so the next tester can compare the two side by side.
Test the vocabulary list on the names that caused the most errors. Dictate a paragraph that includes each difficult name and confirm the spelling. Add the names that still fail to the list and note how to speak them. Voiskey adapts punctuation, formatting, and tone to the document you are working in, so the test should use the same document types the team drafts. Download Voiskey when the team wants to test the guide across several practice groups and keep one editing routine. Record the test date and the version of the list that was used. Compare the spelling before and after the list is loaded, and note the names that still need a spoken hint.
Collect the test feedback and decide what changes. Keep a log with the tester, the document type, the rules tested, and the corrections observed. List each proposed change with the reason and the person who approves it. If a rule conflicts with a court requirement, the court requirement wins and the guide should say so. If two practice groups need different rules, write separate sections rather than a compromise that serves neither. Download Voiskey and attach the test log to the guide so the next revision starts from evidence. Set a date for the next test, so the guide is reviewed again after the first set of changes is published.
Publish the guide in the place where the team already looks for instructions. Keep it short, use headings that match the document types, and put the vocabulary list in an appendix that can be updated separately. Add a version number and a date. Send a short announcement that names the three rules most likely to save time. Do not publish a guide longer than the team will read; a short guide with a strong vocabulary appendix is more effective than a long manual. Make the owner and the change process visible on the first page. Link the guide from the document template, so a drafter can open it from the place where the work starts.
Train the team with a short session and a practice document. Walk through the Speak-Polish-Type-Edit routine, the punctuation and number rules, and the vocabulary list. Ask each participant to dictate one paragraph and compare the result with a partner. Collect the questions and add the answers to a short FAQ at the end of the guide. Voiskey supports 100+ languages and translation when the team dictates in more than one language, and it adapts formatting to the document. Download Voiskey to prepare the training document and the FAQ in one pass. Keep the recording of the session and the practice document in the same folder as the guide, so a new team member can catch up without waiting for the next session.
Maintain the guide on a fixed cycle. Review the vocabulary list monthly, because names and matters change faster than rules. Review the rules quarterly, and after any court rule change or client guideline update. Record each change with a date and a reason. Retire rules the team no longer uses. Voiskey supports a team plan with shared vocabulary and workflows, which helps when several practice groups use the same guide and want consistent terms. Download Voiskey and keep the guide, the list, and the change log in one shared location. Put the review dates on the first page, so the next review is visible to everyone who opens the guide.
Measure whether the guide is working. Track the corrections that recur, the time spent per document type, and the questions the team asks. Compare the results with the audit that started the project. If a defect disappears, note which rule fixed it; if a new defect appears, add it to the next audit. Review the guide with the people who use it, not only with the people who wrote it. A style guide is a living document, and its value depends on a short, evidence-based revision cycle rather than on a perfect first edition. Report the results in the same format as the audit, so the team can see the change over time.
Voiskey is an AI voice typing app for the desktop. Press a shortcut and speak a sample passage using the guide's rules, and the text appears at the insertion point in the document you already have open. It removes filler words, stutters, false starts, and grammar slips, so each test shows the written result the rule produces rather than a rough transcript.
Yes. Voiskey learns names, jargon, acronyms, and spelling preferences, which helps when a guide's vocabulary list covers party names, defined terms, and recurring phrases. The rules still live in the guide, and a drafter checks the written result against them. A team plan adds shared vocabulary and workflows for groups that want consistent terms.
Press a shortcut and speak the passage, and the text appears at the insertion point. Voiskey removes filler words, stutters, and false starts and adapts punctuation, formatting, and tone. The polish step is where you apply the guide's rules for numbers, citations, and names. At up to 220+ words per minute, the routine produces a draft for the edit pass.
Yes. Voiskey is system-level, so text appears at the insertion point in whatever app or text field holds the test document. You speak passages and corrections directly into the file and revise them in the same place, with no separate suite to open. The workflow is Speak-Polish-Type-Edit, so each test reflects the guide's real output.

Download Voiskey for Mac and Windows and keep every draft moving from first note to final check.
Use it across macOS, Windows, iOS, and Android