FILE OPERATIONS · 7 MIN READ
A Dropbox workflow for real estate photo editing
Dropbox can be a practical file layer for a property-media team. It works best when the folder structure answers where files belong while a separate job record answers who acts next and whether the work is approved.
QUICK ANSWER
Create one folder per property job with stable subfolders for source files, editor input, review, approved finals and archive. Give the job a unique identifier, keep instructions in the job record or a clearly named brief, restrict write access by role, and move or copy files only at defined handoffs. Track ownership and approval outside the folder tree so a filename is never mistaken for a production decision.
Create one durable job root
Name the root with a stable job identifier and a human-readable property label. Do not rely on the address alone: spelling and unit formats change, and two jobs can revisit the same property.
Inside it, separate raw capture from working files and client-ready exports. Keep rejected or superseded versions away from the approved package.
| Folder | What belongs there | Handoff rule |
|---|---|---|
| 01_SOURCE | Original uploads grouped by service | Photographer or intake owner confirms completeness |
| 02_EDITOR_INPUT | Selected sources and current brief | Coordinator records editor assignment |
| 03_REVIEW | Proposed edited versions | Reviewer approves or requests a specific change |
| 04_APPROVED | Only accepted delivery files | Delivery owner checks the client view |
Make permissions and responsibility explicit
Give each role only the access needed for its part of the workflow, following the studio’s own data-handling policy. The photographer needs a reliable upload destination; an external editor does not necessarily need access to every client or archive.
Assign responsibility on the job, not by guessing who last touched the folder. A sync icon or modified date cannot prove that a reviewer approved the work.
Use a controlled editor handoff
Before sharing editor input, verify the property identity, expected services, source completeness, output specification and current instruction version. Send a direct folder reference tied to the job rather than asking the editor to search a shared drive.
When edits return, place them in the review area. Keep revision notes attached to the relevant version and move only approved output into the approved folder.
- Use consistent filenames within each service set.
- Keep one current brief and retire superseded instructions.
- Record missing sources before editing begins.
- Test the intended access path with a non-owner view.
Separate file retention from daily production
After delivery, apply the studio’s documented retention and archive policy. Do not leave every active collaborator on archived jobs, and do not delete originals merely because a client package exists.
Planned PhotoTrackly workflows can coordinate job state around an existing file system; they should not be described as replacing Dropbox or providing storage features unless those capabilities are available.