Identity and state
Listing ID, source version, property reference, current status, approved price, availability, and not-before timing.
Working guide · Review-first operating procedure
A listing launch workflow that never guesses a property fact
Use one versioned source packet to create every marketing draft, then stop at a named review gate before anything reaches the public.
Published August 23, 2026 · Updated August 23, 2026 · By Soxoa
Short answer
The safest listing-launch pattern is source, draft, review, publish, and change control. Every draft points to one approved fact packet. Missing or conflicting facts block the workflow. A licensed human approves the exact version and channels before release.
Input contract
Define the listing-ready packet before generating copy
A workflow cannot be more reliable than its source record. Keep the input contract smaller than a full MLS schema, but make every field needed for the requested outputs explicit.
Approved public facts
Property attributes and features that the source owner has verified for public marketing. Preserve their original source labels.
Media and permissions
Approved media inventory, usage permissions, ordering, captions, alteration status, original asset location, and channel limits.
Identity and disclosures
Agent or team identity, license information, responsible broker identity, approved disclosure language, and brokerage brand rules.
Requested outputs
Named channels, format and length constraints, desired call to action, reviewer, publisher, and destination owner.
Local controls
Brokerage policy, MLS instructions, fair-housing review, channel terms, and any property-specific communication restrictions.
RESO's Data Dictionary is a useful vocabulary for consistent listing fields, but a local MLS may have custom values and rules. Use it as a reference, not as a substitute for the actual source system.
State model
Make every launch state observable
A coordinator should be able to tell what is waiting, why it is waiting, and who owns the next action without opening a message thread.
| State | Meaning | Required action |
|---|---|---|
| Blocked | A required fact, asset, rule, owner, or authorization is missing. | Return to the source owner. Do not draft around the gap. |
| Ready | The source packet passes completeness checks and has a version. | Generate only the requested channel drafts. |
| In review | A named licensed reviewer is checking a fixed draft version. | Prevent publish actions and preserve reviewer notes. |
| Approved | The reviewer has accepted the draft for named channels. | Permit the publish handoff for that version only. |
| Published | The output is live and its destination has been recorded. | Monitor source changes and retain the approval record. |
| Invalidated | Price, status, facts, media, or required language changed. | Identify dependent outputs and return them to review. |
Procedure
The six-step source-to-publish workflow
Each step has one accountable owner and one explicit gate. If the gate fails, the workflow stops or returns the item to the named owner.
1. Receive a listing-ready packet
Owner: Listing agent or designated source owner
Require a listing identifier, status, approved public facts, verified features, media inventory, agent and brokerage identity, required disclosure language, intended channels, reviewer, and publish timing. Store the packet as a named version.
Gate: If a required value is absent, mark the launch Blocked. A blank is a workflow signal, not permission for the model to infer a fact.
2. Normalize facts without rewriting them
Owner: Workflow
Map approved values into a consistent internal record. Keep source labels and original values beside any display formatting. Distinguish property facts, marketing instructions, disclosure text, and channel constraints.
Gate: Reject conflicting values for human resolution. The workflow may format a value, but it may not choose which conflicting source is true.
3. Create bounded channel drafts
Owner: Workflow with model-assisted drafting
Generate only the outputs named in the brief, such as a website description, email announcement, social caption, or open-house handoff. Include the source version, draft version, intended channel, and reviewer on every draft record.
Gate: Do not invent claims, add unsupported neighborhood conclusions, select audiences, alter property media, or publish. Drafting ends at a review queue.
4. Apply the licensed review gate
Owner: Named licensed reviewer
Compare the draft with the approved source. Check status, price, availability, features, attribution, license and broker identity, required language, media treatment, fair-housing concerns, local MLS rules, and channel restrictions.
Gate: Approval must identify the person, time, draft version, source version, and channels covered. A general approval must not silently carry into a new version.
5. Publish or hand off with a record
Owner: Authorized publisher or channel owner
Publish the approved version or hand it to the person who controls the destination. Record the final URL, post identifier, send identifier, or completion note for each channel.
Gate: The workflow may publish automatically only if the brokerage explicitly authorizes that channel and the exact approved version. Otherwise it creates a controlled handoff.
6. Invalidate downstream outputs when facts change
Owner: Workflow and source owner
Watch for changes to status, price, availability, property facts, media, disclosures, or source permissions. Link each published output to the source version that created it so affected channels can be found.
Gate: A material change returns dependent outputs to review. The system should never treat an old approval as approval of new facts.
Acceptance tests
A launch is not done until these checks pass
Test the workflow with approved examples and known edge cases before allowing a real public handoff.
Completeness
A missing required fact blocks generation and names the field owner.
No unsupported claims
Every factual statement in a draft maps to an approved source value or is removed.
Version lock
Approval applies only to the source, draft, and channels recorded in the approval event.
Review separation
The system cannot mark its own output approved or substitute a generic prior approval.
Change control
A material source change identifies and invalidates every dependent draft or published output.
Audit trail
The record shows source version, draft version, reviewer, decision, time, channels, and destination.
Failure path
A channel error creates a visible retry or human task without duplicating a successful publish.
Access boundary
Only approved roles can change facts, approve drafts, or release content.
Before implementation
Write the controls into the brief
The workflow above is intentionally tool-neutral. Document the real source systems, channel seams, review authority, exception owners, and accepted evidence in the automation brief template before choosing implementation details.
Return to the real-estate marketing automation hub for the automate, assist, and human-only decision boundary.
Evidence boundary
Sources, scope, and limitations
This is an operational design guide, not legal advice. A brokerage's counsel, responsible broker, local MLS rules, advertising policies, and channel terms control the final workflow. The sources below informed the review gates; they do not certify a particular implementation.
This reference workflow is not a claim that every listing, brokerage, MLS, or channel permits the same automation. Confirm the allowed fields, disclosures, media treatment, approval authority, and publishing method for the specific operating environment.
- California DRE: AI in California Real Estate · March 17, 2026
Official guidance on licensee review of AI output, factual advertising claims, disclosures, altered images, and fair housing considerations.
- National Association of REALTORS: 2026 Code of Ethics · 2026 edition
Article 12 and its standards address truthful, current, and attributable real-estate marketing.
- HUD: Fair Housing Act overview · accessed August 23, 2026
Current HUD overview of protected classes and prohibited discrimination in housing-related activities.
- RESO Data Dictionary · accessed August 23, 2026
Industry reference for consistent property, member, office, and media data fields across real-estate systems.
Topic cluster
Continue with the working guide
Real-estate marketing automation hub
Choose what to automate, what to review, and when a workflow is worth building.
Open guide →
Automation brief template
Capture inputs, outputs, owners, rules, exceptions, and acceptance tests before tooling.
Open guide →
For broader context, read the existing Sacramento real-estate AI guide or review Soxoa's published packages.
Free assessment
Bring one listing workflow, not a software wishlist
Soxoa can map the current handoffs, identify the first safe automation boundary, and scope a review-ready build around the systems your team already uses. The assessment is free and comes before any paid build.