How to Let Photography Clients View and Select Their Favorite Images

Give the client one clear decision at a time

The most dependable client selection workflow separates browsing, favorites, submitted choices, approval and delivery. A heart beside a photograph means that someone liked it. It does not by itself say which product they want, whether their partner agrees, whether retouching is complete or whether the studio may send an album to print.

A private online gallery can make that conversation much easier. The client sees a considered selection on their own device, marks photographs and sends a manageable response. The studio still needs to define what that response means and connect it to the correct originals. This article follows the entire decision lifecycle, including competing preferences and later changes, rather than simply describing how to turn on a Favorites feature.

Our existing proofing guide provides the basic proof-to-approval record. Here we go deeper into the client experience and the gallery settings that support it. Pixieset and ShootProof examples below come from their current official documentation. They are not firsthand service tests, endorsements or evidence that Lightbox Pro already operates a hosted gallery.

Favorites, submitted selections, approval and delivery are different states

Begin by naming four states in language the client can understand. Favorites are a working shortlist. Submitted selections are the list the client says is ready for the studio’s next step. Approval authorizes a specified result, such as the layout in album proof v03. Delivery makes agreed finished files or products available. One state should not silently trigger the others.

This distinction protects creative freedom as well as production. A couple can explore choices without fearing that every heart becomes a paid retouch. The photographer can start work from a submitted list without interpreting an unfinished browsing session. When the final crop matters, a separate proof can show it before any print order is released.

A studio-defined lifecycle; the gallery provider may use different labels

State	What the client is saying	What the studio may do
Browsing	We are looking through the photographs.	Offer help; do not infer a completed selection from activity.
Favorites draft	These are possibilities for a named purpose.	Inspect emerging questions without treating the list as authorization.
Submitted list v01	Use this identified list for the next agreed stage.	Confirm receipt, reconcile identities and begin the specified work.
Proof approval v03	This exact result is approved within the stated scope.	Check production readiness and release only the approved version.
Delivery	The agreed output is now available.	Confirm correct files, permissions and retention information.

Agree how submission happens. It might be the provider’s Send Favorites action followed by the studio’s receipt, or a specific written confirmation alongside an exported list. Avoid inventing a lock if the provider still allows edits. Preserve the submitted membership yourself when an immutable snapshot is not supplied.

Write the selection brief before sending the link

A useful gallery invitation answers six questions: what the client is choosing, where to put choices, how many are requested, whether notes are wanted, when the list is due and how to tell the studio it is finished. Include one contact route for difficulty. The gallery should reinforce those instructions, rather than asking the client to remember a conversation from several months earlier.

For an illustrative wedding, ask for a first album shortlist and a separate print request. Explain whether the album count is a preferred starting point, a contractual maximum or an advisory range. Those meanings are not interchangeable. A hard cap can frustrate a couple who thinks they are saving possibilities; an unrestricted list can frustrate a photographer who believes a final design selection was requested.

Describe what clients should evaluate now. If the gallery contains final color-treated proofs awaiting detailed retouch, say that. If a particular photograph is a story reference only, make that explicit. Do not ask clients to diagnose focus from a tiny phone thumbnail or approve print color from an unknown display. Offer to discuss an important photograph that is difficult to judge.

Set an actual date and time zone for the selection deadline, distinct from gallery expiration. Explain what happens if more time is needed and how a delay affects the next production stage, using the studio’s actual policy. A deadline should coordinate people; it should not surprise a client with an inaccessible gallery while they are still making agreed choices.

Separate album, print and retouch decisions

One undifferentiated Favorites list often becomes overloaded. The client may use it for “I love this,” “Please put this in the album,” and “My parent wants a large print.” The same photograph can legitimately serve all three purposes, but the instructions differ. Name lists by their task and explain whether overlap is allowed.

Pixieset documents multiple Favorite Lists associated with the client’s email. Its preset-list controls let the photographer name a client-specific list and set an optional maximum. Use separate lists for separate decisions, with instructions that explain the limit. Verify the exact account experience before promising a particular client flow.

ShootProof’s Linked Contact documentation describes configurable labels, optional usage limits and privileges tied to the designated contact’s email and access code. That creates a distinction between an ordinary visitor’s favorites and the client’s labeled product choices. Its single Linked Contact model should inform how a studio coordinates a couple or several decision-makers.

Think about products as structured requests. “Prints” alone does not specify quantity, dimensions, crop, finish or destination. A favorite can identify the photograph while a separate order process captures those details. Do not make a free-text gallery note carry every production instruction if the studio has a clearer, checked ordering route.

Make a phone session workable without hiding the important details

Assume the client may begin on a phone between other tasks and finish on a larger screen. Keep the first instructions short, with the full policy available separately. Organize the gallery into understandable moments or sessions. Avoid making the client identify a photograph solely by “the fifth one on the second row,” because layout and order change across devices.

Test the actual visitor path on both narrow and wide screens before sending the invitation. Open the link, enter the intended credentials, view an image, add a choice, add a note if enabled and return to the list. Then reopen in the supported way and confirm that the choices persist. Use synthetic test photographs and your own test identity; do not borrow a real client’s credentials.

The heart or star should have a clear selected state and an understandable undo action. Look for readable filenames or identifiers, usable controls, visible focus and instructions that do not depend on color alone. If the platform’s interaction is difficult for a client, offer an alternate process such as a scheduled review and an exact-ID list. Accessibility is part of helping the decision happen, rather than an extra aesthetic preference.

Tell clients how to return to the same list. Switching email addresses or using a different gallery entry path can make previous choices appear missing even when they remain stored elsewhere. A brief reminder about the expected identity is more useful than telling a distressed client simply to try again. Verify the provider’s recovery behavior instead of promising automatic cross-device recovery in every circumstance.

Plan for two partners, parents and other decision-makers

Ask who can recommend and who can authorize. For a wedding album, both partners may contribute equally while one person submits the consolidated list. A parent may choose photographs for a separate book without changing the couple’s album. A studio assistant may implement requests but have no authority to release a print order. Write these roles in the job record.

Give separate working lists when the service and account support them, or coordinate through one designated submitter. Do not imply that two people sharing an email address are independently identified. Likewise, two separate email lists do not by themselves prove that the couple has reconciled their preferences. The studio needs a final, named source of instruction.

Consider an invented example: one partner selects 52 images and the other selects 48, with 31 in common. Their combined list has 69 distinct photographs, not 100. The shared 31 identify agreement; the remaining 38 need discussion about story, relationships and space. These numbers illustrate set arithmetic, not typical wedding behavior or a provider feature.

Resolve conflict at the decision level. If one partner wants a photograph excluded from wider sharing but the other wants it in the private album, those requests may coexist. If both want contradictory crops on the same printed spread, they need an explicit resolution. Do not treat the most recent click as an agreed instruction merely because the software recorded it last.

Turn photo comments into actionable requests

Ask for notes tied to a photograph and a purpose. “Please soften the temporary mark on my left cheek for the album” is more usable than “Fix this.” Confirm perspective when left or right could be ambiguous, and clarify any request affecting identity or an important feature before work starts. Keep sensitive personal discussion in the studio’s appropriate private communication channel.

Pixieset’s favorite-note instructions describe an optional notes setting and visibility to the photographer and the client who wrote the note. Enable and test that behavior deliberately. A note attached to someone’s favorite list should not be assumed visible to another decision-maker.

Separate a request from a promise. Some changes are straightforward, others depend on the original or require additional work and agreement. Record whether the request is accepted, needs clarification or cannot be achieved appropriately. If a comment says “use the wider frame,” identify the alternate photograph rather than inventing missing surroundings or assuming the client approved an automated reconstruction.

Once a request is fulfilled, show the client the relevant result at the agreed stage. A resolved checkbox is a studio tracking event; it is not the same as client approval. Where the note affects an album crop or a large print, show the actual placement. Preserve enough context to explain why the output differs from the earlier gallery proof.

Create a deliberate finish signal and keep a snapshot

Clients may browse over several evenings. Notifications of individual favorites are useful activity signals, but they do not establish completion. Ask for one clear finish action and acknowledge it. The acknowledgment should identify the task, list name, version or capture date, image count and any unresolved questions.

ShootProof’s Favorites Notification workflow lets an enabled Linked Contact send the completed favorites with an optional note; the studio receives a dashboard and email notification. Treat receipt as the beginning of reconciliation. It does not independently establish a final crop, retouch approval or authorization to order a product.

Save the actual submitted memberships through the service’s documented export or reporting route. Keep that original report and a human-readable snapshot alongside the job record. Check counts and exact photograph identities before creating editing tasks. If the receiver finds 74 distinct originals for a submitted count of 75, investigate the mismatch before claiming that the list is ready.

If the client changes the gallery list afterward, preserve the earlier submission and record the delta: added IDs, removed IDs, changed notes and the effect on work already started. Avoid replacing the old report with a fresh download under the same filename. A simple version sequence is usually clearer than trying to infer decisions from an ever-changing online view.

1. PrepareCurated proofs, stable identities, access rules and one brief
2. ExploreWorking favorites grouped by album, prints or retouching
3. SubmitNamed decision-maker sends an identified selection snapshot
4. ReconcileStudio matches originals, clarifies notes and records revisions
5. ApproveClient reviews the particular finished image or layout version
6. DeliverChecked outputs are released with clear access and retention terms

Distinguish visibility, authentication and download permission

A gallery hidden from a portfolio is less discoverable, but anyone with a functioning direct link may still reach its entry point. A password gate adds a condition; it does not make authorized viewers unable to copy what they see. Requiring a typed email can identify a submitted address without necessarily proving control of that mailbox. Read the platform’s actual mechanism before calling it verified identity.

Pixieset’s privacy documentation distinguishes homepage visibility, collection passwords and client-only views. Hiding a collection does not disable its direct link. ShootProof likewise separates gallery status, public/private access and optional password or email requirements. Configure the layers for the intended audience rather than treating the word “private” as a complete security specification.

Use a unique appropriate gallery password and share access only with the agreed recipients. Confirm whether clients may forward the link to guests and whether particular sets or photographs should be withheld. A wedding gallery may contain children, private preparation moments or people who do not want broad circulation. Decisions about wider publication deserve their own discussion rather than being inferred from an album favorite.

Downloads are another permission. Pixieset documents controls for eligible contacts, downloadable sets and download counts. Choose those deliberately for the phase of work. A selection cap and a download cap serve different purposes; neither is a promise that a visible image cannot be captured from a screen.

Protect the studio account as well as the gallery. ShootProof requires account two-factor authentication and documents alternative methods. Use the safeguards provided for every staff user, appropriate permissions and a recovery plan. Those controls reduce specific risks; they do not justify a blanket assurance that client photographs are impossible to access or redistribute.

Make expiration and retention part of the handoff

Record three dates separately: when selections are requested, when the gallery stops being available and how long the studio retains the agreed production records. They may differ. A gallery’s availability is not a complete archive service, and an access deadline should not silently become a deletion instruction for the only surviving originals.

Tell the client what they should download, when and where to ask for an extension. Check how the chosen service handles expiration, reactivation and existing list access in the account you use. If the service cannot preserve an approval record in the required way, retain an appropriate separate copy through the studio’s established process. Do not invent a provider guarantee from a setting’s name.

Keep reminders proportionate and useful: state the pending action, correct link and revised consequence if any. If access expires during a revision round, confirm the intended next step with the client before restoring or changing permissions. Avoid sending repeated automated reminders for a task that the studio has already received but failed to acknowledge.

A change needs a version and a production consequence

Suppose a client replaces one album favorite after the retoucher has finished it. Record the removed image, replacement image and request date. Check whether the change affects retouching, neighboring layouts, print crop or a parent album. The cost is not simply “one fewer and one more” when downstream work already depends on the original choice.

Define revision rounds in the actual service agreement, without assuming a universal industry policy. At each round, distinguish corrections, new creative preferences and changes to previously approved work. Give the client a clear summary and any agreed impact before proceeding. A system that tracks decisions well can support a calm conversation instead of making the change feel like blame.

For formal approval, identify the precise artifact and scope: “Album proof v03, interiors and cover wording,” for example. Keep who approved it and when, along with the visible proof and relevant messages. This is an operational recommendation, not a claim about legal enforceability. A heart on one photograph cannot provide all of that context.

The connected workflow Lightbox Pro is working toward

Lightbox Pro’s long-term direction is to connect a client’s print and album selections back to the photographer’s catalog. A useful future implementation would retain original identity, list purpose, submitter, revision and approval scope rather than returning an unexplained star. The photographer should be able to see which photograph the client chose and what it was chosen for.

In the reviewed build 0.1.2 (65), hosted client galleries, synchronized returned favorites, client delivery and an album designer are not implemented as completed services. The current native application provides catalog organization and manual selection tools. It does not establish an automatic importer for a gallery provider’s favorites report. The client approval page describes the intended workflow and identifies its illustration.

You can improve the process today with an established gallery service, a clearly named decision-maker and an exact selection record. Before inviting the next client, run one rehearsal from their entry link to the studio’s matched originals, including a changed choice and a separate approval. The best selection experience leaves both sides knowing what happens next.

Sources and verification

Official references reviewed 21 October 2026. Prices, service terms, versions and supported systems can change. Application statements use Lightbox Pro development build 0.1.2 (65), source 3f3e29f11e2ae18a2d93cc2337c16e6fc6172550. Native test results are recorded engineering evidence rather than tests rerun on this Windows website workstation.

• Pixieset: creating multiple Favorite Lists
• Pixieset: preset Favorite Lists and maximum selection
• Pixieset: client notes on favorite photographs
• Pixieset: gallery, collection and client-only privacy options
• Pixieset: download limits, eligible contacts and sets
• ShootProof: Linked Contact labeling and hiding, September 2026 update
• ShootProof: Favorites Notification
• ShootProof: gallery access, status, password and email settings
• ShootProof: required account two-factor authentication

Zippi Technologies is the developer of Lightbox Pro, independently of the other companies named. Product references do not imply affiliation or endorsement. Current local features, unfinished development and future ambitions have different acceptance requirements.