An audiobook pickup note should tell a producer exactly what is wrong, where it occurs, and what a successful replacement will contain. “This line sounds off” is difficult to act on. A precise note connects the manuscript location, audible issue, approved wording, and surrounding context so the repair can be made without introducing another defect.
Identify the passage in two ways
Use a stable chapter and paragraph or scene ID, then add an approximate timestamp from the reviewed file. The text location survives timing changes; the timestamp helps the editor find the issue quickly in the current version.
Record the filename and revision reviewed. A timestamp without that information can point to a different sentence after earlier corrections are inserted. Include the first few words of the affected passage as a third, human-readable cue.
Quote only the text needed to locate the issue within your authorized manuscript. Keep the replacement text in its own field so the producer does not mistake the reviewer's explanation for words to record.
The ACX audio review article discusses reviewing production work at checkpoints. A structured pickup sheet makes those observations usable between review and final assembly.
Describe the defect and the expected result
Classify the issue: omitted word, extra word, incorrect pronunciation, wrong voice, truncated sound, unsuitable pause, or incorrect source text. These categories point toward different repairs.
Write the audible observation concretely. “The recording says fifteen; the approved manuscript says fifty” is actionable. “Bad emphasis” needs more detail, such as “the stress implies only the second option is available, while the sentence introduces both.”
For a pronunciation correction, reference the approved glossary entry and its sample. Avoid adding a fresh unreviewed phonetic guess to the pickup sheet.
For a character mismatch, reference the voice continuity sample. State whether the voice assignment is wrong or whether the correct voice needs a new take in context. The editor should not have to infer which problem you mean.
Request enough context for a clean join
Specify a complete replacement unit, usually a sentence or short paragraph. An isolated word may be efficient to generate but difficult to insert naturally between existing syllables. Let the editor choose a clean acoustic boundary within the approved text.
Include the preceding and following sentence as context when needed, clearly marked as context. This helps preserve meaning and rhythm without implying that every surrounding line must be replaced.
For a scene transition, describe the intended structural boundary rather than only asking for “more silence.” The editor needs to know whether the pause marks a paragraph, scene, or chapter.
If several defects occur in the same passage, group them into one coherent pickup. Separate requests for overlapping phrases can create competing versions and make it unclear which recording should become the final replacement.
Close the loop on the assembled chapter
Give each note an ID and status: open, replacement supplied, assembled, or verified. A supplied replacement is not yet a verified fix. The final chapter must be checked after insertion.
Listen through both joins and compare the replacement against the manuscript. Confirm that the correction did not duplicate a word, remove a nearby phrase, change the character assignment, or shift a meaningful pause.
Record the final audio revision associated with closed notes. If a chapter is exported again, confirm that the export includes the corrected assembly rather than an older timeline. Keep unresolved editorial questions visibly separate from routine production fixes.
Generate approved replacement passages in the voice studio, download them with their pickup IDs, and hand them to the editor with this sheet. Finish the review only when every required correction has been heard in its final context and the closed notes identify the exact released chapter.
