A script lands with a same-day deadline and the instinct is to panic-record immediately. The better instinct is to spend the first five minutes deciding what your normal workflow can safely skip today, because a rush job's real risk isn't running out of time to record, it's running out of time to catch a mistake before delivery. A well-run audition pipeline already trains a version of this skill, moving fast without cutting corners that actually matter, and a rush job is just that same discipline under a tighter clock.
What to Skip, and What Never Gets Skipped
- Skip: a leisurely multiple-pass read-through. One focused read to flag trouble spots is enough under real time pressure.
- Skip: recording extra alternate takes "just in case" beyond what the brief actually asked for. Rush jobs reward a clean, confident single pass more than options nobody has time to review anyway.
- Never skip: marking up the script for pronunciation, emphasis, and pacing before hitting record. This takes minutes and prevents the exact re-takes that eat the most time on a tight deadline.
- Never skip: a final listen-through of the finished file before sending, even a fast one. Sending an unreviewed take to save two minutes is the single most common rush-job mistake, and it's the one most likely to come back as a revision request that costs far more time than the review would have.
Setting a Rush Fee That's Actually Fair to Both Sides
A rush fee isn't a penalty for the client's poor planning; it's compensation for the real cost you're absorbing, dropping other commitments, working outside normal hours, and accepting more delivery risk with less buffer for problems. Negotiating rates directly with clients applies the same principle here: state the surcharge plainly and early, before starting the work, rather than adding it as a surprise on the invoice. A same-day turnaround commonly carries a meaningfully higher surcharge than a next-day one, since same-day genuinely forecloses your ability to take on anything else that day.
Typical Rush Surcharges by Turnaround Window
These ranges aren't a rulebook, and a repeat client with an otherwise good, steady relationship might reasonably get a smaller surcharge than a first-time client asking for the same turnaround. What matters more than the exact number is having a default in mind before a rush request lands, so you're not calculating a fair number for the first time while also under deadline pressure yourself.
↗ Try the tool
Auto Clean Up
The editing and cleanup pass is where rush jobs lose the most time to manual work. Auto Clean-Up handles noise reduction and leveling automatically so a tight deadline doesn't mean skipping the polish a client expects.
Open Auto Clean Up →Frequently Asked Questions
When should I just say no to a rush job?
When accepting it would genuinely compromise quality below what you'd normally deliver, or when the deadline simply isn't physically achievable given your current commitments. A rushed job delivered late or delivered badly does more damage to a client relationship than a polite decline with an honest, slightly later alternative time.
Does remote direction change under rush pressure?
Remote sessions over Source-Connect or Zoom generally save real time on a rush job compared to arranging any kind of in-person alternative, since there's no travel or setup delay on either side, which is one more reason remote-capable rush work has grown alongside overall demand.
Should a rush job be invoiced differently than a normal one?
Line-itemize the rush surcharge separately from the base rate on the invoice rather than folding it into a single higher number. A transparent breakdown is easier for a client's own accounting to process and makes clear exactly what they're paying extra for.