Pricing Rush Photo Approvals and Expedited Turnarounds

Why a flat 50% surcharge is the wrong starting point

Search for rush pricing and you will find a rule of thumb: add 25%, 50% or 100% for fast turnaround. We could not find a source worth naming for any of them, so treat them as folklore. The trouble is structural. A percentage of the project fee scales with the size of the job, but the cost of a rush scales with the disruption, and a small job can be just as disruptive as a big one.

Take two jobs due in 24 hours instead of 5 days. One is a $600 headshot set that needs 3 hours of editing. The other is a $4,000 campaign that needs 14. A 50% surcharge gives you $300 and $2,000. The headshot rush pays you $100 per extra-effort hour; the campaign rush pays about $143. Neither number says anything about the evening you gave up or the client you pushed back.

Build the fee from the cost side first, then check it against the percentage as a sanity test, not the other way round.

Build the fee from three costs

A rush has three separate costs. Most quotes capture the first and ignore the other two.

• Overtime hours. The editing you would have done during the week now lands in an evening or weekend. Price those hours above your normal rate, because they are hours you did not plan to work.
• Displacement. Every job already in the queue slips. If any of them has a deadline, the rush has a real price, and you either pay it or pass it on.
• Review risk. A fast turnaround compresses the client's review window too. A rushed round that comes back with changes means a second rush, and you need to decide up front who pays for it.

Here is a worked example. Your normal editing rate is $75 an hour, and you price out-of-hours work at 1.5 times that.

The $150 and the half-pass are judgement calls, not market data. The point of the table is that every line is yours to defend if a client asks why.

Pricing displacement honestly

Displacement is the cost most photographers skip because it feels abstract. Make it concrete with one question: what is each day of delay worth to the job you are about to push?

Suppose you have a $2,400 project due Thursday and a rush request arrives Monday for the same Wednesday window. If you take the rush, the Thursday job either slips a day or absorbs your evenings. Slipping a day has a cost only if that client cares, so ask. A client who says "Friday is fine" has a displacement cost of zero, and the rush fee can shrink accordingly. A client with a launch on Thursday has a cost you cannot recover with money, and the right answer is to decline.

A simple displacement rule

Give each queued job a delay cost of zero, low or high, based on a direct question to that client or your own contract. Zero means you can move it freely. Low means you move it only with a heads-up and a small credit. High means it does not move. If every job in your queue is high, you have no capacity for a rush, and you should say so before you open the spreadsheet.

This also protects the relationship with the client you are rushing for. Telling them honestly that the answer depends on what else is in your week is far better than agreeing, scrambling, and delivering something you would not normally put your name to.

Set tiers by calendar, not by adjectives

"Rush" and "urgent" mean different things to you and the client. Tie each tier to a delivery date so nobody has to interpret them. Pair this with the review deadlines in proofing deadlines clients will actually meet: a rush turnaround only helps if the client's own review window shrinks to match.

Keep it to three. A fourth tier invites negotiation between them. If a client asks for something faster than Express, the answer is that the shoot's own scope has to shrink, for example 40 frames instead of 120, because speed in post-production is bought mainly with fewer frames.

Where the rush fee goes on the quote, and how to word it

Show the fee as its own line item with the tier name, not folded into a higher day rate. A separate line does two things. It lets the client choose a slower tier if the number surprises them, and it gives you a clean reference when a client requests a rush mid-project.

Our post on how many revision rounds a photo contract should include covers the other half: a rush turnaround should state how many revision rounds it includes. A common structure is one round inside the rush window, with later rounds returning to standard turnaround.

Write the rush terms before you need them

The cheapest moment to agree rush terms is before anyone is in a hurry. Add a short clause to your standard agreement or quote template that covers four things:

1. The tiers and their delivery dates. Standard, Priority and Express, each with a calendar definition, as above.
2. How a rush is requested. In writing, with the tier named, and effective only when you confirm it back.
3. What a rush includes. Frame count, number of review rounds, and file formats. Anything beyond that returns to standard turnaround.
4. The client's side of the clock. If the client takes longer than agreed to review, the delivery date moves by the same amount.

That last point is the one most often forgotten. A rush is a promise from both sides. If you deliver on time and the client sits on the gallery for four days, the fee has bought them nothing and bought you a late evening for no reason. Writing the client's response window into the rush terms keeps the fee honest in both directions.

It is also worth deciding in advance what you do when a rush round comes back with changes. Some photographers quote the rush fee as covering delivery of the first round only, and price corrections at the normal rate on the normal clock. Others keep the rush tier running across a single correction round. Either works, so long as the client knows which before they say yes.

Say it once, plainly

Rush pricing goes badly when it arrives as an apology. Compare two ways of saying the same thing.

Always offer the next tier down alongside the one requested. Clients who hear only one price negotiate; clients who see a choice pick.

The review side matters as much as the editing side. A single review link with per-image comments keeps a rushed round in one place instead of scattered across email replies, which is where rushed rounds tend to lose notes. That is the one place a tool like Appruva earns a mention in a rush workflow: it shortens the gap between delivery and the client's answer.

When to say no to a rush

Some rushes should simply be declined. Use these tests:

1. The queue test. If taking the job would push a committed deadline for another client, decline or move that other client with their consent.
2. The scope test. If the rush needs more than about 12 overtime hours in a week, the quality will suffer and the fee cannot fix that. Do the arithmetic: 12 hours plus a normal 40-hour week is 52.
3. The pattern test. If the same client rushes every job, the deadline is not the problem. Quote them a faster standard tier in a retainer instead.

A rush fee is also a signal. If clients pay it without comment, it is too low. If every client refuses it, the price or the way you present it needs work. Review your accepted-versus-declined count after ten quotes and adjust.