A family may approve a photograph on Tuesday, ask for a different crop on Wednesday and later discover that somebody still has Monday's file in an email attachment. When several tiles are involved, informal names such as final-new.jpg and final-2.jpg stop communicating which design was actually approved. A version system gives every image a stable identifier, preserves earlier decisions and makes one exact working export the authoritative candidate for production review.
This does not assume any particular Wallpics uploader or order-confirmation workflow. The family can maintain its own control record regardless of how it eventually places an order. The method should track source, edits, review status and permission separately. It should also allow corrections without silently replacing a file that someone already approved. The purpose is practical clarity rather than complicated project management: each tile needs one unmistakable image identity and an explicit current version.
Assign an identifier to the image, not just its filename
Choose a short code that remains attached to one photographic source across revisions. A birthday collection might use BDAY-023 for a particular scene even if several crops are tested. The code should not be reused for a different photograph. Keep the original filename, capture source and contributor in a private index, since names generated by phones can repeat across devices. A consistent image identifier enables the family to refer to a picture precisely without relying on a visual thumbnail.
Add a revision number and meaningful label to the export filename, such as BDAY-023_v04_facecrop. This communicates more than a generic final label, yet still leaves room for additional edits. Preserve the camera original unchanged and assign a separate working master where an editor can retain nondestructive changes. The naming system is useful only if everyone follows it; a highly elaborate code that nobody can interpret will create another form of confusion.
Separate source files, working edits and review exports
A camera original and an image prepared for a tile have different purposes. The original preserves available source detail and capture history. The working edit may contain color adjustments and an editable crop. The review export is the image a family member actually sees and comments on. Place them in distinct locations or use unambiguous labels. An approved JPEG may be valid for presentation while the original HEIC or RAW file remains the source for future changes.
Do not allow someone to change the contents of a supposedly approved file without changing its version. Otherwise a label such as v03 could refer to two different pictures depending on when it was downloaded. A new change, even a seemingly minor caption correction, should produce a new candidate and a fresh approval note. Retain superseded versions for traceability but keep them out of the current handoff area.
Describe the precise change from one revision to the next
A useful revision note explains what changed and why. Instead of writing improved photo, record that the crop moved to include a child's hand or that a distracting reflection was reduced. Distinguish visual preference from factual correction, such as fixing a date verified against the family archive. These notes help a reviewer assess the specific difference without reexamining every pixel. They also reveal when a change requested by one person was not implemented in the next exported file.
Compare the new version with the previous approved candidate, not just with the untouched original. An editor may accidentally start from an older working copy and lose a correction that had already been accepted. A side-by-side contact sheet can show identifiers, crops and revisions together. Check that any new lighting or color treatment leaves people recognizable and does not introduce invented details or privacy problems.
Record approval at the level of each intended tile
Use a simple table listing image code, exact revision, reviewer, approval date and any outstanding issues. A phrase such as the pictures are fine can hide disagreements about one child's photograph or an unverified professional image. Ask people to confirm the numbered file they actually reviewed. Where consent or copyright questions remain, record a separate hold; a design approval is not permission to reproduce someone else's photograph.
A five-tile family set can be controlled with a small ledger: tile 01 uses the agreed picnic portrait, tile 02 the birthday scene, and each points to one exact filename and version. If a relative requests a different crop for tile 03, create revision two for that item rather than renaming the entire folder 'final-final'. A review screenshot should identify the current revision so no one mistakenly approves a thumbnail that is no longer the file to be printed.
Define who has authority to sign off on each image when contributors are numerous. A family may welcome general suggestions while reserving the final decision for the photo owner or gift giver. Make the process clear before discussions become repetitive. If feedback arrives after approval, log a new revision and mark the earlier decision as superseded. Avoid calling the set ready merely because a deadline is approaching.
Reconcile the actual files before handoff
Compare the final approval list against the files in the current handoff folder. Every intended image should have one corresponding export, and every export should have a valid identifier and revision. Check for duplicated pictures, missing relatives, old crops and wrong orientations. Inspect text and captions separately because a file can have the correct photograph but an earlier spelling correction. Keep the original source association visible so an unexpected difference can be investigated.
Actual seller formats and upload behavior should be verified using current business instructions. A successful upload does not necessarily prove that the photographer's permissions are cleared or the family approved the displayed crop. If a proof is supplied by a printer, label it with the same image identifier and store it as a separate review artifact. This connects the customer's creative decision to the specific downstream file without making unsupported promises about production.
Archive a clean snapshot for future display changes
Keep a copy of the final working exports, the version table and any recorded permissions in a stable archive. If the family expands the display later, it can identify the original photographs and avoid recreating editing decisions from memory. Back up the unmodified sources as well as the final derivatives. A clear record becomes especially useful when the person who made the original crops is no longer available to explain them.
The most reliable photo-tile project is not the one with the most elaborate naming convention. It is the one in which an ordinary family member can answer exactly which image, crop and revision were chosen and why. Stable identifiers, concise change notes and explicit signoffs prevent old proofs from silently becoming the final product. Creative flexibility remains, but the file intended for production review is never ambiguous.