How to Review 10 Scripts a Week Without Burning Out
Producers, development execs, and contest readers can use audio script readers to manage high script volumes without sacrificing their evenings or their judgement.
If you work in development, acquisitions, or contest reading, you know the script pile. It never shrinks. There's always another batch of submissions, another round of contest entries, another stack from the agency. The volume is relentless, and the expectation is that you read everything thoroughly enough to make informed decisions.
The maths is brutal. Ten scripts a week at 100-120 pages each is 1,000-1,200 pages. At roughly 1 page per minute of careful reading, that's 16-20 hours of reading time - on top of everything else you do.
Something has to give. Usually it's either your evenings, your reading quality, or both.
Audio script readers offer a different approach: convert scripts to audio and listen during time you're already spending on something else.
The script pile reality
Let's be honest about how most high-volume readers actually work:
The skim method. Read the first 10 pages carefully. If it hasn't grabbed you, skim the rest - maybe the midpoint, a few random scenes, the last 5 pages. Fast, but you miss good scripts with slow openings. And you've all met that script that starts quiet and absolutely ignites at page 25.
The weekend binge. Save everything for Saturday and Sunday. Read 5-6 scripts across the weekend. By Sunday evening, every script blurs into the same story. Your notes get thinner and less useful as the stack grows.
The late-night grind. Read after dinner, in bed, until your eyes cross. You're tired, you're not absorbing properly, and the scripts that land in the bottom half of your pile get the worst version of your attention.
None of these approaches are great for the scripts or for you. The problem isn't discipline - it's that sitting and reading requires dedicated, uninterrupted time that your schedule doesn't have enough of.
Audio as a first-pass filter
Here's the approach: instead of reading every script with the same level of attention, use audio to create a two-tier system.
Tier 1: Listen. Convert the script to audio. Listen at 1.25x speed while commuting, exercising, running errands, or doing admin. In about 90 minutes per script, you'll know whether it warrants a full sit-down read.
Tier 2: Read. For the scripts that pass the listen test - maybe 2-3 out of 10 - sit down and read them properly. Take notes, mark up the page, evaluate structure and craft with the attention they deserve.
This isn't about cutting corners. It's about triaging intelligently. The scripts that aren't right for you - wrong genre, wrong tone, weak concept, underdeveloped characters - you'll know within 20-30 minutes of listening. The scripts that have potential will pull you in and you'll keep listening. Trust that instinct.
The commute library
Most script pile readers have some form of daily commute or routine downtime that's currently spent on podcasts, music, or silence.
Let's map out a realistic week:
| Time slot | Duration | Scripts covered |
|---|---|---|
| Morning commute (Mon-Fri) | 5 x 30 min = 2.5 hrs | ~1.5 scripts |
| Evening commute (Mon-Fri) | 5 x 30 min = 2.5 hrs | ~1.5 scripts |
| Gym/exercise (3x per week) | 3 x 45 min = 2.25 hrs | ~1.5 scripts |
| Weekend errands/walks | 2 x 60 min = 2 hrs | ~1.5 scripts |
| Lunch breaks (2x per week) | 2 x 30 min = 1 hr | ~0.5 scripts |
| Total | ~10 hrs | ~6-7 scripts at 1.25x |
That's 6-7 scripts listened to during time that was previously unproductive (for work purposes). Add 2-3 proper sit-down reads for the scripts that passed the listen test, and you're at 10 scripts a week without a single late night.
What listening reveals (and what it doesn't)
What you'll catch by listening
Concept strength. Within the first 15 minutes, you'll know if the concept has legs. Is the world interesting? Is the central conflict compelling? Do you care about what happens next?
Dialogue quality. This is where audio excels. Bad dialogue is immediately obvious when spoken aloud. Stilted exchanges, on-the-nose exposition, characters who all sound the same - your ear catches these faster than your eye.
Pacing feel. You'll know if the script moves. If you reach for the fast-forward (or wish you could), the script has a pacing problem. If 45 minutes fly by and you're still engaged, you've probably found something worth reading properly.
Tone and voice. The writer's voice - or lack of it - comes through clearly in audio. You can hear whether the script has a distinctive personality or feels generic.
What you'll miss
Visual formatting. Page density, white space usage, action line length - these are signals experienced readers use to gauge writing quality. Audio flattens them.
Structural precision. You won't be counting page numbers or tracking act breaks as precisely by listening. For a first pass, this usually doesn't matter. For a development note, it does.
Detail retention. Listening is more impressionistic than reading. You'll remember how the script made you feel better than specific plot details. For a first-pass filter, that's actually ideal - you're evaluating vibes and potential, not writing coverage.
Setting up your workflow
1. Batch conversion
Set aside 15-20 minutes at the start of your week. Upload all the scripts you need to get through. Assign voices quickly - you don't need to carefully cast each script. Just make sure you can distinguish character A from character B.
2. Queue management
Treat your script audio like a podcast queue. Organise by priority: submissions with deadlines first, general reading pool second. Most podcast apps or music players handle MP3 playlists well if your script reader tool supports audio export.
3. The 20-minute rule
Give every script at least 20 minutes of listening. Some scripts are slow starters. A concept that doesn't grab you in the first 5 pages might hook you by page 15. Twenty minutes at 1.25x speed covers roughly 25 pages - enough to make a fair assessment.
If you're not engaged after 20 minutes, move on. This isn't a contest submission you owe a full read. This is triage.
4. Quick capture
Keep a simple system for capturing your impression as you listen. A voice memo, a quick note on your phone, or even a mental rating (yes / maybe / no). Don't try to write detailed notes while listening - that defeats the purpose of concurrent activity.
After each script, spend 30 seconds recording: title, your one-line impression, and whether it's a "sit-down read" or a "pass." That's your filter output.
5. The deep read
For scripts that pass the listen test, schedule proper reading time. This is where you sit with the page, annotate, and form the detailed opinion that goes into your notes or coverage. The difference is that now you're spending your precious reading time on scripts you already know have potential, not on scripts that were never going to work.
Speed settings and how to use them
Most audio tools let you adjust playback speed. Here's how to think about it:
| Speed | Use case | Notes |
|---|---|---|
| 1.0x | Scripts you're enjoying, key scenes | Natural rhythm, best for evaluating dialogue pacing |
| 1.25x | Standard first-pass listening | Slightly faster, still natural-sounding. Most people adapt within a minute |
| 1.5x | Scripts you're on the fence about | Gets through the material faster. Dialogue starts to feel rushed |
| 1.75x+ | Not recommended for creative evaluation | You'll hear words but lose all pacing and tonal information |
1.25x is the sweet spot for most readers. It's fast enough to save meaningful time (a 2-hour script becomes 1:36) without sacrificing comprehension or dialogue feel.
The objections
"Real readers read properly." They do. And the best readers still will - on the scripts that matter. The question is whether your current method of reading everything at the same level of attention is actually serving those scripts better than a tiered approach.
"I need to see the formatting." For a first-pass filter, no you don't. Formatting tells you about writing craft, which matters at the consideration stage. At the triage stage, story and dialogue are what you're evaluating.
"Listening is passive." Listening while doing something else is less focused than reading in a quiet room, yes. But reading in a tired slump at 11pm isn't particularly focused either. The question isn't "is listening optimal?" - it's "is listening better than my current approach for getting through volume?"
"I'll miss things." You will. You'll also catch things you wouldn't have caught reading - especially dialogue problems. The point isn't to replace reading. It's to filter intelligently so your reading time goes to the scripts that deserve it.
The realistic outcome
If you adopt this approach consistently:
- You get through 6-7 scripts per week by listening during otherwise-dead time
- You do 2-3 deep reads per week on scripts that passed the listen filter
- You cover 8-10 scripts weekly with better quality attention on the ones that matter
- Your evenings are mostly free
- Your weekend reading is focused on material you're already excited about
The script pile won't shrink. But your relationship with it changes. Instead of a source of dread, it becomes a commute playlist - and the scripts that deserve your full attention actually get it.