DELIVERY · 6 MIN READ
How to handle client revisions after property-media delivery
Once a client has received media, overwriting files without a revision record makes it hard to know what changed, what remains valid and which version the client can access.
QUICK ANSWER
Treat a post-delivery request as a new revision event on the original property job. Preserve what was delivered, record the exact requested change and affected files, clarify whether it is a correction or new scope, assign an owner and due time, then run review again. Replace or supplement the client package only with a clearly approved version.
Capture the request before changing files
Record the client, property, request time, affected deliverable or file, desired result and any deadline. Ask a precise question when the request is ambiguous. Keep the delivered version and event visible so the team can compare the proposed change with what the client received.
Do not let a message thread become the only source of the request.
- Exact file, clip, floor plan or package affected.
- Requested outcome in the client’s words.
- Correction, preference change or additional scope decision.
- Owner, due time and next client update.
Separate correction from new scope
A mismatch with the agreed brief may be handled differently from a newly requested output or creative change. Use the business’s current service policy and name the person authorized to decide. The production team should not infer commercial terms or silently expand the order.
Once scope is clear, attach the revision to the same job and current instruction.
| Request type | Decision needed | Next owner |
|---|---|---|
| Incorrect or incomplete output | Confirm the agreed acceptance condition | Production or QC lead |
| Preference change | Confirm whether the brief changes | Account owner |
| New deliverable | Confirm scope and commitment | Authorized commercial owner |
| Unclear factual change | Verify source and authority | Coordinator |
Use an illustrative revision cycle
A fictional client asks for one photo to be replaced and a floor-plan label to change. The coordinator records two affected items, confirms the label with the client contact and preserves the original delivery. The photo editor and floor-plan owner submit a new version; QC approves both before the delivery owner updates the package and tells the client exactly what changed.
This is a process example, not a promise about revision entitlement or timing.
Close the new delivery event
Reopen the client-facing package as the client would, verify the corrected version and remove superseded access where appropriate to your process. Record the new delivery time and recipient. If the request reveals a recurring intake or QC issue, improve that rule after the immediate recovery.
- Never approve from the message alone.
- Recheck the complete affected deliverable.
- Tell the client whether the link changed.
- Keep the original and revised delivery events distinguishable.