Proofing Deadlines Clients Will Actually Meet

Why "when you get a chance" never gets a reply

A review request with no date competes against everything that does have one. Your client has a launch, a board meeting, an invoice run. Looking at your gallery is important to you and optional to them, so it slides to the bottom of the list and stays there. That is not rudeness. It is how a task with no cost to delay behaves.

Two things make it worse. First, the person you are emailing is rarely the only one who has to look. If an assistant, a creative director and a founder all need to weigh in, nobody feels it is their turn to start. Second, a gallery with no deadline has no natural end, so every late note feels reasonable. A comment that arrives three weeks after delivery is still, technically, inside an unlimited window.

A deadline fixes the first problem by giving the task a place in the queue, and the second by giving the review an end. The date does the work, not the tone of the email around it.

Work backwards from your own calendar

The deadline you give a client should come from a date on your side, not from a feeling about how long they need. Start with the thing that cannot move, such as the retoucher's booked days, the client's publication date, or the print deadline for an album, and subtract.

Here is a worked example for a campaign with a hard publication date. The numbers are illustrative, so swap in your own.

Ten working days back from launch is the date the proof gallery must be sent. The three-day review window sits inside it with nothing spare. If the client takes six days instead of three, the retouching window loses three days (4 − 3 = 1 day of retouching left), and the schedule is broken before anyone has noticed. Showing the client this table, or a one-line version of it, is what turns "please review by Thursday" from a preference into arithmetic.

Notice that the review window is the only step the client controls. Say so plainly: "Retouching starts Monday. Anything not marked by Thursday goes into the next round, which is billed as an extra." That sentence is the reason, the date and the consequence in one go.

Choose a default that costs the client something small

A deadline without a default is a request. The default is what happens when the date passes, and it should be written down before the review starts, ideally in the contract or the project brief, so that applying it does not feel like a punishment.

There are three defaults worth considering, and they suit different jobs.

• Silence means approved. Frames with no note by the deadline are treated as signed off and move to retouching or delivery. This is the strongest option and suits commercial work where a publication date drives everything. It needs to be in the agreement, and you should send a reminder that names it.
• Silence means next slot. The job moves back in your queue and is rescheduled when you have room. This suits solo photographers whose own calendar is full, and it costs the client time rather than money.
• Silence means a fee. A late review attracts a rebooking or holding charge. Use it sparingly. It works for large retouching jobs where you have turned work away to hold the slot, and it damages goodwill on smaller jobs.

Pick one and state it the same way every time. Clients adapt quickly to a rule that is applied consistently and resent one that appears only when you are annoyed.

A reminder cadence you can copy

Most missed deadlines are not refusals. The client simply forgot, and the date was in an email that has since sunk down the inbox. A short, predictable schedule of reminders catches most of that without feeling like nagging, because each message carries new information, namely the number of days left and what happens at zero.

That is four messages for a review window of three working days, and every one of them is short. The day-one message is the most useful and the one photographers skip. It confirms the link arrived and was not caught by a spam filter, which is a surprisingly common reason for silence.

Write the four messages once as templates. Reuse them for every job and change only the date and project name. A cadence you do not have to think about is one you will actually send, and a cadence that is the same for every client reads as process rather than pressure.

Make the request small enough to finish

The deadline is easier to meet when the task is easier to do. A client facing 400 unsorted frames and an open-ended request will put it off. A client given a shortlist, a clear instruction and a way to respond on each frame will often do it on the same afternoon.

• Send selects, not everything. Fewer frames means a shorter review and fewer opinions to reconcile. The workflow for this is in the post on running an approval round without email.
• Name one decider. If three people need to look, say who has the final word. Otherwise the deadline gets stretched while they negotiate among themselves.
• Ask for one thing. "Mark your picks and flag anything that needs a change" is a task. "Let us know what you think" is an essay.
• Keep responses attached to frames. A note pinned to the photo it concerns takes seconds to write. A paragraph about "the third one in the second row" takes minutes and invites misreading.

This is where a single review link helps. Appruva gives the client one URL where they can mark picks and leave per-frame notes without an account, so the response is a few clicks rather than an email to compose. The same effect is possible with a shared folder and a spreadsheet if you are disciplined about it. Either way, the lower the effort of replying, the less the deadline has to do.

What open-ended review costs you

It is worth putting a number on silence, because it is the argument that persuades you to hold the line the first time a good client misses a date. The figures below are a model with assumptions stated, not survey data. Replace them with your own.

Suppose each late review costs you 20 minutes across the chasing: drafting a reminder, checking whether they opened the gallery, rereading the thread to remember where you were, and context-switching back into the job. Suppose 8 of your shoots a month run late.

Thirty-two unbilled hours a year is four working days of eight hours (32 ÷ 8 = 4) spent asking people to do something they agreed to do. And that excludes the larger cost, which is that the delayed job sits half-finished while you start the next one, so you pay the cost of switching back to it later. We look at this in more detail in the hidden cost of chasing clients for photo selects.

If the model is wrong for you, it is wrong in a useful way. Run it with your own minutes and your own count of late shoots for one month. The result usually makes the deadline conversation easier to have.

Handling the client who misses it anyway

Some will. Have the response ready so you are applying a rule, not improvising a confrontation.

1. Apply the default, in writing, on the day. "As agreed, frames without notes are now approved and retouching has started. Late notes go into a second round." Say it kindly and say it once.
2. Offer a way back in. A late reply is not a disaster, it just costs something. "We can fit changes in the next available slot on the 14th, or as a billed extra round this week." The client picks, and the choice makes the cost visible.
3. Keep the record. The deadline, the reminders and the client's replies should live in one place that you can point to. If a dispute comes later, a dated trail settles it faster than memory does.
4. Learn what the miss was. If the client missed it because the real decider was on holiday, move the date or name a stand-in next time. If they missed it because the gallery was too big, send fewer frames. A miss is information about the process.

The point is not to win an argument. It is that the next job with this client starts with a shared understanding of how reviews work, and most clients, once they have seen the default applied calmly once, meet the next date.