Client Deadline Policy for Audio Pros: Rules and Wording

By /

A client deadline policy is a short written agreement that says when your client owes you feedback, files or approval, and what happens to your schedule if they are late. Put it in your quote or contract before work starts. Include a feedback window, one named approver, a pause clause for late responses, and a rule for what silence means. The sections below give you each piece, with wording you can adapt.

Audome
Keep Audio Feedback in One Place
Audome brings audio project communication and time-stamped feedback into one hub, helping professionals manage revisions without scattered notes.

Visit Audome

TL;DR

  • Give every delivery a feedback window of a few days, stated as a date and time, not “soon.”
  • Name one approver and one place where feedback must be sent.
  • Write that your turnaround pauses while you wait on the client’s notes or files.
  • Use a staged follow-up: reminder, second-channel nudge, formal pause notice.
  • Say in advance what silence means: a pause, a deemed approval, or a move to the next open slot.

Table of Contents

Why audio work needs its own deadline policy

Most deadline advice is about your deadlines. In audio, the delay that wrecks a schedule is usually the client’s. You deliver a mix on Monday, the client goes quiet, then sends notes from three people on Friday. Meanwhile you booked the next job into the slot you were holding.

A mixing contract guide from Violet Recording makes the point plainly: if you define your deadline without defining client delays, you own a deadline you cannot control. The fix is not to be harsh. It is to agree on the rules at the start, when everyone is friendly and nobody is behind.

This applies to mixing and mastering engineers, podcast producers, post-production teams, voice-over editors and studio owners. The wording changes a little. The structure does not.

The five parts of a client deadline policy

1. A feedback window

The feedback window is how long the client has to respond after you deliver. Violet Recording suggests a few days after delivering a mix, with the client consolidating notes into one list per round.

Two practical rules make the window work:

  • State it as a date and time. “Feedback due Thursday, November 12 by 5 p.m. Eastern” cannot be misread. “Within a few days” can.
  • Set it per delivery, not once for the whole project. Restate the due date in every delivery message.

For common US business use, count business days, and say so. Weekends and holidays are where most arguments about “three days” start.

2. One approver and one feedback location

The fastest way to lose a week is to let five people send notes by text, email and voicemail. Gruv’s guide to podcast production scopes recommends a single named approver and stating exactly where feedback must be submitted.

MixMasterPro adds that, at kickoff, you should settle who has final approval, the delivery target and how many revision rounds are included. If the band, the manager and the label all have opinions, the approver is the one person who collects them. Anything not routed through that person does not count as feedback.

If you want a model for how approval stages work when several people are involved, this write-up on approval before anything goes out shows the same idea in another creative field: one sign-off point, clear routing, and a known effect on the schedule. For audio specifically, our own guide to a podcast approval workflow covers the stages in detail.

3. A pause clause

This is the most important sentence in the policy. It says your clock stops when the client’s work is outstanding.

Gruv recommends defining late-feedback handling in writing and choosing what happens: the schedule pauses, shifts by the delayed business days, or moves to the next slot. A freelancer contract template from Groundwork shows a simple version: delays caused by late feedback or missing assets extend the timeline by the same number of days.

Pick one. Do not leave it open. “Equal extension” is the gentlest. “Next available slot” is the firmest, and it makes sense if your calendar is booked weeks out.

4. A rule for silence

What if the client never answers? Two approaches show up in real terms of service from US and Irish production companies:

Deemed approval suits recurring work with a release date, like a weekly podcast. For a one-off album mix, a pause with an expiry works better: after a set period of silence, the project is closed or moved to the back of the queue, and restarting may carry a rebooking fee. Either way, write it down.

5. Revision rounds

A deadline policy and a revision policy are two halves of the same thing. Rounds without time limits drift forever. Violet Recording notes that two or three rounds is common, with further changes billed separately, and that it belongs in the quote and the contract so it is agreed instead of improvised.

We go deeper on the numbers in how many revisions mixing engineers should include and on pricing extra rounds in when to charge for revisions.

Build in a buffer before you promise a date

Your policy protects you from client delays. Your quoted delivery date should also leave room for them. Twine’s guide to voiceover production timelines says each added approval layer typically adds one to two business days and recommends building a 15 to 25 percent buffer into estimates.

A quick example. You estimate a podcast episode edit at six working days. A 20 percent buffer is just over one extra day, so you quote seven. If the client has an extra approver (a sponsor, a guest), add the one to two days on top. Now you are quoting eight or nine, and a single slow reply does not break your promise.

That is a rule of thumb from one source, not a law. Adjust it to how your own jobs usually run. But a buffer you chose in advance always beats an apology you write later.

A follow-up schedule you can copy

A policy only works if you follow it. Decide the steps now so you are not agonizing over tone when a client has been silent for a week.

Lyniti recommends a staged approach: a friendly reminder after one missed deadline, an impact note after two or three business days, a formal pause warning after a week, then a recorded pause with restart conditions. Planet Media uses a similar protocol: a reminder at the deadline, a second-channel follow-up three business days later, and written notice at seven business days that the project is paused.

Here is a version for audio work:

Day Action Example wording
Due date, end of day Friendly reminder, same channel “Quick nudge: notes on the mix are due today by 5 p.m. Send them as one list and I’ll turn the revision around in two business days.”
+3 business days Follow up by a different channel (phone or text), with one clear question “Can you confirm when I’ll have your consolidated notes? I’m holding Thursday for your revision.”
+5 business days Impact note “Without notes by Friday, I’ll need to move your revision to my next open slot.”
+7 business days Formal pause notice, in writing “Per our agreement, your project is now paused. To restart, send consolidated notes and I’ll confirm a new delivery date.”

The timings are a starting point you can change. What matters is that the schedule is in the contract, that you send each message on time, and that the tone stays calm.

When the client does come back, do not just resume. Check your calendar first. Brief Topaid’s guidance on late feedback suggests asking when consolidated feedback will be ready, checking capacity before confirming a revised date, and asking the client to agree to any proposed pause.

A follow-up schedule you can copy

Wording you can paste into a contract

Adapt these lines to your situation. They are plain-language examples, not legal advice. If your contracts carry significant money or rights, have a US attorney review the final text.

Feedback window. “Client will provide consolidated feedback within three business days of each delivery. The due date and time will be stated in each delivery message.”

Approver. “Client designates [name] as the sole approver. Feedback is accepted only through [the project page or this email address].”

Pause. “Delivery dates assume timely feedback and files. If Client’s feedback or materials are late, delivery dates extend by the same number of business days, and my work on the project may be rescheduled to my next available slot.”

Silence. “If no feedback is received within [seven] business days after written notice, the project will be paused. Work resumes once Client sends feedback and I confirm a new delivery date. Projects paused for more than [30] days may be closed, and a rebooking fee may apply.”

Rounds. “The fee includes [two] revision rounds. Each round is one consolidated list of notes. Additional rounds are billed at [rate].”

Notice what the last one shares with the others: each is specific, short and measurable.

Wording you can paste into a contract

Does a deadline include the day stated?

This is the question your clients will ask, and the answer is whatever your policy says. A deadline phrased as “by Friday” is ambiguous: end of the day, close of business, or Thursday night? A client who sends notes at 11 p.m. Friday and a producer who stopped checking at 5 p.m. will both feel right.

So remove the doubt:

  • Give a time and a time zone, not just a date.
  • Say whether submissions on the due date are accepted. Usually yes, up to the stated time.
  • Say whether weekends and holidays count.

“Due Friday at 5 p.m. Eastern; notes received by then are on time” settles it. If you use the day before as an internal target, keep that for yourself. Do not tell the client the deadline is Thursday when it is Friday.

How to tell a client you missed a deadline

You will miss one eventually. A guide to freelancer communication from Work From Anywhere Guides advises telling the client as soon as you can explain the risk clearly, giving a realistic new date, and saying what you will do next and what decision you need from them.

For an audio job, that looks like this:

“The master won’t be ready today as planned. I found a phase issue in the second half of the mix that I want to fix properly. You’ll have the master by Wednesday at noon. If you need something sooner for the playlist pitch, I can send a reference version tonight. Which would you prefer?”

Three things are in there: ownership of what you controlled, a date you can hit, and an option. The same source also suggests offering to prioritize the essential parts of a delivery when the original date is fixed. Do not pad the message with excuses.

If your policy already treats your own delays fairly (for example, a small credit or a free extra round when you run late), mention it. It makes the whole policy feel mutual.

Perspective

We built Audome because the deadline problem in audio is really a feedback problem. When notes arrive as scattered emails, voice memos and texts, nobody can say what was asked, when, or whether it was handled. That is where late work and disputes start.

Our view is that a deadline policy should live where the work lives. Clients leave time-stamped comments right on the waveform, so each note points to an exact moment. They do not need to create an account to do it, which removes the most common excuse for delay. Version tracking is automatic, so you can always show what was delivered and when.

We also think the policy should carry real consequences without making you the bad guy. Revision limits and paid extra rounds let the project settings enforce what your contract already says, so you do not have to argue it out in a tense email.

Kreg

Put the policy to work with Audome

A written policy is easier to keep when your tools back it up. Audome gives audio professionals one place to share lossless files up to 96kHz/24-bit, collect time-stamped feedback on the waveform, track versions automatically, and set revision limits, with optional billing for paid revisions through Stripe. Clients review through a password-protected, branded portal and do not need to log in.

Audome

Plans start at $12.50 per month for Studio ($150 per year) and $48 per month for Pro ($576 per year), and there is a free trial. See the details on the Audome pricing page, or look at the full platform overview.

Two of our guides pair well with this one: the change order process with payment lock for work beyond scope, and the studio approval process for holding final files until payment clears.

FAQ

Should I set deadlines for client feedback at all?

Yes. Without a date, the client has no way to know their delay costs you anything. A stated feedback window, tied to a pause clause, makes it clear that your schedule depends on theirs. Some freelancers prefer an expiration period for silent projects instead of a short window; either is fine if it is written down.

What should I do if a client misses a feedback deadline?

Follow your staged schedule: a friendly reminder on the due date, a second-channel nudge a few business days later, then a written pause notice if the silence continues. When they return, check your calendar before you promise a new delivery date. Keep every message in writing so the record is clear.

Is the deadline the last day to submit?

Only if your policy says so. State a date, a time and a time zone, and say that anything received by then is on time. That removes the guesswork about whether “Friday” means the morning, the close of business or midnight.

Should silence count as approval?

It can, if the client agreed to it in advance. Some production companies state in their terms that unreviewed work is deemed approved after a set number of days. This fits recurring, date-driven work like podcasts. For one-off projects, a pause with an expiry date is often a gentler fit.

Sources

Scroll to Top