A Customer-Selected Grouping Map for Mixed Photo Bundles

A customer sends a bundle of mixed prints to a digitisation service: different sizes, different decades, some loose, some in envelopes. They know how they would like the finished scans organised, but the service sees only a pile. This article proposes a grouping map as an example workflow. It is a proposal, not a report of observed results. The map is not a contact-sheet ordering tool and it does not involve publishing or sharing the images themselves.

The aim is to capture the customer's chosen groups using neutral labels, so the service can keep physical items and scan files organised the way the customer intended.

Inputs

A numbered list of groups, written by the customer. Each group has a short label of the customer's choosing, such as "Group A: loose prints" or "Group B: the envelope marked with a blue band." Labels refer to physical features of the bundle, not to who or what is in the images.
A rough count of items per group, marked as an estimate.
A choice for what to do with an item that does not fit any group: "put in a separate 'unsorted' group" or "hold and ask me."
A choice for what to do with items found inside another item, such as a smaller print tucked behind a larger one: "treat as its own item in the same group" or "hold and ask me."
Optional: one line on whether the original physical order within a group matters to the customer.

The service offers the choices. It should not require the customer to pick a particular option where several are acceptable.

Decision branches at intake

When the bundle arrives, the service compares it with the map.

Do the groups match the physical bundle? If yes, proceed group by group.
Is there a group on the map that cannot be found, or an extra physical group not on the map? Pause and send the customer a short note: "We found something that does not match the map. Please choose how to handle it."
Do estimated counts differ greatly from what arrived? Note the difference and carry on only if the customer has chosen "carry on" on the form. Otherwise hold.
Is an item unclear in belonging? Follow the customer's choice from input 3.

Stop conditions

Stop work on a group when the labels become ambiguous, for example two envelopes both fit "the envelope marked with a blue band," or when the customer's chosen action is "hold and ask me." Do not guess a grouping to keep the job moving. Stopping affects only that group; other groups may continue.

Privacy by design

The map should use physical descriptions, not names of people or places depicted. Staff handling intake need to see only the labels and counts. If a customer wishes to add personal descriptions, that is their choice, but the form should not request them, and the service should not copy them into file names unless asked.

Example (proposed, illustrative)

A customer lists three groups: Group A, loose prints, about forty; Group B, the envelope with a blue band, about twenty; Group C, a small box of smaller prints, unknown count. For stray items they choose "separate unsorted group." For items tucked behind others they choose "hold and ask." On intake, staff find a fourth, unlabeled envelope. They pause only that envelope, message the customer with a photo of the outside, and continue with groups A to C.

What the map is not

It does not set the order in which scans appear within a group, it does not describe the content of images, and it does not authorise sharing or publishing them. Those decisions need their own agreement.

Practical acceptance test

Prepare a mock bundle of ordinary sample items, such as blank cards or stock images, grouped in three envelopes and a loose pile. Give a colleague only the filled-in map.

They sort the bundle by the map alone.
Add one deliberate mismatch: an extra envelope.
See whether they pause the right item and follow the customer's chosen action.

Pass if all groups end up matching the map, the extra envelope is held rather than silently merged, and the counts noted are within the estimate or flagged. Fail if the mismatch gets merged into a group. Adjust the wording of the form and repeat with a different mock bundle.

Conclusion

A grouping map lets the customer decide the structure, while the service keeps to neutral, physical labels. It makes ambiguity visible early and sets clear behaviour for items that do not fit. Which choices to offer, and how detailed the labels should be, is for each service to tune. What is worth keeping is the pause rule: when the map and the bundle disagree, ask rather than guess.