A phrase set and a render check that keep dictated documents consistent.

Spoken Commands for Document formatting work best when the destination is settled before you open your mouth. Decide whether the result is a memo, a one-page brief, a checklist, or a section of a larger report, and name the elements that format requires. A memo needs a title, a date line, and short headed sections. A brief needs a summary box and a recommendation. A checklist needs numbered steps with owners. Write those elements down in the order they should appear. When the shape is decided in advance, every spoken instruction has a target, and you spend less time moving blocks around after the text arrives.
Inventory the elements you use most: headings at two levels, bulleted lists, numbered steps, short tables, quoted passages, and captions. Give each element one name and use that name every time. If you call the same thing a heading on Monday and a title on Tuesday, your instructions will drift and the document will show it. Put the inventory in a style note beside the template. Include one example of each element in the note, so a reader can see the expected result rather than infer it. A small, named vocabulary is the foundation of consistent formatting. Name them once and keep the list short.
Settle the quiet decisions that cause most cleanup: numbering style, capitalization in headings, spacing before and after lists, table header wording, and whether captions sit above or below their object. Write these rules as single sentences in the style note, not as a paragraph of preferences. Each rule should be checkable by looking at the page for a second. When a rule is hard to check, it is usually too vague to follow. Keep the list under a dozen items. A dozen checkable rules prevent more rework than a forty-page style guide that nobody reads during a busy afternoon.
Define what a finished page looks like before you dictate. A finished page has the required elements, in the required order, with the agreed styles applied and no leftover placeholder text. Test the definition on an existing document: does the definition let you spot what is wrong without rereading the prose? If not, tighten it. Then save a short sample that meets the definition and keep it beside the style note. The deliverable for this stage is a style note with named elements, a dozen checkable rules, and one sample page that a colleague could match. Save the list with the template.
Build a phrase set of about ten instructions and use them exactly. Typical entries include new heading one, new heading two, start bullet list, end bullet list, start numbered list, new table with three columns, quote this, plain paragraph, and caption below. Say the instruction first, then the content, with a short pause between them. The pause matters because it separates the command from the words that belong in the document. Write the phrase set on a card and keep it visible for the first week. Ten phrases cover most business documents, and a set that small is easy to remember under pressure. Keep the card beside the keyboard.
Phrase lists and tables so their boundaries are unmistakable. For a list, say the start phrase, then each item as a complete sentence, then the end phrase. For a table, say the number of columns and the header names before the first row, then say each row as a sequence of values. Never describe a table in prose and hope the shape appears. If an item contains a comma, say comma or rephrase the item so the value boundary is clear. These habits reduce the edits that happen after insertion, when the document is harder to change safely and the column count is easy to lose.
Avoid words that mean different things to different readers. Terms like format this, make it nice, and clean it up give no instruction that can be followed or checked. Replace them with a named element or a specific rule from the style note. Say new heading two rather than make this a subtitle, and say start bullet list rather than add some bullets. When you catch yourself using a vague phrase, stop and restate it. One specific instruction is worth three corrections later, and the restatement takes two seconds. Say the element name first, and let the result follow the name.
Practice the set on a sample page before you use it on real work. Take a one-page document with a heading, two lists, and a small table, then rebuild it from scratch by voice while the original sits beside you. Compare the two pages element by element. Mark every phrase that produced the wrong element and rewrite it. Repeat the drill once a week until the phrases are automatic. The drill is short, it uses no real work, and it turns a list on a card into a habit you can rely on when a deadline is close. Say the element name twice if the result is wrong.
Speak the outline before you speak the prose. Say the title, then each heading in order, then one line under each heading describing what belongs there. Stop and read the outline on screen. If the order is wrong, fix it now, while the document is only a dozen lines. An outline is cheap to change and expensive to discover later. When the outline is right, speak each section in its own pass. This sequence keeps you from producing a long block of text that has to be cut apart and reorganized after the fact. Read the outline aloud to catch a missing section.
Draft one section at a time and review each section before starting the next. Read the inserted text, check that the heading matches its content, and confirm the element type is correct. Small errors are easier to catch while the section is short and the context is fresh. If a section grows beyond a screen, split it with a new heading rather than continuing. A document that is built section by section tends to keep its structure, because each pass ends with a visible, checkable unit rather than a growing wall of text. Keep a list of the sections you split so the outline stays honest.
For tables, dictate the header row first and confirm it before adding rows. Say the column names in the order they should appear. Then add one row at a time, saying each value in sequence and pausing between rows. After three rows, stop and check the alignment. A table that drifts after the third row is usually a sign that a phrase was skipped or a value was spoken out of order. Fixing the header and the first rows early prevents a long table from arriving with a scrambled middle. Keep the table narrow enough to read without scrolling sideways.
Refine by moving and merging, not by retyping. When a paragraph belongs under another heading, say the move instruction with a clear anchor: move this paragraph under heading two, or merge this list with the list above. Confirm the result after each move, because spoken edits act on what is selected or nearest, and a wrong anchor changes the wrong block. If two attempts produce the same wrong result, switch to manual editing for that operation. The goal is a clean page, not a perfect record of doing everything by voice. Save a copy before a batch of moves so you can compare the result.
Read the rendered page, not the editing view. Change to the view a reader will see and check three things in order: the heading hierarchy, the lists, and the tables. A heading that looks right in the editor can break the outline in the rendered page, and a list that looked aligned can lose its numbering. Before a formatting-heavy week, download the current version of Voiskey on the computer you use for documents, so a difference you notice reflects the page rather than a stale build. Then read the whole page once at normal reading speed, as if you were the recipient.
Check consistency with a short scan rather than a full reread. Look at every heading and confirm the capitalization rule. Look at every list and confirm numbering and indentation. Look at every table and confirm the header row and the column count. Look at the spacing before each heading and after each list. These four passes take two minutes on a normal document and catch the errors readers notice first. Keep the scan order fixed, because a changing order means a missed element. Consistency is what makes a document look deliberate. Mark each check on a sticky note as you finish it.
When the rendered page differs from what you intended, fix the source rather than patching the output. A manual space added to align a list will break the next time the list changes. Select the element, apply the correct named style, and remove the manual adjustment. If a table has an extra column because a value was spoken twice, correct the row rather than hiding the column. Keep a short note of each fix and the phrase that caused it. That note is the raw material for improving the phrase set, and it turns a one-off correction into a lasting improvement.
Finish with a delivery check. Confirm the title, the date, the author line, and any required footer. Confirm that no placeholder text remains and that every caption belongs to its object. Read the first and last paragraphs aloud, because those are the parts readers remember and the parts most likely to be edited late. Save the reviewed page as the sample for the next document of this type. The deliverable for this stage is a rendered page that passes the scan, a short note of fixes, and one sample kept beside the style note. Keep the sample in the same folder as the template.
Decide the document shape and name each element before you speak. Say the heading or list phrase first, pause, then say the content, and check the result before moving on. Voiskey adapts punctuation and formatting to what you are trying to do, so a clear instruction produces a cleaner element than a vague request.
Keep about ten phrases: two heading levels, bullet and numbered lists, a table with a stated column count, a quote, a plain paragraph, and a caption. Say the phrase first and the content second. Add no phrase you cannot check on the rendered page, and retire any phrase that causes repeated corrections.
Switch to the rendered view and scan in a fixed order: headings, lists, tables, then spacing. Confirm the numbering, the table header, and the capitalization rule. Read the first and last paragraphs aloud. Fix the source element rather than adding manual spacing, and record the fix so the phrase set can improve.
Yes. Keep one phrase card and one style note in the shared folder, name an owner, and align both with the templates the group uses. New members rebuild a sample page by voice and compare it with the original. Update the card with a date whenever a template or phrase changes, and review the set each quarter.

Download Voiskey for Mac and Windows and dictate a clean, well-formatted page today.
Use it across macOS, Windows, iOS, and Android