A Repeatable Post-Production Checklist for Photographers

Why a post-production checklist beats good habits

Habits fail at the edges: the rushed shoot, the second shooter's cards, the client who replies three weeks late. A checklist is written for those edges, not for the easy case.

Consider the arithmetic of a single skipped step. Say you shoot 4 jobs a month and each has 11 steps. That is 44 step-executions a month, or 528 a year. If you miss just 2% of them, that is about 10 misses a year (528 × 0.02 = 10.56). Each miss is a wrong file delivered, a note not applied, or a gallery left online. The 2% is an illustration, not a measurement, but the point holds: at this volume, "I usually remember" still leaves you with roughly one preventable mistake a month.

The second reason is handoff. The moment a second person touches a job, whether a retoucher, an assistant or a second shooter, anything unwritten is lost. The checklist is the contract between you and them. If you already name files consistently, see our guide to file naming conventions for photo teams; the checklist assumes that groundwork exists.

The eleven steps, in order

Group the steps into four stages. Each stage ends in a gate: a condition that must be true before the next stage starts. Gates are what make this a system instead of a to-do list.

Step 6 looks redundant next to step 5, and it is the most valuable line on the list. Freezing the selects means the client cannot quietly add twelve more frames after you have retouched thirty. Additions after the freeze are a new, priced request, which we cover in what to do when a client wants changes after final approval.

Gate 1 and 2: ingest and select

Ingest is the only stage where a mistake is unrecoverable, so it gets the strictest gate. Copy to two places, open a few files from each, and only then clear the card. Do not rename in the same pass as copying; rename after you know the copy is good.

The first-pass cull should be subtractive and fast: reject only what is clearly unusable. Resist ranking. Ranking at this stage is effort spent on frames the client may never choose. Build the proof set, then send one link. Sending a gallery by email in three pieces creates three conversations to reconcile.

Decide in advance how many frames the client sees. A short proof set returns faster and with clearer notes; we weigh that trade-off in should clients see every frame or only your selects.

Gate 3: editing from a frozen list

Do the global edit before the retouch. Colour, exposure and crop applied to a hundred selects take one pass; applied after you have retouched, they mean redoing finished work. Retouching is the expensive step, so it goes last, on the smallest set.

When the client's notes come back, the failure point is rarely the retouching itself. It is the translation from a comment to a changed pixel. Anchored, per-frame notes remove most of the guesswork; our piece on per-image comments versus whole-gallery feedback shows why. Keep a single list of what is open and what is done, so "done" lives in one place rather than being retyped in an email, a spreadsheet and a chat.

If the retoucher works in Photoshop, Appruva's Photoshop panel can show the numbered notes next to the open file, place the client's markup on it as a layer, and deliver the finished frame back as a new version, closing the notes you ticked. That collapses steps 8 and 9 into one place instead of a folder, an export and an email. It is a Photoshop panel only, and it delivers JPEG or PNG.

Gate 4: sign-off and archive

Sign-off is a recorded event, not a feeling. Whether it is a button on a review link or a reply email you save, you want a dated record of which round the client approved. When the client says in six months that they never saw the crop, you can point to it.

Then close the job properly: export finals in the agreed formats, move the originals to the archive location you chose, and set the gallery expiry so you are not hosting finished work indefinitely. The reasoning for the expiry decision is in how long to keep client photo galleries online.

Where a post-production checklist usually breaks

Checklists rarely fail on day one. They fail in week six, in one of four predictable ways.

• The list lives somewhere you do not look. A checklist in a folder you open once a quarter is an archive. Put it inside the tool where the job already lives, and copy it per job so ticking a box is part of the work.
• Gates get waived "just this once". The first waiver is usually step 6: a friendly client, a tight deadline, retouching begun on the cull. It goes fine, so the next waiver is easier. Hold the gate on friendly clients too; they are the ones who send a second list.
• One owner for everything. If you own all eleven steps, the checklist is a private reminder. If a retoucher owns steps 7 to 9, they need the list too, and they need to know what the gate before them guarantees.
• Steps with no definition of done. "Global edit" means nothing without a boundary. Write what finished looks like in a few words: "exposure and white balance matched across the set, crop set to the delivery ratio".

A useful test is to hand the checklist to someone who was not on the shoot and ask what they would do first. If they ask you a question, the list has a gap. Fix the gap on the page, not in conversation, so the answer survives you being unavailable.

Time is the other hidden variable. Add a start date and a target date to each stage when you open the job, and you will see immediately where a delay originates. A job stuck at the Select gate for two weeks is a client problem and needs a reminder. A job stuck at Edit is yours. Distinguishing the two stops you apologising for delays you did not cause and stops you blaming clients for delays you did.

Finally, review the checklist itself twice a year. Look back over your last ten jobs and ask which step caught a real mistake, which step was skipped without consequence, and which mistake happened that no step covers. Add one, merge one, and leave the rest alone. A checklist that never changes is not being used; one that changes every week is not a checklist.

Adapting the checklist to your shoots

Do not treat the eleven steps as sacred. Treat the gates as sacred and the steps as defaults. A wedding adds an album-design stage between steps 6 and 9; a product shoot may compress steps 3 to 5 into a single bulk review. A solo photographer can merge the Edit steps; a team should assign an owner to every gate, not every step.

Start by printing the table and running your next job against it, ticking each line as you go. Note every step you skip and every step you invent. After three jobs, your list will differ from this one, and that difference is the checklist becoming yours. Store it where you open it, not where you filed it: a template in your job-tracking tool, or a plain text file duplicated per job. If you want a lightweight way to track status as jobs move through, see our simple photo status tracking system.