The thirty day backlog plan: week by week

Thirty days is enough to clear a backlog and change the thing that built it, but only if the month has a shape. This is the week by week version: one week to see what you owe, one to close every first pass, one to ship whole galleries, one to fix the cause. Dated targets, honest hours, and the point where the plan stops working.

Run this when the pile has stopped growing

This is not the plan for the week when nine galleries are late and a wedding lands tonight. That week has its own order and it takes two days: every job gets one verdict, you ship what is nearly done, you move the dates you cannot hold, you park the rest. That is the 48 hour triage version, and it is what you run first if you are reading this at midnight with your inbox closed.

The thirty day plan starts where triage ends. It assumes three things are already true: every outstanding job has a verdict, nobody with a date inside the week is waiting in silence, and new cards get backed up the day they are shot. If any of those is false, spend two days making them true and come back. A recovery plan applied to a queue that is still growing is a slower way to be late. The goal is not an empty queue, it is to get current and stop the same pile rebuilding in October, which is why the month has four weeks with one job each rather than a daily schedule you abandon by Wednesday.

Be honest about the hours before you plan a block. Most photographers can hold about four focused ninety minute blocks in a weekday, which is six working hours, not the imaginary twelve between breakfast and bedtime. Plan against six and the month survives contact with a real week.

Week one: build the ledger and protect the files

Day one is a table, not a catalog. Every undelivered job gets one row: client, shoot date, promised date, whether two copies exist, whether the first pass is finished, edit status, and the single next action. Nine jobs takes about thirty minutes. Do it before you open Lightroom, because the moment the table exists the backlog stops being a fog and becomes a list, and lists end. The longer version of that ledger is in the full backlog repair kit.

Then add the column most people skip: hours remaining. Estimate the picking, editing and delivery time left on each job and total it. Counting folders tells you how guilty to feel. Counting hours tells you whether thirty days is realistic, and it usually shows two jobs carrying most of the weight while five are an evening each.

Backups come before any creative work. Any job on a single drive or still on a card is urgent whatever its promised date says, because a card failure on top of a backlog turns a bad month into a business event. Verify the second copy, and format nothing until you have.

With the table sorted by promised date, week one has one more task: the messages. Every client whose date is at risk hears from you this week, before they chase you, with a specific new date you have already blocked out in the calendar. Never write soon, and never name a date whose production blocks do not exist yet, because the second missed date costs far more than the first. If the writing is what stops you, our client email templates have wording you can adapt in minutes.

Resist editing this week unless a deadline is genuinely inside it. Week one buys the thing you have not had for a month: an accurate picture of what you owe.

Week two: close every first pass, in blocks

One rule governs week two: nothing gets edited until its selection is finished. An unpicked shoot is not one item on a list, it is an unknown quantity of work, and unknown quantities are what a tired brain refuses to start. Once the set is closed, the edit has a size you can schedule.

Work in two ninety minute blocks a day, no more, each with a written stop point. Selection is rapid judgment repeated thousands of times and it degrades faster than editing does, which is why late night picking produces sets you disagree with a week later. Run the same sequence in every block so you are not inventing a method while tired.

1. Technical rejects first: missed focus, blown frames, misfires, the shot of the floor.
2. Then near identical frames, one keeper per burst, chosen by eyes and expression rather than by sharpness alone.
3. Then the story pass: the moments, the family groups, the details you promised.
4. Stop at the line you wrote, record the keeper count and the next decision, and close the job.

Decide the delivered number before you open the folder. Typical wedding coverage produces 2,000 to 4,000 frames and delivers 400 to 800 of them, and the top of that range is roughly double the editing work of the bottom for the same fee. Flag 1,500 and you have not finished picking, you have moved the decision into the edit where it costs several times as much.

Then leave it alone. Going back through a folder you have already worked is the largest silent time sink in post production. The habits that make a decision stick are in rejecting photos without second guessing every frame.

Week three: batch the edits, ship whole galleries

Week three has one instruction: finish things. Take the oldest promise first and complete it before opening anything else. Nudging five galleries forward so everyone is slightly less late is the most expensive habit in a backlog. Five half done catalogs deliver nothing, and every reopen costs twenty minutes of loading the shoot back into your head.

Now that several jobs have closed selections, edit by condition rather than by job order where you can. Build a reference frame for each lighting situation, prep by the window, ceremony, portraits, reception, then apply that base across the group and refine only where your eye changes the result. Batching is not one look pushed blindly across rooms with different light. It is refusing to make the same exposure decision four hundred times.

Set a delivery floor and hold it, because in a backlog perfectionism does a convincing impression of professional standards. The floor is the contracted count, consistent exposure, white balance and crop, your normal edit applied evenly, and nothing extra. No bonus images because you feel guilty, no five versions of one portrait. Padding a gallery is not generosity when it is what makes you late, which is the case made in why over delivering costs you more than it gives the client.

Give export and gallery setup their own block rather than treating delivery as an afterthought at the end of an editing day. Rushed exports are how a backlog doubles, so run the same short check before every send. Then send it, mark the row done, take the next one.

Week four: fix the cause while the evidence is fresh

A reset fails if incoming work puts you straight back where you started, so the last week goes on the cause rather than the queue. You now have a ledger showing exactly where each late job stalled. Read it before you theorize.

The stall is almost always at one of three places, and each has a different fix. A fourth cause, promising a turnaround shorter than the work has ever taken you, is really the arithmetic problem at the end of this piece.

• The first pass never started. If three late galleries all sat unpicked for two weeks, the fix is a deadline on picking, not on editing. Every shoot gets its selection closed within a fixed number of days of the shutter closing, and you defend that number like a client date.
• There was no protected production time. If the work only happened when a week was quiet, put a recurring block in the calendar whose only allowed output is a delivered gallery, and book it before the season rather than during it.
• The galleries are too big. Delivered count is an editing hours dial. Set it in the contract and let the first pass enforce it, and every future job gets shorter without a single change to your booking calendar.

Look at the booking pattern too, because a double wedding weekend in peak season shows up six weeks later as a backlog, and that change belongs in next year's calendar rather than in your work ethic. Then pick one change. Not five. A single rule you keep beats a redesigned workflow you abandon in the second busy week.

The twenty minute review that keeps the queue dead

Finish the month by installing the smallest habit that stops the pile rebuilding: one weekly review, twenty minutes, same slot every week. It answers four questions and nothing else. What is due next? What is still on one drive? Who needs a message? What gets the next production block? Keep it simple enough to use on a tired Friday, because a system that needs a good mood is not a system.

Add one monthly capacity check: the hours the booked work will need against the production hours the month actually contains. Five minutes, done before you accept the next date rather than after.

Then watch one number: days from shoot to finished first pass. It is the leading indicator for everything downstream, and it warns you a job will be late while there is still time to act. Editing hours and days to delivery are worth logging too, but they report a problem that has already happened.

When thirty days is not enough

Here is the part a recovery plan should say out loud. Total the hours column in your ledger, then compare it with the production hours next month genuinely holds after shoot days, travel, admin and life. If the work needs more hours than the month contains, you do not have a discipline problem. You have an arithmetic problem wearing a workflow costume, and no plan on this page fixes arithmetic.

The options at that point are all uncomfortable and all legitimate. Shoot fewer jobs at a higher price. Deliver a smaller set, since every extra two hundred files is another two hundred to pick, edit, export and store. Move your standard promise to a number you hit in August. Buy capacity by outsourcing part of the edit, picking the frames yourself first so you hand over an organized batch. Or pause inquiries for two weeks, a cheaper boundary than adding clients to a queue you are not clearing. The fuller sum is in booking more without adding editing hours.

One thing does not belong on that list: a month of all nighters. A tired session produces inconsistent color, missed exports and files you redo, so the night usually costs more hours than it saves. If dread of opening the catalog has become the real obstacle, that is a different problem with a different fix, and the burnout guide is the companion read.

Backlogs shrink through visible decisions, not heroic weekends. Thirty days is enough to make every decision visible, deliver the promises you owe, and change the one thing that put you here. That is a better month than catching up, because catching up is temporary and this is not.

FAQ