From eight weeks to two: a plan that survives August

An eight week gallery is rarely one giant editing problem. It is a pile of small waits: cards sitting for two days, a first pass spread over three evenings, no protected block, and two jobs already ahead of it. This is the stage by stage version of halving that, plus the honest part most guides leave out, which is where the problem stops being process and starts being capacity.

Most of eight weeks is waiting, not working

Before changing anything, take your last three galleries and write down the date each stage actually happened: shoot, ingest, backup, first pass finished, selection final, edit started, edit finished, export, upload, link sent. The blank stretches are the article you are reading.

A typical eight week wedding contains a fraction of that in hands on work. The rest is queue. You shoot Saturday, ingest Monday, pick over three evenings, put the job behind two older ones, edit in scattered hours, then wait for a free weekend to export. Every one of those gaps is elapsed time your client experiences and you do not.

Sort the timeline into three buckets and it becomes obvious what to attack. Production time is selection, editing, retouching, export and checking. Queue time is days when the job was ready and something else was in front of it. Friction time is hunting for a card, fixing a catalog, waiting on an upload, or answering a question that should have been settled at booking.

If you have never measured your real number, do that first. The four timestamps to log on every job, and why you should quote the median and the worst case rather than the average, are set out in turnaround as a feature. What follows assumes you know which gap is your biggest, because for most photographers it is not the one they expected.

Decide what two weeks actually means

Two weeks is not a promise until it has an edge. Fourteen calendar days or ten business days? The full gallery, or a preview and then the gallery? Color corrected, or retouched? Vague promises are how a photographer hits the date and still has a disappointed client.

For most wedding work the responsible version is the normal final gallery: selected, color corrected, consistent, delivered through the usual platform. Detailed retouching, album design and print orders keep their own timelines and should be named separately in the contract.

Then add a buffer before you publish anything. If your measured workflow finishes in eight business days when nothing goes wrong, promise ten business days or two calendar weeks. The buffer is what absorbs a second shooter who is traveling, a camera clock that was an hour out, or the week your youngest is ill. A promise you keep is worth more than a promise that is short, and if you want to sell the shorter version rather than give it away, that belongs in a priced tier, which is the subject of charging for fast turnaround.

Week one: kill the delay at the handoff

The largest single saving on most jobs is available in the first 24 hours, and it costs about 45 minutes. If cards wait until Tuesday, a Saturday wedding has already spent a fifth of a two week promise doing nothing at all.

Build a post shoot routine that does not depend on remembering anything.

1. Ingest every card to a fast working drive with one consistent job folder name, such as 2026-08-15_Smith-Jones_Wedding.
2. Make a second copy before any card is formatted, and verify it by file count or with backup software that checksums.
3. Collect second shooter files by a method agreed in writing before the wedding, not a hopeful text on Sunday.
4. Sync camera clocks, apply your metadata preset at import, and rename if renaming is part of your normal system.
5. Start the first pass while the day is still fresh in your head, flagging the moments and family groups you know matter.
6. Send the couple one short message saying the files are safely backed up, and restate the delivery window.

That last line does more work than it looks. It answers the question they were going to email you on Wednesday, and it sets the date once instead of five times. If you also want fifteen images out the door before you sleep, the compressed version of that routine is in the next morning sneak peek workflow.

Week one: make the first pass a finite stage

Galleries stall because selection and editing happen at the same time. You adjust exposure on one frame, compare it with six neighbors, drift into email, come back without having decided anything. Treat picking as its own pass with a start, a finish line and a calendar block: two 90 minute sessions, or one three hour block, not "whenever I get to it."

Set the target before you open the folder. Typical wedding coverage produces 2,000 to 4,000 frames and delivers 400 to 800 of them. If you have flagged 1,500, you have not finished picking, you have deferred the decision into the edit where it costs four times as much. Do a second comparison pass, commit, and end with an edit ready collection you do not revisit.

Tools help here and it is worth knowing what each one actually does. Photo Mechanic is a browser: it makes you faster without deciding anything. Lightroom Classic now ships Adobe's Assisted Culling, in early access, scoring subject focus, eye focus and eyes open, which Adobe describes as optimized for portraits and headshots. Dedicated selection tools such as Aftershoot and Narrative Select propose picks and group near duplicates on the desktop. All of them shrink the pile. None of them knows that the woman in the third row is the bride's grandmother. If you want the hour by hour method for a large shoot, it is in picking 1,000 photos in an hour.

Week two: batch first, polish second

Once the selection is closed, edit in passes rather than chasing one image at a time to perfection. Start with a representative frame from each lighting situation: prep by the window, ceremony, portraits, reception, exit. Set the base, then synchronize across small coherent groups.

1. Exposure, white balance, profile and lens corrections, per scene rather than per photo.
2. Crop and straighten only the frames that need it, and do not turn every crop into a creative decision.
3. Check skin tones and mixed light reception frames at 100 percent only where the image calls for it.
4. Reserve masks and retouching for hero images and genuine distractions, not as a tax on all 600 files.
5. Finish with one consistency pass through the gallery in order, watching for color shifts and near duplicates that slipped in.

Batching is not applying one edit blindly across rooms with different light. It is spending your attention where your eye actually changes the result, and letting the repetitive part be repetitive. The stretch after this one, export through to the delivery email, has its own set of fixes that have nothing to do with the calendar, and they are collected in delivering galleries faster.

Protect the blocks before the season starts

A two week plan dies when editing loses every argument with whatever arrived in the inbox that morning. Production blocks go on the calendar before wedding season, treated like shoot dates, because that is what they are.

A pattern that survives contact with a real week: Saturday shoot, Monday intake and first pass, Tuesday and Wednesday editing, Thursday quality check and upload, Friday as buffer. Add one short admin block a day so client messages have somewhere to go other than the middle of an edit.

Shooting two weddings in a weekend changes the shape. Finish the first pass on both jobs quickly, then assign named edit blocks to each, rather than completing one gallery entirely while the other ages. Two jobs at day nine is a better position than one at day four and one at day fourteen.

Standardize everything that does not need fresh thought: one folder structure, one import preset for copyright and contact metadata, one export recipe for downloads and one for web, one email template for the backup confirmation and one for delivery, one place where open questions live. Every one of those decisions you make weekly is a small tax on the week.

Where process stops and capacity starts

Here is the part that most turnaround advice skips. Some of your eight weeks is not process at all. It is arithmetic, and no checklist fixes arithmetic.

Do the sum honestly, on paper, for your busiest month rather than an average one.

If that last line is negative, you do not have a workflow problem. You have a booking problem wearing a workflow costume, and working later is a loan against next week that you always repay with interest.

The honest options at that point are all uncomfortable and all fine. Shoot fewer jobs at a higher price. Deliver a smaller gallery, since every extra 200 files is another 200 to pick, edit, export, check and store. Move the standard promise out to a number you hit in August rather than in January. Or buy capacity, by outsourcing the edit or bringing in help. The one option that does not exist is fitting 120 hours of work into 80 hours of month by caring more.

There is a fuller version of this arithmetic, including what a realistic ceiling looks like, in booking more without adding editing hours. And if you are reading this already buried, do not start with a redesign of the system: triage first, ship what can ship, renegotiate what cannot, using the backlog triage order. A new workflow applied to a queue of nine overdue galleries is just a slower apology.

Four numbers, and the traps

Log four numbers at the end of every job: hours from shoot to backup, days from shoot to finished first pass, editing hours, days from shoot to delivery. The second one is the leading indicator. It tells you whether a job will make its date long before the export happens, which is the only point at which the information is still useful.

Read them across several weddings rather than one. If the first pass is consistently three days late, the fix is intake and selection. If picking is quick but editing spills into week three, look at image count, lighting consistency and whether your blocks are real. If everything falls apart only after a double weekend, that is the capacity conversation above, not a discipline failure.

The traps are consistent enough to name. Over delivering image count, which multiplies every downstream stage. Editing from an unfiltered catalog instead of a closed selection. Letting a handful of portfolio favorites hold a finished gallery hostage. Adding automation without keeping a review step. And promising two weeks publicly in your busiest month before piloting it on three real jobs.

FAQ