A transcript is a record, not something meant to be read start to finish.

An hour of conversation between two or three people turns into eight or nine thousand words once it's transcribed — longer than most feature articles, and written the way people actually talk, with false starts, cross-talk and the same point made three different ways before it lands. Opening that file expecting to read it the way you'd read an email is where the problem starts. It isn't meant to be read that way, and nothing about a transcript being long means anything went wrong.

Why a transcript runs this long

People speak at somewhere around 130 to 150 words a minute in an ordinary conversation, and a transcript captures every one of those words, from both sides, in order. A 45-minute client call with two people talking for most of it is comfortably five to six thousand words before anyone reaches the interesting part. A three-person planning meeting that runs an hour and a half can clear ten thousand. None of that is padding — it's what a full, honest record of speech actually looks like once it's on a page instead of in the air, where nobody notices its length because nobody's trying to read it.

What to read instead

Coii AudioNotes turns the transcript, plus whatever you typed alongside it, into minutes: the decisions that got made, the actions someone owns, and the questions that were raised but not settled. That's usually a few hundred words for an hour of talking — the shape of the meeting, not a transcription of it. Minutes are a different kind of document from a transcript, built for a different job: the transcript is what was said, the minutes are what it amounted to.

Read the minutes first, every time. If a decision needs the exact wording it was made in — because someone will ask "did we actually agree to that" — that's when the transcript underneath earns its length. It's there for the one question that needs it, not for a start-to-finish read. How minutes actually get written from a transcript covers what goes into that step.

Why a long transcript feels worse than a long document usually does

Most long documents you deal with have some structure that helps you skip around — headings, paragraphs organized by topic, a table of contents. A transcript has none of that by default: it's one continuous stream of turns, in the order people happened to speak, with the important sentence sitting in the same visual weight as the small talk before it and the "sorry, can you say that again" after it. A ten-thousand-word report with headings is navigable. A ten-thousand-word transcript with no headings looks, at a glance, like a wall of text regardless of how much of it actually matters — which is part of why it reads as "too long" faster than a document of the same length would.

The other factor is that spoken language is simply less dense than written language for the same amount of information. A paragraph someone writes has usually been edited down to the point that needs making. A paragraph someone says out loud usually includes the thinking that led to the point, restated once or twice, before landing on it. Neither is wrong — writing and speaking are different processes with different amounts of revision built in — but it does mean a transcript of a decision takes noticeably more words than a written summary of the same decision would, on top of already being a record of everyone in the room rather than one author's version of events.

What actually happens to a transcript once it's timestamped and speaker-labelled

Coii AudioNotes doesn't leave the transcript as a single unbroken stream. Because it's timestamped and each turn is attributed to a speaker by voice print, it can be scanned by time or by who was talking, which already narrows a long call down before any summarizing happens — skipping to the last ten minutes of a ninety-minute call, or to everything one particular person said, is a much smaller task than reading the whole thing from the top. The minutes are the shortest path through it, but the timestamps and speaker labels are what make even the full transcript navigable rather than a single undifferentiated block.

When the length is actually a problem

Sometimes a transcript is longer than the meeting deserves because it captured audio it shouldn't have — a call that ran long after the actual business finished, or a recording left running through a break. If a transcript looks unusually long for what you remember discussing, check the recording's actual duration against what you expected; a transcript that's twice the length of the meeting on your calendar is worth a second look, not a symptom of anything the app got wrong.

Searching instead of scrolling

If you remember roughly what was said but not where, searching the transcript for a name, a number, or a distinctive phrase gets to that moment directly, the same way regardless of whether the call was five minutes or five hours. Searching past meetings covers the mechanics; the short version is that length stops mattering once you're searching instead of scrolling, because the app is finding the line, not you.

Asking a question instead of reading

For a question that spans the whole call rather than one moment in it — "did we ever land on a launch date," "what did the two vendors quote" — asking the app directly is faster than either reading the minutes or searching the transcript, because it reads the whole thing on your behalf and gives you the answer instead of the passage it came from.

Turning the long parts into something short and actionable

If what you actually need out of a long transcript is a list of what to do next, rather than a narrative summary, pulling action items out of it directly skips the minutes entirely and goes straight to a checklist — useful after a meeting that was mostly discussion with three or four real commitments buried inside it. A product manager coming out of a customer call with forty minutes of feature requests is exactly who this saves the most time for.

What a long transcript is not telling you

It's tempting to treat transcript length as a signal about the meeting itself — a nine-thousand-word transcript must mean a meeting that ran too long or covered too much ground. It usually doesn't mean either. A tightly focused thirty-minute call between two people who talk quickly can produce nearly as many words as a slower ninety-minute call with long pauses between turns. Length tracks how much was said and by how many people, not how well the meeting was run or how much of it mattered. Judging a meeting by its transcript's word count is measuring the wrong thing; the minutes are a much better read on whether the time was well spent, because they're what the conversation was actually for.

Comparing several long transcripts against each other

The problem compounds when it's not one long transcript but a stack of them — a week of client calls, a series of candidate interviews, a quarter of one-on-ones. Reading back through several nine-thousand-word files to find a pattern across them is a much bigger task than reading any one of them, and it's the situation where minutes and search matter most: comparing five sets of a few hundred words each, or searching across all of them for one recurring phrase, finds the pattern in minutes rather than an afternoon. The length problem doesn't multiply as badly once the transcript itself stops being the thing you're reading.

Sharing a long transcript with someone else

If the reason the length matters is that you need to hand the record to someone who wasn't on the call — a manager, a client who missed the meeting, a colleague catching up — sending the raw transcript is rarely the right move regardless of how good it is; nobody who wasn't there wants to read nine thousand words to catch up on a meeting they weren't in. The minutes are what's actually shareable: short enough to read in the time it takes to open the email, and built to stand alone for someone with no other context on the call. The full transcript stays available for the one time somebody who did get the minutes asks a follow-up question the summary didn't answer.

The instinct to shorten the meeting instead

Sometimes a long transcript prompts a different reaction: cut the meeting down, so there's less to transcribe. That's worth doing on its own merits — plenty of meetings run longer than the topic needed — but it's solving a different problem than an unreadable transcript is describing. A twenty-minute meeting that could have been ten still produces a transcript nobody's going to read start to finish; it's just a shorter wall of text instead of a longer one. The fix for a meeting that ran long is a better agenda. The fix for a transcript that's hard to get through is reading the minutes instead of the transcript, regardless of how long the meeting actually needed to be.

Why the app doesn't just hand you a shorter transcript

It would be possible to generate a transcript that's already trimmed down to "the parts that matter," but that requires the software to have already decided, on your behalf, which parts those are — and it's frequently wrong about that in ways you only discover later, when the sentence that got trimmed turns out to have been the important one. Keeping the full transcript intact and building the short version as a separate document — the minutes — means the decision about what to skip happens at read time, by you, rather than being baked into the record itself before anyone's had a chance to disagree with it.

A transcript you never intend to read in full is still worth keeping

Even a transcript nobody reads end to end is doing its job as long as it's there when it's needed — for the one contested decision, the one client who asks "what exactly did we agree," the one moment six months later that only the record settles. The length that makes it unreadable as a document is exactly what makes it complete as a record. Keep the whole thing; read the part that's short.

What it costs

Coii AudioNotes is $19 once, for three of your own Macs, with a 30-day trial that needs no card and no account. It runs on macOS 13 Ventura or later, generates minutes and lets you search or ask questions across every meeting it's recorded, all without anything leaving the Mac. What a meeting summary actually is covers how the minutes get built from the transcript underneath them.