QUALITY CONTROL · 6 MIN READ
How to prevent the wrong property images reaching a client
A polished image can still be the wrong image. Property identity must survive every handoff from capture through editing, review and the final client link.
QUICK ANSWER
Prevent wrong-property delivery by giving every job a stable identifier, verifying that identifier at upload and editor handoff, reviewing files inside the correct job context, separating approved output from working versions, and opening the final package as the client before sending it. The delivery owner should confirm property, recipient, ordered services and approved versions together.
Carry one job identity through the workflow
Assign a stable job identifier when the order is created and include it in upload destinations, handoff records and working folders. Keep the human-readable address or property label too, but do not depend on spelling alone.
At intake, compare the uploader, appointment and ordered services with the job. Stop mismatches before files enter an editor queue.
| Checkpoint | Identity check | Stop condition |
|---|---|---|
| Upload | Job ID, property label, photographer | Destination or source set disagrees |
| Editor handoff | Job ID, ordered services, file manifest | Inputs cannot be reconciled |
| Review | Job record and proposed output | Unexpected scene, count or service |
| Delivery | Property, recipient, approved package | Any field is ambiguous |
Keep proposed and approved output separate
An editor submission belongs in review, not in the final client area. The reviewer should approve an identifiable version and move or release only that accepted set. Superseded exports should remain traceable but unavailable from the delivery link.
If files from several properties are reviewed in one session, complete one job-level check before opening the next. That small boundary reduces cross-job copying and selection errors.
Run a client-view delivery check
Open the exact package or link the recipient will receive. Confirm the displayed property, client, media types, file count or expected set, access settings and approved version. Check representative files at full view instead of trusting thumbnails alone.
For a partial delivery, label what is included and what remains outstanding. Do not make an incomplete package look like the final order.
- Right property and intended recipient.
- Every included item is approved.
- No unrelated or superseded files.
- Link access works from the intended view.
Recover without hiding the incident
If an incorrect item is sent, restrict or replace the package when the delivery method permits, contact the affected client through the studio’s approved process and record exactly what was exposed and corrected. Follow applicable privacy and contractual procedures rather than improvising.
Then trace the failed control: identity at intake, folder separation, approval state or final-package check. Change that control and assign an owner for verifying the correction.