The client photo selection workflow
Album selects are the step that stalls for months. Most of the fix is in how you hand the folder over, not in what the couple uses to open it.
A client photo selection workflow that actually completes has four parts: a target number, a deadline, a single tool the couple can start without you, and a defined return format. Missing any one of them is what turns a two-week step into a six-month one.
The bottleneck is almost never the couple's willingness. It is that "choose your favourites" from a 10,000-photo folder is not a task anyone can start, so it gets postponed indefinitely.
Where the workflow actually breaks
If you have delivered more than a few weddings, you have seen the same three failures:
- Nothing comes back. The couple opened the folder once, saw the scroll bar, and closed it. No deadline meant no forcing function.
- Too many come back. Six hundred selects, which means they did not choose — they deferred, and now you are choosing.
- The wrong files come back. Renamed, renumbered, or run through a phone's photo app and re-compressed to something you cannot print.
All three are preventable in the delivery message. None of them are preventable by the tool alone.
1. Give them a number
"Pick your favourites" is unbounded. "We need about 200, and the album holds around 80 of them" is a task with an end. Say both numbers — couples who are told only the album size hand over exactly that many and leave you no design room.
For a multi-day Indian wedding, 250–400 is the usual ask, because each function needs its own short story. The reasoning is laid out in how many photos a wedding album needs if you want something to forward.
2. Give them a deadline and a default
A date alone is weak. A date plus what happens if it passes is what works: "if we have not heard by the 30th, we will make the selection ourselves and send you a proof." Most couples would rather choose than be chosen for, and the ones who genuinely do not mind have now given you permission to move.
Put it in the delivery email, not in the contract. Nobody re-reads the contract.
3. Give them something they can start alone
Whatever you send has to survive being opened at 11pm by someone who is not going to ask you a question first. That rules out anything needing an account they have to create, a plan they have to choose, or an install that will prompt them about permissions they do not understand.
The realistic options:
| Option | Who pays | Couple can start alone | You get back |
|---|---|---|---|
| Client gallery (Pixieset, Pic-Time) | You | Yes | A favourites list, automatically |
| Free local browser tool | Nobody | Yes, on a laptop | A folder they send back |
| Lightroom flags | Them | Rarely | Whatever they manage to export |
| "Send me a list of filenames" | Nobody | Yes | A list, if they finish |
If you already run a gallery, use it — it is the smoothest path and the favourites come back to you without a handover step. Where a free local tool fits instead covers the cases where it does not.
4. Brief the method in three lines
This is the highest-leverage part and it costs you nothing. Paste this into the delivery email:
- Go through once quickly and reject rather than rank. Ask only "is there a reason this could not be in the album?"
- When you hit a burst of near-identical frames, keep one and move on.
- Do it together, in one sitting, out loud. Separately produces two lists and an argument.
Couples who get those three lines finish. Couples who get "let me know your favourites!" do not. If you want to send the long version instead, the culling guide is written for exactly this and is free to forward.
5. Define what comes back
Say explicitly which you want:
- A folder of the selected files, original filenames intact, zipped. Unambiguous, survives being forwarded to an album designer, large.
- A plain text list of filenames, one per line. Small, and filters straight into your catalogue.
And say the two things not to do: do not rename anything, and do not send the photos through a messaging app or phone photo service that re-encodes them. This page says it for you if you would rather link than explain.
6. Sanity-check before you design
Before the album goes into layout, spend five minutes on the returned set:
- Is the count in range? Under target means gaps; far over means they deferred.
- Is every function represented, or did the sangeet get skipped because it was the biggest folder?
- Are both families present? This is the correction that hurts most after a proof.
- Is there orientation variety in the moments you will build spreads around?
- Did they flag any must-haves or exclusions? If not, ask now.
Catching a missing function here costs a message. Catching it after the first proof costs a redesign.
A delivery message you can copy
Template
"Your photos are ready — link below. Next step is choosing the album selects. We need around 200 photos; the album itself holds about 80, and the extra gives us room to build spreads.
Three tips that make this take an evening rather than a month: go through once quickly and only reject what could not be in the album, keep just one frame when you see a burst of near-identical shots, and do it together in one sitting. If it helps, this free tool opens the folder straight from your laptop with no upload and no sign-up: shaadi-pic.aicleanerpro.app
Send the selects back as a zipped folder with the filenames unchanged — those names are how we find the frames. Could we have them by the 30th? After that we will make a selection ourselves and send you a proof to react to."
Where this sits in the whole delivery
Cull, edit, deliver, client selects, album design, proof, print. The selects step is the only one where the clock is not yours, which is why it is worth engineering rather than hoping about. Everything above exists to make that one step finite.
The free tool for the picking part
Shaadi Pic opens the wedding folder straight from your
drive — nothing is uploaded, there is no account and there is no charge.
Left arrow skips, right arrow keeps, Z undoes. Your keepers
are copied into a /selected subfolder with filenames
unchanged, ready to zip and send back.
Open your folder and start picking →
Free · runs locally · no sign-up · needs a laptop running Chrome, Edge, Brave, Arc or Opera
Frequently asked questions
- How do I stop clients taking months to choose album photos?
- Give them a specific number, a deadline with a stated default if it passes, a tool they can start without you, and three lines on the method. The delay is almost never unwillingness — it is that an unbounded ask from a 10,000-photo folder cannot be started.
- How many photos should I ask a couple to select?
- More than the album holds. For a 20-40 spread album that holds 60-120 photos, ask for 150-250, or 250-400 for a multi-day Indian wedding. Tell them both numbers so they understand why the ask is larger than the album.
- What format should client selects come back in?
- Either a zipped folder of the selected files with original filenames intact, or a plain text list of filenames, one per line. Specify which, and tell them not to rename files or send them through an app that re-compresses images.
- Should I just choose the album photos myself?
- It is a legitimate default when a deadline passes, and saying so upfront often gets the selects moving. As a first option it is riskier: you cannot know which cousin has to appear or which guest should not, so a proof round is still needed.
- Do I need a client gallery for this?
- No, though a gallery is the smoothest route if you already run one, since favourites come back automatically. If you do not, a free local tool the couple opens on their own laptop covers the selection step without a subscription.