Send the vendor this exact question: “Will you deliver each edited photo with the applicable AI or virtual-staging disclosure burned into the image, plus a record linking it to the original photo?” A clear yes establishes that the deliverable includes disclosure-ready files and provenance; anything less may leave you with edited images and a Friday-afternoon compliance job.
Consider a composite example. At 4:17 p.m. on Friday, Dana, a listing agent in Sacramento, is sitting in her car outside the property with twelve staged JPEGs open on her laptop. The vacant living room now has a sofa, rug, and floor lamp. The vendor’s folder contains no originals, no visible disclosures, and no explanation of what changed.
Her seller expects the listing to launch that evening. If Dana uploads the photos as delivered, the listing may go live without the disclosure required for altered listing images. If she holds the photos, she misses the promised launch. The vendor’s support desk has not confirmed whether the files were meant for direct MLS use.
The problem began before the images arrived. Dana asked for virtual staging, but she never defined the final deliverable.
What the question forces the vendor to confirm
“Do you support disclosure?” is too broad. A vendor can answer yes because its website mentions disclosure, its dashboard offers a label, or its terms tell agents to follow local rules. None of those answers confirms what will be inside the downloaded file.
The more precise question separates three outputs that are easy to confuse:
- An edited image shows the visual changes but may contain no disclosure.
- A disclosure-ready image carries the applicable notice directly on the image, where the requirement calls for it.
- A provenance record connects the edited version to its source photo and documents the relationship between them.
That distinction matters in California. What AB 723 actually requires on a listing photo is more specific than a general statement that artificial intelligence was used somewhere in the marketing process. Rules and association guidance can differ by state, MLS, image type, and use, so the agent still has to confirm what applies to the listing.
A burned-in notice also does a different job from metadata. Metadata may be stripped when a file is exported, resized, uploaded, or passed between systems. A visible disclosure travels with the image. A provenance page or paired original provides a separate record of what the edited file came from.
How to evaluate the vendor’s reply
A useful answer should identify exactly what arrives in the download. Ask the vendor to confirm the wording, placement, and format of the disclosure, along with how the original and edited files remain associated.
Watch for replies such as “We support compliance,” “Disclosure is available,” or “Agents are responsible for local requirements.” The final statement may be legally prudent, but it does not tell you whether the file is ready to upload.
The operational answer should be concrete: the disclosure is visibly embedded in each applicable image; the original remains available; the edited file can be matched to that original; and the vendor explains any steps the agent must complete before publication.
If the vendor provides only clean edited JPEGs, plan for another tool or manual process. Someone must determine the applicable wording, apply it consistently, retain the original, and verify that the finished export still displays the disclosure at a readable size. Running staging and disclosure as separate tools can work, but the handoff between them becomes part of your listing workflow.
Why provenance belongs in the same question
A disclosure tells the viewer that an image was altered. Provenance helps establish which original produced that image.
That record becomes useful when the seller asks what changed, a broker reviews the file, or an MLS question arrives after publication. A folder full of filenames such as `living-room-final-3.jpg` provides little help if nobody can locate the source photo.
Keep the original, the edited version, and the disclosure record together. Use stable room names or image identifiers. Record the vendor and completion date. These are simple habits, but they reduce guesswork when a listing moves from photographer to agent, transaction file, MLS, portal, and social post.
NestPath Listing Studio addresses this workflow by turning an agent’s own listing photos into a kit with virtually staged images, a burned-in per-state AI disclosure, and a public provenance page. It also includes a narrated Remotion tour video and an MLS-ready text pack with a fair-housing check. The software assists with disclosure and documentation; the agent remains responsible for applying current law, MLS rules, and state-association guidance.
The file check before Friday’s upload
Back in Dana’s car, the vendor finally confirms that the folder contains edited images only. She postpones the upload rather than guessing at the disclosure. The listing does not launch that evening, but the risk is now visible and fixable.
For the next property, she sends the precise question before paying the invoice. When the download arrives, she checks one staged image for a visible notice, opens its matching original, and confirms the provenance record before reviewing the rest of the kit.
That small change moves the compliance check to the start of the order, when there is still time to choose the right vendor or add the missing disclosure step.
Comments
No comments yet.