A wedding season workflow you can run twenty times

Wedding season rarely fails at the camera. It fails in the gap after the wedding, when cards wait, a couple asks for previews, and three galleries want the same Tuesday evening. The fix is not working harder in August. It is building a system in February that a tired version of you can run without deciding anything. Here is how to build it.

A workflow is what you did once. A system is what survives twenty times.

Most photographers have a workflow. It lives in their head, it worked beautifully in March, and it quietly comes apart in the third week of August. That is not a discipline problem. A workflow asks you to make the same forty small decisions on every job: what to name the folder, how many preview images to send, which drive, which preset group, when to answer the email that just arrived. Forty decisions is nothing on wedding one. By wedding twelve you are making them at midnight, and half of them are getting made badly.

A system is the same sequence with those decisions already made, written down, and out of your head. The test is simple. Could a version of you who slept five hours and has three galleries open run it correctly, tonight, without asking anyone anything and without reopening an old email thread? If the answer is no, that part of your process is still a workflow.

Two things this is not. It is not the single wedding sequence, card to gallery, which we walked through step by step in from shoot to delivery. And it is not the rescue plan for a season that has already stacked up, which is eight weddings in six weeks. This is the thing you build in the quiet months so neither of those becomes an emergency.

Set the delivery promise once, from your August capacity

Almost every broken season starts with a promise made from a February turnaround. Six weeks is easy when a job arrives alone. It is a different animal when the job in front of it is still open and you are shooting again on Saturday. Your contract timeline should be set from your worst realistic month, not your best one, and then it should never be negotiated under pressure.

Work backward from the full gallery date and put the checkpoints in the calendar at the moment the date is booked, not the week the wedding happens. On a six week promise that might read: previews by day three, picks finished by day five, first edit block in week two, gallery built and proofed in week five, delivered in week six. The exact dates matter less than the fact that they exist before the job does.

Give each wedding a block, not a hope. A full day is typically 2,000 to 4,000 RAW frames and 400 to 800 delivered images, which is a known quantity of post-production work, so treat it like a shoot: it goes in the calendar with a start and an end. A season where every wedding has a booked production day is a season where the eighth job is inconvenient rather than fatal.

Write your standing answers down, on one page

This is the part almost nobody does, and it is the part that makes a season repeatable. Every recurring decision gets one answer, written once, kept somewhere you can see it. Not a manual. One page.

The two rows people skip are the ones that cost the most. Written criteria for a keeper stop you re-litigating your own standards at 1am, and the method for setting them is in building your culling criteria. A second shooter agreement written before the season saves you a day of untangling files per wedding, which is the whole argument in onboarding a second shooter.

Print the page. Tape it inside the cupboard door where you keep the card readers. A system you have to search your email for is not a system.

The shoot day is not over until the files exist twice

The single most expensive habit in wedding photography is formatting a card before the job is safe. Make the end of the day a fixed routine that never changes, however late the reception ran.

Before you leave the venue, account for every card and keep full ones separated from empty ones by a physical convention you cannot misread in the dark: one side of the wallet for shot, the other for clean, labels facing out. Back at the desk, copy to two physically separate destinations and verify counts or checksums before anything is formatted. The full version of that routine is in our backup workflow for photographers, and it is worth following exactly rather than approximately.

Then write the notes while they still exist in your head. The mother in law who is not to be photographed beside the father's new partner. The ring shot you were asked for and got at 4pm. The delay that cost you twenty minutes of golden hour. Three lines in the job folder, written on the same night, will answer a question in week five that you would otherwise answer wrongly.

Same three passes, same order, every time

Making technical, duplicate and storytelling decisions all at once is what makes a wedding feel endless, because each one uses a different part of your judgment and switching between them is the expensive part. Fix the order and never vary it.

First pass, technical: missed focus, blinks, the frame you took of your own feet. Second pass, comparison: burst clusters and near identical frames judged against each other, not one at a time. Third pass, story: coverage, balance, the moments the day actually turned on. Anything you cannot decide gets a label and keeps moving, because a stalled frame costs more than a wrong one you fix later. The detail of each pass is in the wedding culling workflow.

Software fits into the first two passes, not the third. Adobe now ships Assisted Culling in Lightroom Classic and cloud Lightroom, scoring subject focus, eye focus and eyes open, which is worth checking before you add anything else to the stack. Whatever you use, run it in the same slot in the week every time. That consistency is what makes it measurable, and measuring it is a separate job with its own method, laid out in the AI culling time audit.

The preview is a pipeline, not a project

Previews are the highest return thing you send all season, and they are also where repeatability breaks first, because it is tempting to make each one special. Resist that. The preview should be the same size, built the same way, from the same template, sent on the same day of the week after every wedding.

Set the count once and hold it. Choose the frames during the story pass rather than as a separate job: when you hit the one that made you put the camera down, it goes in the preview folder as you pass it. Export with the same preset, drop it into a gallery template that already has the settings right, and send it with a saved email. Done properly the whole thing is thirty minutes, not an evening.

What actually goes in it, and how many is too many, is its own question and we answered it in how many sneak peeks to send. For the system, the only thing that matters is that a preview never becomes a decision again.

Checklist the client facing end, because that is where a good job looks careless

Gallery setup, vendor credits, album prompts and the delivery email are easy to postpone because they are not image making. They are also the parts a couple experiences most directly, and a small mistake there undoes a beautiful edit. Give them a checklist rather than attention.

Before a gallery goes out: names spelled correctly, cover image chosen, download permissions set the way your contract says, expiry date correct, print settings on or off deliberately, vendors tagged, and one test download performed as a client on a phone rather than as yourself on the desktop where you are already logged in. Five deliberate minutes prevents the confused email that costs you twenty.

Batch these. Delivering three galleries in one sitting on a fixed afternoon is faster than three separate half hours across a week, and it keeps the standard consistent because you are running the same list three times in a row.

Review after every third wedding, and change exactly one thing

A system becomes repeatable through revision, not obedience. After every second or third wedding, sit down for fifteen minutes and answer two questions. Which step created the longest wait? Which step did I do differently from the written page, and why?

Then change one thing. One. If previews are always late because favorites are not tagged during the first pass, add the tag to the pass and see whether the next preview goes out a day earlier without getting worse. If you change four things at once you will never know which one worked, and in the middle of a season that is a whole month of not knowing.

Write the change on the page, date it, and leave everything else alone until the next review. The version of the system you carry into next season should be the one that survived twenty weddings, not the one you designed in February.

Kepla is being built for this shape of work, and here is where it honestly sits. The booking page is live and free today: it sends a couple a page, holds the date and takes the deposit, so the job enters your system the same way every time instead of arriving as a message thread you have to reconstruct. The picking app for iPhone, iPad and Mac is still in development. The idea is a first pass on the phone on the drive home, then the same shoot open on the Mac for the frames that need a big screen, with nothing ever deleted, moved or renamed, so every frame it set aside stays one tap away. Build the system first. Any tool you add later should slot into a step that already has a name.

FAQ