From Messy Speech to Polished Prose: How AI Text Cleanup Actually Works
A walkthrough of the three jobs that turn a raw speech transcript into clean text, from filler removal to grammar correction to restructuring, and how to check the result.
Say something into your microphone the way you would say it to a colleague, and the transcript might read: "So um I think what we should, what we really need to do is like basically the the model needs to, you know, converge faster so that um so that we can actually ship this by Friday." Every word may be transcribed correctly. The result is still hard to read, because spoken language is full of fillers, false starts, and repetitions that we never notice when listening.
AI text cleanup is the step that turns an accurate transcript into text you would actually send. It does three jobs: removing fillers, correcting grammar and punctuation, and restructuring sentences that were built for the ear rather than the page. Understanding those jobs, and where each can go wrong, helps you get better output from any dictation tool and know when to trust the cleanup versus when to edit by hand.
The cleaned version of that sentence: "The model needs to converge faster so we can ship this by Friday." Same meaning, far fewer words, and actually readable.
What Raw Transcription Actually Looks Like
Modern speech recognition can be very accurate at capturing what you said. OpenAI's Whisper paper reports performance close to professional human transcribers on one English test set.[1] But accuracy and readability are different problems. A transcript can contain every spoken word correctly and still be unreadable, because natural speech includes hesitations ("um," "uh"), discourse markers ("so," "like," "basically"), false starts, and repeated words.
Here is an illustrative example of natural speech, transcribed verbatim:
```
"OK so basically what I wanted to, I wanted to talk about is um the quarterly
results were actually pretty good like we we beat the the revenue target by
about twelve percent which is you know not bad at all and I think I think
going forward we should probably um double down on the the enterprise segment
because that's where that's where the growth is coming from."
```
And the same content after cleanup:
```
"The quarterly results were strong. We beat the revenue target by about
twelve percent. Going forward, we should double down on the enterprise
segment because that's where the growth is coming from."
```
The raw version is 69 words. The cleaned version is 32. The facts are the same. That is the job: not summarizing, not paraphrasing, but removing the scaffolding of live speech so the structure underneath shows.
Stage 1: Filler Word Detection Is Harder Than You Think
The naive approach to filler removal is a word list: find every "um," "uh," "like," "you know," and "basically," then delete them. That breaks quickly. "So" is a filler in "so, um, I think we should" but a conjunction in "so the model converges." "Like" is a filler in "it was like really good" but a preposition in "languages like Python and Rust." A blunt list mangles both.
Context-aware approaches look at the surrounding words before deciding. One common framing is sequence labeling: each token gets a label such as keep or remove, with categories like hesitation, discourse marker, false start, or repetition. Large language models can do a similar job when prompted to remove disfluencies while keeping the speaker's words.
Here is what token-level labeling looks like for an illustrative sentence:
```
Token: "So" "um" "I" "think" "the" "so" "the" "model"
Label: FILLER FILLER KEEP KEEP FILLER KEEP KEEP KEEP
```
The first "so" is a filler because it leads into a hesitation. The second "so" works as a conjunction. The "the" before the false start is removed too. A word list cannot make those distinctions.
The trickiest cases involve hedging. "I mean," "you know," and "I think" sometimes carry real meaning. In "I think we should delay the launch," the "I think" signals uncertainty the speaker wants to keep. In "I think, I think we should," the first instance is a false start.
| Filler type | Example | How hard to detect | Common false positive |
|---|---|---|---|
| Hesitation markers | um, uh, er | Usually easy | Rare |
| Discourse markers | so, like, basically, well | Harder | Conjunctions and prepositions |
| False starts | "I wanted to, I wanted to talk" | Harder | Intentional repetition for emphasis |
| Repetitions | "the the," "we we" | Usually easy | Deliberate repetition in quotes |
| Hedging phrases | "I mean," "you know" | Hardest | Genuine uncertainty the speaker meant |
Stage 2: Grammar Correction Without Changing Your Voice
Once fillers are gone, the text has a different problem: it is grammatical in the loose way speech is grammatical. Punctuation is missing, sentences run together, and agreement can slip across long clauses. Homophones such as "their," "there," and "they're" also need choosing, because the speaker never had to pick a spelling.
The core constraint is preserving the speaker's voice. If someone dictates short, punchy sentences, cleanup should not merge them into flowing prose. If someone uses contractions, cleanup should not expand them. The goal is minimal intervention: fix what is broken, leave the rest.
Two families of approaches are common. Tagging approaches treat correction as a set of edits applied to each token: keep, delete, replace, or insert. The GECToR paper describes "a simple and efficient GEC sequence tagger using a Transformer encoder," and reports inference "up to 10 times as fast as a Transformer-based seq2seq GEC system."[2] Generative approaches, including sequence-to-sequence models and large language models, rewrite the sentence. They are more flexible, and more prone to unnecessary rewrites if not constrained.
Here is an illustrative post-filler sentence with three errors, and the edits a tagging approach would apply:
```
Input: "the model need to converge faster so we can ships this by friday"
Edits: [KEEP] [KEEP] [REPLACE:needs] [KEEP] [KEEP] [KEEP] [KEEP] [KEEP] [KEEP] [REPLACE:ship] [KEEP] [KEEP] [REPLACE:Friday]
Output: "The model needs to converge faster so we can ship this by Friday."
```
Three targeted edits. Sentence structure, word choice, and tone are untouched.
Speech produces some errors typing rarely does. A typist can see the subject while typing the verb. A speaker who starts with "the list of all the items that we reviewed" may say "were" instead of "was" because the nearest noun is "items." Cleanup has to handle these long-distance dependencies.
Stage 3: Restructuring Sentences That Were Never Meant to Be Read
Spoken syntax is not written syntax. When you speak, you build sentences incrementally: start a thought, add an aside, return to the main clause, correct yourself, and land on a conclusion. Written text usually puts the main point first and tucks details into subordinate clauses.
Sentence boundary detection comes first. Raw speech often arrives as one long run-on, and cleanup has to find the natural breakpoints. Then clause reordering moves the main point forward, pulls asides into their own sentences, and collapses nested clauses.
Three illustrative examples at increasing intensity:
Simple cleanup:
- Before: "We should update the docs and also we need to fix the login bug."
- After: "We should update the docs. We also need to fix the login bug."
Moderate restructuring:
- Before: "The thing about the new API is that it's faster but the problem is that it doesn't support batch requests which is what most of our users actually need."
- After: "The new API is faster, but it doesn't support batch requests. Most of our users need batch support."
Heavy rewrite (approaching the boundary):
- Before: "So what happened was the deploy failed because, and this is the part that really frustrated me, the CI pipeline didn't catch the type error because the tests were, they weren't updated when we refactored last sprint."
- After: "The deploy failed because the CI pipeline didn't catch a type error. The tests hadn't been updated since last sprint's refactor."
The third example is where restructuring approaches the line. "This is the part that really frustrated me" carried feeling the speaker chose to include. Conservative cleanup keeps it. Aggressive cleanup drops it. The right answer depends on whether the output is a quick chat message or meeting notes meant to capture sentiment.
Why Order Matters
Running the jobs in order, fillers first, then grammar, then restructuring, means each step works on simpler input. A grammar step that sees "the the model um needs" has to decide what to do with the repetition and the filler. A grammar step that sees "the model needs" has nothing to fix.
The same logic explains a common failure of doing everything in one aggressive pass: the model may paraphrase rather than clean up, which changes wording the speaker cared about. Whatever approach a tool uses, the test is the same. Compare the cleaned text with the raw transcript and check that every fact, number, name, and negation survived.
| Cleanup level | What it changes | Good for |
|---|---|---|
| Light | Removes hesitations, adds punctuation | Legal, medical, or quoted material |
| Moderate | Also removes discourse markers and repetitions, fixes grammar | Meeting notes, documents |
| Heavy | Also restructures sentences freely | Quick emails and chat messages |
For quick messages, heavier cleanup is fine. For notes that others will rely on, use moderate cleanup and keep hedges that carry meaning. For legal or medical dictation, keep cleanup light: remove hesitations, fix clear punctuation errors, and do not let the tool restructure sentences. Always read the result before it leaves your draft.
Running Cleanup Locally
Cleanup works on the content of what you say. A sentence like "the patient presents with symptoms consistent with early-stage lymphoma" is private. Sending it to a cloud service for grammar correction means a third party receives your most sensitive dictation.
Running cleanup on the device avoids that exposure for the cleanup step. Auditory applies grammar, punctuation, and filler-word cleanup to the draft, and its AI text improvement can use local models through Ollama, so the text does not need to go to a cloud API for that step. You can read more about the hardware side in our explainer on how Apple's Neural Engine accelerates local Whisper transcription, and about privacy trade-offs in our article on where cloud transcription liability sits.
When AI Cleanup Gets It Wrong (and How to Catch It)
Every cleanup approach has failure modes. Knowing the common ones helps you spot errors quickly.
Failure 1: Removing meaningful hedges. A speaker says "I mean, we could try option B, but I'm not confident." Removing "I mean" makes the sentence sound more certain than intended. Hedges followed by "but" or a contrasting clause deserve a second look.
Failure 2: Homophone miscorrection. The transcript reads "there system is down," and cleanup changes it to "they're system is down" instead of "their." Without the audio, the correction is ambiguous. Scan sentences with "their/there/they're," "your/you're," and "its/it's."
Failure 3: Meaning-altering restructures. Original: "We should not, under any circumstances, deploy on Friday." A restructure that moves the negation can weaken a strong prohibition. Check every sentence with "not," "never," "unless," or "only."
For domain-specific content such as medical terms, legal language, or technical jargon, general cleanup can "correct" a valid term it does not recognize. Use light cleanup, add terms to a custom vocabulary, and review carefully. Our guide to measuring word error rate shows how to track raw transcription accuracy separately from cleanup.
Frequently Asked Questions
Does AI text cleanup change what I actually said?
It should not change meaning, but it can. Light and moderate cleanup mostly removes verbal scaffolding and fixes punctuation. Heavy cleanup may drop hedges or emotional qualifiers. Compare cleaned text with the raw transcript when it matters.
How is this different from a typical grammar checker?
Grammar checkers are built for typed text and expect sentences with punctuation and boundaries. Speech cleanup has to handle run-ons, missing punctuation, homophones, and filler words that typed text rarely contains.
Can I trust cleanup for legal or medical dictation?
Use it for drafts, with light settings, and always review before filing or adding to a record. The main risks are homophone errors, changed negations, and miscorrected domain terms, all of which show up in a careful read-through.
Does cleanup work in other languages?
Fillers are language-specific: English "um," French "euh," and Japanese "eto" all play the same role. Quality depends on how well the underlying model handles your language. Test with your own dictation.
Your Cleanup Checklist: Five Habits That Improve Output Quality
- 1.Speak in complete thoughts. Pause between ideas rather than bridging them with "and then" or "so basically." Clean breakpoints make sentence boundaries easier to find.
- 1.Choose your cleanup level before you start. Quick message: heavier. Client document: moderate. Legal brief: light.
- 1.Dictate punctuation for critical content. Saying "period" or "comma" gives clear boundary signals. Our guide to spoken punctuation covers the habit.
- 1.Review homophone-heavy sentences. Scan sentences containing "their/there/they're," "your/you're," or "its/it's" first.
- 1.Track your post-editing time. The best single measure of cleanup quality is how long you spend editing each paragraph afterwards. If it trends down, your habits and settings are well calibrated.
Start by dictating one email today with cleanup enabled. Time how long you spend editing afterwards. That number is your baseline.
References
[1] Radford et al., Robust Speech Recognition via Large-Scale Weak Supervision (2022). https://arxiv.org/abs/2212.04356
[2] Omelianchuk et al., GECToR: Grammatical Error Correction: Tag, Not Rewrite (2020). https://arxiv.org/abs/2005.12592
Related articles
- How On-Device AI Models Actually Work on Apple SiliconA plain-language breakdown of the Neural Engine, GPU, and unified memory, and how they let a speech model like Whisper transcribe on your Mac without a network connection.
- Word Error Rate: How to Measure If Your Dictation Tool Is Good EnoughWord Error Rate is the standard metric for transcription accuracy, but most dictation users have never calculated it. Here's how to benchmark your setup and fix what's wrong.
- Multilingual Dictation: How to Switch Languages Without RestartingHow multilingual speech models detect language, why some language pairs are harder than others, and the dictation habits that help bilingual professionals switch smoothly.
Ready to try Auditory?
Privacy-first speech to text. Download free for macOS.