From Client Favorites to the Wedding Album

The difficult handoff starts after the favorites arrive

A client’s favorite photographs become an album only after their identities, purposes and approved versions survive several more decisions. A list is not a finished sequence. A layout is not the final print export. The useful connection is the one that lets the studio explain, for every placed photograph, which client choice led to it and which version was approved.

This article focuses on that connection. Our wedding album design guide covers visual rhythm, crop, resolution, bleed and production craft in depth. Here we follow a hypothetical submitted list into an editable album, through revisions and into a release package. The challenge is keeping decisions attached to photographs while specialist applications each do their part.

The worked example uses 75 selected images from a 620-image gallery. Those numbers are invented for teaching. They are not typical wedding averages, a recommended package size or evidence from a real client. The album’s size and capacity still depend on the couple’s brief, the design and the chosen physical product.

Start with a receipt for exactly what the couple submitted

Call the incoming list Harbor_AlbumSelections_v01. Retain its original export or report, submission date, submitter and stated purpose. Count distinct photograph identities, not rows alone. Repeated rows can represent an accidental duplicate, or one photograph requested for two products. Resolve that meaning rather than deleting repeated entries automatically.

Confirm that these 75 are album candidates and not every general favorite collected during browsing. Ask whether the couple expects all of them to appear, whether a few are essential and whether the designer may suggest alternates. An invitation to “choose your favorites” may not have established any of those rules. Clarifying now is less disruptive than redesigning a finished book around an unstated assumption.

Keep any existing print list separate. A photograph chosen for a framed enlargement may also belong in the album, but the crop and retouch request can differ. Capture those uses as related instructions for one source identity. Do not generate multiple untraceable copies merely because the same image has two destinations.

Send a concise receipt once the list is reconciled: the list version, 75 distinct candidates, any mandatory inclusions and the next review stage. If a match remains uncertain, identify that exception instead of claiming the whole packet is accepted. A clear receipt turns a gallery action into a shared production starting point.

Match each gallery photograph to the correct working original

The gallery may show a rendered filename such as Harbor_A_0317_web.jpg, while the catalog references Harbor_A_0317.CR3 and the retoucher supplies Harbor_A_0317_album_v02.tif. Keep an explicit mapping between those roles. Never assume that stripping everything after the first underscore produces a unique source name.

Two cameras can both produce IMG_0317. The same source can also have color and monochrome interpretations. A unique job-and-camera identity, plus a derivative/version field, is more informative than a filename alone. If the existing project lacks that structure, preserve the original names and build a mapping; do not rename an active design’s sources casually to impose a new scheme.

A small synthetic extract from the 75-image handoff

Client choice	Working identity	Production instruction
Harbor_A_0317_web.jpg	Harbor_A_0317, album treatment v02	Required ceremony photograph; keep both hands in the crop.
Harbor_B_0317_web.jpg	Harbor_B_0317, album treatment v01	Different camera photograph; supporting reaction.
Harbor_A_0528_mono.jpg	Harbor_A_0528, approved monochrome	Do not silently substitute the color interpretation.
Harbor_A_0604_web.jpg	Unresolved until inspected	Two candidate working files; stop this placement and compare.

For each ambiguous match, inspect content, dimensions, orientation and available capture context against the proof. A matching basename is evidence, not a sufficient identity test when collisions exist. Open the full working image rather than relying only on cached thumbnails. Keep the exception visible until a person confirms the intended photograph.

For the example, suppose the first search returns 73 exact matches and two ambiguous names. The correct intermediate result is 73 accepted plus two unresolved. It is not a 75-image ready folder. Resolve both, then create an album-candidate collection or list whose membership can be compared with the submitted record.

Prepare a design handoff without losing the version map

The designer usually needs appropriately finished, supported image files, not every camera original and every historical export. Agree the intended representation, dimensions, profile and revision process. Keep the editable retouch master and source photograph elsewhere in the job’s preservation structure, with the mapping available. A simple flattened design input can be correct without becoming the only master.

Use a dedicated, versioned design-input folder and a manifest of its contents. Include the source identity, current filename and relevant restriction or request. If the designer is external, provide only the photographs and instructions needed for the job through the studio’s agreed transfer route. Do not include private client correspondence because it happened to be stored beside an export.

SmartAlbums’ February 2026 troubleshooting note warns that changing imported filenames can lead to incorrect high-resolution images in exported spreads. Its recovery instructions should be consulted for that specific problem. The broader lesson is to qualify replacement and relinking behavior before introducing later image versions into any active design.

Rehearse one revised file before replacing the whole set. Can the designer identify the changed image, refresh the intended source and confirm that the crop still means the same thing? Keep the prior input package while doing so. A visually similar replacement may have different pixel dimensions or orientation and invalidate a previously accepted placement.

Use the 75 choices as a brief, not a fixed grid

Now ask what each photograph contributes. Separate required relationships, important events, atmosphere and optional repetitions. This is a conversation about the couple’s experience of the day, not a ranking contest. A technically modest image of someone important may deserve a careful smaller placement; a striking landscape may need less space if it does not serve this album.

For an illustrative allocation, the 75 candidates might include 9 setting/preparation photographs, 18 ceremony photographs, 16 family and group photographs, 12 portraits, 17 reception photographs and 3 closing images. These counts total 75. They are a starting inventory, not an obligation to devote space proportionately or an industry recommendation.

Mark a few non-negotiable inclusions together. Keep alternate suggestions outside the accepted selection until the couple agrees to add or substitute them. If a missing transition would improve the story, present the particular option and its reason rather than silently expanding the scope. The studio can exercise editorial judgment while maintaining a transparent link to the submitted choices.

Distinguish a count of unique photographs from a count of placements. Repeating one image on a cover and inside the book adds a placement without adding a source identity. Two interpretations of the same frame require their own treatment record. The production list should be able to answer both how many photographs were selected and where each was used.

Make the selection-to-placement relationship visible

Consider one ceremony opening. The client required photograph A_0317 and selected supporting reaction B_0317 and detail A_0324. The exact names matter: the two 0317 endings describe different photographs. Give the opening a stable spread number and keep each placed image connected to its identity and treatment. That makes a later request meaningful even when the layout changes.

1. Spread 06 · left pageDominant placement: A_0317 · treatment v02 · client-required momentCheck: both hands retained; essential subjects away from binding-sensitive positions.
2. Spread 06 · right pageSupporting placement: B_0317 · treatment v01 · reactionDetail placement: A_0324 · treatment v01 · contextual link

Approval of A_0317 as a favorite does not establish approval of a crop that removes a hand. Nor does approval of the left page establish the suitability of the right-page sources at their placed sizes. Use the actual photographs and the selected supplier’s production template for those decisions. The diagram explains accountability; it cannot certify physical clearance or image quality.

If the designer rearranges this opening in v02, retain the spread’s identity or explicitly document any renumbering. A client’s “please change page twelve” becomes ambiguous if the proof, designer and lab each count pages differently. State whether a reference means a facing spread, left/right page or exported file, and include a thumbnail or exact artifact reference where needed.

Proofing software helps only when the review object is clear

The client should review the album as an album: sequence, actual crops, neighboring photographs, cover wording and the relevant physical options. A gallery Favorites page cannot show all of those relationships. Identify the proof version and explain which decisions are requested now, including any limitations of an online representation for color or fine print detail.

In the current SmartAlbums Cloud Proofing documentation, commenters must be added as clients; a guest view does not provide the same comment access. Its notification reference distinguishes draft uploads, submitted feedback and album approval. Confirm which action completed rather than interpreting an unsubmitted comment as the final response.

There is also a dated product transition. SmartAlbums’ October 2026 notice schedules the new SmartAlbums Proofing for 2 November 2026 and Cloud Proofing’s sunset for 2 November 2027. At this article’s review, that new platform is announced rather than the current workflow. Check the notice before starting a project; do not assume old and new proofing features are interchangeable.

Fundy’s Design Proofer walkthrough separates placed comments, sending feedback and Approve for Print, including a final confirmation and initials. These are documented external product controls. The studio still needs to connect the approved design to the exported files it actually sends to production.

Handle a three-image change as a delta, not a new mystery list

Suppose the couple’s first review requests three substitutions, one wider crop and a cover-text correction. Keep the accepted 75-image list v01 and record the new list v02. If three unique images are removed and three different ones added, the candidate count can remain 75 while six membership events require attention. A same-sized list is not an unchanged list.

Record each operation with its exact identifiers and affected location. For example: remove A_0440 from spread 09, add A_0444 with its approved treatment, inspect the replacement crop, and review the neighboring group photograph. A crop change is another kind of event: the source stays the same while the placement changes. Keep those distinctions so the retoucher does not unnecessarily redo an unchanged source.

Fundy’s revision instructions recommend duplicating and clearly naming an album revision before handling proof comments. Use the applicable product procedure and retain the prior state. This makes it possible to explain which version a comment concerned and inspect the exported result against that version.

Do not resolve a comment merely because the editing operation was performed. Inspect the new proof for the intended result and any side effects: a neighboring crop, a substituted image, a reordered spread or a text wrap. Summarize the changes for the client, with outstanding questions kept visible. A new proof starts a new review event; it does not erase the earlier one.

Release the exact approved design, not the latest open window

Keep separate sign-offs where they serve different decisions: image selection, layout and crops, cover wording, and physical product options. Identify who is authorized to approve the order. If both partners contribute comments but one is the designated submitter, make that agreement explicit. Avoid inferring agreement from silence, a viewed email or a heart in the original gallery.

Save the exact approved proof, corresponding editable design and source-package version. Record the scope and time of approval through the studio’s established process. If a visible design change occurs afterward, create another identified version and obtain the appropriate review. A “small improvement” can still alter a crop or wording that the client specifically accepted.

Distinguish approval from the studio’s technical release. The client can approve the sequence while the photographer still must resolve a missing link or a lab warning. A useful release note says that proof v03 was approved and production export r01 was checked against it. Those are two complementary responsibilities, rather than competing sources of permission.

1. 75 candidatesRetain the client’s exact submitted membership and purpose
2. Matched sourcesResolve each identity and the required image treatment
3. Placed designMap approved candidates to spread, crop and source version
4. Revision deltaRecord substitutions, crop changes and proof version
5. Production releaseCompare checked export with the approved design
6. Reprint packageRetain the inputs, links, decisions and lab order record

The lab handoff is another identity check

Export to a new, clearly identified destination using the exact product’s current requirements. Determine whether it expects individual pages, spreads, a particular image format or a prescribed PDF route. Keep cover handling and physical options separate where the supplier requires them. The detailed album production guide explains the craft checks; here the question is whether this output is the design the client approved.

Open the exported files independently. Check order, dimensions, missing or substituted images and the important crops against the approved proof. Inspect the tricky identities, such as A_0317 and B_0317, not only the overall number of files. A cached design preview can look correct while the full-resolution export points to the wrong source.

Review the supplier’s ordering preview and warnings before release. Record any difference between the chosen product template and the current layout. If a correction changes visible content, return to the appropriate approval stage. Do not hide the correction by replacing production files under an already approved name.

Keep the package that explains a future reprint

A reproducible package includes the submitted lists, source-to-derivative mapping, placed-image list, editable design, approved proof, checked production export and order specification. Keep original and working photographs within the studio’s established backup plan. Record dependencies such as application version and fonts, respecting the relevant licenses rather than assuming every asset can be redistributed.

SmartAlbums documents copying filenames of placed images back into a Lightroom search. Use that kind of reconciliation to compare the design’s actual usage with the accepted candidate list. Confirm identities after searching; similar names can produce broader matches than intended. Keep unused candidates identified rather than implying every favorite was printed.

For a parent album or different size, preserve the relationship to the main album while treating the new layout as its own version. Different dimensions can change crop, flow and physical constraints. A reprint request should begin from the retained release package, then check whether the product and software route still exist, rather than reconstructing the book from the current online gallery.

What an integrated selection connection would need to preserve

A useful future Lightbox Pro connection would return more than 75 stars. It would retain which original each client choice references, the list’s purpose and version, any request, and the approved placement or output. Changes should remain explainable after a photograph is retouched, a gallery expires or the album passes through another specialist application.

Reviewed Lightbox Pro build 0.1.2 (65) can organize catalog candidates with sets, ratings and labels and help compare photographs. It does not provide a completed hosted gallery, automatic returned-favorites integration, delivery service or album designer. Use established external tools for those stages today. The long-term product vision is a connection worth designing carefully, not a claim that this entire pipeline already exists.

For the next real album, try one improvement: retain an exact selection snapshot and reconcile the placed images before the first client proof. That makes the handoff testable. The result is a book whose creative decisions and production history remain connected to the photographs that started it.

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.

• SmartAlbums: identifying placed images back in Lightroom
• SmartAlbums: changed filenames and incorrect exported spreads, updated February 2026
• SmartAlbums: adding clients to current Cloud Proofing albums
• SmartAlbums: current Cloud Proofing notification behavior
• SmartAlbums: announced November 2026 proofing transition
• Fundy: versioned album revisions for Design Proofer
• Fundy: comment submission and Approve for Print workflow

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.