EDITING · 6 MIN READ
How to keep property photo editing consistent across multiple editors
Consistency is not achieved by telling every editor to copy a vague “house style.” The team needs references, decision boundaries and feedback that survive beyond one job.
QUICK ANSWER
Define a small set of visible editing standards, pair each rule with approved reference images, keep property-specific exceptions on the job, and route every submission through a consistent human review. Record recurring feedback in the shared standard instead of correcting each editor through separate private messages.
Define standards that can be observed
Describe the decisions a reviewer can actually compare: overall color direction, exposure balance, vertical treatment, window handling, output dimensions and the boundary for object changes. Use approved examples to show the intended result and a short note to explain why it passed.
Keep the core standard separate from requests that apply only to one property or client.
Use the same handoff and review states
Give every editor the property job, sources, output list, reference version, special instructions and due time. After submission, a named reviewer approves or requests a file-specific correction. Do not let one editor treat upload as completion while another waits for explicit approval.
| Layer | Where it belongs | When it changes |
|---|---|---|
| Studio standard | Versioned style guide | When a repeated decision is approved |
| Client preference | Client or account instructions | When the client confirms a change |
| Property exception | Current job brief | Only for the affected job |
| QC feedback | Submitted version and review record | At each review decision |
Calibrate with an illustrative sample set
A fictional production lead gives two editors the same small practice set, then compares the submitted results against approved references. Differences become precise instructions: which image, which decision and what should change. The lead updates the standard only when the feedback should apply to future jobs.
This calibration is an operating example, not a claim that one visual style suits every market or client.
Measure recurring rework, not personal taste
Track which rules repeatedly cause corrections and whether the source brief was complete. A high number of window corrections may reveal an unclear reference; inconsistent delivery sizes may reveal a missing output rule. Improve the shared instruction before concluding that every variation is an editor problem.
- Review against the current reference version.
- Cite affected files in correction requests.
- Retire contradictory examples.
- Give editors a clear escalation path for ambiguous changes.