Time tracking for photographers: how long editing a shoot takes
· 7 min read
Most photographers price the shoot and absorb the edit. You know what a half day on location costs, and then you guess at “a few evenings” of culling, developing and retouching, which is where the margin quietly goes. The fix is not a stopwatch you will forget to start. It is a record of where your desk hours went, kept automatically, so that after three or four jobs you know your real post-production hours per shoot and can price them.
Why the edit is the part nobody measures
Shoot time is easy to track because it has a start, an end and a client standing in front of you. Post-production has none of that. It happens in twenty-minute pieces between other things, across four evenings, interleaved with email about the next booking. By the time you deliver, the hours have dissolved.
Two habits make it worse. Culling feels like nothing: you are looking at pictures, not working, right up until you notice two hours are gone. And retouching has no natural stopping point, so it expands to fill whatever time exists before the deadline.
An automatic record of which app was in front of you catches both without asking you to do anything while you work. That is the specific thing it is good at.
What a Mac record can and cannot tell you
Be clear about the limit up front. A tracker that watches the frontmost app knows app names, not projects. So it can tell you that you spent five hours in your raw developer on Tuesday and Wednesday. It cannot tell you which wedding those five hours belonged to.
For a photographer that limit is less painful than it sounds, because of how the work is shaped. Most photographers work one job at a time through post. You shoot Saturday, you cull Sunday, you develop Monday and Tuesday, you deliver Wednesday. The dates do the project separation for you. Write the job name on the days it covered, and the app totals become per-job totals.
If you genuinely run four edits in parallel, an app-name record will not split them and you should know that before you rely on it. Punchcard does no per-project or per-client tracking at all: no projects, no tags, no timers to start. It notices which app is in front, app names only, never window titles or document names, and prints a receipt of the day. Do you need a project picker? Probably not makes the case for why most solo workers do not, and it is worth reading before you decide.
The measurement: three shoots, no extra effort
This takes no discipline during the work, which is the point.
- Pick three upcoming jobs of the same kind. Three portrait sessions, or three weddings. Do not mix a corporate headshot day with a two-day wedding and expect a useful average.
- Write the shoot date and the delivery date for each one on a card or in a note. That is your window.
- Let the tracker run. Do not change how you work. Do not try to be efficient for the experiment; you want a normal number, not a best case.
- At the end of each day in the window, look at the day’s record and write the job name on it. One word. If you print receipts, write it on the paper.
- When you deliver, add up the hours in the editing apps across that window.
What you get out is a number like “eleven hours of post for a four hour portrait session”. That number is worth more than any figure in any pricing guide, because it is yours, on your Mac, with your workflow and your standards.
Split the post hours into the four real stages
Once you have the totals, break them apart. Photographers tend to find the time is distributed very differently from how they imagined.
- Ingest and backup. Copying cards, verifying, building a second copy. Often the Finder line on your record, and longer than anyone guesses, because it involves waiting.
- Culling. Your raw developer or a dedicated browser, moving fast, making choices. The stage most likely to be double what you expected.
- Developing and retouching. The stage you priced for. Frequently not the biggest one.
- Export, delivery and client admin. Gallery uploads, a browser line, email, invoicing. Almost never counted in a quote, and on small jobs it can rival the retouching.
The last one is where the surprise usually lives. If your record shows an hour and a half of browser and mail time per job, that is part of the cost of the job, and it belongs in the price. Freelancers: the difference between hours open and hours billed is about exactly that gap.
Turn the number into a price
With per-shoot post hours in hand, the arithmetic is simple and slightly uncomfortable.
Take your target hourly figure. Multiply by the real total hours for a job of that type, shoot plus post plus admin. Compare that to what you currently charge. If the gap is large, you now know what you have been donating, and you can decide what to do about it with a number rather than a feeling.
There are three honest responses, all better than continuing to guess:
- Raise the price to cover the hours the job really takes.
- Reduce the hours by capping deliverables: fewer finished images, a tighter retouching standard, less admin in delivery.
- Keep the price and accept the rate, deliberately, for work you want in your portfolio.
The time audit to do before raising your rates covers the conversation that follows, and How to estimate hours for a quote when you never tracked the last job is the one to read if a quote is due before your three jobs are done.
Keep the receipts as the paper trail
There is a second use for a daily record that has nothing to do with pricing. When a client asks why a reshoot request is not free, or why the album took three weeks, a stack of dated records showing the hours is a calm answer. It does not need to be an official document. It needs to exist and to be consistent.
Punchcard keeps its data in one SQLite file in your own Library folder, exports CSV, and can export a day as a 1080x1350 PNG if you want to show the work publicly. There is no cloud and no account, which matters when your Mac holds client images under a contract. Proving your hours when a client disputes an invoice goes into how to use that well.
Questions
Can a Mac tracker tell one shoot’s editing from another? Not by itself. It records app names, not documents or projects. Dates do the separating, so write the job name on each day and the totals become per-job.
Does culling in a browser-based gallery get counted? It counts as browser time, because that is the app in front. If a lot of your culling happens in a web gallery, expect your browser line to carry it.
Is an app-name record enough for a photographer who shoots two jobs a week? Usually yes, if you edit them in sequence. If you edit two jobs on the same afternoon, the record cannot split that afternoon and you will need to note it yourself.
How many jobs before the average is useful? Three of the same type is enough to stop guessing. Five makes it solid. The first one alone will mislead you, because the first job you measure is never typical.