1. Start with campaign jobs, not file counts
Ask what the viewer should understand and do, where the video will appear, and who owns the response. A property-page overview, MLS-compatible tour, vertical social teaser, open house reminder, email thumbnail, and agent portfolio piece are different deliverables even when they share footage or listing photos.
| Campaign job | Viewer question | Likely version decision | Do not assume |
|---|---|---|---|
| Property overview | What is the property story and route? | Clean horizontal master or hosted property cut | Every room or every available image belongs |
| MLS or syndication path | What media does the current local workflow accept? | Verified unbranded file, player, page, or link | One national rule or upload method applies |
| Short-form social | Which property evidence earns the next action? | Vertical edit with new framing, timing, text, and CTA | A center crop is a completed story |
| Event or status update | What changed and what is current now? | Dated derivative built from a clean master | Temporary facts should be burned into every file |
| Email or direct share | Why should this recipient open the property destination? | Thumbnail, hosted video, text fallback, and tested link | The video should be attached to every message |
Use the real estate media package checklist when the choice is broader than video. Photos, floor plans, aerials, interactive tours, video, and property pages answer different buyer questions; ordering every medium is not the same as designing a coherent package.
2. Write one delivery-manifest line per file
Put the manifest in the brief and quote before capture or editing. “Three videos” is not enough; neither side can tell whether the third file is a crop, a new story, a clean master, an audio-free export, or a separate event asset.
Project / property: [approved identifier / source-record version]
Deliverable ID: [D01 / D02 / D03]
Campaign job: [property overview / MLS / social / event / email / other]
Destination and account: [exact publishing workflow / owner]
Story: [opening evidence / route / ending / CTA]
Technical brief: [orientation / aspect ratio / resolution / runtime range / file type / file-size limit if verified]
Identity: [clean / branded / unbranded / required labels / title and end cards]
Audio and language: [music / narration / natural sound / mix / captions / transcript / localization]
Source inputs: [approved photos / footage / logo / facts / script / music / license record]
Review: [rough cut / consolidated feedback / correction check / final approver]
Delivery: [deadline / filename / folder / link / expiry / download owner]
Rights and lifecycle: [permitted uses / transfer / archive / change trigger / retirement owner]
Verify technical requirements at the actual destination near production time. Save the source URL or documented platform, MLS, brokerage, or provider requirement with the manifest rather than turning a remembered specification into a permanent “industry standard.”
3. Separate master, branded, unbranded, and clean versions
These labels describe different layers and should not be used interchangeably. A file may be visually unbranded while its player, page, URL, thumbnail, title, description, or surrounding destination still contains agent identity. Confirm the complete publishing path.
| Version | Purpose | Define explicitly |
|---|---|---|
| Clean property master | Reusable approved property story without temporary campaign text | Music, narration, captions, address, labels, end card, date-sensitive facts |
| Branded publishing version | Agent or brokerage channel where identity is permitted and useful | Logo, name, brokerage, contact, license or other required identity, CTA |
| Unbranded version | Specific verified workflow that restricts promotional identity | File, audio, text, player, host, page, URL, thumbnail, description, redirects |
| Event or status derivative | Open house, coming soon, price update, or other time-bound job | Full date, current fact source, destination, expiration, replacement plan |
| Review copy | Time-coded feedback before final export | Watermark, review link, access, expiry, download setting, version number |
The branded versus unbranded guide provides a field-by-field version record and shows why the media file cannot be reviewed separately from its host and destination.
4. Treat horizontal and vertical as deliberate edits
Orientation changes composition. A wide room view may lose the doorway that explains flow; a two-person agent segment may no longer fit; lower-third text may cover the feature; and a slow horizontal opening may not work in a shorter vertical sequence. Decide whether the source will support both edits before capture or photo selection.
| Decision | Horizontal version | Vertical version |
|---|---|---|
| Opening | Can establish exterior, room width, or a wider route | Needs a focal subject that survives the narrow frame |
| Shot or photo selection | May preserve context across the full width | May need alternate source frames or a different sequence |
| Text | Placed for the verified host and player | Repositioned and shortened for the actual mobile placement |
| Pacing | Built for the property-viewing job and destination | Rebuilt around fewer pieces of evidence and one action |
| Approval | Reviewed as the exact horizontal export | Reviewed independently—not inferred from the master |
Use the video sizes and formats guide to verify the destination, aspect ratio, resolution, file constraints, upload path, and live presentation. The brief should describe the target; the final QA should test the actual file.
5. Specify captions, audio, thumbnails, and publishing assets
The video file is only part of the delivery. If the agent is expected to publish it, name the supporting assets and who creates, approves, uploads, and updates them. Otherwise the final handoff can leave the most visible property facts to an improvised title or post.
- Synchronized caption file, open-caption version, reviewed transcript, and language for each approved version
- Music track identity, license or provider record, permitted destinations, and audio-free export if required
- Narration script, voice file, name pronunciation, property-fact source, mix, and correction owner
- Thumbnail or cover source, crop variants, visible text, branding state, alt text, and lifecycle owner
- Video title, description, property URL, CTA, required identity or disclosures, and current contact route
- Hosted playback or download link, access setting, expiry, password if appropriate, and test owner
- Source manifest, rights record, approval log, final filenames, and published URL register
Use the real estate video captions workflow to distinguish synchronized captions, open captions, on-screen property graphics, the transcript, and social post copy. They share source facts but are different deliverables with different error and maintenance paths.
6. Define feedback, corrections, revisions, and new work
Put the review units, deadlines, included rounds, decision maker, and out-of-scope work in the agreement. “Two revisions” is ambiguous until the team defines whether feedback is consolidated, which cut it applies to, and how a correction differs from a new creative ask.
| Request type | Example | Pre-agreed decision |
|---|---|---|
| Objective correction | Approved address, price, name, caption, or export requirement was implemented incorrectly | Evidence source, correction path, timing, affected versions |
| Creative revision | Change music, pacing, shot choice, narration, graphics, or sequence within the agreed deliverable | Included rounds, consolidated feedback, deadline, final decision maker |
| New deliverable | Add a vertical cut, drone-only edit, no-agent version, new runtime, or status campaign | New scope, quote, schedule, source and rights review, approval |
| New source work | Reshoot a room, record new narration, replace photography, or obtain new aerials | Access, provider, weather, cost, rights, seller approval, schedule |
| Post-approval change | Update after final sign-off or after a version is published | Change order, downstream corrections, new final manifest |
Project / deliverable / version: [property / D-ID / filename or review link / version number]
Timecode: [start–end]
Observed issue: [what the reviewer sees or hears]
Approved source or requirement: [record / link / brief line]
Requested outcome: [specific correction or creative decision]
Request class: [correction / included revision / proposed new deliverable / new source work]
Affected versions: [master / branded / unbranded / vertical / captions / thumbnail / published URLs]
Consolidated by: [single authorized feedback owner / date]
The editing service comparison helps agents evaluate intake, rough cuts, source handoff, revision process, rights, delivery, and lifecycle work before choosing a provider.
7. Review every exact final version
Watch, read, and test each final file from beginning to end. Do not approve a vertical edit by watching the horizontal master, approve open captions by reading a transcript, or approve an unbranded file without testing the complete destination.
- Filename and manifest line match the property, deliverable ID, version, orientation, identity state, and date
- The opening, route, transitions, and ending communicate the intended property story without inventing space or condition
- Address, price, status, measurements, features, names, contact information, and dates match the approved current record
- Every generated frame, virtual edit, crop, graphic, map, floor plan, and label is accurate and appropriately disclosed
- Narration, music, natural sound, silence, fades, captions, pronunciation, and text timing work in the final export
- Branding and required identity are present where approved and absent throughout the complete unbranded path where required
- The file plays on representative mobile and desktop paths without broken links, unexpected crops, unreadable text, or blocked access
- CTA, property destination, form, phone, email, reply, and response owner are current and tested
- Usage rights, people, property authority, music, source assets, and destination permissions cover this exact version
- The final approver records approval, exceptions, filename, date, and the versions or URLs that may publish
If the production uses listing photographs, compare the final video with the approved source set. The real estate video from photos guide includes selection, sequencing, motion, narration, and frame-level property review.
8. Control delivery, rights, storage, and access
A delivery link is not a durable rights record or archive plan. Confirm what the agent may publish, edit, transfer, retain, and reuse; what the provider retains; whether raw media or project files are included; and how long review and download links remain available.
Final manifest: [one line per delivered filename / checksum or size if used / approval status]
Supporting assets: [captions / transcript / thumbnail / copy / rights and source records]
Delivery location: [folder or service / access owner / link expiry / download confirmed]
Permitted publishing: [users / organizations / accounts / destinations / paid or organic / term]
Excluded materials: [raw footage / project files / fonts / templates / music file / stock / other]
Provider retention: [source / projects / finals / duration / deletion or recovery terms]
Agent archive: [controlled folder / owner / backup / access / record retention]
Published URLs: [destination / version / publisher / date / maintenance owner]
Closeout triggers: [status / price / event / correction / representation / rights / expiration]
Do not assume that payment transfers copyright, editable projects, raw files, music, or unrestricted reuse. Read the controlling agreement and use the listing-media rights register to map creator ownership, licenses, adaptations, destinations, transfer, duration, and reuse.
9. Maintain the package through listing changes
Every deliverable should have a change trigger and owner. A current property master may stay useful while a price graphic, open house reminder, coming-soon cut, host description, paid ad, thumbnail, or QR destination becomes inaccurate.
| Trigger | Review | Possible action |
|---|---|---|
| Price, status, fact, access, or seller instruction changes | Every file, caption, thumbnail, post, ad, page, host, and link carrying the field | Correct, replace, pause, redirect, remove, or escalate |
| Open house or campaign event ends | Dated video layers, scheduled posts, registration, description, email automation | Stop invitations; retain only approved current property content |
| Representation or publishing authority changes | Accounts, property permission, identity, inquiry route, transfer, portfolio use | Pause and obtain the responsible review before continued use |
| Listing closes or leaves market | MLS or portal path, property page, ads, lead forms, QR codes, portfolio plan | Close out, archive, redirect, remove, or create a separately approved status asset |
| Later reuse proposed | Media license, seller or subject permission, current facts, disclosure, purpose, destination | Approve as a new use rather than relying on file possession |
Use the listing-video repurposing workflow to build derivatives from controlled source layers instead of repeatedly editing published files. Then use the video marketing checklist to publish, measure, update, and retire every approved version.
Frequently asked questions
What video files should a real estate agent request?
Request only the versions tied to approved campaign jobs and destinations. A common scope might need a clean property master, a branded publishing version, an unbranded version for a verified MLS workflow, and a deliberate vertical edit—but the exact package depends on local rules, property story, channels, rights, budget, and maintenance capacity.
Is a vertical crop a separate real estate video deliverable?
Treat it as a separate deliverable when it needs new framing, shot selection, timing, on-screen text, captions, branding, CTA, or approval. Naming it in the brief avoids assuming that a mechanical center crop will preserve the property evidence or produce a usable vertical story.
What is the difference between a correction and a new video version?
Define the difference before work begins. A correction can address an agreed deliverable that does not match an approved fact, source, or technical requirement. A creative revision changes an agreed edit, while a new deliverable changes the format, runtime, structure, branding, audio, channel, or campaign job. The actual agreement should control the project.
Should agents ask for raw footage or project files?
Do not assume they are included. Raw media, project files, fonts, music licenses, graphics, stock assets, and editable templates can have separate ownership, licensing, storage, transfer, and cost terms. Request them only when there is a defined business need and confirm the scope in writing before production.
How should an agent approve a listing video?
Watch each exact version from beginning to end, compare all property facts and visuals with the approved source record, check audio and captions, test the destination and mobile presentation, consolidate time-coded feedback, and retain the final approval with the file manifest. Approval of one master does not automatically approve every derivative.