A progress bar can tell you a chapter rendered. It cannot tell you the chapter is right. Export twelve memoir chapters on a Sunday because the screen says "done," and on Monday a friend asks why chapter six apologizes twice. The revised paragraph had been pasted above the old one, and both were generated. The software had no way to know the first apology was meant to go, so it narrated the file.
Done means the file exists. Ready means you have heard it. A listening pass is what makes the difference. No report listens for you. Narration QA on the Pro plan reads the manuscript and returns a readiness score from 0 to 100. Critical issues lower that score more than warnings or notes. The score is a review aid. It is not a certificate that a retailer will accept the audio, and it is not a substitute for your ears.
Set up a pass you will finish
Listen to one chapter at a time, with the text in front of you. Use the same speakers or headphones you used for the voice audition. Sit back. If you only scrub for errors at double speed, you will catch repeats and miss stress. Play the chapter once at a normal pace. Mark the timeline or the paragraph. Do not fix during the first pass or you will lose your place and declare the rest "probably fine."
Have a pen and three columns: wrong word, wrong stress, leftover junk. Wrong word means a name, number, or term. Wrong stress means the sentence claimed something else. Leftover junk means a heading, a bracket, a duplicate, a "chapter six" you did not want spoken.
A chapter credit covers a chapter, typically up to 2,500 words. Listening is not billed as a second credit. Regenerating after you find a problem is a new generation. The pass is how you avoid doing that blindly.
What to mark
Listen for these, in this order. Order matters because a bad join makes everything after it feel worse than it is.
- Joins. Where a long chapter was split, the pace or the loudness may step. VoxAnvil splits a chapter longer than about 4,500 characters into smaller requests and joins the audio. Breaks you placed at paragraph boundaries are easier to forgive than breaks mid-sentence. If a join repeats a word, the text overlaps. Fix the text.
- Names and rules. Every name on your pronunciation list should appear as you decided. If it does not, the rule did not fire or the text spelling changed. Do not "get used to" the wrong name.
- Negations and numbers. "Not," "only," years, and doses. Pause and repeat the claim out loud. If you cannot, the listener cannot.
- Duplicates. The same sentence twice is usually a paste error. The Pro report flags repeated lines in the text. Still listen, because two different sentences can say the same fact in a way the report will not catch.
- Junk. Stage directions, link text, unclosed brackets, a tag spoken as a word. An unrecognized or unclosed square bracket is exactly the sort of thing the text report is good at. Believe it, close the bracket, regenerate that section.
- Breath and shout. All-caps lines and a pile of ellipses show up as notes in Narration QA. Your ear confirms whether the line actually shouted or hesitated. If it did and you did not mean it, change the text, not the volume knob. The studio is not a mastering desk.
Use the report, then ignore it as a verdict
Run Narration QA before you generate if you have Pro, and read it again if you change tags. It looks for unclosed brackets, tags the studio does not recognize, repeated lines, very long sentences, dense ellipses, acronyms without a pronunciation rule, and all-caps lines that may be over-emphasized. It can also ask for a short editorial pass on pronunciation, pacing, repeated material, speaker ambiguity, and production formatting. Those are text risks. A chapter can score well and still stress the wrong word. A chapter can score lower because of an acronym you have already decided to leave as letters. Read the items. Do not chase the number to 100 by deleting a real name.
After the listening pass, fix the text, regenerate only the chapter you marked, and listen to the marked spots plus ten seconds on either side. A fix at a join can create a new join. Hear it.
A typical miss: a chapter sounds polished until minute fourteen, where "2014" becomes "two thousand fourteen" and the next sentence says "twenty fourteen" because one instance was rewritten and the other was not. The report may not call that a contradiction. Your two columns will. Add one spoken form, make the text consistent, regenerate, and listen to that minute again. That is a complete pass. Export after it, not before.
The distribution checklist in the studio covers the kinds of file, loudness, and metadata questions retailers publish. Treat it as preparation. Confirm the current rules on the retailer's site before you upload. Nothing in the listening pass submits your book.
A short written log
Write three lines at the end of the pass: what you regenerated, what you accepted on purpose, and what you will check in the next chapter because it is a series risk. "Accepted the flat read on the grocery list" is useful. "Sounds good" is not. The next chapter benefits from the log more than this one does. Pair it with the pronunciation list so accepted names stay accepted.
If you are narrating lessons rather than chapters, the same pass works on each chunk. The workflow for scripts is the order. Listening is still the last gate before export.
Frequently Asked Questions
Q: Is a readiness score of 100 a finished audiobook? A: No. It means the text checks that feed the score did not find issues. You still listen, and you still confirm any retailer's current technical rules yourself.
Q: Can I listen at 1.5x? A: Use a faster speed only as a second pass for duplicates and long silences. Judge stress and names at the speed you expect listeners to use.
Q: What if I hear a click at every join? A: Check whether the split fell mid-sentence and whether the text repeats a word at the boundary. Move the break to a paragraph, regenerate, and listen again. If you need sample-level repair, that is an audio editor after export. The chapter generator joins speech. It is not a waveform editor.
Q: Should someone else listen? A: If you can ask one person who has not read the chapter, do it. They will hear the missing "not" you compensated for because you know the story. Give them the careful sentences, not a request to "see if they like the voice."
Which minute of the chapter have you not actually played?