Check Photo Coverage Across Different Parent Wedding Albums

A parent album may be a smaller copy of the couple’s album, or it may have a different selection. Confirm which service was agreed before building a separate checklist. Identical copies rarely justify an additional version-management tool.

Give each version its own selection rules

Use columns for photo ID, couple album, parent album A and parent album B. Mark a photo as required, excluded or unrestricted for each version. Keep unrestricted distinct from required: a favorite in one album does not automatically become mandatory in every other album.

Use exact stable filenames or IDs. If files were renamed, record the mapping. Avoid matching on a shortened number alone when two photographers may both have an IMG_0412. An ID that cannot be resolved should remain an exception.

Compare rules with actual usage

For every required ID, check whether the used-photo list contains it. For every excluded ID, check that it is absent. List repeated IDs for review, because intentional repeats exist. A conflict where an ID is both required and excluded needs a person to decide which instruction is current.

Suppose IMG_0412 is required in both parent albums but appears in only one draft. The matrix identifies the missing version without asking the designer to recall every image across both layouts.

Keep the design tool

Fundy describes duplicating albums for parents and revisions. Use its existing capabilities first. AlbumSubset is a planned $19 one-time check of supplied filename manifests. It would not read flattened spread images or guarantee that a manually entered manifest matches the exported design.