Turn Rough Voice Notes Into Publishable Writing

Capture messy on purpose

The point of voice capture is volume of raw material, and phrasing well while speaking works against that. Say the whole idea in one go, including the parts you would delete, because you can cut text far faster than you can generate it.

• Finish every sentence you start, even if the sentence is bad.
• Say the obvious version first. Precision comes in the editing.
• Talk through the argument as if explaining it to one specific person.
• When you lose the thread, say the next thing you know and keep going.
• Do not stop to check whether a word landed correctly.

Ten minutes of loose talking produces more usable raw material than an hour of careful sentence-by-sentence dictation. The unfinished sentence is the only real enemy here, since a fragment gives the model no context and gives you nothing to edit. Half-formed thoughts are fine; half-formed sentences are not.

Know what cleanup already handled

Before you start editing, know which problems are gone so you do not spend attention re-solving them. This is the difference between opening a transcript and opening a draft.

Auri Voice runs that cleanup locally on Mac by default, so it applies with the network off and the quality does not depend on your connection. What survives is the work that requires judgment, which is where your time belongs. If your tool sends text out for cleanup, expect a rougher starting point on days when you are offline.

Pass one: structure

Structure first, always. Fixing sentences in a paragraph you are about to delete is the most common way to waste an editing session. Read only for shape on this pass and resist touching wording.

1. Read the draft once and write a one-line summary of each paragraph in the margin.
2. Reorder those lines until the argument runs in the order a reader needs.
3. Move the paragraphs to match, without rewriting them.
4. Delete the first thirty seconds of the capture, which is almost always warm-up.
5. Merge any two paragraphs that make the same point twice.

Spoken drafts tend to bury the conclusion, because you talk your way toward it. Look for the sentence where you finally said what you meant and move it up near the top. That single move improves most dictated drafts more than any amount of sentence polishing, and it takes about a minute once you know to look for it.

Pass two: facts

Facts get their own pass because they need a different kind of attention. Reading for accuracy while reading for flow means you catch neither, and fluent cleanup makes wrong details easier to miss.

• Check every name against the way that person or product spells it.
• Read numbers aloud digit by digit, including prices and counts.
• Confirm dates and weekdays agree with each other.
• Verify every claim you would not want to defend, or remove it.
• Retype identifiers rather than trusting a dictated URL or address.

Do this pass with the source open: the email, the spreadsheet, the meeting notes. Working from memory is how a plausible wrong figure survives into a published draft. If a claim cannot be checked in ten seconds, either soften it into something you can support or cut it, since a hedged accurate sentence beats a confident wrong one.

Pass three: voice

Last comes the pass that makes it sound like a person wrote it. Dictated prose has real advantages here, since spoken sentences carry rhythm that typed sentences often lack. The work is trimming, not rewriting.

1. Read the draft aloud. Every place you stumble is a sentence to shorten.
2. Cut hedges: kind of, sort of, I think, a bit, probably.
3. Replace vague nouns with the specific thing you meant.
4. Break any sentence longer than about thirty words.
5. Cut the weakest twenty percent of the whole draft.

The final cut is the one people skip and the one readers notice. Spoken drafts overexplain, because in conversation you keep talking until the other person nods. On the page that turns into three sentences doing the work of one. Reading aloud catches it reliably, which is fitting for something you spoke into existence in the first place.

A repeatable twenty-five minute session

Put the passes on a clock so the process survives a busy week. This fits into one focused block and produces a finished short piece or a solid section of a longer one.

1. Five minutes: capture by voice, loose, without stopping.
2. Ten minutes: structure pass. Reorder, merge, delete the warm-up.
3. Five minutes: facts pass with sources open.
4. Five minutes: voice pass, read aloud, cut twenty percent.

Two habits make it repeatable. Label each capture with a two-word topic so a stack of notes stays sortable, and keep captures to one idea each so the structure pass has clean pieces to move. Searchable local history helps on the days when a browser document eats a paragraph; Auri Voice keeps that history on your Mac. Run the block twice and it stops feeling like a process and starts feeling like how you write.

FAQ