Dictating an Email with a Table or List

A repeatable way to speak lists and table details into a readable message.

Voiskey Voiskey Team
Gmail DictationChrome ExtensionDictating Email Table

Decide the Shape Before You Speak

Dictating an Email with a table or a list goes badly when you decide the structure halfway through. Before you speak, sketch the shape in a scratch note: a short intro, an ordered list, and a closing action. Count the items you plan to include and say the count out loud once. If the content needs columns, decide whether you can express each row as one sentence instead. A clear shape tells you when to pause and when to move to the next item, which keeps the spoken draft readable and easy to review. Write the number, the intro promise, and the closing action on one line so the shape fits on a small note.

Choose between a list and a paragraph based on the reader's job. A list helps when the reader must compare items, check completion, or pick one option. A paragraph helps when the items form a single argument and the order is less important than the flow. Write your choice in the scratch note and stick to it. Mixing the two forms without a reason produces a draft that looks busy but reads slowly. The reader should be able to tell at a glance why the items are separated. If two readers need different formats, send two short messages instead of mixing a list and a paragraph.

Name the columns or fields before you dictate them. For table-like content, write the field names in the scratch note and repeat them in the same order for each row. If you say owner first for one row and deadline first for the next, the result is confusing even when every fact is correct. Keep the order fixed and speak one row per sentence. When the field names are stable, the reader can scan the block without rereading each line to find the same kind of value. Repeat the field order in the scratch note before every row, and check the first row against it.

Set a limit on how much structure one message should carry. A list with three to seven items is easy to scan; a list with twenty items belongs in an attached document or a separate message. If the content exceeds the limit, split it by decision or by owner rather than by page. Say the split plan aloud before you begin. A message that respects its own scope is more likely to be read and acted on than a dense block that tries to carry everything at once. Write the split rule in the note so the next person can make the same choice without asking you.

Speak Lists as Ordered Items

Speak list items in a clear, numbered rhythm. Say the number, then the item, then a short pause before the next number. Voiskey adapts formatting and punctuation to what you are doing, so a steady cadence produces a cleaner list than a rushed stream. Keep each item to one sentence if possible. If an item needs detail, finish that item before moving on. The reader should be able to match each number with one action or one fact. If an item runs longer than one sentence, treat that as a sign to split it into two numbered items. Two short items are easier to scan than one crowded line.

Put the most important item first. Readers often stop after two or three lines, so the item that requires action should not be buried in the middle. If the order is naturally sequential, such as steps in a process, keep the sequence and say the numbers explicitly. Add a short lead-in sentence that tells the reader what the list contains and how many items to expect. That sentence is a promise the list must keep. Put the action item at the top and label it clearly, so a reader who stops early still sees the request. The lead-in should name the list and the number of items it contains.

Keep the grammar parallel across items. Start each item with the same kind of phrase, such as a verb, so the list reads as one unit. If the first item begins with a verb and the second begins with a date, the reader has to reset. Say the pattern aloud once before you record the list. Parallel phrasing is not a style preference here; it is what makes a spoken list survive the conversion into a written message. If two items begin with different parts of speech, rewrite the second one so the pattern holds. Parallel openings make the whole list read as one block.

Stop speaking when the list is finished and check the count. Count the visible items and compare them with the number you announced in the lead-in. If one item was dropped or merged, add it before you continue. Look for a stray word that joined two items because you paused too briefly. Fix that boundary first, then review the content. A list with the right facts in the wrong structure still costs the reader time. If the count is wrong, do not continue until the list matches the number in the lead-in. A quick count now saves a confused reply later.

Handle Tabular Content Carefully

A true table is harder to dictate than a list, so decide whether you need one. If the reader only needs a few values, write each row as a sentence with the field names in the same order. For example, state the item, the owner, and the date in one line. This reads well in an email and avoids the alignment problems that appear when spoken text is placed into columns. Use a real table only when the comparison across rows is the point, and build that table in the message after the draft is clean. Do not force a table into a message that only needs three values.

Say the field names before the first row, not after it. The reader needs a frame before the values arrive. Keep the field order identical for every row, and pause between rows so the boundaries are obvious. If a value is missing, say the field name and the word pending rather than skipping it. Skipping a value silently makes the row look complete when it is not. A visible gap is easier to resolve than a hidden one. Repeat the field names in the same order for every row, even when a value is pending. A skipped value hides a gap that the reader will find later.

Watch for numbers that sound alike. Say amounts with units, dates with the month name, and identifiers one group at a time. If two values are easy to confuse, add a short qualifier such as the start date or the total amount. Do not rely on the reader to infer which column a number belongs to. When you review the draft, check each number against the scratch note, especially when the page lagged during dictation. Say the unit after each number, and name the month instead of using a numeric date. Two similar numbers in one row deserve a short label each.

Keep the table small enough to verify. If a row contains more than four fields, move part of the detail into a sentence above or below the table. A smaller table is easier to check and easier to read on a small screen. If the content must stay large, split it into two tables with clear labels. The goal is a message the reader can verify quickly, not a document that reproduces a spreadsheet. If a table needs more than four fields, move the extra detail into a sentence above the block. Smaller tables are easier to verify on a narrow screen.

Review Structure in Your Message Field

When you download Voiskey, you can keep the whole structured draft inside your message field rather than moving it between tools. Speak the intro, the list, and the closing at the insertion point, then review the structure in place. Because Voiskey adapts formatting, punctuation, tone, and word choice to what you are doing, a spoken list can arrive with readable separators and consistent phrasing. Read the block as a reader would and check that every item starts on its own line. Keep the scratch outline visible beside the field so you can compare the structure without leaving the draft. Leave it open until the message is sent.

Check the boundaries first, then the content. Scan for two items that merged into one sentence, a missing number, or a lead-in that promises five items while six appear. Fix the structure before you polish the language, because a merged item can hide a missing fact. If a row lost its field order, restore the pattern from the scratch note. Voiskey removes filler words and false starts, but it cannot decide which column a value belongs to. That judgment stays with you. Scan the lead-in number first, then count the visible items, then check the field order for each row.

Read the list aloud as a final test. If an item is hard to say in one breath, it is probably too long for a list. Split it or move the detail into prose. If two items sound nearly identical, merge them or make the difference explicit. A spoken read also catches a date that sounds wrong even when the digits are correct. Use the same voice and pace you used to dictate, so the review reflects the draft you actually produced. If the spoken read sounds choppy, the list is probably carrying too much detail per item. Move the extra detail into prose and keep the item short.

Close with a single action line that tells the reader what to do next. If the list is for reference only, say so and remove any accidental request. If the reader must choose an item, name the decision and the deadline. Place that line after the list, not inside it. A structured message succeeds when the reader can act without hunting through the rows for the instruction. Make the action line separate from the list so it is not mistaken for another item. If the reader must choose, name the options and the deadline in that line. A separate line is easier to act on.

Reuse a Formatting Pattern

Download Voiskey on each computer where you write, and save your best structured messages as patterns. Keep a small file with the intro sentence, the field order, and the closing action for the lists you send often. When a similar message arrives, speak the pattern and replace the values. A stable pattern reduces the chance that a field is dropped under time pressure. It also makes your messages easier for the same reader to scan across weeks, because the shape stays familiar. Keep the pattern in the same file as your scratch outline so both are open when you write.

Vary the content, not the skeleton. A weekly status list and a handoff list can share the same field order while carrying different facts. Keep the labels consistent and change only the values and the closing request. If a new message type needs a different skeleton, add it to the file instead of bending an existing one. Two clear patterns are better than one overloaded pattern that tries to cover every case. If a new message does not fit a pattern, start a second one instead of stretching the first. A pattern that covers everything usually serves no one well.

Review the pattern after a few uses. If readers repeatedly ask for the same missing detail, add that field to the skeleton. If a field is always blank, remove it. Ask one frequent reader which part of the message they use most, and put that part first. Voiskey learns names, jargon, acronyms, and spelling preferences, so consistent labels also reduce spelling corrections over time. The pattern should evolve from actual use, not from a one-time design. Ask one frequent reader which field they check first, and move that field to the front. A pattern revised from feedback is easier to trust than one designed in isolation.

Teach the pattern to anyone who writes on your behalf. A short example with the field order and one filled row is enough. Include the rule for missing values, such as writing pending instead of skipping the field. When several people follow the same structure, the reader sees a consistent format regardless of who sends the message. That consistency is the real benefit of a reusable pattern, and it costs far less than rebuilding the structure for each send. Include a filled example with the pattern so a new writer can see the expected shape. Consistency across senders is the main reason to reuse a skeleton.

FAQ s

Decide the list shape first, then speak each item in order with a short pause between items. Voiskey types at the insertion point and adapts formatting and punctuation as you go. Announce the item count in the lead-in, review the boundaries, and confirm that every item arrived.

Voiskey adapts formatting and punctuation to the task, but you still choose the structure. For table-like content, speak the field names in a fixed order and say one row per sentence. Review the alignment and values in your message field, because the judgment about which value belongs where stays with you.

Say the number before each item and pause between items. Keep the grammar parallel and repeat the field order for every row. Voiskey removes filler words and false starts, which makes the boundaries easier to see. After dictation, count the items and compare them with the number you announced.

Use the Speak-Polish-Type-Edit workflow. Speak the intro, the list, and the closing in short blocks, let Voiskey clean the text, then review the structure and values before you send. Keep the scratch outline beside the message field so you can check the order without leaving the draft.

Say less. Get more
Say less. Get more
Say less. Get more
Say less. Get more
VoiskeyVoiskey

Your voice, amplified.

Download Voiskey for Mac and Windows to speak structured lists and table details into any message field.

Use it across macOS, Windows, iOS, and Android

Use it across