How to Price Rush Turnarounds on Video Revisions (Without Burning Out)
Rush revision requests arrive as favors and quietly eat your evenings. Define your standard turnaround, publish a rush fee, cap the nights you sell, and speed becomes a product instead of a leak.
The message always arrives the same way. The client is thrilled with the cut, truly, and then comes the sentence that eats your evening: could we possibly have the changes back by tomorrow morning? Rush requests rarely feel like decisions about money. They feel like favors between friends. That is exactly why they need a price, set in advance, before anyone is tired, grateful, or under pressure.
Pricing rush turnarounds is not about punishing clients for being busy. It is about making speed a product they can choose, with a cost that reflects what speed costs you: the rescheduled evening, the dropped personal plans, the slower and more error prone work that fatigue produces. Charge for it properly and rush stops being a slow leak in your business.
Define Rush Before You Price It
A rush fee only makes sense against a standard turnaround that the client already knows. State yours plainly in your proposal and your first email: revision rounds are returned within two business days, or whatever honest number your schedule supports. Rush is then anything faster than that, and the definition does the arguing for you. Without a published standard, every deadline is a negotiation and every fee feels invented.
Be specific about what the clock measures. Your turnaround starts when complete, consolidated feedback lands in one place, not when the first of nine messages arrives. A rush fee buys your speed, not a rescue from a scattered review process, and saying so kindly at the start saves a hard conversation later.
Two Fee Structures That Work
The simplest structure is a percentage uplift on the revision work: fifty percent for next day, one hundred percent for same day or overnight. Percentages scale with the size of the job, clients understand them instantly, and the math takes seconds on a call. The second structure is a flat fee per rush round, which suits small repeat jobs where percentages produce awkwardly tiny numbers.
- Percentage uplift: best for larger projects, because the fee grows with the work being rushed.
- Flat rush fee: best for small edits and retainer clients, because it is predictable for both sides.
- Rush slots: a limited number of rush rounds per month on retainers, priced in advance and gone when they are gone.
Whichever you choose, publish it where clients sign. A rush fee that appears for the first time in a tense moment reads as a penalty. The same fee in the original proposal reads as a menu, and clients who know speed costs money plan their feedback better all by themselves.
What the Fee Is Really Buying
Clients accept rush fees when they understand the trade. You are not charging for typing faster. You are charging for reordering a queue that other clients are standing in, for working hours you do not normally sell, and for the extra checking that tired work demands. A rush revision is still video production work, and the teams that treat it that way, such as the producers at Envy Creative, quote turnaround as part of the job instead of apologizing for it.
Hold that line in your own quotes. When a client asks for tomorrow morning, answer with the option, not an apology: yes, that is a rush turnaround, the fee is this, and the cut will be with you by nine. A calm menu quote turns an awkward favor into a simple purchase, and most clients respect the professionalism of it.
Protect the Hours the Fee Is Buying
A rush fee that burns you out is underpriced, whatever the number says. Decide your limits while you are rested: how many evenings a week you will sell, the latest hour you will start a rush round, and the turnaround you will never promise at any price. Same day delivery of a full revision round, for instance, might simply not be a product you offer, because the quality risk lands on your name.
- Cap rush work at a set number of nights per week, and let the cap be real.
- Charge more for the second rush request in a week than the first.
- Never let a rush round skip your normal export checks, however late it is.
- After a rush delivery, protect the following morning instead of stacking another deadline.
Notice what happens to quality, too. A priced rush round comes with a defined scope, one consolidated set of notes, one delivery. The unpaid favor version tends to arrive with rolling feedback all evening, because nothing about it feels scarce. Price creates the boundary that keeps the work clean.
Put the Feedback Deadline in Writing
The other half of a sane rush system is the client's deadline, not yours. State that rush turnaround is measured from complete feedback, and that feedback arriving after an agreed cutoff, say eight in the evening, starts the clock the next morning. Use File Approved to make this effortless: the client leaves every note as a timecoded comment on one link with no login, and when they generate their Certificate of Approval or send the final note list, you both can see the exact moment the round was complete.
That shared timestamp ends the most common rush dispute, the one where feedback dripped in until midnight but the deadline was somehow still nine the next day. With one link and one record, the clock is a fact instead of an opinion.
When to Say No
Sometimes the right price for a rush job is no. Say it when the deadline would force you to ship work you cannot check, when the client has made every round a rush round and the fee has stopped meaning anything, or when the honest answer is that another client already bought those hours. A clear no, given early, protects the relationship far better than a resentful yes followed by a mediocre cut.
Write your rush policy this week, while nobody is asking. Set the standard turnaround, pick a fee structure, decide your caps, and put all of it in your proposal template. The next time the tomorrow morning message arrives, you will not be deciding what your evening is worth under pressure. You will just be reading the menu you already wrote.