1. Set the operating rules before the folders
A folder tree is useful only when the team agrees what each location means. Write the rules beside the template, assign an owner, and test the structure with one active listing before moving an entire archive.
- One listing has one stable internal key and one authoritative root folder.
- Original deliveries remain unchanged; edits and derivatives are new files.
- A working folder can contain drafts. A publish package contains only approved, destination-ready assets.
- “Latest” is recorded in the manifest, not inferred from a vague filename or modified date.
- Access to a file does not prove permission to publish, edit, transfer, or reuse it.
- Every live destination and temporary share link has an owner and maintenance trigger.
- Private client and transaction records stay outside broadly shared marketing packages.
- Archive and deletion rules follow current brokerage policy, agreements, law, and system requirements.
The objective is not the most elaborate taxonomy. It is a small system that prevents the wrong listing, old price, draft caption, unapproved edit, branded file, or expired link from becoming the public version.
2. Copy this eight-folder listing structure
Number the top-level folders so they stay in workflow order across common storage tools. Use a reusable template, then duplicate it when the listing becomes active enough to need a marketing workspace.
[listing-key]_[short-property-label]/
↳ 00_read-me-and-manifest/ — owner, status, source index, current approvals, and live links
↳ 01_intake-rights-and-brief/ — approved facts, scope, access, agreements, licenses, and decision log
↳ 02_source-media/ — untouched photo, video, audio, floor plan, logo, and document deliveries
↳ 03_working-files/ — selections, scripts, edits, graphics, project files, and review exports
↳ 04_approved-masters/ — approved clean masters and controlled source-of-truth derivatives
↳ 05_publish-packages/ — exact MLS, property-page, social, email, print, and presentation packages
↳ 06_live-links-and-reporting/ — destination URLs, publish log, corrections, measurements, and seller reports
↳ 07_archive-and-closeout/ — final manifest, retention decision, permissions, takedown record, and allowed reuse
Keep transaction contracts, financial documents, identity records, access codes, lockbox information, private correspondence, and other sensitive material in the brokerage's approved transaction system—not in a marketing folder shared with photographers, editors, sellers, or vendors.
3. Use filenames that answer six questions
A useful filename identifies the listing, asset, version, identity treatment, approval state, and revision without requiring the file to be opened. Use plain characters that survive downloads and transfers. Keep the pattern consistent and the controlled values short.
Pattern: [listing-key]_[asset]_[destination-or-frame]_[identity]_[state]_[revision].[ext]
Photo example: 1847-oak_photo-gallery_mls_clean_approved_r02.jpg
Video example: 1847-oak_video_9x16-social_branded_approved_r03.mp4
Review example: 1847-oak_video_16x9-propertypage_branded_review_r02.mp4
Caption example: 1847-oak_captions_16x9-propertypage_clean_approved_r01.vtt
Thumbnail example: 1847-oak_thumbnail_youtube_branded_approved_r02.jpg
| Field | What it tells the team | Useful values |
|---|---|---|
| Listing key | Which property record controls the file | Stable internal ID or short non-sensitive property label |
| Asset | What the file contains | photo, video, floorplan, flyer, captions, thumbnail, script |
| Destination or frame | Where or how it was prepared to run | mls, propertypage, youtube, email, print, 16x9, 9x16 |
| Identity | Whether agent or brokerage identity appears | branded, clean, team, co-list, as defined in the brief |
| State | Whether use is permitted at this stage | working, review, approved, retired |
| Revision | Which controlled iteration this is | r01, r02, r03; never final-final or new-new |
Do not encode every fact in the filename. The manifest carries the approval date, source, rights, owner, publish window, and lifecycle state. Also avoid client names, phone numbers, access details, or private notes that may be exposed when a file or link is shared.
4. Separate source, working, approved, and live states
File type and approval state are different. An MP4 can be raw source, a rough edit, an approved master, a destination export, or a downloaded copy of a live post. The folder and manifest should make that state explicit.
| State | Rule | Who usually needs access | Never assume |
|---|---|---|---|
| Source | Preserve the original delivery; record creator, date, and source | Asset owner, assigned producer, and recovery administrator | Possession equals broad editing or publishing rights |
| Working | Allow iteration, but keep every review file visibly non-final | Assigned creators, coordinator, and named reviewers | A draft link is safe to publish or forward |
| Approved | Move or copy only the exact approved version; lock its identity in the manifest | Publisher and campaign owner; read access for relevant reviewers | Approval of one crop, brand treatment, or caption approves every derivative |
| Live | Record the destination, version, date, owner, and change trigger | Campaign owner, responder, measurement owner, and updater | A live destination still matches the stored file or current listing |
Preserve the link between source and derivative. The video quality-control checklist shows how to compare the exact render with approved property evidence, facts, identity, rights, accessibility, and destination requirements.
5. Keep a listing asset manifest
The manifest is the small index that makes the folder usable. It can be a spreadsheet, database view, or controlled document, but the team should not need to scan every folder to identify the current photo gallery, clean video, vertical cut, captions, flyer, or live URL.
Listing key and approved property label: [ID / public address format]
Campaign owner and backup owner: [name / role / contact route]
Current listing state: [prelaunch / active / event / price change / pending / sold / withdrawn / other]
Asset ID: [stable row identifier]
Asset type and purpose: [photo / video / floor plan / graphic / copy / document]
Source: [creator / delivery date / source folder / original filename]
Rights record: [agreement / permitted uses / edits / term / attribution / restrictions]
Current approved file: [exact filename / revision / approval date / approver]
Destination package: [exact folder / requirements / identity treatment]
Live destination: [URL / publish date / publisher / current status]
Update or retirement trigger: [date / listing change / agreement / correction]
Archive and reuse decision: [location / access / allowed future use / review owner]
Add one row per meaningful asset or controlled package, not necessarily every raw camera file. For a large source delivery, the row can identify the collection, creator, rights, checksum or item count, and storage location while the approved selects receive individual entries.
6. Attach rights and authority to the asset
Receiving a download and paying an invoice do not, by themselves, describe every permitted use. Store the controlling agreement or license, creator, allowed destinations, editing and derivative authority, transfer or sublicense terms, attribution, time period, geography, restrictions, and post-listing reuse decision where the team can find them before publishing.
TheU.S. Copyright Office's photography circular explains that the person who takes a photograph is generally its author and initial copyright owner. Agreements and work-made-for-hire rules can affect ownership and permissions, so use the actual contract and obtain qualified legal guidance when the answer matters. The photography usage-rights checklist provides a fuller operating record for MLS, social, video, ads, print, and reuse.
- Track seller or property authority separately from copyright and creator permission.
- Record whether photos may be cropped, retouched, animated, virtually staged, combined, or used in video.
- Keep music, stock, font, voice, logo, map, floor-plan, and testimonial permissions with the relevant project.
- Do not move an asset into an approved master or publish package while a required permission remains unclear.
- When another agent's listing or media is involved, record the exact authority, attribution, approval, status, and takedown owner.
7. Build destination-specific publish packages
A master is not automatically the file to upload everywhere. Build a small package for each approved destination so the publisher does not have to choose among drafts, improvise a crop, rewrite the identity treatment, or search for the matching captions and copy.
| Package | Possible contents | Final check |
|---|---|---|
| MLS or syndication | Verified clean media file or supported link, approved gallery order, and requirement record | Current local rules, identity treatment, field, host, permissions, and live display |
| Property page | Branded master, poster image, captions, transcript, approved copy, and current action | Playback, mobile crop, accessibility, facts, links, analytics, and ownership |
| Vertical social | Deliberate 9:16 edit, cover, caption, on-screen text, identity, link route, and expiration | Safe areas, sound-off understanding, current state, destination, and response owner |
| Thumbnail or preview image, accessible text, approved subject and body, and durable landing link | Recipient context, permissions, link behavior, current facts, and reply route | |
| Print or presentation | Print-ready PDF or slide asset, image credits when required, QR destination, and version note | Bleed or display specs, readable text, live QR target, quantity, and disposal of stale copies |
Use the video deliverables checklist to define masters, vertical edits, clean and branded versions, captions, thumbnails, review rounds, raw-media expectations, and closeout before production begins.
8. Share narrowly and preserve approvals
Give each collaborator the least access needed for the assigned job. A photographer may need an upload route; an editor may need source media and a brief; a seller may need a specific review link; a publisher may need approved packages. None automatically needs the complete listing workspace.
- Share a specific folder or review item instead of the listing root when practical.
- Use read-only access for approved masters and source deliveries that should not change.
- Keep external upload locations separate from internal working and approved folders.
- Record approvals against the exact filename, revision, and accompanying copy.
- Set owners for temporary links, guest access, former team members, and vendor offboarding.
- Review access at launch, material listing changes, campaign closeout, and team changes.
Do not rely on an email such as “looks good” without preserving what was reviewed. Store the approval date, approver, exact file, copy or destination package, requested corrections, and final decision in the manifest or decision log.
9. Plan backup and recovery
Synchronization improves access but can also repeat deletions or unwanted changes. Decide which source files, approved masters, agreements, manifests, project files, and publish records are critical; then maintain a protected recovery path and test that the team can restore a real listing package.
CISA's ransomware guidance recommends offline, encrypted backups of critical data and regular tests of backup availability and integrity. Apply the brokerage's approved security, privacy, retention, and incident-response requirements to the actual storage system rather than improvising a personal archive.
Critical package: [listing / assets / agreements / manifest]
Primary location and owner: [system / account / role]
Recovery copy: [separate protected location / coverage / encryption]
Recovery permissions: [primary and backup administrator]
Last successful restore test: [date / sample / result / elapsed decision points]
Gaps found: [missing file / stale manifest / access / corruption / undocumented dependency]
Correction owner and date: [person / action / completion]
10. Close, archive, and reuse deliberately
A sold, withdrawn, expired, or otherwise closed listing still has live URLs, downloaded copies, share links, permissions, performance records, and possible portfolio value. Close the marketing campaign as deliberately as it was launched.
- Confirm the final state: record the listing change, effective time, source, and owner.
- Review live destinations: update, redirect, label, unpublish, or retire each placement as the current rules and campaign require.
- Capture the record: keep final URLs, approved versions, meaningful measurements, corrections, and seller-reporting outputs.
- Resolve access: remove unneeded guests, expire temporary links, and preserve the owners required for retention or recovery.
- Decide reuse: document whether each asset may appear in an agent portfolio, presentation, case explanation, future social post, or derivative.
- Archive intentionally: move the controlled package, manifest, rights, approval, and closeout record to the approved archive.
- Test retrieval: another authorized person should be able to find the final gallery, video, rights record, and live-history row without asking the original creator.
The 2026 NAR Code of Ethics requires REALTORS® to present a true picture and to use reasonable efforts to keep website information current. The exact retention, advertising, MLS, agreement, and brokerage obligations for a listing may differ; this folder template is an operating aid, not a universal records policy.
Copyable listing-media setup card
Listing key and root: [ID / approved storage path]
Campaign owner and backup: [people / roles]
Approved property record: [location / source date / approver]
Source deliveries: [creator / date / collection / original count]
Rights and authority: [agreements / permitted uses / restrictions]
Working owners: [photo / video / design / copy / review]
Approved masters: [asset IDs / exact current filenames]
Publish packages: [destinations / identity / specifications]
Live records: [URL / version / date / publisher / maintenance trigger]
Access review: [internal / external / temporary / last checked]
Recovery path and last test: [location / owner / date / result]
Closeout: [final state / takedown / archive / retention / reuse]
Frequently asked questions
How should a real estate agent organize listing photos and videos?
Create one listing root identified by a stable internal key, then separate intake and rights, untouched source media, working files, approved masters, destination packages, live links, reporting, and archive records. Keep drafts out of publish-ready folders and use a manifest to record the current approved version.
What should a real estate marketing file name include?
Use a consistent listing key, asset type, destination or frame, identity treatment when relevant, approval state, and revision. A name such as 1847-oak_video_9x16_branded_approved_r03.mp4 is more useful than final-video-new.mp4. Keep private client information out of filenames and shared links.
Should raw listing photos be stored with edited images?
Keep original source files read-only and separate from edited, selected, or destination-ready versions. That preserves the source record, makes changes traceable, and reduces the chance that a draft or derivative replaces the original delivery.
What should happen to listing marketing files after a property sells?
Close the campaign deliberately: capture the final live links and performance record, remove or update time-sensitive publishing, preserve required records, document any allowed post-sale reuse, revoke unnecessary access, and move the controlled package to an archive governed by brokerage policy, agreements, and applicable requirements.
Is cloud storage alone a backup for listing media?
A synchronized cloud folder can repeat deletion, corruption, or unwanted changes. Define a separate recovery copy for critical assets, protect access, and test that the team can restore the files and records it actually needs. Follow the brokerage's security and retention policies.