Run the Friday check in three columns: image, remarks, and both. Classify the applicable requirement before you select files for the MLS, portal, social post, or email, because a disclosure that belongs on an altered image cannot be repaired by polished remarks alone.
In September 1983, Stanislav Petrov was on duty at the Soviet early-warning center at Serpukhov-15 when the system reported incoming U.S. missiles. The decision was still uncertain: treat the signal as an attack, or classify it as a false alarm. Petrov judged the warning unreliable, and the alert was later found to be false. David E. Hoffman documents the incident in The Dead Hand.
A Friday listing review is smaller in every respect, but the operating discipline is familiar. Do not start by asking which finished files look ready. Start by asking what kind of requirement you are dealing with, and where it has to travel.
Build the three columns before you export anything
Open a simple note or spreadsheet with three headers: Image, Remarks, and Both. Then put each applicable state rule, MLS rule, brokerage policy, or advertising requirement into one column before publishing.
The Image column is for requirements tied to the visual itself. If an altered photo needs disclosure to stay with the image, treat the disclosure as part of the asset. Check the exported JPEG or PNG, not only the design preview. A caption can disappear when a photo is shared, cropped, screenshotted, or uploaded to a different platform.
The Remarks column is for requirements that belong in the listing text. This could include wording your MLS expects, a brokerage-required note, or copy that gives buyers context about a material feature. Review the final MLS description after pasting it in. Fields can truncate text, and agents often revise remarks after the photo package is approved.
The Both column is where Friday mistakes tend to happen. An agent may correctly add a note to remarks, then send a virtually staged hero image into a channel where the remarks never appear. Or the image carries a disclosure, but the MLS description omits information required by local policy. The safest response is to identify each obligation separately and publish the matching materials together.
Treat the listing kit as separate publishable parts
A listing kit can feel like one finished package. In practice, each part travels differently.
Your MLS photo carousel, public property page, Instagram post, agent email, and printed flyer may display different combinations of imagery and text. That means the compliance question is not “Does this kit have a disclosure?” It is “Does this specific placement carry the disclosure and context it requires?”
For a virtually staged image, keep the original photo, the altered export, and the published version together in your records. If the image needs a burned-in disclosure under the rule you are applying, inspect the actual exported file at usable size. A disclosure that sits in a margin or overlay can be lost in a crop. For a closer look at that risk, see What Happens When a Virtual Staging Disclosure Is Cropped Out?.
For remarks, paste the reviewed text into the destination field and read it there. Confirm that virtual staging language, property facts, and fair-housing-sensitive phrasing survived the handoff. The source document is useful, but the published field is what a buyer and MLS reviewer will see.
Use the “both” column to catch split-channel risk
The Both column deserves its own pass because it reflects how listing marketing actually gets distributed.
Say you have a virtually staged living-room image and an MLS description that explains the staging. If the image goes to a portal feed or social graphic without the accompanying remarks, the explanatory text may be absent where the image appears. If you only add a disclosure to the image but your local requirement or brokerage policy also expects text in remarks, the image file does not complete the review.
This is where a per-state disclosure workflow can help. NestPath Listing Studio creates virtually staged photos with a burned-in per-state AI disclosure, plus an MLS-ready text pack and a public provenance page. That gives you materials to review in the correct columns. It does not decide the applicable rule for you. Your legal judgment, MLS rules, brokerage policy, and state association guidance remain the authority.
California AB 723 and rules in roughly 38 other states make this a real operational issue for agents using AI-altered listing imagery. The details can vary, which is exactly why a generic “AI generated” label should not be treated as a universal answer. Review the wording and placement against the market where the listing will be advertised. MLS AI Image Disclosure: Why Maya Put It on Every Virtually Staged Photo covers the practical value of keeping disclosure with the image.
Make Friday review a publish decision, not an asset review
Before anything goes live, review each channel against the three columns:
- Confirm every altered image has the image-level disclosure required for that use.
- Confirm the final MLS remarks contain any required text-level disclosure or context.
- For anything in Both, verify the image and remarks will appear together where you are publishing, or that each can stand on its own when they separate.
- Retain the original, altered file, final published version, and the rule or guidance you relied on.
Petrov’s decision at Serpukhov-15 turned on refusing to treat one kind of signal as another. Your Friday check has the same modest, useful discipline: classify first, then publish the exact files and remarks that belong in that channel.
Comments
No comments yet.