Voice Acting Audition Checklist: 15 Things to Verify Before You Submit
You have the script ready, the mic is warm, and the read sounds good. That is exactly the moment when most auditions go out with a small, avoidable flaw still inside them. Not a weak performance — a file named wrong, a slate that names the wrong character, a fridge hum that only shows up on headphones. Casting rarely writes back to explain. They simply move to the next submission. Everything below takes seconds to check and covers the fifteen things most likely to sink an otherwise solid take.
Read the Specs Before You Read the Copy
The casting notice is a spec sheet as much as a creative brief. Before you open your mouth, extract the facts from it and write them on a sticky note: file type, sample rate, whether a slate is wanted, how many takes, the naming convention, and the deadline with its timezone. A notice that asks for a 128 kbps MP3 with no slate and files named Lastname_Firstname_Role will not be impressed by a 96 kHz WAV with a fifteen-second slate and a filename like audition final v3.wav.
Pull these out every time, even when you have worked with the studio before:
- Format and settings — WAV or MP3, bit rate, mono or stereo, sample rate.
- Slate — required, optional, or explicitly forbidden.
- Number of takes — one clean take, or one plus alternates.
- Naming convention — exact spelling, order, and separators.
- Submission route — attachment, link, portal upload, or reply to a thread.
- Deadline — date, hour, and which coast or country that hour belongs to.
If something genuinely is not stated — say, whether they want the slate on a separate file — one short question before the deadline is professional. Asking about something clearly written in the brief is not.
The Slate: Keep It Short, Get It Right
A slate is an introduction, not a second audition. Name, and only what they asked for: your name, sometimes your location or agency, sometimes the character. Deliver it at roughly the same energy as the read, slightly flatter, and get out of the way. Five seconds is generous; three is better.
The mistakes here are boringly consistent. Actors slate the wrong project because they reused yesterday's session. They use their legal name while their submission email used a stage name, leaving casting to guess whether these are the same person. They perform the slate like a movie trailer, then start the actual read in a completely different register, which tells the listener nothing useful about the performance. And when the brief says no slate, they slate anyway — a small act of ignoring instructions is still an act of ignoring instructions.
Before recording, say the character name out loud from the script header, not from memory. If you record alternates, keep the slate on the first file only unless told otherwise.
Pronunciation and the Small Script Details
Pronunciation is where careful actors separate themselves, because a mispronounced brand name is the first thing a client hears and the last thing they forget. Check company names, place names, product names, and people's names properly — look at how the company pronounces itself in its own advertising, or ask. Guessing confidently is worse than asking once.
Then walk the script for the quieter traps:
- Heteronyms — lead, read, live, close, record, wind, bass. Context decides, so decide before you hit record.
- Acronyms — said as a word or spelled letter by letter? Pick one and stay consistent.
- Numbers, dates, currency — "two thousand and twenty-five" or "twenty twenty-five"; "one hundred dollars" or "a hundred bucks".
- Contractions and punctuation — read what is written. Do not add words, drop commas, or "improve" the copy.
- Unfamiliar words — if you are not certain, record an alternate of that line and flag it in your email.
Small courtesies matter too: if the script has a typo that changes the meaning, mention it in the message rather than silently fixing it in the read.
File Format, Naming, and Clean Edits
Export to the settings in the brief and keep your processing light. Casting wants to hear your voice, not your plugin chain. A little cleanup is fine; heavy compression, reverb, and aggressive EQ make it harder to judge how you will sit in a mix.
Naming deserves the same attention as the read. Match the convention exactly, character for character. No spaces, no "final", no version numbers unless requested. If the brief gives an example filename, copy its shape precisely.
Then check the head and the tail. Leave roughly a quarter to half a second of room tone before your first word and after your last, so the editor is not slicing into a consonant. Trim breaths that draw attention, but do not sterilise the file into something unnatural. Play the exported file on a second device — a phone speaker is a good, humbling test — and confirm it is the right length and the right take.
The Honest Listen: Noise Floor and Room Tone
Put on headphones and listen to the quiet parts at a higher volume than feels comfortable. That is where the truth lives: laptop fan, fridge compressor, a ticking clock, traffic, a phone buzzing on the desk. Record ten seconds of silence in your booth and watch the meter while you listen. If you can hear hiss, it is in the audition, and someone will hear it through a client's speakers.
Listen for mouth clicks, plosives on plosive-heavy lines, and any change in distance from the mic between takes. If a flaw can be fixed by re-recording a single line in thirty seconds, re-record it. Repair tools leave artifacts, and artifacts are more distracting than a slightly imperfect read. A small amount of natural room tone is not a problem; a buzzing noise floor is.
Ship It Clean: Delivery Details
The last mile is administrative, and it is where good auditions quietly fall apart. Use a clear subject line: your name, the role or project, and the word audition. Keep the body to a few lines — confirm you have followed the specs, note any alternates and their timestamps, give your availability, and stop. If you are attaching files, check the total size against what the studio's inbox will accept; when in doubt, send a download link as the brief allows.
Then mind the clock. A deadline of Friday end of day in Los Angeles arrives on Saturday morning in Rome, so submit with buffer rather than at the last hour. Save a copy of the brief, the script, and the exported file in a folder named for the project, so that when the callback comes three weeks later you are not rebuilding the session from memory.
The Final Pass
None of this replaces a good read, but it protects one. Run this in the two minutes before you hit send:
- Specs re-checked against the brief, line by line.
- Slate correct, or absent if they asked for no slate.
- Every name and number pronounced the way you intended.
- Filename matches the convention exactly.
- Head and tail clean, file plays on a second device.
- Noise floor acceptable at headphone volume.
- Subject line, body, and delivery route correct.
- Sent with time to spare, and a copy saved.
Do this often enough and it stops being a checklist and becomes a habit — the quiet, unglamorous part of the job that lets the performance do the talking.
Photo: cottonbro studio / Pexels