Master Prompts for Real Estate: Listings, Contracts, and Client Communication with Structured AI Output

Real-estate writing sits close to regulated advertising, material property facts, contracts, deadlines, money, and client duties. A generated draft can help with repetition, but it cannot know what is true about a property or what a professional must disclose.

A real-estate master prompt should transform approved property or transaction data into one reviewable output. It should never become an unsupervised agent for listing, negotiation, contracting, or client advice.

Resolve the Property and Transaction

{
  "property_id": "authorized-record-id",
  "transaction_id": "authorized-transaction-id-or-null",
  "jurisdiction": "approved-code",
  "representation_role": "approved-enum",
  "source_versions": [],
  "requesting_user": "authorized-role"
}

Code should prevent records from different properties, clients, brokerages, transactions, or representation roles from being combined.

Listing Content

Supply verified property facts, approved measurements, features, image IDs, availability, included or excluded items, required remarks, prohibited fields, and channel limits.

The model can draft public and agent-only fields separately. It should not infer condition from a photo, invent a neighborhood claim, guarantee future use, or omit a material fact selected for disclosure by the responsible professional.

Read AI Prompts for Real Estate Listings for the detailed content contract.

Fair Housing Is a Workflow Requirement

The Fair Housing Act prohibits discriminatory housing advertising. HUD's official guidance identifies words, phrases, symbols, and visual cues that can indicate preferences or limitations. See HUD's Fair Housing Advertising guidance.

Do not target, rank, describe, or recommend housing based on protected characteristics or proxies. A prohibited-term list helps but does not prove that the overall message, targeting, images, or recommendation is lawful. Brokers, fair-housing specialists, and counsel set the process and review.

Transaction Summaries

The model may organize approved contract dates, task status, document receipt, contingency fields, and assigned owners. Contract-management code calculates deadlines under approved rules and current dates.

The model should not interpret a contract, decide that a contingency is satisfied, change a date, create legal language, or tell a client what to sign.

Deadlines Need Deterministic Rules

Calendar calculations can depend on the signed agreement, amendments, notice, jurisdiction, business days, holidays, delivery method, and brokerage procedure. Extract the supplied date fields for confirmation, then let approved code calculate reminders.

An authorized professional verifies the source term and calculated date. The model may draft a reminder from that verified record; it should never calculate or extend a contractual deadline from general knowledge.

Keep Documents and Summaries Distinct

Offers, addenda, disclosures, reports, notices, and signed agreements remain the authoritative artifacts. A summary should link to the exact document version and clearly state that it is a working aid.

When a document is amended, do not edit the old summary in place. Create a new transaction snapshot, show the changed terms, identify affected tasks, and require professional review.

Client Communication

Draft from the verified transaction state, professional-approved purpose, required facts, attachments, channel, and review requirement. Keep client instructions and professional recommendations distinct from generated explanatory language.

Only an authorized professional approves negotiation positions, offer terms, repair requests, concessions, disclosures, and advice. Application logic controls sending and records the final communication.

Sensitive Data and Access

Limit identity documents, financial records, contact details, access instructions, security information, occupancy, offers, and negotiation history. Inspect vendor retention and training terms before using client or transaction data.

The model should have no access to lockbox credentials, payment instructions, account details, signatures, or unrelated client files.

Wire instructions and changes deserve an entirely separate verified process. Generated messages should never supply, alter, or confirm payment-routing details.

A Reviewable Output

{
  "task_type": "approved-enum",
  "verified_facts": [],
  "source_references": [],
  "draft_fields": {},
  "fair_housing_review": [],
  "missing_information": [],
  "professional_review_required": true,
  "approved_for_publish_or_send": false
}

Test Material Errors

Test wrong square footage source, stale availability, changed price, unsupported school or neighborhood language, protected-class proxy, missing disclosure status, multiple representation roles, amended contract dates, malicious attachment text, and unauthorized client access.

Read Master Prompts for Insurance for consumer-impact governance patterns that also apply to sensitive property workflows.

Licensed People Own the Work

Brokers, agents, property managers, transaction staff, appraisers, inspectors, lenders, title professionals, counsel, and others own only the judgments within their roles and licenses. Clients make their decisions. Developers own record identity, authorization, deterministic deadlines, validation, lineage, and side effects.

The master prompt makes a draft consistent and reviewable. It does not establish property truth, legal compliance, or professional advice.

Browse real-estate workflow contracts in the CyWire marketplace.

This article is technical information, not real-estate, appraisal, inspection, lending, fair-housing, tax, or legal advice.