
One wedding is a project. Eight weddings in six weeks is a queue, and queues fail differently. This is about the arithmetic of peak season, the weekly rhythm that keeps it moving, and the honest list of things you should stop doing until October.
Nothing goes wrong at wedding one. Wedding one gets the sneak peek in 36 hours, the gallery in nine days, and a lovely email back. Wedding two is fine. By wedding five you are still shooting beautifully and you have four unfinished jobs sitting on a drive, and you have started to feel a low hum of dread every time your inbox loads.
That is not a discipline failure. It is arithmetic. A full wedding day is typically 2,000 to 4,000 RAW frames, so eight of them in six weeks is somewhere between 16,000 and 32,000 frames arriving while you are also shooting. Every wedding brings a fixed block of post-production work, and Saturdays are not available for post-production because Saturdays are weddings. Six weeks of eight weddings gives you roughly thirty working days to absorb eight full jobs. If a job takes more than three and a half days of your working time, the queue grows no matter how hard you work.
The whole game, then, is to know that number for your own business and to build a week that respects it. If your queue has already grown past the point where a rhythm alone fixes it, start with the editing backlog fix, which is about digging out. This piece is about not going under in the first place.
The single biggest change is mental. Stop thinking of the Fletcher wedding, the Osei wedding and the Delgado wedding as three separate things you owe three separate couples. Think of one line of work with eight items in it, moving in order.
Three rules make that real.
Put the queue somewhere you can see it. A whiteboard, a note on the fridge, one page in whatever app you already use. Every wedding, one line: date shot, backed up yes or no, picked yes or no, edited yes or no, delivered yes or no, promised date. When the whole season is on one page you stop making decisions based on which client emailed most recently, which is the worst possible scheduling algorithm.
Limit how many jobs are open at once. One wedding in the editing stage at a time. Not two, not three. Switching between half-edited galleries with different lighting and different presets costs you more than you think, because every switch means rebuilding the whole mental model of that day. Finish, deliver, then open the next.
Go in order, and only break order for a real reason. First shot, first out. The legitimate exceptions are a contracted date that lands sooner and a wedding where something went wrong and the couple needs reassurance. "They emailed twice" is not an exception, it is a communication problem, and the fix for that is in the next section.
Peak season runs on a template week, not a to-do list. The point is not that you follow it perfectly. The point is that on any given morning you know what today is for without deciding, because deciding is the resource you are short of.
| Day | The one job | What it protects |
|---|---|---|
| Saturday | Shoot | The work itself |
| Saturday night | Ingest, back up, verify counts | The files. This is non-negotiable |
| Sunday | Off, entirely | You, and everyone who lives with you |
| Monday | Pick photos, both passes, plus the sneak peek | The queue, and the couple's patience |
| Tuesday | Edit block one | Momentum on the oldest open job |
| Wednesday | Edit block two, deliver if ready | Something leaving the queue every week |
| Thursday | Admin, inquiries, invoices, next week's timelines | The business, in one contained block |
| Friday | Light. Prep, pack, early night | Saturday |
Two things about that table matter more than the specific days. The first is that Sunday is off. Not off unless something comes up. Off. A six-week season with no full day of rest ends in the state described in wedding photographer burnout, and the recovery costs more than the day you saved.
The second is that something leaves the queue every week. One delivered gallery per week against one wedding shot per week is break-even, and break-even is a survivable season. If two weeks pass with nothing delivered, that is your early warning, not the month when you notice you have five galleries outstanding.
You cannot add hours, so the only lever is subtraction. Every one of these is a real thing photographers do that is genuinely worth doing in a normal month and is a net loss in peak season.
What you do not cut: the same-night backup, the sneak peek, and your day off. Those three are the load-bearing walls.
Ten to fifteen finished images, sent within 48 hours, is the cheapest thing you can do for your own timeline. It reads as generosity. It functions as scheduling.
A couple who has seen nothing since Saturday fills the silence themselves, and what they fill it with is anxiety. That anxiety arrives in your inbox as a polite question about when the gallery will be ready, and answering it costs you fifteen minutes and, worse, tempts you to jump the queue for them. A couple who has already cried over eight photographs and had their friends share them will wait the full contracted time without a single email.
Pick the sneak peek during the story pass, not as a separate job. When you find the frame that made you put the camera down, put it in a folder called peek. By the end of picking, the peek is chosen and you are thirty minutes from sending it.
Set the expectation once, in writing, before the season starts, and then never negotiate it under pressure. What couples actually expect and how far it has moved is covered in what clients expect on delivery speed.
The thing that degrades in week four is not your shooting. It is your judgment on the sofa at 10 PM, on wedding six, on the eleventh version of the same first dance frame.
Research on choice is fairly blunt about why. Iyengar and Lepper's well-known jam study found that more options produced less satisfaction and less decisive action, and Barry Schwartz's work on the paradox of choice describes how a larger option set raises regret rather than quality. Research also suggests that making many decisions in a row degrades the quality of later ones, though parts of that literature are contested. You do not need the studies to be settled to recognize the feeling of the fourteenth burst.
Three defenses hold up across a long season.
Write your criteria down before the season, not during it. Sharp where it matters, eyes open in group shots, expression over technical perfection, one frame per moment unless the second one says something different. When you are tired you follow the list instead of relitigating your standards. Building your picking criteria walks through how to make yours specific enough to be useful.
Timebox instead of finishing. Ninety minutes, then a break, and stop for the night at a fixed hour even mid-wedding. A pass you resume tomorrow is better than a pass you rush at midnight, because the midnight pass is the one you re-do.
Make the fast pass low-risk. The reason quick decisions feel dangerous is the fear of losing a frame you would have wanted. Once nothing is thrown away, and unpicked simply means not chosen yet, you can move quickly and go back. That is why we built Kepla to mark picks and never to delete, move or rename a single file. The picking app for iPhone, iPad and Mac is still being built. The part that is live and free today is the booking page, which at least keeps the front of the season organized while we finish the back of it.
Eight weddings is eight ten-hour days on your feet, eight late drives, and eight weeks of eating whatever the venue had left at 9 PM. Photographers plan the files and not the person carrying them.
Book the recovery before the season, the way you would book a second shooter. A standing Sunday with nothing in it. Food you did not have to think about, in the fridge, before the Saturday. A hotel near the venue for anything over an hour's drive, priced into the package rather than absorbed at 1 AM on the motorway. None of this is indulgence. A tired photographer misses the reaction shot, and a tired photographer picking photos delivers a weaker gallery from the same day's work.
Watch for the specific signals: dreading the inbox, delivering later each week, no longer looking forward to shoots you were excited about in February. Those are workload readings, not character flaws, and the photographer burnout guide treats them as such.
The season is not over when the last reception ends. Give yourself two weeks to close it properly, and do these four things while the memory is fresh.
Clear the queue to zero. Every gallery delivered, every album order placed, every invoice paid or chased. Carrying two unfinished weddings into November means they are still there in January.
Archive properly. Move each season's finished work to long-term storage on a consistent structure, verify the copies, and note where they are. Future you, fielding a print request in three years, will be grateful.
Count what it actually took. Hours per wedding, from ingest to delivery. Not a guess. That number tells you whether eight in six weeks was ambitious or reckless, and it is the only honest input into next year's calendar.
Then decide: fewer dates or higher prices. If the season only worked because you gave up every evening, the answer is one of those two, and the quiet months are when you set it up. The slow season playbook covers what to do with the months that follow, and they are where next year's eight weddings get booked or turned down.
It depends less on stamina than on how long your post-production actually takes. Work out your real hours per wedding from ingest to delivery, then check whether the working days between weddings can absorb it. If a job takes longer than the gap between shoots, the queue grows every week no matter how hard you push. Most photographers find their honest ceiling is lower than their ambition.
Deliver one gallery for every wedding you shoot, every week. That is break-even, and break-even is survivable. Keep one job in the editing stage at a time, work first shot first out, and put the whole season on one visible page so you schedule by date rather than by whoever emailed most recently. Two weeks with nothing delivered is your early warning.
Back up that night, always, but leave the selection for a clear head. After a ten-hour day your judgment on expression and focus is at its worst, and a rushed pass is the one you end up redoing. Copy to two drives, start the cloud upload, check the file counts match, then sleep. The picking goes faster on Monday morning than at 2 AM.
Custom presets for every couple, same-week blogging, daily social posting, album design, and answering email as it arrives. Batch the albums into one block in the autumn and tell couples upfront. What you never cut is the same-night backup, the sneak peek within 48 hours, and one full day off each week. Those three hold everything else up.
Within 48 hours, ten to fifteen finished images. It is the highest leverage half hour in the whole workflow. A couple who has seen nothing fills the silence with worry and emails you about it, which costs you time and tempts you to jump your own queue. A couple who has already shared their favorites will wait the full contracted timeline happily.
Often yes, even at the cost of some margin. Compare the per-wedding fee against what those hours are worth to you, including the weddings you turn down because the queue is full and the price of arriving at October exhausted. Many photographers outsource only during peak weeks and bring the work back in-house once the calendar loosens.
Kepla for Mac clears the obvious misses from a card, names the reason on every frame it sets aside, and leaves the choosing to you. Nothing is ever deleted, moved or renamed. Free through the private preview · the first hundred photographers keep it at $99 a year.