Enquiry and booking
The client asks about availability, price, style, deliverables, and timing. This stage needs clear expectations and a simple way to move toward booking.
Simple private galleries for easy client selection.
Guide · photographer workflow
A strong photography workflow does not end when the shoot is finished. It guides the client from curated proofs to a clear selection, useful comments, retouching, approval, delivery, and archive. This guide shows where Abistu fits into that client decision stage.
No credit card. Works in any browser. Your client does not need an account.
A good photographer workflow protects your time, your files, and the client decision.
Most workflow problems do not happen during the shoot. They happen at handoff points: after culling, during proofing, when the client selects images, or when final files are delivered.
A clean process separates each stage. Capture is not culling. Proofing is not final delivery. Client selection is not a chat conversation.
When the client can select photos, leave a comment on each selected image, add one general request comment, and submit everything in one place, the next production step becomes much easier.
In one line
The client selection stage should not live inside your chat history.
Tools change from photographer to photographer. The core stages are usually the same.
The client asks about availability, price, style, deliverables, and timing. This stage needs clear expectations and a simple way to move toward booking.
Confirm the goal of the shoot: portraits, wedding coverage, product images, event documentation, commercial assets, album images, or social content.
The photography stage is creative and technical, but the final selection already starts here: capture enough coverage while thinking about how the client will choose later.
Import the files, back them up, remove mistakes, duplicates, technical failures, and frames you do not want the client to choose from.
Upload a curated set for client review. The client should choose visually, not reply with screenshots, filenames, or vague descriptions.
The client selects images, adds per-image comments where needed, writes one general request comment, and submits the selection in one structured request.
Work from the submitted selection. Retouch, export, resize, prepare print files, prepare web files, or finalise the commercial deliverables.
Send final files through your normal delivery method, then archive originals, finals, notes, and the selection record so the project remains traceable.
Friction appears where a decision moves from one person or tool to another.
Client messages in WhatsApp, files in Drive, notes in email, proofs in a folder, invoices somewhere else. The work moves forward, but the source of truth disappears.
The client sends screenshots, filenames, or descriptions like “the one near the window.” You then translate their words back into image files.
If the client sees too many near-duplicates or weak frames, selection becomes slow. Good workflow starts before proofing: send a curated set.
Proofs are for choosing. Finals are for using. If both stages are mixed, clients may download unfinished work or approve the wrong version.
Likes, chat replies, and screenshots are not reliable records. Later you need to know exactly which images the client chose and why.
If the selection is vague, retouching begins on shaky ground. Every unclear approval increases the chance of rework.
The improvement is not only organisation. It is whether you can move forward without decoding scattered messages.
A good workflow does not require one tool to do everything. It requires the right tool for each job.
A private gallery is not just a prettier folder. It is a way to collect a visual decision.
The client marks the photos they like most before you prepare retouching, album work, print options, or featured delivery.
The client chooses exactly which photos should move into final editing. You avoid spending hours on images that will not be used.
Wedding, family, portrait, and event clients can select images for albums, wall prints, gifts, covers, or final sequences.
Brands and agencies can approve product shots, campaign images, web assets, press images, or social media selections.
Clients can leave comments about crop, expression, colour, usage, priority, retouching, or changes on the relevant selected images.
A gallery can also collect interest in extra retouching, additional images, prints, copies, another session, or an expanded package.
A simple, repeatable process is often better than a large system nobody uses well.
The client should not review technical rejects, weak duplicates, or material you would not recommend. Your selection is part of your professional value.
Proofs help the client decide. Final files are delivered after the decision. Mixing them creates confusion and unnecessary revisions.
Do not ask only for opinions. Ask the client to select favourites, choose photos for retouching, approve a set, or leave comments on selected images.
Send the link wherever you communicate, but keep the actual selection inside one structured gallery instead of email, chat, and screenshots.
Your future self needs to know which images were selected, what comments were attached, and what the client requested.
A selection gallery can be lightweight. Keep heavy final delivery, RAW archives, contracts, and invoices in the tools built for those jobs.
The details change by genre, but the client decision stage remains similar.
Separate preview delivery, album selection, print selection, final delivery, and archive. Couples should not choose album photos through a chat thread.
Clients often need to choose a smaller number of images for retouching. A clean proofing step prevents confusion between proofs and final edits.
Agencies and brands need structured selections for retouching, licensing, web use, product pages, campaign assets, or social content.
Organisers can select press images, website images, speaker photos, sponsor moments, recap images, or internal assets quickly.
Emotional images can overwhelm clients. A calm gallery and simple selection process make the decision easier.
Privacy matters. Client selections should not move through public folders or casual screenshots when the images are sensitive.
Small workflow mistakes accumulate into delays, extra messages, and unnecessary editing.
Unless the client specifically paid for all images, sending everything creates overwhelm and exposes weak duplicates or technical rejects.
The client should choose from a professional proof set, not solve the first technical selection for you.
Retouching before selection can waste hours on images the client will not use.
Filenames are practical for storage, but clients decide visually. Do not make them build a list manually.
A positive message is not always a final decision. Use a submitted selection when approval matters.
After delivery, keep originals, finals, and the approved selection in a predictable structure.
Clear instructions prevent slow replies and vague selections.
Please open the gallery, select the photos you would like me to retouch, add a comment to any selected image if needed, and submit the request.
Please select the images you would like included in the album. You can add per-photo notes and one general comment before submitting.
Please mark the images that should move into final retouching. I will use the submitted selection as the working list.
Please choose the images you want for the press kit, website, or internal communication, then submit the selection from the gallery.
Please review the final images and select the ones you approve for delivery, publication, or production.
Please select the images you would like printed and include size, quantity, or framing notes in the general comment.
Abistu is the lightweight client-facing layer for selection, comments, and structured requests.
Clients choose photos directly inside the gallery. You do not have to match screenshots back to files.
The client can add a comment on each selected image, so feedback stays connected to the right photo.
The final request includes selected images, per-image comments, one general request comment, and the client contact.
After submitting, the client receives an email copy of the request, so both sides know what was sent.
The client opens the private link, reviews the gallery, selects images, comments, and submits. No app, no login, no registration.
Keep Lightroom, Capture One, Pixieset, ShootProof, Drive, Dropbox, or your CRM. Use Abistu for the selection gap.
A focused tool should be honest about its boundaries.
Keep RAW files, masters, and originals in your normal storage, backup, and editing system.
There is no lab integration, cart, checkout, fulfilment, or full print store. Use a dedicated platform if print sales are central.
It does not manage contracts, invoices, booking calendars, questionnaires, or automated client pipelines.
A proofing gallery is for review, selection, and requests. You can still deliver final high-resolution files through your usual method.
Use this before sending the next client gallery.
This is a live gallery — not a screenshot. Tap any image to mark it. Press the button to send a request. This is what your client sees.
One proof gallery. One client selection. One structured request.
A photographer workflow is the repeatable process from client enquiry to booking, shoot, import, backup, culling, proofing, client selection, retouching, final delivery, and archiving.
Client proofing usually sits after internal culling and before final retouching or delivery. It is the stage where the client decides which images move forward.
Usually no. A curated proofing set makes the decision faster, protects your standards, and avoids overwhelming the client with weak duplicates.
Yes. In Abistu, the client can select images and leave a comment on each selected image when specific feedback is needed.
Yes. The client can add one general request comment for the whole submission, such as timing, quantity, usage, print size, or overall preference.
You receive selected images, per-image comments, general comment, and client contact together, so the request becomes a clear working list.
Yes. The client receives an email copy of the request after submitting, which makes the selection easier to confirm later.
No. Keep your editing, delivery, print sales, CRM, and archive tools. Abistu is a lightweight layer for private gallery selection and structured requests.
Send one proof gallery, let the client choose visually, collect item comments and a general request comment, and receive one clear selection back.
No screenshots. No filename archaeology. No lost decisions.
Currently in early access — no credit card, no commitment.