California AB 723 changes a Monday listing launch by making disclosure part of the image-publishing workflow for virtually altered property photos. Before a California agent publishes a virtually staged image, they need to consider the required AI disclosure, where it appears, and whether it stays visible wherever that image travels.
At 8:17 on a Monday morning, Elena, an illustrative Los Angeles listing agent with coffee cooling beside her keyboard, is reviewing the hero photo for a townhouse scheduled to go live before noon. The original room was empty. The new version has a sofa, two chairs, and a dining table placed to show the room’s scale.
Her seller has already approved the staged image. The MLS entry is nearly finished. Then Elena notices that the disclosure is sitting in a separate caption field, while the image file itself has no visible disclosure.
That creates a real risk. If the image is downloaded, cropped for an MLS preview, shared in an email, or carried to a portal without its caption, a buyer could see a digitally altered room with no accompanying notice. The listing could need correction after launch, and Elena could be left explaining why the disclosure disappeared between her desktop and the public listing.
AB 723 makes the image file part of the compliance conversation
Virtual staging can help an empty room communicate its possible use. It can also alter what a viewer believes they are seeing. California AB 723 puts disclosure at the center of that distinction when AI is used to materially alter a property image.
For an agent, the practical shift is simple: treat the disclosure as part of the publishable asset, not as a final line of listing copy added after the photos are ready.
That does not mean an agent can assume one placement works everywhere. MLS systems, portals, social platforms, email attachments, and screenshot previews can each display images differently. A disclosure placed only in an MLS remarks field may be separated from the photo later. A graphic label positioned too close to an edge may be lost in a crop.
The useful question on Monday morning is: if this image is separated from the listing page, can a viewer still tell it was virtually altered?
That question also keeps the agent focused on the actual image in use. A staged living room, a removed piece of furniture, or an altered yard photo can create different disclosure considerations. Your state association guidance, brokerage policy, MLS rules, and legal counsel remain the right sources for deciding what your specific listing requires. Software can support a documented workflow. It cannot make that legal judgment for you.
The launch path now needs a disclosure check before upload
Elena’s problem is not that she used virtual staging. The problem is that the staged asset and its disclosure can split apart as the launch moves from one system to another.
A stronger Monday workflow begins before the MLS upload:
- Keep the original source image and the virtually staged version clearly named and stored together.
- Use the disclosure treatment required for the image, rather than relying on a disconnected caption alone.
- Review the image at the sizes and placements likely to appear in the MLS and public previews.
- Check every listing channel where the staged image will appear, including social posts and downloadable marketing materials.
- Keep a record of the version approved for publication.
The final step matters when a seller, buyer, broker, or MLS reviewer asks what changed. An agent should be able to identify the original image, the staged version, and the disclosure shown with the published asset.
For a closer look at how a disclosure can disappear after an upload, see What Happens When a Staged Image’s Disclosure Does Not Survive MLS Upload?.
A public provenance record helps keep assets aligned
At 9:02, Elena replaces the caption-only approach with a staged image that carries a visible disclosure. She also saves the original image and the approved listing version in the property’s launch folder. The immediate pressure lifts because the asset she uploads now carries its own context.
That is the operational value of a provenance record. It gives an agent a place to point when someone asks how a listing image was produced and what was altered. NestPath Listing Studio creates virtually staged photos with a burned-in, per-state AI disclosure and a public provenance page alongside the listing kit. The agent still needs to review the output, confirm the disclosure is appropriate for the listing, and check how each publishing destination displays it.
A public record also helps reduce the familiar scramble that happens when a listing has several versions of the same room in circulation. The photo sent to the seller, the photo uploaded to MLS, and the photo used in a video should be easy to trace back to the same approved asset.
Monday launches need a handoff, not a last-minute assumption
By 11:36, Elena is looking at the listing preview rather than hunting through image exports. The seller-approved staged photo is live with its disclosure visible. The original remains available in the launch folder. Her next task is the ordinary work of launching a listing, not reconstructing what happened to an image after it left her computer.
That is the standard worth building toward: every person who touches the launch can see which file is approved, what was changed, and where the disclosure belongs. It makes the handoff from editing to publishing easier to inspect before a buyer sees the listing.
If an MLS preview crops a label or a portal changes how image captions display, pause and correct the asset before treating the launch as complete. A fast launch is useful. A launch you can explain later is better.
Comments
No comments yet.