When AI culling actually saves time: a workflow audit

AI culling does not save time simply because it puts stars on your photos. It saves time when it takes over a stretch of work that is both repetitive and slow, without handing you a cleanup job of the same length. Whether that describes your evenings is a question about your workflow, not about the software. Here is the audit that answers it.

The saving is conditional, so measure it

Every tool in this category promises hours back. None of them has watched you work. The saving is real for some photographers and close to nothing for others, and the difference is not the software, it is the shape of the job you feed it.

Culling is a double-digit slice of a working photographer's year, according to the one survey in this field that asked photographers rather than customers. We used that survey and the arithmetic that follows from it in how much time AI culling actually saves, along with the five costs the marketing math leaves out. This article is the other half: the measurement that produces the numbers you put into that arithmetic.

It is a before and after audit. You time your current process on jobs you would have shot anyway, you run one comparable job the assisted way, and you compare like with like. It costs you a notebook and some attention. It replaces a decision you would otherwise make from a feeling, in a month when you are tired and a vendor's landing page is very convincing.

One warning before you start. Compare a stopwatch against a stopwatch, never against a memory. Memory always flatters the way you already work, and it will also flatter a new toy in its first week.

Time your current process in stages, not as one number

A single figure for the whole evening is useless here, because a total cannot tell you which part of the evening a tool would touch. Break the job into stages and time each one separately. Three jobs, not one. A demo is a story, an average of three is a business case.

Pick three recent jobs that represent your normal work rather than your best day. A bright outdoor wedding with a disciplined second shooter, a dark reception, a family session with a toddler on the loose, a long conference: these produce very different culls, and if all three of your test jobs are easy, the audit will tell you something that is not true in November.

Copy that sheet three times and fill it in as you go, in minutes. Do not reconstruct it on Sunday from memory. The stage that matters most is the one that is repetitive and consistently slow across all three jobs, because that is the only stage assisted culling can attack. If your technical pass and your burst comparison together dwarf your story pass, there is a saving waiting for you. If your first pass is already short because you shoot tight, and your real delay is client feedback or retouching, no culling tool will fix your calendar.

Keep your time and the computer's time in separate columns

This is the single most common reason an audit gives the wrong answer. Twenty five minutes of analysis that runs while you are backing up cards, replying to an email, or driving home is not the same twenty five minutes as sitting there unable to start. Both belong in the log, in different columns.

Active time is you clicking, zooming, comparing, correcting a rating, chasing an export. It is the number that limits how many jobs you can take. Waiting time is preview building, file copying, uploading to a cloud tool, a model scoring frames. It is calendar time, and it decides when you can deliver, not how much capacity you have.

Both matter, so do not merge them. A tool that cuts your active time in half while adding an hour of upload has made your capacity larger and your turnaround worse. If you sell fast turnaround, that trade is a bad one, and only a two-column log makes it visible.

One more line worth its own place in the log: context switches. Count how many separate sittings a job takes from card to handoff. Three short evenings cost more than one longer one, because each restart makes you reload what you had already decided.

Write the pass mark before you start the trial

Decide what would count as success while you are still neutral. A threshold written afterwards is not a threshold, it is a justification for the money you already spent.

Write one sentence, with your own numbers in the blanks: this earns a place in my workflow if it cuts active first-pass time by at least ___ minutes per ___ frames, preserves the ratings and labels my editing workflow depends on, and misses no more than ___ frames I would have delivered. Sign it and date it in the same notebook as the baseline.

Set the tolerance by consequence, not by file count. A 2,000-frame branding day and a 2,000-frame wedding do not carry the same risk. In a controlled headshot session, the criteria inside a near-identical group are clear: eyes open, expression on brief, hair and wardrobe right, focus on the near eye. You can accept a tighter automated first pass there. A first look or a parent watching the vows happens once, so your tolerance for a missed frame should be close to zero, whatever the software scored.

That leads to an always-review list, written before you start. For a wedding: processional, vows, first kiss, family formals, first dances, speeches, exit. For sports: scoring plays, awards, celebrations, athlete portraits. For events: speakers, sponsors, group photos, the wide room. Software narrows the stack; the checklist is what stops speed from turning into omission.

Run one comparable job the assisted way

Now the after. Use the same kind of shoot, at a similar frame count, ideally in the same season of your year. A 900-frame family session and a 3,400-frame wedding are not the same test, and comparing them tells you about shoot size rather than about the tool. If you want the size effect on its own, that is a separate curve.

Time the whole route, starting where the baseline started. Ingest, upload if the tool is cloud based, the wait you cannot walk away from, the review of what it proposed, and the disagreements. That last one is where the minutes hide. Every tool in this category will set aside a frame you wanted and hand you two near-identical ones where you needed the better one, and sorting that out is work.

Two rules keep this honest. Do not review every frame anyway. If fear sends you back through the whole card, the workflow has not changed and your log will show a saving that does not exist in real weeks. And do not run the trial in the same week you are learning the shortcuts. Everyone is slower at first, everyone forgets to count it, and that is why so many photographers conclude in week one that a tool did nothing.

Time is not the only question, and it is a mistake to answer both at once. Whether a tool would have found the frames you actually delivered is an accuracy test with its own method, and we wrote it up as a test you run against a gallery you already delivered. Run that one separately, on an old job, before you time anything on a live one.

Time the handoff, because that is where savings vanish

A fast first pass that creates metadata repair work is not fast. Before you credit a tool with an hour, confirm that its output travels in the direction you actually work.

If you start in Photo Mechanic and finish in Lightroom Classic, check that stars, flags and color labels write to XMP and survive the import. If you work in the cloud, run one complete job through sync, edit, export and archive rather than admiring a demo folder. If you hand work to someone else, the format your editor can read is part of the test, and a tidy handoff is worth money on its own, which is the whole argument in cull before you outsource.

Check what you already own before you add a subscription. Adobe now ships Assisted Culling in Lightroom Classic and cloud Lightroom, under Catalog Settings, Metadata, Assisted Culling. It scores subject focus, eye focus and eyes open, and it can run at import. Adobe describes it as optimized for portraits and headshots, so it is not a universal answer, but if you already pay for the photography plan then your baseline comparison should probably be against that rather than against nothing. We went through what it does and does not do in our Lightroom Assisted Culling review.

What the result actually tells you

Put the two logs side by side and look at the pattern rather than the total. Four patterns come up again and again, and each one points somewhere different.

Notice that only the first row is a buying decision. The other three are diagnoses, and two of them are about your workflow rather than about any product. That is a good outcome for an afternoon of note-taking, because it stops you paying a subscription to fix a problem you do not have. If you want a rate to compare your baseline against before you start, our culling time benchmarks are built for exactly that.

Re-audit after five jobs, then leave it alone

The first job is the worst version of the result. Log the next four as well, including the parts nobody counts: preference adjustments after a lens change, the extra minutes a very dark reception costs, the occasional odd result you have to think about. A tool that saves an hour per wedding and costs ten minutes of setup still wins comfortably. One that saves fifteen minutes probably does not survive another subscription and a fragile export step.

Then look downstream, because the effects that matter most are the ones a stopwatch on the cull will never show. Can you start editing the same night instead of the next weekend? Can you send a tighter, more predictable set to an outside editor? Do you make fewer late-night one-more-pass decisions on work that was already finished? An hour of active time saved is worth less than a gallery that goes out a day earlier, and both are worth less than not culling at 1am.

Re-run the audit when something structural changes: a new camera body with a faster burst rate, a jump in volume, a genre you have not shot before, a change in what you deliver. Otherwise leave it alone. The point of measuring is to stop having the argument, not to keep having it with better numbers.

This is the workflow Kepla is being built for, and the honest version of where it sits today. 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 picked up on the Mac for the frames that need a big screen, with nothing ever deleted, moved or renamed, so every frame it set aside is one tap away. When it ships, run the audit on it the same way you would on anyone else's. The booking page is live and free today.

FAQ