Write Listing Descriptions: make listing copy map with fact-only feature notes reviewable

For listing description, bring the rough note "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." and turn it into a listing description with property facts, feature hierarchy, buyer appeal, and compliance-safe claims visible from the first pass.

Start with the right jobUse this workflow when your note, output, and switch point line up.

First move: First move: run the prompt only after the audience, source material, stop rule, and reviewer for listing description quality, property facts and feature hierarchy, and local-compliance restraint are named; otherwise collect context before copying.
Keep after run: Keep after run: the original note, the variables that changed the answer, and the section where source notes, examples, constraints, and reviewer judgment is separated from assumptions before reuse.
Wrong page signal: Wrong page signal: switch to ChatGPT Prompts for Real Estate Agents if the user cannot supply property facts, features, neighborhood context, photo notes, and compliance limits, if the desired result is not a listing description, or if property facts, feature hierarchy, buyer appeal, and compliance-safe claims is no longer the controlling decision.

First usable run

Start with the note you actually have

A realistic example is loaded. Try the flow once, then clear it and paste your own working notes.

1/3 ready

Next stepFinish the run setup2 items still need context before this becomes reusable.

Current note

Paste source notesMust keepDo not allow

PrepareSource noteReal notes are loaded.
RunCopy run prompt2 checks before copy.
ReviewReview answerCurrent choice: Repair.
SaveSave reusable version0/3 save checks closed.

Keep working laterPage work stays on this device until you save it.

Try the sample firstSee one messy note become a usable write listing descriptions run

Messy input: A rough listing description note comes in: "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." is the rough request. Before reusing listing description, the usable version reads as a listing description, keeps property facts, feature hierarchy, buyer appeal, and compliance-safe claims visible, names the checker, and protects this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.
Better answer should: A usable listing description handoff would return copy options grouped by angle, audience, proof point, and revision note; separate supplied notes from assumptions, name the review owner, prepare listing copy map with fact-only feature notes, and make the human pass focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint.
Human edit: real estate agent should revise write listing descriptions by keeping the structure that saved time, replace polished filler with source-backed lines inside a listing description, remove private or one-time information, and rewrite the final wording for a buyer, seller, lead, or broker reviewer; compare the answer with "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." and make sure The final description should be accurate, inviting, compliant, and easy to verify against the listing sheet.

Fix before reuse2 gaps before reuseCopy can start the first pass, but the answer is not reusable until these checks are closed.

Separate facts from assumptionsMark which must-keep details came from the user and which details still need a human decision.
Name who checks it and the stop ruleKeep the handoff honest by assigning one person to test the answer against the rough note and final audience. must know what to reject before the answer is reused.

Real note: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Phrase shopping in write listing descriptions fails because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This write listing descriptions run should turn that note into a listing description. For write listing descriptions, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.
What will change: Start by pasting the rough note, then replace the variables that control audience, source material, and the reviewer for listing description quality, property facts and feature hierarchy, and local-compliance restraint.
Human check: Source review, write listing descriptions: the answer uses the supplied property facts, features, neighborhood context, photo notes, and compliance limits and does not fill missing facts with confident guesses.

Open run previewCheck the exact prompt before copying.

Run prompt preview

Copy this after checking the notes

Task: ChatGPT Prompts for Real Estate Agents to Write Listing Descriptions
Who checks it: Keep the handoff honest by assigning one person to test the answer against the rough note and final audience.

Paste source notes:
Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Phrase shopping in write listing descriptions fails because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This write listing descriptions run should turn that note into a listing description. For write listing descriptions, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.

Must keep:
Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.
property facts, features, neighborhood context, photo notes, and compliance limits
property facts, feature hierarchy, buyer appeal, and compliance-safe claims

Do not allow:
Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Reject it if the output sounds polished but does not become a listing description.

Readiness before copy:
- Separate facts from assumptions: Mark which must-keep details came from the user and which details still need a human decision.
- Name who checks it and the stop rule: Keep the handoff honest by assigning one person to test the answer against the rough note and final audience. must know what to reject before the answer is reused.

Run prompt:
Act as a careful assistant for Real Estate Agents.
Task: help me write listing descriptions. Target result: a listing description.
Source material I can provide: [source_material]. Typical source for this task is property facts, features, neighborhood context, photo notes, and compliance limits.
Audience or stakeholder: [audience]. The output must work for a buyer, seller, lead, or broker reviewer.
Task-specific focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return copy options grouped by angle, audience, proof point, and revision note.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.
Check cue: The user should get a working version they can inspect against the supplied notes.

Stop rule: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Record to keep: Save a short record of the original note, the prompt variables that changed the answer, the section that still needs listing description quality, property facts and feature hierarchy, and local-compliance restraint, and the final reason the accepted version can become listing description prompt pattern with source notes, constraints, and review checklist.

Open answer reviewUse this after ChatGPT returns the first answer.

After ChatGPT answers

Check the answer before saving it

Check against: Source review, write listing descriptions: the answer uses the supplied property facts, features, neighborhood context, photo notes, and compliance limits and does not fill missing facts with confident guesses. Output shape, write listing descriptions: the result clearly becomes a listing description, not broad advice about the task.
Reject if: Evidence issue, write listing descriptions: the answer invents or overstates source notes, examples, constraints, and reviewer judgment. Task drift, write listing descriptions: it ignores property facts, feature hierarchy, buyer appeal, and compliance-safe claims and moves into a neighboring workflow.
Keep after run: Save a short record of the original note, the prompt variables that changed the answer, the section that still needs listing description quality, property facts and feature hierarchy, and local-compliance restraint, and the final reason the accepted version can become listing description prompt pattern with source notes, constraints, and review checklist.

Open first answer choiceChoose accept, repair, or reject only after review.

First answer choice

Pick accept, repair, or reject before reuse

After the first write listing descriptions answer, the real estate agent should choose Accept, Repair, or Reject before saving anything as listing description prompt pattern with source notes, constraints, and review checklist. The decision must compare "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." with copy options grouped by angle, audience, proof point, and revision note, property facts, feature hierarchy, buyer appeal, and compliance-safe claims, and source notes, examples, constraints, and reviewer judgment.

Choose when: Choose Repair when the answer has a useful shape but loses one of the required pieces: property facts, feature hierarchy, buyer appeal, and compliance-safe claims, source notes, examples, constraints, and reviewer judgment, the reviewer role, the source note, or the reusable fields needed for listing description prompt pattern with source notes, constraints, and review checklist.
Do next: Ask ChatGPT for a second pass that keeps the usable structure, rewrites only the weak sections, adds missing proof questions, and returns a listing description in copy options grouped by angle, audience, proof point, and revision note without inventing details.
Keep after run: Keep the weak answer beside the repair note, mark which line failed listing description quality, property facts and feature hierarchy, and local-compliance restraint, and save the corrected line only after it can be traced back to "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.".

Answer choice prompt

Repair this write listing descriptions answer instead of accepting it. Source note: "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." Weak answer: [paste_chatgpt_output_here]. Preserve any useful structure, but fix the parts that hide property facts, feature hierarchy, buyer appeal, and compliance-safe claims, turn source notes, examples, constraints, and reviewer judgment into unsupported certainty, or skip the reviewer for listing description quality, property facts and feature hierarchy, and local-compliance restraint. Return a repaired copy options grouped by angle, audience, proof point, and revision note, a list of changed lines, and one remaining question before this can become listing description prompt pattern with source notes, constraints, and review checklist.

Do not save a reusable listing description prompt pattern with source notes, constraints, and review checklist until one option has a written decision. The saved version must keep "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." as the example, turn private or one-time details into variables, and keep the risk check "avoid claims about safety, schools, investment return, or legal facts without source support" visible for the next run.

Open saved versionTurn the reviewed answer into a reusable saved version.

Saved version

Save the final answer, human edit, and variables

Save only after review. The reusable version needs the answer, the human edit, and the reuse rule in one place.

Final answerHuman editReusable variables

Save only when

The final answer passed the answer review.The human edit names what changed before reuse.Who checks it and reuse rule are saved with the asset.

Who checks it: The human owner who approves the final packet for Real Estate Agents to Write Listing Descriptions before it is saved, shared, or reused.
Reuse rule: Reuse listing description only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a listing description, and the review rule for property facts, feature hierarchy, buyer appeal, and compliance-safe claims still appears in the reusable prompt. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible.
Saved: 0/3 checks

Saved version preview

Final saved version for: ChatGPT Prompts for Real Estate Agents to Write Listing Descriptions
Who checks it: The human owner who approves the final packet for Real Estate Agents to Write Listing Descriptions before it is saved, shared, or reused.
Use or revise before saving: Repair

Save only after review:
- Source review, write listing descriptions: the answer uses the supplied property facts, features, neighborhood context, photo notes, and compliance limits and does not fill missing facts with confident guesses.
- Save a short record of the original note, the prompt variables that changed the answer, the section that still needs listing description quality, property facts and feature hierarchy, and local-compliance restraint, and the final reason the accepted version can become listing description prompt pattern with source notes, constraints, and review checklist.
- Keep the original note, the exact prompt variables that changed the answer, the section that proves listing description quality, property facts and feature hierarchy, and local-compliance restraint, and the final accept reason before the result reaches a buyer, seller, lead, or broker reviewer.
- Current answer choice: Keep the weak answer beside the repair note, mark which line failed listing description quality, property facts and feature hierarchy, and local-compliance restraint, and save the corrected line only after it can be traced back to "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.".

Source note used:
Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Phrase shopping in write listing descriptions fails because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This write listing descriptions run should turn that note into a listing description. For write listing descriptions, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.

Final answer:
A usable listing description handoff would return copy options grouped by angle, audience, proof point, and revision note; separate supplied notes from assumptions, name the review owner, prepare listing copy map with fact-only feature notes, and make the human pass focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Human edit:
real estate agent should revise write listing descriptions by keeping the structure that saved time, replace polished filler with source-backed lines inside a listing description, remove private or one-time information, and rewrite the final wording for a buyer, seller, lead, or broker reviewer; compare the answer with "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." and make sure The final description should be accurate, inviting, compliant, and easy to verify against the listing sheet.

Reusable variables:
[source_material]: property facts, features, neighborhood context, photo notes, and compliance limits
[audience]: a buyer, seller, lead, or broker reviewer
[goal]: make a listing description easier to review, adapt, and use in a real real estate agents workflow
[constraints]: avoid claims about safety, schools, investment return, or legal facts without source support

Reuse rule: Reuse listing description only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a listing description, and the review rule for property facts, feature hierarchy, buyer appeal, and compliance-safe claims still appears in the reusable prompt. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible.
Stop if: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.

First run setup

Set up the first run

Edit notes

First move: Start by pasting the rough note, then replace the variables that control audience, source material, and the reviewer for listing description quality, property facts and feature hierarchy, and local-compliance restraint.
Bring first: Bring the rough case note: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.
Switch if: The user cannot provide property facts, features, neighborhood context, photo notes, and compliance limits and would need ChatGPT to invent the important facts.
Keep after run: Save a short record of the original note, the prompt variables that changed the answer, the section that still needs listing description quality, property facts and feature hierarchy, and local-compliance restraint, and the final reason the accepted version can become listing description prompt pattern with source notes, constraints, and review checklist.

Choose where you areGo to runner

Go to runnerWithin five minutes, the user should have a first listing description prompt pattern with source notes, constraints, and review checklist, one copied run prompt, and a reviewer check that keeps listing description quality, property facts and feature hierarchy, and local-compliance restraint and source notes, examples, constraints, and reviewer judgment visible before sharing anything. Start with: Start by pasting the rough note, then replace the variables that control audience, source material, and the reviewer for listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Go to runner

Open switch notesWhat to bring, who checks it, and when to change workflows.

Who checks it

Keep the handoff honest by assigning one person to test the answer against the rough note and final audience.

Check before using

Inspect property facts, features, neighborhood context, photo notes, and compliance limits, the case note "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.", and any open proof around source notes, examples, constraints, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.

Compare later

Result listing description real estate agents check: open the top results and record whether they solve the task, not only a prompt phrase.

Visitor question: I have property facts, features, neighborhood context, photo notes, and compliance limits and need a listing description for a buyer, seller, lead, or broker reviewer; can this write listing descriptions page turn "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." into copy options grouped by angle, audience, proof point, and revision note without hiding property facts, feature hierarchy, buyer appeal, and compliance-safe claims?
5-minute outcome: Within five minutes, the user should have a first listing description prompt pattern with source notes, constraints, and review checklist, one copied run prompt, and a reviewer check that keeps listing description quality, property facts and feature hierarchy, and local-compliance restraint and source notes, examples, constraints, and reviewer judgment visible before sharing anything.
Wrong page signal: This is the wrong page if the work is closer to ChatGPT Prompts for Real Estate Agents, if property facts, feature hierarchy, buyer appeal, and compliance-safe claims is not the controlling decision, or if the user only wants broad ideas instead of a reviewable a listing description.
Why this page fits: Save the rough note, the accepted prompt variables, the listing description query language, and the section that proves this a listing description is not interchangeable with ChatGPT Prompts for Real Estate Agents.
Reuse decision: Reuse the output only when the answer traces back to property facts, features, neighborhood context, photo notes, and compliance limits, respects the risk check "avoid claims about safety, schools, investment return, or legal facts without source support", and gives a buyer, seller, lead, or broker reviewer a clear accept, repair, or reject path.

Wrong page? ChatGPT Prompts for Real Estate AgentsReturn to the role guide to choose by situation, output, and reviewer.

Working brief

Check the job before copying

It is not interchangeable with a neighboring prompt because the source has to become a listing description, and the acceptance test is whether a buyer, seller, lead, or broker reviewer can use it without guessing the missing pieces.

Use this when: The page is for the moment when real estate agents have enough notes to create a listing description, but still need a decision about property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Paste this kind of note: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Phrase shopping in write listing descriptions fails because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This write listing descriptions run should turn that note into a listing description. For write listing descriptions, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.
Expected result: A usable listing description handoff would return copy options grouped by angle, audience, proof point, and revision note; separate supplied notes from assumptions, name the review owner, prepare listing copy map with fact-only feature notes, and make the human pass focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint.
Stop before reuse if: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Human check: Source review, write listing descriptions: the answer uses the supplied property facts, features, neighborhood context, photo notes, and compliance limits and does not fill missing facts with confident guesses.

Bring first: Bring the rough case note: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.
Build when: Use this when the notes are ready and the next useful output is copy options grouped by angle, audience, proof point, and revision note, not more brainstorming.
Stop if: Stop if the answer hides missing context, blurs assumptions, or cannot trace key claims back to the notes.
Save when: Copy the external review checklist, record what changed, and save a version with reusable variables instead of private details.

Copy prompt Check answer

Fit and safety notes

Use this page for

Real Estate Agents who have real notes or context and need a structured first version of a listing description.
Users who want ChatGPT to ask clarifying questions before it commits to copy options grouped by angle, audience, proof point, and revision note.
Teams that repeat write listing descriptions and need a prompt they can adapt without losing the review step.

Do not use for

Users who want ChatGPT to invent facts, credentials, numbers, or personal details.
Situations where the output needs final approval from a qualified human before it reaches a buyer, seller, lead, or broker reviewer.
Work that includes private data that has not been removed or summarized safely.

Wrong page?ChatGPT Prompts for Real Estate AgentsReturn to the role guide to choose by situation, output, and reviewer.

Editorial method Safe use About this library

Write listing descriptions Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become a listing description.

Real input: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Phrase shopping in write listing descriptions fails because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This write listing descriptions run should turn that note into a listing description. For write listing descriptions, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.
Target output: A usable listing description handoff would return copy options grouped by angle, audience, proof point, and revision note; separate supplied notes from assumptions, name the review owner, prepare listing copy map with fact-only feature notes, and make the human pass focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint.
Reject if: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.

Scenario: An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access. The write listing descriptions work happens inside a public listing where facts, fair-housing boundaries, and buyer expectations meet. For real estate agents listing description, current source notes should come first; stale or partial inputs should trigger a fresh listing copy map with fact-only feature notes pass instead of another saved answer. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible. For write listing descriptions, those constraints decide what the answer is allowed to do; without them, ChatGPT can sound finished while skipping the detail a real estate agent checks first.
Bring: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. property facts, features, neighborhood context, photo notes, and compliance limits property facts, feature hierarchy, buyer appeal, and compliance-safe claims
Check: The final description should be accurate, inviting, compliant, and easy to verify against the listing sheet. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible. Before handing off write listing descriptions, the final human edit should keep the useful structure, remove unsupported details, add verified context, and check listing description quality, property facts and feature hierarchy, and local-compliance restraint before the output reaches a buyer, seller, lead, or broker reviewer, with a short record of what changed before reuse and where For real estate agents listing description, current source notes should come first; stale or partial inputs should trigger a fresh listing copy map with fact-only feature notes pass instead of another saved answer.

Variable Builder

[source_material]The notes, facts, examples, or raw material behind write listing descriptions.[audience]Who will read, use, approve, or act on the output.[goal]The decision or work outcome the response should support.[constraints]Rules, tone, length, channel, privacy limits, and required sections.[review_lens]The most important thing a human should check after the answer.[task_focus]The task-specific detail that keeps this prompt from becoming generic.

Filled prompt

Copy this filled version

Act as a careful assistant for Real Estate Agents.
Task: help me write listing descriptions. Target result: a listing description.
Source material I can provide: [source_material]. Typical source for this task is property facts, features, neighborhood context, photo notes, and compliance limits.
Audience or stakeholder: [audience]. The output must work for a buyer, seller, lead, or broker reviewer.
Task-specific focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return copy options grouped by angle, audience, proof point, and revision note.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.
Check cue: The user should get a working version they can inspect against the supplied notes.

Show raw template

Act as a careful assistant for Real Estate Agents.
Task: help me write listing descriptions. Target result: a listing description.
Source material I can provide: [source_material]. Typical source for this task is property facts, features, neighborhood context, photo notes, and compliance limits.
Audience or stakeholder: [audience]. The output must work for a buyer, seller, lead, or broker reviewer.
Task-specific focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return copy options grouped by angle, audience, proof point, and revision note.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.
Check cue: The user should get a working version they can inspect against the supplied notes.

Expected output: Expect copy options grouped by angle, audience, proof point, and revision note that explicitly separates source-based content from assumptions and ends with a review pass for listing description quality, property facts and feature hierarchy, and local-compliance restraint.

First run

Run this page in four moves

Concrete outputA usable listing description handoff would return copy options grouped by angle, audience, proof point, and revision note; separate supplied notes from assumptions, name the review owner, prepare listing copy map with fact-only feature notes, and make the human pass focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Keep after runSave a short record of the original note, the prompt variables that changed the answer, the section that still needs listing description quality, property facts and feature hierarchy, and local-compliance restraint, and the final reason the accepted version can become listing description prompt pattern with source notes, constraints, and review checklist.

Reject before reuseReject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.

PrepareCollect ContextUse this when the real estate agent source notes are still uneven or missing the detail that would shape a listing description.CopyBuild The AssetUse this when the notes are ready and the next useful output is copy options grouped by angle, audience, proof point, and revision note, not more brainstorming.GradeReview The AnswerUse this when ChatGPT has already answered and the risk is accepting fluent wording before listing description quality, property facts and feature hierarchy, and local-compliance restraint is checked.SavePrepare HandoffUse this when the answer is close but needs to become a repeatable asset for a real estate agent, not a one-off chat result.

Work notes

Start from the real note, not a blank prompt

Current input: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Phrase shopping in write listing descriptions fails because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This write listing descriptions run should turn that note into a listing description. For write listing descriptions, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.
First move: Start by pasting the rough note, then replace the variables that control audience, source material, and the reviewer for listing description quality, property facts and feature hierarchy, and local-compliance restraint.
Who checks it: Keep the handoff honest by assigning one person to test the answer against the rough note and final audience.

Stop rule: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Keep after run: Save a short record of the original note, the prompt variables that changed the answer, the section that still needs listing description quality, property facts and feature hierarchy, and local-compliance restraint, and the final reason the accepted version can become listing description prompt pattern with source notes, constraints, and review checklist.

PrepareCollect ContextBring the rough case note: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.CopyBuild The AssetExpect copy options grouped by angle, audience, proof point, and revision note that explicitly separates source-based content from assumptions and ends with a review pass for listing description quality, property facts and feature hierarchy, and local-compliance restraint.GradeReview The AnswerCompare the answer against the original notes and mark every line that depends on source notes, examples, constraints, and reviewer judgment.SavePrepare HandoffCopy the external review checklist, record what changed, and save a version with reusable variables instead of private details.

Do not start if: Stop if the answer sounds polished but still cannot show the source notes behind property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Human check: Source review, write listing descriptions: the answer uses the supplied property facts, features, neighborhood context, photo notes, and compliance limits and does not fill missing facts with confident guesses.

Real note check

Check the answer against your note

This works best when the answer stays tied to the note you pasted, the question people search, and the person who can review it.

Question to compare: chatgpt prompts for real estate agents listing description

Open reference checks

Paste into ChatGPT: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Phrase shopping in write listing descriptions fails because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This write listing descriptions run should turn that note into a listing description. For write listing descriptions, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.
Question to compare: chatgpt prompts for real estate agents listing descriptionResult listing description real estate agents check: open the top results and record whether they solve the task, not only a prompt phrase.
Reference page: HUD Fair Housing Act overviewUsed for real estate prompts where property, neighborhood, buyer, seller, and listing language must avoid unsupported or discriminatory claims.
Who checks it: Keep the handoff honest by assigning one person to test the answer against the rough note and final audience.Inspect property facts, features, neighborhood context, photo notes, and compliance limits, the case note "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.", and any open proof around source notes, examples, constraints, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.

Use this listing descriptions page when real estate agents already have property facts, features, neighborhood context, photo notes, and compliance limits and need the answer to become a listing description, not a loose idea list. The prompt should ask for property facts, features, neighborhood context, photo notes, and compliance limits, the audience, the intended channel, and the constraints before it tries to format the result. listing descriptions artifact check: inspect listing copy map with fact-only feature notes before accepting the answer. Accept the answer only when listing description quality, property facts and feature hierarchy, and local-compliance restraint can be checked and the open questions are visible. Avoid unsupported claims about pricing, safety, schools, or investment outcomes. Before using the output, run the follow-up prompt and check the result against the real context for a buyer, seller, lead, or broker reviewer.

Real use plan for treating the prompt like a work note

0/12 checked

The plan starts with the rough note, then forces a check against listing description quality, property facts and feature hierarchy, and local-compliance restraint before a listing description reaches a buyer, seller, lead, or broker reviewer; that keeps the useful structure while making unsupported claims easy to reject.

Before copying

Paste the messy notes first: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.Name the real audience for a listing description: a buyer, seller, lead, or broker reviewer, plus the channel, deadline, or approval point.Add the non-negotiable constraint from this case: The prompt must use actual property facts and avoid protected-class or unsupported claims.Keep the task narrow by naming property facts, feature hierarchy, buyer appeal, and compliance-safe claims before asking for copy options grouped by angle, audience, proof point, and revision note.

After ChatGPT answers

Compare the answer against the original notes and mark every line that depends on source notes, examples, constraints, and reviewer judgment.Keep source-backed sections separate from assumptions so listing description quality, property facts and feature hierarchy, and local-compliance restraint can be checked quickly.Ask one follow-up only after the first answer proves it understood property facts, feature hierarchy, buyer appeal, and compliance-safe claims.Turn the accepted answer into listing description prompt pattern with source notes, constraints, and review checklist only after removing one-time names and details.

Reject the answer if

Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.Reject it if the output sounds polished but does not become a listing description.Reject it if avoid claims about safety, schools, investment return, or legal facts without source support is handled as a style note instead of a hard boundary.Reject it if the final description should be accurate, inviting, compliant, and easy to verify against the listing sheet. cannot be verified by a human reviewer.

Choose the next move

Start by turning the rough request into named fields before asking for a listing description.

Build The Asset

Use this when the notes are ready and the next useful output is copy options grouped by angle, audience, proof point, and revision note, not more brainstorming.

Open section

Do now: Copy the recommended prompt, replace the variables, and ask for a listing description with assumptions separated from source-backed details.
Bring first: Bring the task focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims. Add the channel, deadline, and any required sections.
Stop if: Stop if the first answer gives broad advice instead of a concrete a listing description.
Next check: Use the run sheet's review mode before sharing anything with a buyer, seller, lead, or broker reviewer.

Open prompt Prepare context Check answer

Before copying

Paste the messy notes first: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.
Name the real audience for a listing description: a buyer, seller, lead, or broker reviewer, plus the channel, deadline, or approval point.
Add the non-negotiable constraint from this case: The prompt must use actual property facts and avoid protected-class or unsupported claims.

Accept only if

Compare the answer against the original notes and mark every line that depends on source notes, examples, constraints, and reviewer judgment.
Keep source-backed sections separate from assumptions so listing description quality, property facts and feature hierarchy, and local-compliance restraint can be checked quickly.
Ask one follow-up only after the first answer proves it understood property facts, feature hierarchy, buyer appeal, and compliance-safe claims.

Reject when

Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.

Know when the answer is ready

Use this quick check before saving the answer, rerunning the prompt, or switching to a neighboring workflow.

Ready signal

Finish the run only when the answer turns "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." into copy options grouped by angle, audience, proof point, and revision note, keeps property facts, feature hierarchy, buyer appeal, and compliance-safe claims visible, and gives the person approving a listing description a clear accept, repair, or reject choice before a buyer, seller, lead, or broker reviewer sees it.

First run action

Open with the rough note property facts, features, neighborhood context, photo notes, and compliance limits, the intended a listing description, the audience, the stop rule "avoid claims about safety, schools, investment return, or legal facts without source support", and the proof needed for source notes, examples, constraints, and reviewer judgment.

Keep after run: Save a short record of the original note, the prompt variables that changed the answer, the section that still needs listing description quality, property facts and feature hierarchy, and local-compliance restraint, and the final reason the accepted version can become listing description prompt pattern with source notes, constraints, and review checklist.
Use or revise: the person approving a listing description should approve the output only if it can be traced back to property facts, features, neighborhood context, photo notes, and compliance limits, shows what is assumed, and does not turn source notes, examples, constraints, and reviewer judgment into a confident claim without review.
What makes this page different: This page can beat a short prompt list by tying the query "chatgpt prompts for real estate agents listing description" to a fillable prompt, a realistic case, an answer repair path, and a no-fake-metrics proof boundary instead of only listing prompt phrases.
Why this page exists: This route is worth keeping for the listing description query because write listing descriptions changes the source material, reviewer, output shape, and failure mode; sending the user to a nearby real estate agent page would hide property facts, feature hierarchy, buyer appeal, and compliance-safe claims and weaken the final a listing description.

Editor margin

Second pass before the answer becomes reusable

Source line

Editor margin source for write listing descriptions: "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." It is the sentence most likely to disappear when a smooth answer starts too quickly.

Reviewer voice

a working editor checking listing description quality, property facts and feature hierarchy, and local-compliance restraint reads the first ChatGPT answer beside the rough note and decides what survives. The pass is intentionally narrow: preserve the note, remove unsupported confidence, ask for the missing proof, then rewrite only the part that changes the decision. The check belongs before the prompt is saved as listing description prompt pattern with source notes, constraints, and review checklist.

Keep

the rough note "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit" as the visible source line for a listing description

Keep this because the rough note is the only part a real estate agent can compare against the answer when copy options grouped by angle, audience, proof point, and revision note starts to sound finished.

The accepted answer should repeat or clearly map back to "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." before it adds structure.

Cut

any confident claim about source notes, examples, constraints, and reviewer judgment that the pasted note does not prove

Cut it because the proof around source notes, examples, constraints, and reviewer judgment is the review risk for this page, and fluent wording can make an unsupported detail look approved.

If the source note does not show the fact, the answer should move it into a needs-checking line or remove it.

Ask

the missing audience, owner, or review detail needed before a buyer, seller, lead, or broker reviewer uses the answer

Ask before reuse because a listing description only helps a buyer, seller, lead, or broker reviewer when the channel, approval owner, and open proof are visible.

The next run should name the missing field instead of burying it inside a polished answer.

Rewrite

the first polished paragraph so it shows property facts, feature hierarchy, buyer appeal, and compliance-safe claims before tone improvements

Rewrite the opening because this task is about property facts, feature hierarchy, buyer appeal, and compliance-safe claims, not a general write listing descriptions answer that could fit any role page.

A reviewer should see property facts, feature hierarchy, buyer appeal, and compliance-safe claims in the first accepted section and again in the saved reuse rule.

Why this feels hand-edited

a working editor checking listing description quality, property facts and feature hierarchy, and local-compliance restraint leaves this margin pass because the page has to protect a real source note, not only offer another prompt. For real estate agents working on write listing descriptions, the human-feeling part is the specific tradeoff: keep "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.", cut unsupported certainty, ask for the missing owner, and rewrite the answer around property facts, feature hierarchy, buyer appeal, and compliance-safe claims. That proof trail makes the page feel edited rather than assembled from interchangeable blocks.

Run the margin pass

Run an editorial margin pass for this task. Source note: "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." Output being reviewed: [paste ChatGPT answer]. Mark four decisions: Keep the source-backed detail that should survive, Cut any unsupported claim about source notes, examples, constraints, and reviewer judgment, Ask the missing question that blocks a buyer, seller, lead, or broker reviewer from using the result, and Rewrite the section so property facts, feature hierarchy, buyer appeal, and compliance-safe claims stays visible before polish. End with one accept, repair, or reject decision and a reuse rule for listing description prompt pattern with source notes, constraints, and review checklist.

Task actions for the next useful move

Start by pasting the rough note, then replace the variables that control audience, source material, and the reviewer for listing description quality, property facts and feature hierarchy, and local-compliance restraint.

CollectCollect ContextBring the rough case note: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.CopyBuild The AssetExpect copy options grouped by angle, audience, proof point, and revision note that explicitly separates source-based content from assumptions and ends with a review pass for listing description quality, property facts and feature hierarchy, and local-compliance restraint.CheckReview The AnswerCompare the answer against the original notes and mark every line that depends on source notes, examples, constraints, and reviewer judgment.HandoffPrepare HandoffCopy the external review checklist, record what changed, and save a version with reusable variables instead of private details.

Wrong page ifThe user cannot provide property facts, features, neighborhood context, photo notes, and compliance limits and would need ChatGPT to invent the important facts.

Stay hereThe page is for the moment when real estate agents have enough notes to create a listing description, but still need a decision about property facts, feature hierarchy, buyer appeal, and compliance-safe claims. First move: Start by pasting the rough note, then replace the variables that control audience, source material, and the reviewer for listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Switch ifChatGPT Prompts for Real Estate AgentsReturn to the role guide to choose by situation, output, and reviewer.

Stop ifThe user cannot provide property facts, features, neighborhood context, photo notes, and compliance limits and would need ChatGPT to invent the important facts. The desired result is not a listing description or cannot be shaped as copy options grouped by angle, audience, proof point, and revision note.

Not forUsers who want ChatGPT to invent facts, credentials, numbers, or personal details. Situations where the output needs final approval from a qualified human before it reaches a buyer, seller, lead, or broker reviewer.

Before you use the answer, make the call

Who checks it: Before handoff, the reviewer comparing the answer with the pasted notes compares the answer with the rough case note for write listing descriptions and decides what can reach a buyer, seller, lead, or broker reviewer.
Check before using: Inspect property facts, features, neighborhood context, photo notes, and compliance limits, the case note "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.", and any open proof around source notes, examples, constraints, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.
What this changes: The user should leave judging readiness, not shopping for wording: does this a listing description show property facts, feature hierarchy, buyer appeal, and compliance-safe claims, name what came from property facts, features, neighborhood context, photo notes, and compliance limits, and give a buyer, seller, lead, or broker reviewer a clear next step?
Do next: The final description should be accurate, inviting, compliant, and easy to verify against the listing sheet. Then save only the repeatable fields, not the one-time case details, so the next run still asks for listing description quality, property facts and feature hierarchy, and local-compliance restraint.
Before saving for reuse: Before reusing the answer, keep any search, traffic, ranking, or popularity claim out of the final asset unless someone can point to Search Console evidence or other real search data after publishing for "chatgpt prompts for real estate agents listing description" and record where it came from.

Working case file: Write Listing Descriptions working case for Real Estate Agents

This is the work moment before a real estate agent should copy the prompt. The user has enough material to start, but not enough to trust a smooth answer unless the prompt keeps property facts, features, neighborhood context, photo notes, and compliance limits, copy options grouped by angle, audience, proof point, and revision note, and the person approving a listing description in the same run.

Rough note

An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access. The rough note says: "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." The desired result is a listing description for a buyer, seller, lead, or broker reviewer.

Constraint to keep visible

The answer has to protect property facts, feature hierarchy, buyer appeal, and compliance-safe claims before it improves wording. Carry this rule into every section: avoid claims about safety, schools, investment return, or legal facts without source support.

What the user brought

The supplied case is "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.", so the answer should begin from the user's actual wording and not from broad write listing descriptions advice.

The finished a listing description should point back to property facts, features, neighborhood context, photo notes, and compliance limits and show how property facts, feature hierarchy, buyer appeal, and compliance-safe claims changed the answer.

What is still missing

The model should ask for audience, channel, approval owner, and any proof needed for source notes, examples, constraints, and reviewer judgment before it treats the result as usable.

Missing inputs belong in a needs-checking line, not inside polished wording that a buyer, seller, lead, or broker reviewer might treat as settled.

Who accepts the answer

the person approving a listing description should inspect listing description quality, property facts and feature hierarchy, and local-compliance restraint, compare the answer with the rough note, and decide whether the output is ready, repairable, or too thin.

The page should leave a visible owner for the final check instead of implying that ChatGPT approval is enough.

What gets saved

The reusable version should keep variables for source notes, audience, reviewer, proof need, stop rule, and property facts, feature hierarchy, buyer appeal, and compliance-safe claims.

One-time details should be removed only after the accepted answer proves that copy options grouped by angle, audience, proof point, and revision note works for this case.

Before copying

Can the user point to the exact property facts, features, neighborhood context, photo notes, and compliance limits ChatGPT is allowed to use?
Is property facts, feature hierarchy, buyer appeal, and compliance-safe claims visible before the prompt asks for a listing description?
Has the user named the reviewer who checks listing description quality, property facts and feature hierarchy, and local-compliance restraint?
Is there a stop rule for unsupported claims about source notes, examples, constraints, and reviewer judgment?

Checks before sharing

Compare the first answer with "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." and mark any section that invents context.
Check whether the output is shaped as copy options grouped by angle, audience, proof point, and revision note, not a general explanation.
Move uncertain claims into a needs-checking block before sharing the answer with a buyer, seller, lead, or broker reviewer.
Save the pattern as listing description prompt pattern with source notes, constraints, and review checklist only after private or one-time details become variables.

Run this case first

Use this case file before writing. Start from this rough note: "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." Build a listing description as copy options grouped by angle, audience, proof point, and revision note. Keep property facts, feature hierarchy, buyer appeal, and compliance-safe claims visible, separate supplied facts from assumptions, ask for missing proof around source notes, examples, constraints, and reviewer judgment, name the person approving a listing description as the checker, and stop before using any claim that the source notes do not support.

Ready means the result can move to a buyer, seller, lead, or broker reviewer with supplied notes, assumptions, and checks still separated. The accepted version should tell a buyer, seller, lead, or broker reviewer what is ready, what needs checking, and which fields the next user must replace before rerunning the prompt.

Input triage before running ChatGPT

Which problem is most likely to break this write listing descriptions run before a buyer, seller, lead, or broker reviewer can use it?

Selected issue

Missing context

Build context

Symptom: Write Listing Descriptions starts from a rough note like "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." but the audience, decision, or approval point is still implied.
Ask now: What does a buyer, seller, lead, or broker reviewer already know, what source notes are available, and what must the final a listing description decide?
Do next: Start by rewriting the rough note into named fields before asking for copy options grouped by angle, audience, proof point, and revision note, then confirm the reviewer can inspect each field.
Prompt move: Before writing, ask me up to four questions needed to produce copy options grouped by angle, audience, proof point, and revision note; do not fill gaps with assumptions.
Stop if: Stop if the answer sounds polished but still cannot show the source notes behind property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Who checks it: a buyer, seller, lead, or broker reviewer

Build context Readiness check

Notes to save before reusing this prompt

Sort the rough note "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." before running write listing descriptions in a public listing where facts, fair-housing boundaries, and buyer expectations meet. This note sheet tells ChatGPT what it may use, what it must label, and which part the reviewer comparing the answer with the original note checks before a buyer, seller, lead, or broker reviewer sees listing copy map with fact-only feature notes. For real estate agents listing description, current source notes should come first; stale or partial inputs should trigger a fresh listing copy map with fact-only feature notes pass instead of another saved answer.

Known material to preserve

Capture: Capture the concrete case first: An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access. The note says "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." and the requested asset is listing copy map with fact-only feature notes. For real estate agents listing description, current source notes should come first; stale or partial inputs should trigger a fresh listing copy map with fact-only feature notes pass instead of another saved answer.
Keep: Keep the facts that directly affect copy options grouped by angle, audience, proof point, and revision note, especially the audience, task focus, channel, and any details already present in property facts, features, neighborhood context, photo notes, and compliance limits.
Verify: Verify that every useful line in the answer can point back to the rough note or to property facts, features, neighborhood context, photo notes, and compliance limits.
Prompt direction: Tell ChatGPT to use only listed facts for the first pass and to put any extra idea in a needs-checking line.
Who checks it: the reviewer comparing the answer with the original note checks whether the answer still reflects listing description quality, property facts and feature hierarchy, and local-compliance restraint after the first pass.
If skipped: If this row is skipped, a listing description can sound specific while drifting into generic write listing descriptions advice.

Missing inputs to ask about

Capture: List what the user did not provide but the answer may need: missing audience detail, missing proof around source notes, examples, constraints, and reviewer judgment, or an approval step for a buyer, seller, lead, or broker reviewer.
Keep: Keep assumptions outside the usable sections until the user confirms them or chooses a safer fallback.
Verify: Check whether the answer names what is unknown before it recommends wording, order, or next steps.
Prompt direction: Ask ChatGPT to return a short assumption list before writing any final copy or checklist.
Who checks it: the reviewer comparing the answer with the original note decides which assumptions are acceptable and which ones need another user answer.
If skipped: If assumptions are hidden, the answer may pass a style check while failing the real decision about property facts, feature hierarchy, buyer appeal, and compliance-safe claims.

Non-negotiable constraints

Capture: Record the rule from this case: The prompt must use actual property facts and avoid protected-class or unsupported claims. Also include avoid claims about safety, schools, investment return, or legal facts without source support and this field friction before the model writes: listing copy can overclaim property, neighborhood, or market facts. Failure pattern for listing description with real estate agents: the listing description can sound polished while listing copy can overclaim property, neighborhood, or market facts, so the page should make that miss easy to catch.
Keep: Keep the constraint near the requested format so it governs the whole copy options grouped by angle, audience, proof point, and revision note, not only the final paragraph.
Verify: Check whether the answer obeys the constraint even when it would be easier to produce a smoother or broader response.
Prompt direction: Tell ChatGPT to stop and ask before continuing if the constraint conflicts with the requested output.
Who checks it: the reviewer comparing the answer with the original note checks the constraint before approving any handoff to a buyer, seller, lead, or broker reviewer.
If skipped: If this row is skipped, the model may produce a fluent answer that the user cannot safely use.

Case-only material to remove

Capture: Mark names, private identifiers, account details, student or customer records, confidential strategy, and one-time case details before they enter the prompt.
Keep: Keep summaries that preserve meaning but remove details that should not travel into a reusable prompt.
Verify: Check whether the answer repeats private or one-time information that should have stayed outside the saved version.
Prompt direction: Ask ChatGPT to replace private details with role-safe descriptions and to flag anything it cannot safely generalize.
Who checks it: the reviewer comparing the answer with the original note confirms that the final a listing description can be shared in the intended channel.
If skipped: If this row is skipped, the page helps the user copy faster but may teach a bad reuse habit.

Repeatable prompt controls

Capture: Name the fields that should change next time: source notes, audience, output format, proof needed for source notes, examples, constraints, and reviewer judgment, reviewer, and stop rule.
Keep: Keep property facts, feature hierarchy, buyer appeal, and compliance-safe claims, listing description quality, property facts and feature hierarchy, and local-compliance restraint, and listing copy map with fact-only feature notes as required fields so the saved prompt does not collapse into a generic role prompt. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible.
Verify: Check whether the reusable version still asks for the facts that made this case work, instead of saving the finished wording alone.
Prompt direction: Tell ChatGPT to return a reusable prompt with variables and a reject-if rule after the human accepts the current answer.
Who checks it: the reviewer comparing the answer with the original note signs off only when private details are removed and the next user can fill the variables without guessing.
If skipped: If this row is skipped, the user may save polished wording instead of a repeatable listing description prompt pattern with source notes, constraints, and review checklist.

Copy these saved notes with the prompt only after the real estate agent can point to the supplied facts, the uncertain parts, the hard limit, the reusable fields for property facts, feature hierarchy, buyer appeal, and compliance-safe claims, and the place where listing copy can overclaim property, neighborhood, or market facts. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible. Outside proof for listing description with real estate agents: an independent resource must mention the listing description page visibly before listing copy map with fact-only feature notes becomes an authority claim.

Iteration loop: run the prompt as a working thread

Write Listing Descriptions works best as a short conversation, not as one copy action. Start from the rough note "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.", then ask ChatGPT to write, question, challenge, and hand off listing copy map with fact-only feature notes without hiding source notes, examples, constraints, and reviewer judgment. For real estate agents listing description, current source notes should come first; stale or partial inputs should trigger a fresh listing copy map with fact-only feature notes pass instead of another saved answer.

Thread goal

Thread goal for real estate agent: turn the rough case from An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access. into copy options grouped by angle, audience, proof point, and revision note for a buyer, seller, lead, or broker reviewer, while the reviewer accountable for listing description quality, property facts and feature hierarchy, and local-compliance restraint can still inspect listing description quality, property facts and feature hierarchy, and local-compliance restraint, property facts, feature hierarchy, buyer appeal, and compliance-safe claims, unsupported assumptions, and the friction that listing copy can overclaim property, neighborhood, or market facts. Failure pattern for listing description with real estate agents: the listing description can sound polished while listing copy can overclaim property, neighborhood, or market facts, so the page should make that miss easy to catch.

Write Listing Descriptions is finished only when the handoff names what is ready, what still needs checking, and which fields become variables next time. The loop is stronger than a one-shot prompt because it makes the model show its first version, missing context, challenge, and reusable handoff before the real estate agent treats listing copy map with fact-only feature notes as finished. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible.

1
First run
Use this first when the source note is messy but concrete enough to produce a reviewable a listing description.
```
Write Listing Descriptions first run: use the rough note "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." from An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access.; build a listing description as copy options grouped by angle, audience, proof point, and revision note; rely on supplied facts for the main answer, label assumptions, keep property facts, feature hierarchy, buyer appeal, and compliance-safe claims visible, and end with the proof still needed for source notes, examples, constraints, and reviewer judgment.
```
Keep
Keep the exact source note, the requested output shape, and any line that directly supports property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Accept if
Accept the first answer only if it separates source-backed details from assumptions and gives the reviewer accountable for listing description quality, property facts and feature hierarchy, and local-compliance restraint something concrete to inspect.
Stop if
Stop if the answer invents missing context, treats source notes, examples, constraints, and reviewer judgment as proven, or drifts into general write listing descriptions advice.
2
Gap fill
Use this after the first answer when the shape is useful but the model skipped questions that block real use.
```
Write Listing Descriptions gap fill: compare the first answer with the rough note already in this thread; name the missing inputs that prevent a buyer, seller, lead, or broker reviewer from using the result; ask up to five questions grouped by audience, source proof, channel, reviewer, and reuse field, then say which part can continue with a safe fallback.
```
Keep
Keep any section that maps to property facts, features, neighborhood context, photo notes, and compliance limits; move guesses into open questions instead of deleting the whole answer.
Accept if
Accept this turn only if the missing questions would help a real estate agent make a clearer decision before rerunning or revising.
Stop if
Stop if the model asks generic questions that do not affect copy options grouped by angle, audience, proof point, and revision note, listing description quality, property facts and feature hierarchy, and local-compliance restraint, or the final handoff.
3
Skeptic pass
Use this before sharing the answer, especially when it sounds polished enough to hide weak evidence.
```
Write Listing Descriptions skeptic pass: compare the current answer with the rough note already in this thread; mark unsupported claims, unclear owners, privacy issues, and weak spots around source notes, examples, constraints, and reviewer judgment; give each issue a repair sentence that keeps property facts, feature hierarchy, buyer appeal, and compliance-safe claims visible without adding new facts.
```
Keep
Keep the usable structure from the first answer, but require every claim and recommendation to survive the skeptic pass.
Accept if
Accept this turn only if it gives repair instructions that the reviewer accountable for listing description quality, property facts and feature hierarchy, and local-compliance restraint can apply without rewriting the whole asset from scratch.
Stop if
Stop if the critique only says the answer is good or bad without naming the exact line, risk, and repair move.
4
Handoff
Use this after the answer survives the gap fill and skeptic pass and is ready to become a working asset.
```
Write Listing Descriptions handoff: prepare the accepted a listing description, a needs-checking block for source notes, examples, constraints, and reviewer judgment, a reviewer note for the reviewer accountable for listing description quality, property facts and feature hierarchy, and local-compliance restraint, and a reusable version with variables for source notes, audience, output format, proof need, stop rule, and property facts, feature hierarchy, buyer appeal, and compliance-safe claims; remove one-time private details before saving.
```
Keep
Keep the accepted wording, the repair decisions, and the variables that make listing description prompt pattern with source notes, constraints, and review checklist safe to rerun.
Accept if
Accept the handoff only if a buyer, seller, lead, or broker reviewer can tell what is ready, what needs review, and what must be replaced next time.
Stop if
Stop if the final version saves polished case details instead of a reusable prompt structure with visible boundaries.

Prompt readiness check before you copy

Use this quick pass to decide whether to collect more context, build a context pack, or run the prompt and grade the answer.

0/6 ready

Source notes readyNeed MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Phrase shopping in write listing descriptions fails because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This write listing descriptions run should turn that note into a listing description. For write listing descriptions, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.Audience or recipient knownReal Estate Agents who have real notes or context and need a structured first version of a listing description.Constraints and no-go rules clearAvoid unsupported claims about pricing, safety, schools, or investment outcomes. Ask ChatGPT to label assumptions and verification needs before using a listing description.Facts to verify listedListing Description reader check: who will read or approve this a listing description, and what do they already know? Listing Description source sort: which lines in the rough note are facts, preferences, constraints, or open questions?Checker is namedKeep the handoff honest by assigning one person to test the answer against the rough note and final audience.Reuse rule clearReuse listing description only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a listing description, and the review rule for property facts, feature hierarchy, buyer appeal, and compliance-safe claims still appears in the reusable prompt. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible.

Do next

Collect context first

The prompt can run, but the answer will likely fill gaps with assumptions. Start by collecting notes, constraints, and the person who will check it.

Use this prompt when: Real Estate Agents who have real notes or context and need a structured first version of a listing description.
Wait if: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Who checks it: Keep the handoff honest by assigning one person to test the answer against the rough note and final audience.
Reuse rule: Reuse listing description only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a listing description, and the review rule for property facts, feature hierarchy, buyer appeal, and compliance-safe claims still appears in the reusable prompt. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible.

Collect context Open prompt Context pack Output grader

Session handoff: finish the run without losing the thread

Track the four decisions that turn a copied prompt into a usable work session.

0/4 steps

Context readyBuild a context pack before copying anything.Open stepPrompt runRun the recommended prompt with the prepared context.Open stepAnswer checkedGrade the answer against the task checks and repair weak sections.Open stepReuse decisionDecide whether to save the run, rerun it, or discard it.Open step

Next action

Collect working context

Start by getting source notes, constraints, the person who checks it, and the stop rule into one place.

Working note: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Phrase shopping in write listing descriptions fails because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This write listing descriptions run should turn that note into a listing description. For write listing descriptions, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.
Who checks it: Keep the handoff honest by assigning one person to test the answer against the rough note and final audience.
Stop rule: Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Reuse choice: Reuse listing description only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a listing description, and the review rule for property facts, feature hierarchy, buyer appeal, and compliance-safe claims still appears in the reusable prompt. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible.

Open next step Prompt Context Grade

Work note: what the rough note changes

Use this when the answer must carry the original note, the missing context, and the review decision into the final prompt run.

Original working note

A rough listing description note comes in: "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." is the rough request. Before reusing listing description, the usable version reads as a listing description, keeps property facts, feature hierarchy, buyer appeal, and compliance-safe claims visible, names the checker, and protects this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.

Received note: Received note for Real Estate Agents Write Listing Descriptions: "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." arrives as the source note inside a public listing where facts, fair-housing boundaries, and buyer expectations meet, with The prompt must use actual property facts and avoid protected-class or unsupported claims. as the first human concern and listing copy map with fact-only feature notes as the target artifact.
Question before run: Before the first run, ask which part of "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." is fixed source material and which part is only preference, guesswork, or a missing approval point for the person who will approve a listing description.
First answer flaw: First answer flaw for Real Estate Agents Write Listing Descriptions: the first answer may sound polished while it drops the rough-note constraint, skips the reviewer, and turns source notes, examples, constraints, and reviewer judgment into an implied claim instead of a checkable line.
Human edit: Human edit for Real Estate Agents Write Listing Descriptions: rewrite the answer so each useful section names what came from the note, what still needs source notes, examples, constraints, and reviewer judgment, and where the person who will approve a listing description should stop before sharing it; the editor also has to replace polished filler with source-backed lines inside a listing description; the edit has to preserve "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." and leave listing copy map with fact-only feature notes ready for a reviewer, not just prettier.
Reusable field: Reusable field for Real Estate Agents Write Listing Descriptions: save the reusable fields as source note, audience, output shape, reviewer, stop rule, and property facts, feature hierarchy, buyer appeal, and compliance-safe claims; do not save private details or one-time facts as fixed wording. Keep the field set alert to this repeat risk: listing copy can overclaim property, neighborhood, or market facts.

Questions before reuse

Listing Description reader check: who will read or approve this a listing description, and what do they already know?
Listing Description source sort: which lines in the rough note are facts, preferences, constraints, or open questions?
Listing Description blank rule: what should stay blank or flagged if source notes, examples, constraints, and reviewer judgment is missing?

Who checks it

Keep the handoff honest by assigning one person to test the answer against the rough note and final audience.

Listing Description source note: treat "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." as the factual base, not decorative background; the next usable asset is listing copy map with fact-only feature notes.
Listing Description evidence check: mark any section where source notes, examples, constraints, and reviewer judgment is assumed instead of shown, especially when listing copy can overclaim property, neighborhood, or market facts.
Listing Description scope check: keep the answer on property facts, feature hierarchy, buyer appeal, and compliance-safe claims; do not drift away from a public listing where facts, fair-housing boundaries, and buyer expectations meet.
Listing Description final polish: rewrite final wording only after listing description quality, property facts and feature hierarchy, and local-compliance restraint is clear enough for the buyer, seller, lead, or broker reviewer owner, then replace polished filler with source-backed lines inside a listing description.
Listing Description freshness rule: For real estate agents listing description, current source notes should come first; stale or partial inputs should trigger a fresh listing copy map with fact-only feature notes pass instead of another saved answer.

Usable output

A usable listing description handoff would return copy options grouped by angle, audience, proof point, and revision note; separate supplied notes from assumptions, name the review owner, prepare listing copy map with fact-only feature notes, and make the human pass focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Save this noteRough note that changes the prompt: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Task-specific source material: property facts, features, neighborhood context, photo notes, and compliance limits Human check to keep visible: listing description quality, property facts and feature hierarchy, and local-compliance restraint

Stop hereReject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.

Save for reuseReuse listing description only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a listing description, and the review rule for property facts, feature hierarchy, buyer appeal, and compliance-safe claims still appears in the reusable prompt. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible.

Build context pack Check output Open work sample

Prompt run from pasted notes

Use this pass to see what should happen between the rough note and the answer that is safe enough to review.

Pasted notes

Real Estate Agents bring write listing descriptions source notes: An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access. The source says "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." The answer needs to become listing copy map with fact-only feature notes for a buyer, seller, lead, or broker reviewer; the run lives in a public listing where facts, fair-housing boundaries, and buyer expectations meet and has to respect this rule before any wording polish: The prompt must use actual property facts and avoid protected-class or unsupported claims.

Why this input is messy

This write listing descriptions input needs care because the note carries facts, preferences, limits, and open approval points in one line; a quick answer can smooth over source notes, examples, constraints, and reviewer judgment, miss property facts, feature hierarchy, buyer appeal, and compliance-safe claims, or make a listing description look ready before the person approving a listing description checks it, especially when listing copy can overclaim property, neighborhood, or market facts.

First prompt move

real estate agent should start write listing descriptions by asking ChatGPT to ask ChatGPT to restate the source notes in three buckets before writing: facts it can use, assumptions it must not hide, and missing points that affect source notes, examples, constraints, and reviewer judgment; this is a context pass before polish because copy options grouped by angle, audience, proof point, and revision note has to stay traceable to the original note.

Questions ChatGPT should ask

Reader detail in write listing descriptions: who will read this a listing description, and what do they already know?
Source detail in write listing descriptions: which note details are verified facts, and which parts still need source notes, examples, constraints, and reviewer judgment?
Constraint detail in write listing descriptions: what tone, length, channel, or approval rule matters before the answer reaches a buyer, seller, lead, or broker reviewer?
Reuse detail in write listing descriptions: which person will inspect listing description quality, property facts and feature hierarchy, and local-compliance restraint, and what would make the answer unsafe to reuse?

Usable answer shape

The write listing descriptions answer should return copy options grouped by angle, audience, proof point, and revision note, separate source-backed sections from assumptions and open questions, show how property facts, feature hierarchy, buyer appeal, and compliance-safe claims shaped the result, name the person approving a listing description, and end with a short check for listing description quality, property facts and feature hierarchy, and local-compliance restraint before the answer is shared or saved.

Human revision

real estate agent should revise write listing descriptions by keeping the structure that saved time, replace polished filler with source-backed lines inside a listing description, remove private or one-time information, and rewrite the final wording for a buyer, seller, lead, or broker reviewer; compare the answer with "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." and make sure The final description should be accurate, inviting, compliant, and easy to verify against the listing sheet.

Save or discard

Save the write listing descriptions run only when the note, output shape, checker, listing copy map with fact-only feature notes, and reuse rule stay visible; rerun or discard the answer when it could fit another real estate agent task without changing the source notes, or when source notes, examples, constraints, and reviewer judgment is implied but not checkable.

Run prompt Grade answer Repair answer

Why this page is not interchangeable

Work moment

The page is for the moment when real estate agents have enough notes to create a listing description, but still need a decision about property facts, feature hierarchy, buyer appeal, and compliance-safe claims.

Why this page

Do first

Next best workflow

ChatGPT Prompts for Real Estate AgentsReturn to the role guide to choose by situation, output, and reviewer.

What to look for

Rough note that changes the prompt: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.
Task-specific source material: property facts, features, neighborhood context, photo notes, and compliance limits
Human check to keep visible: listing description quality, property facts and feature hierarchy, and local-compliance restraint
Evidence pressure point: source notes, examples, constraints, and reviewer judgment

Wrong page if

The user cannot provide property facts, features, neighborhood context, photo notes, and compliance limits and would need ChatGPT to invent the important facts.
The desired result is not a listing description or cannot be shaped as copy options grouped by angle, audience, proof point, and revision note.
The task would be safer on ChatGPT Prompts for Real Estate Agents because the main decision is closer to that workflow.

Nearby workflow differences

Use this when the page looks close, but the thing you need to make or the person checking it is different.

Write buyer emails: Use this page
Stay with ChatGPT Prompts for Real Estate Agents to Write Listing Descriptions when your notes already include this check: Task-specific source material: property facts, features, neighborhood context, photo notes, and compliance limits.; Switch instead
Switch to Write buyer emails when the thing you need to make or the person checking it matches that workflow: Useful next step when this workflow needs a related real estate agents output or review pass.; Keep separate
Keep the pages separate if The user cannot provide property facts, features, neighborhood context, photo notes, and compliance limits and would need ChatGPT to invent the important facts.
Write seller scripts: Use this page
Stay with ChatGPT Prompts for Real Estate Agents to Write Listing Descriptions when your notes already include this check: Human check to keep visible: listing description quality, property facts and feature hierarchy, and local-compliance restraint.; Switch instead
Switch to Write seller scripts when the thing you need to make or the person checking it matches that workflow: Useful next step when this workflow needs a related real estate agents output or review pass.; Keep separate
Keep the pages separate if The desired result is not a listing description or cannot be shaped as copy options grouped by angle, audience, proof point, and revision note.
Follow up after open houses: Use this page
Stay with ChatGPT Prompts for Real Estate Agents to Write Listing Descriptions when your notes already include this check: Evidence pressure point: source notes, examples, constraints, and reviewer judgment.; Switch instead
Switch to Follow up after open houses when the thing you need to make or the person checking it matches that workflow: Useful next step when this workflow needs a related real estate agents output or review pass.; Keep separate
Keep the pages separate if The task would be safer on ChatGPT Prompts for Real Estate Agents because the main decision is closer to that workflow.

Run the page by work state

Start by turning the rough request into named fields before asking for a listing description.

Build The Asset

Use this when the notes are ready and the next useful output is copy options grouped by angle, audience, proof point, and revision note, not more brainstorming.

Open section

Do now: Copy the recommended prompt, replace the variables, and ask for a listing description with assumptions separated from source-backed details.
Bring: Bring the task focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims. Add the channel, deadline, and any required sections.
Stop if: Stop if the first answer gives broad advice instead of a concrete a listing description.
Next check: Use the run sheet's review mode before sharing anything with a buyer, seller, lead, or broker reviewer.

Bring this

Bring property facts, features, neighborhood context, photo notes, and compliance limits; add the reviewer, the audience, and the boundary from this case: The prompt must use actual property facts and avoid protected-class or unsupported claims.

Reusable handoff

A usable handoff is copy options grouped by angle, audience, proof point, and revision note with assumptions, source-backed sections, and a reviewer note for listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Reality checks

Does the page-specific note "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." change the prompt, or could this still fit another task unchanged?
Can the reviewer check listing description quality, property facts and feature hierarchy, and local-compliance restraint without asking ChatGPT to invent missing facts?
Does the answer become a listing description, or does it stay at broad write listing descriptions advice?
Would a buyer, seller, lead, or broker reviewer know what was provided, what was assumed, and what still needs review?

Prompt path by where the work is stuck

advanced

Write listing descriptions Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become a listing description.

Use this when: Use before asking ChatGPT for write listing descriptions so the model has enough task-specific context.
When this fits: Turn property facts, features, neighborhood context, photo notes, and compliance limits into a listing description for a buyer, seller, lead, or broker reviewer.
Do next: Compare the answer against the original notes and mark every line that depends on source notes, examples, constraints, and reviewer judgment.

Open this prompt card

Context pack before copying

0/8

Source notes are availableAudience or recipient is namedConstraints are explicitFacts to verify are listedChecker is named

Working notesConstraintsWho checks it

Ready to paste

Context brief for the next prompt

Context pack for Real Estate Agents to Write Listing Descriptions

Goal: Find a copyable prompt workbench that helps real estate agents write listing descriptions with the right source material, review lens, example, and follow-up prompts.
Working scenario: An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access. The write listing descriptions work happens inside a public listing where facts, fair-housing boundaries, and buyer expectations meet. For real estate agents listing description, current source notes should come first; stale or partial inputs should trigger a fresh listing copy map with fact-only feature notes pass instead of another saved answer. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible. For write listing descriptions, those constraints decide what the answer is allowed to do; without them, ChatGPT can sound finished while skipping the detail a real estate agent checks first.

What I know:
Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Phrase shopping in write listing descriptions fails because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This write listing descriptions run should turn that note into a listing description. For write listing descriptions, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.

Constraints and no-go rules:
Avoid unsupported claims about pricing, safety, schools, or investment outcomes. Ask ChatGPT to label assumptions and verification needs before using a listing description. Do not paste private names, identifiers, account details, student records, customer records, or confidential strategy when a summarized version is enough.

Who checks it:
Keep the handoff honest by assigning one person to test the answer against the rough note and final audience.

Readiness checks:
- [ ] Source notes are available
- [ ] Audience or recipient is named
- [ ] Constraints are explicit
- [ ] Facts to verify are listed
- [ ] Checker is named

Ask ChatGPT to request missing context before writing. Keep assumptions separate from source-based claims.

Output grader before reuse

0/5

Paste ChatGPT output

0 words checked against Keep the handoff honest by assigning one person to test the answer against the rough note and final audience.

Source review, write listing descriptions: the answer uses the supplied property facts, features, neighborhood context, photo notes, and compliance limits and does not fill missing facts with confident guesses.Output shape, write listing descriptions: the result clearly becomes a listing description, not broad advice about the task.Handoff clarity, write listing descriptions: the answer names missing inputs and the next human check for listing description quality, property facts and feature hierarchy, and local-compliance restraint.Audience fit, write listing descriptions: the result works for a buyer, seller, lead, or broker reviewer, including channel, tone, length, and decision context.Risk boundary, write listing descriptions: the final version respects avoid claims about safety, schools, investment return, or legal facts without source support.

Needs another review pass

a listing description final pass: keep the useful structure, then replace polished filler with source-backed lines inside a listing description; readiness means a buyer, seller, lead, or broker reviewer can see what was provided, what was assumed, why listing copy can overclaim property, neighborhood, or market facts, and what still needs review.

Task-specific output diagnosis

Paste the first Write Listing Descriptions answer and compare it with "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." before checking style. A useful real estate agent output must prove it belongs to this page by keeping property facts, feature hierarchy, buyer appeal, and compliance-safe claims, copy options grouped by angle, audience, proof point, and revision note, and the task reviewer visible.

Pass when

The answer uses "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." as the controlling case, not as decoration, and turns it into copy options grouped by angle, audience, proof point, and revision note with property facts, feature hierarchy, buyer appeal, and compliance-safe claims still visible.
The answer shows which lines come from "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." and which lines remain assumptions before a buyer, seller, lead, or broker reviewer sees the listing description.
The answer gives the task reviewer a clear check tied to "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.", especially the point where source notes, examples, constraints, and reviewer judgment cannot be treated as proven.
The answer can become listing description prompt pattern with source notes, constraints, and review checklist only after the one-time facts in "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." are replaced with variables and the stop rule stays attached.

False pass

It sounds polished but never quotes or preserves the specific case in "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.", so the write listing descriptions output could fit another page.
It gives a generic next step while hiding property facts, feature hierarchy, buyer appeal, and compliance-safe claims, which makes the answer feel useful before it can support the real a listing description.
It skips the task reviewer or buries the review check, so the user cannot tell who should approve the answer before reuse.
It could fit a neighboring workflow because the response hides copy options grouped by angle, audience, proof point, and revision note, source notes, examples, constraints, and reviewer judgment, or the source material that makes this write listing descriptions page different.

Repair next

Rewrite the opening around "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." and keep the first sentence tied to property facts, feature hierarchy, buyer appeal, and compliance-safe claims before improving tone or length.
Add a needs-checking block for source notes, examples, constraints, and reviewer judgment, then separate supplied facts from assumptions before returning copy options grouped by angle, audience, proof point, and revision note.
Mark the line the task reviewer must inspect for listing description quality, property facts and feature hierarchy, and local-compliance restraint, and move unsupported claims out of the usable answer.
Replace one-time details with variables for the saved listing description prompt pattern with source notes, constraints, and review checklist, then rerun only the section that failed the write listing descriptions check.

Red flags

Evidence issue, write listing descriptions: the answer invents or overstates source notes, examples, constraints, and reviewer judgment.
Task drift, write listing descriptions: it ignores property facts, feature hierarchy, buyer appeal, and compliance-safe claims and moves into a neighboring workflow.
Readiness gap, write listing descriptions: it sounds complete while leaving listing description quality, property facts and feature hierarchy, and local-compliance restraint impossible to verify.
Privacy issue, write listing descriptions: it includes details that should have been summarized or removed.
Generic output, write listing descriptions: it produces a broad template that could fit any task in the role.

Answer repair for replies that sound right but are not ready

Weak answer pattern

A rushed Real Estate Agents Write Listing Descriptions pass copies a line like "Here is a polished version based on your notes It covers the main points, keeps a professional tone, and adds a useful next step" and then moves on. Write Listing Descriptions failure to avoid for real estate agent: it also leaves no place for assumptions, missing facts, or a reviewer note; the actual note to protect is Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.

Why it fails

Write Listing Descriptions repair note: the answer looks confident because it uses smooth wording, but it never proves where the key claims came from The next pass must bring back property facts, feature hierarchy, buyer appeal, and compliance-safe claims, show which parts depend on source notes, examples, constraints, and reviewer judgment, make the person approving a listing description visible before a buyer, seller, lead, or broker reviewer sees the result, and handle the real friction: listing copy can overclaim property, neighborhood, or market facts.

Trace the rough note

Problem: The answer mentions a listing description but does not reflect the concrete case: An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access.
Repair: Rewrite the first section around the user note, then mark which details came from the note, which details still need confirmation, and where listing copy map with fact-only feature notes changes the output.

Name the reviewer

Problem: The answer can move forward without anyone checking listing description quality, property facts and feature hierarchy, and local-compliance restraint.
Repair: Add a reviewer line for the person approving a listing description, plus one question that must be answered before the result is shared.

Protect the evidence

Problem: The answer can imply source notes, examples, constraints, and reviewer judgment even when the source notes do not support it.
Repair: Keep unsupported claims in a separate needs-checking block and remove any claim the user cannot verify.

Keep the task narrow

Problem: The response can drift from write listing descriptions into broad advice that does not produce copy options grouped by angle, audience, proof point, and revision note.
Repair: Force the final answer back into copy options grouped by angle, audience, proof point, and revision note, keep property facts, feature hierarchy, buyer appeal, and compliance-safe claims as the main decision point, and replace polished filler with source-backed lines inside a listing description.

Human-edited direction

Human Write Listing Descriptions revision for Real Estate Agents: start with the actual case, name the audience, return copy options grouped by angle, audience, proof point, and revision note, keep supplied notes, assumptions, and missing checks separate, then replace polished filler with source-backed lines inside a listing description, tell a buyer, seller, lead, or broker reviewer what is ready to use, what the person approving a listing description must verify, and how the answer becomes listing description prompt pattern with source notes, constraints, and review checklist without private or one-time details.

Rerun prompt

Rerun Real Estate Agents Write Listing Descriptions: repair this write listing descriptions answer, keep the result focused on property facts, feature hierarchy, buyer appeal, and compliance-safe claims, return copy options grouped by angle, audience, proof point, and revision note, put unsupported claims about source notes, examples, constraints, and reviewer judgment in a needs-checking block, name the reviewer as the person approving a listing description, protect this boundary "avoid claims about safety, schools, investment return, or legal facts without source support", and use only these source notes: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.

Accept when

The answer visibly uses the rough note instead of generic write listing descriptions advice.
The result is shaped as copy options grouped by angle, audience, proof point, and revision note and can be checked by the person approving a listing description.
Any uncertain point about source notes, examples, constraints, and reviewer judgment is separated from the usable parts.
The reusable version keeps property facts, feature hierarchy, buyer appeal, and compliance-safe claims and removes one-time or private details.

Reject when

The answer could fit another real estate agent task without changing more than the title.
The response sounds polished but cannot show where the key claims came from.
The result skips listing description quality, property facts and feature hierarchy, and local-compliance restraint or hides who should approve it.
The answer asks the user to trust the model instead of checking the source notes.

Start from the user's actual notes

Search intent angle

Agents need listing descriptions that are specific, compliant, and grounded in property facts. For write listing descriptions, the page has to answer a agents write listing descriptions need where listing copy can overclaim property, neighborhood, or market facts. Search edge for listing description with real estate agents: show listing copy map with fact-only feature notes, a human review path for a listing description, and the task-specific reason the page deserves the query. Outside proof for listing description with real estate agents: an independent resource must mention the listing description page visibly before listing copy map with fact-only feature notes becomes an authority claim. For a listing description for real estate agents, the useful distinction is that a useful visit starts when the prompt reflects property facts, features, neighborhood context, photo notes, and compliance limits, the actual listing copy map with fact-only feature notes, and the review decision that follows the answer.

Concrete scenario

An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access. The write listing descriptions work happens inside a public listing where facts, fair-housing boundaries, and buyer expectations meet. For real estate agents listing description, current source notes should come first; stale or partial inputs should trigger a fresh listing copy map with fact-only feature notes pass instead of another saved answer. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible. For write listing descriptions, those constraints decide what the answer is allowed to do; without them, ChatGPT can sound finished while skipping the detail a real estate agent checks first.

Real user input

Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Phrase shopping in write listing descriptions fails because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This write listing descriptions run should turn that note into a listing description. For write listing descriptions, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.

Editor take

The prompt must use actual property facts and avoid protected-class or unsupported claims. In this write listing descriptions review, the edit is to replace polished filler with source-backed lines inside a listing description. Failure pattern for listing description with real estate agents: the listing description can sound polished while listing copy can overclaim property, neighborhood, or market facts, so the page should make that miss easy to catch. In the write listing descriptions review, the editor should reward prompts that make source notes, examples, constraints, and reviewer judgment visible and penalize answers that hide missing context behind fluent wording; compare the answer with the actual notes before reuse.

Human polish

The final description should be accurate, inviting, compliant, and easy to verify against the listing sheet. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible. Before handing off write listing descriptions, the final human edit should keep the useful structure, remove unsupported details, add verified context, and check listing description quality, property facts and feature hierarchy, and local-compliance restraint before the output reaches a buyer, seller, lead, or broker reviewer, with a short record of what changed before reuse and where For real estate agents listing description, current source notes should come first; stale or partial inputs should trigger a fresh listing copy map with fact-only feature notes pass instead of another saved answer.

Fast use path

Main card for a listing description: copy the recommended prompt first, not every variation.
Source material for a listing description: replace [source_material] with property facts, features, neighborhood context, photo notes, and compliance limits.
Audience details for a listing description: add the real audience and the constraint that matters most for write listing descriptions.
Review pass for a listing description: run the review prompt against listing description quality, property facts and feature hierarchy, and local-compliance restraint before using the answer.

Specificity signals

An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access.
Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.
property facts, features, neighborhood context, photo notes, and compliance limits
property facts, feature hierarchy, buyer appeal, and compliance-safe claims
source notes, examples, constraints, and reviewer judgment
avoid claims about safety, schools, investment return, or legal facts without source support
listing copy map with fact-only feature notes
listing copy can overclaim property, neighborhood, or market facts
replace polished filler with source-backed lines inside a listing description
a public listing where facts, fair-housing boundaries, and buyer expectations meet
For real estate agents listing description, current source notes should come first; stale or partial inputs should trigger a fresh listing copy map with fact-only feature notes pass instead of another saved answer.
Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible.
Search edge for listing description with real estate agents: show listing copy map with fact-only feature notes, a human review path for a listing description, and the task-specific reason the page deserves the query.
Failure pattern for listing description with real estate agents: the listing description can sound polished while listing copy can overclaim property, neighborhood, or market facts, so the page should make that miss easy to catch.
Outside proof for listing description with real estate agents: an independent resource must mention the listing description page visibly before listing copy map with fact-only feature notes becomes an authority claim.

Real use sample: how the messy note changes the prompt

Messy brief

Ask before copying

Listing Description reader check: who will read or approve this a listing description, and what do they already know?
Listing Description source sort: which lines in the rough note are facts, preferences, constraints, or open questions?
Listing Description blank rule: what should stay blank or flagged if source notes, examples, constraints, and reviewer judgment is missing?
Listing Description stop signal: which visible mistake would stop the team from using the answer?

Checks before sharing

Listing Description source note: treat "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit." as the factual base, not decorative background; the next usable asset is listing copy map with fact-only feature notes.
Listing Description evidence check: mark any section where source notes, examples, constraints, and reviewer judgment is assumed instead of shown, especially when listing copy can overclaim property, neighborhood, or market facts.
Listing Description scope check: keep the answer on property facts, feature hierarchy, buyer appeal, and compliance-safe claims; do not drift away from a public listing where facts, fair-housing boundaries, and buyer expectations meet.
Listing Description final polish: rewrite final wording only after listing description quality, property facts and feature hierarchy, and local-compliance restraint is clear enough for the buyer, seller, lead, or broker reviewer owner, then replace polished filler with source-backed lines inside a listing description.
Listing Description freshness rule: For real estate agents listing description, current source notes should come first; stale or partial inputs should trigger a fresh listing copy map with fact-only feature notes pass instead of another saved answer.
Listing Description failure pattern: Failure pattern for listing description with real estate agents: the listing description can sound polished while listing copy can overclaim property, neighborhood, or market facts, so the page should make that miss easy to catch.
Listing Description decision owner: Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible.

Before and after

Weak answer risk: The weak listing description answer risk is specific: the answer sounds complete while turning "need mls description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit;" into broad advice, hiding missing context around source notes, examples, constraints, and reviewer judgment, and leaving a buyer, seller, lead, or broker reviewer without a clear decision path because listing copy can overclaim property, neighborhood, or market facts. Failure pattern for listing description with real estate agents: the listing description can sound polished while listing copy can overclaim property, neighborhood, or market facts, so the page should make that miss easy to catch.
Improved outcome: A usable listing description handoff would return copy options grouped by angle, audience, proof point, and revision note; separate supplied notes from assumptions, name the review owner, prepare listing copy map with fact-only feature notes, and make the human pass focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint.
Why it feels real: The listing description example feels grounded because: it starts from messy source notes, a public listing where facts, fair-housing boundaries, and buyer expectations meet, a named review moment, and task-level evidence instead of a clean prompt sentence. For real estate agents listing description, current source notes should come first; stale or partial inputs should trigger a fresh listing copy map with fact-only feature notes pass instead of another saved answer.

Reusable version decision

Reuse listing description only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a listing description, and the review rule for property facts, feature hierarchy, buyer appeal, and compliance-safe claims still appears in the reusable prompt. Approval for agents listing description belongs with the accountable reviewer before the answer reaches a buyer, seller, lead, or broker reviewer; keep the listing copy map with fact-only feature notes review standard visible.

The job this page helps finish

Searchers arrive with property facts, features, neighborhood context, photo notes, and compliance limits already in hand and need help turning it into a listing description. The page has to show the source fields, the output shape, and the point where a buyer, seller, lead, or broker reviewer should stop and review. The distinct task pressure is property facts, feature hierarchy, buyer appeal, and compliance-safe claims.

Use Cases

Turn property facts, features, neighborhood context, photo notes, and compliance limits into a listing description for a buyer, seller, lead, or broker reviewer.
Review an existing write listing descriptions answer for listing description checkpoint, missing details, and unsupported claims.
Create a repeatable listing description prompt pattern with source notes, constraints, and review checklist so the next version starts from stronger context.
Make property facts, feature hierarchy, buyer appeal, and compliance-safe claims visible so the answer stays tied to a listing description instead of drifting into a neighboring task.
Condense a long ChatGPT answer into copy options grouped by angle, audience, proof point, and revision note without losing the decisions the human must make.

Input Prep

Write the audience or recipient in one sentence, including what they already know.
Paste or summarize property facts, features, neighborhood context, photo notes, and compliance limits; do not ask the model to guess it.
Name the final decision the write listing descriptions output must support.
Add constraints such as tone, length, required sections, privacy limits, and forbidden claims.
List the facts that must be checked after ChatGPT answers, especially source notes, examples, constraints, and reviewer judgment.
Add the task-specific focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims.

Check the answer against real references

What users are trying to finish

Searchers who land on listing descriptions want a prompt they can run against real material, usually property facts, features, neighborhood context, photo notes, and compliance limits. They should leave knowing which fields to replace, which claims need review, and why property facts, feature hierarchy, buyer appeal, and compliance-safe claims changes the answer. This route has to connect property facts, features, neighborhood context, photo notes, and compliance limits to a listing description, show copy options grouped by angle, audience, proof point, and revision note, and leave listing description quality, property facts and feature hierarchy, and local-compliance restraint with a named human reviewer.

Why the workflow matters

The page earns its place by pairing the recommended prompt with a filled case, a reject-if rule, and a repair prompt tied to property facts, feature hierarchy, buyer appeal, and compliance-safe claims. That gives the page a clearer job than a list of examples: it helps the user decide whether the answer is ready.

External references

Google Search Central people-first content guidanceUsed as the search-quality yardstick because this page must solve a real user task and make source notes, examples, constraints, and reviewer judgment reviewable.
Google Search Central SEO Starter GuideUsed to keep titles, descriptions, links, and page structure focused on helping search engines and users understand a listing description.
OpenAI ChatGPT business overviewUsed for work-related prompt boundaries where AI output should support productivity while staying subject to human review.
HUD Fair Housing Act overviewUsed for real estate prompts where property, neighborhood, buyer, seller, and listing language must avoid unsupported or discriminatory claims.
FTC advertising and marketing guidanceUsed as the second real-estate reference so a listing description keeps property claims, proof language, and marketing assertions reviewable.

Related ways people ask for this task

Main query covered: chatgpt prompts for real estate agents listing description

User intent: copy prompt workflow with template and review intent

Leave out popularity or ranking numbers until you can point to real search data after publishing.

Related ways people ask for this task

listing description chatgpt prompt for real estate agents
best chatgpt prompts for listing description
listing description prompt template for real estate agents
copyable listing description chatgpt prompt
listing description ai prompt with review checklist
chatgpt listing description workflow prompt

What to compare before using this prompt

Check whether ranking pages answer the task directly or only list broad prompts for real estate agents.
Compare whether competitors show a filled example for a listing description and not just a blank prompt.
Look for missing-source risks around source notes, examples, constraints, and reviewer judgment, especially claims that need manual checking.
Verify whether the SERP favors a role hub, a task page, a template page, or a tool-like prompt builder.
Confirm no volume, ranking, CPC, or difficulty number is used unless it comes from a live keyword tool export.

Check the answer before you reuse it

Who checks it

Keep the handoff honest by assigning one person to test the answer against the rough note and final audience.

Real-world case

a listing description scenario: the strongest review starts after ChatGPT returns a fluent answer and real estate agents provide property facts, features, neighborhood context, photo notes, and compliance limits, need copy options grouped by angle, audience, proof point, and revision note, and must keep property facts, feature hierarchy, buyer appeal, and compliance-safe claims visible while checking source notes, examples, constraints, and reviewer judgment. For real estate agents, write listing descriptions is reviewed inside a public listing where facts, fair-housing boundaries, and buyer expectations meet, with listing copy map with fact-only feature notes as the concrete item on the desk.

Checks before sharing

Source review, write listing descriptions: the answer uses the supplied property facts, features, neighborhood context, photo notes, and compliance limits and does not fill missing facts with confident guesses.
Output shape, write listing descriptions: the result clearly becomes a listing description, not broad advice about the task.
Handoff clarity, write listing descriptions: the answer names missing inputs and the next human check for listing description quality, property facts and feature hierarchy, and local-compliance restraint.
Audience fit, write listing descriptions: the result works for a buyer, seller, lead, or broker reviewer, including channel, tone, length, and decision context.
Risk boundary, write listing descriptions: the final version respects avoid claims about safety, schools, investment return, or legal facts without source support.

Compare with other results

Question to compare: chatgpt prompts for real estate agents listing description

Result listing description real estate agents check: open the top results and record whether they solve the task, not only a prompt phrase.
Example listing description real estate agents check: compare whether competing pages show a filled example for a listing description using realistic property facts, features, neighborhood context, photo notes, and compliance limits.
Evidence listing description real estate agents check: mark whether each page explains how to verify source notes, examples, constraints, and reviewer judgment and listing description quality, property facts and feature hierarchy, and local-compliance restraint.
Differentiator listing description real estate agents check: compare the top results against this page promise: Search edge for listing description with real estate agents: show listing copy map with fact-only feature notes, a human review path for a listing description, and the task-specific reason the page deserves the query.
Failure listing description real estate agents check: mark whether competing pages show this failure mode or avoid it: Failure pattern for listing description with real estate agents: the listing description can sound polished while listing copy can overclaim property, neighborhood, or market facts, so the page should make that miss easy to catch.
Freshness listing description real estate agents check: record whether competing pages say how source notes stay current. For real estate agents listing description, current source notes should come first; stale or partial inputs should trigger a fresh listing copy map with fact-only feature notes pass instead of another saved answer.
Page type listing description real estate agents check: confirm whether Google is rewarding a role hub, task page, tool, article, video, or forum thread for this query.
FAQ listing description real estate agents check: record People Also Ask questions that should become FAQ or section coverage before publishing changes.

Do not assume

Confirm the trust pages cite official Search Central guidance for helpful content and SEO basics.
Confirm source references support the safe-use and human-review framing.
Add or keep a role-specific external reference if real estate agents need policy, education, developer, hiring, sales, or marketing context beyond this prompt library.
External proof need: Outside proof for listing description with real estate agents: an independent resource must mention the listing description page visibly before listing copy map with fact-only feature notes becomes an authority claim.

Numbers to leave out unless verified

This page can prove local readiness, source coverage, and review depth. It cannot claim ranking, traffic, search volume, CPC, or difficulty until those numbers come from Search Console or another real search data source after publishing.

Weak prompt: too vague to trust

Help me write listing descriptions for my work.

It gives no source material, no stakeholder, no output shape, and no review lens, so ChatGPT can fill gaps with generic advice.

Stronger prompt: specific enough to review

Help real estate agents write listing descriptions by turning [source_material] into a listing description for [audience]. Keep the task focus on property facts, feature hierarchy, buyer appeal, and compliance-safe claims. Use this output shape: copy options grouped by angle, audience, proof point, and revision note. Do not add facts beyond the source. End with a review checklist for listing description quality, property facts and feature hierarchy, and local-compliance restraint and source notes, examples, constraints, and reviewer judgment.

It names the task asset, required inputs, audience, format, evidence boundary, and human review step, so the answer is easier to adapt and check.

Rewrite case from vague request to usable prompt

Original need

An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access. The user needs help with write listing descriptions, but the real job is to turn a messy request into a listing description that a buyer, seller, lead, or broker reviewer can review without hidden assumptions.

Weak prompt

Write a good write listing descriptions from this: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.

This weak version includes a real situation but gives ChatGPT no output shape, audience rule, evidence boundary, or review owner. It can sound polished while missing property facts, feature hierarchy, buyer appeal, and compliance-safe claims, inventing details, or skipping listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Stronger prompt

Act as a careful assistant for Real Estate Agents.
I need help with write listing descriptions. Use only this source material: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.
The usual source material for this task is property facts, features, neighborhood context, photo notes, and compliance limits.
The audience is [audience], and the output must work for a buyer, seller, lead, or broker reviewer.
Create a listing description in this shape: copy options grouped by angle, audience, proof point, and revision note.
Keep the task focus on property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Respect this editorial rule: The prompt must use actual property facts and avoid protected-class or unsupported claims.
If context is missing, ask up to three clarifying questions before writing.
After the answer, include a review checklist for listing description quality, property facts and feature hierarchy, and local-compliance restraint, source notes, examples, constraints, and reviewer judgment, and this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.

The stronger version gives ChatGPT a role, real input, audience, output shape, editorial boundary, and review lens. It also forces missing-context questions before creation and keeps source notes, examples, constraints, and reviewer judgment visible for human checking.

Sample input

An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access. User notes: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Audience: a buyer, seller, lead, or broker reviewer. Constraints: avoid unsupported claims, protect private details, and keep focus on property facts, feature hierarchy, buyer appeal, and compliance-safe claims.

Simulated output

A useful answer starts by restating the real situation, then provides copy options grouped by angle, audience, proof point, and revision note. It marks assumptions, shows which parts came from the user's notes, includes a concise next action, and ends with checks for listing description quality, property facts and feature hierarchy, and local-compliance restraint, source notes, examples, constraints, and reviewer judgment, and this boundary: avoid claims about safety, schools, investment return, or legal facts without source support. The output should already reflect the practical review target that matters here, so the final description should be accurate, inviting, compliant, and easy to verify against the listing sheet.

Human-edited final version

The human keeps the structure, removes any unsupported claim, adds missing facts from the real source, and saves the prompt as a reusable listing description prompt pattern with source notes, constraints, and review checklist. Before sharing with a buyer, seller, lead, or broker reviewer, the final pass checks tone, privacy, evidence, and whether property facts, feature hierarchy, buyer appeal, and compliance-safe claims is still the center of the answer. The pass is accepted only when the final description should be accurate, inviting, compliant, and easy to verify against the listing sheet.

Fit

Use when real estate agents have real source notes for write listing descriptions.
Use when the desired result is a listing description, not broad advice.
Use when a human can review listing description quality, property facts and feature hierarchy, and local-compliance restraint before the output reaches a buyer, seller, lead, or broker reviewer.

Not fit

Do not use when the model is expected to invent facts, numbers, credentials, or private details.
Do not use when source notes, examples, constraints, and reviewer judgment is unavailable and cannot be checked.
Do not use as final judgment for sensitive decisions covered by this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.

Worked example: Write listing descriptions example from rough notes

Example input

An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access. Raw input: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.

Prompt use

Use the evidence-aware prompt to convert those notes into a listing description, then run the review prompt against this editorial rule: The prompt must use actual property facts and avoid protected-class or unsupported claims.

Sample output shape

A useful answer would return copy options grouped by angle, audience, proof point, and revision note for a buyer, seller, lead, or broker reviewer, while making the source details and assumptions visible. It should preserve the real constraint in the input, keep property facts, feature hierarchy, buyer appeal, and compliance-safe claims at the center, and avoid adding facts that are not present. The final section should tell the user what still needs checking, especially source notes, examples, constraints, and reviewer judgment. The human pass is not decoration here: The final description should be accurate, inviting, compliant, and easy to verify against the listing sheet.

Review notes

Confirm the answer reflects this actual situation: An agent is listing a 3-bedroom home with updated kitchen, small yard, and walkable transit access.
Compare the output against the raw user input: Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit.
Confirm the source material really supports source notes, examples, constraints, and reviewer judgment.
Check that the wording fits a buyer, seller, lead, or broker reviewer.
Confirm the answer handles property facts, feature hierarchy, buyer appeal, and compliance-safe claims instead of a neighboring task.
Remove details that violate this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.

Prompt Workbench

beginner

Write listing descriptions Context Intake Prompt

Use this before write listing descriptions when the notes are rough and ChatGPT should ask clarifying questions first.

Act as a careful assistant for Real Estate Agents.
Task: help me write listing descriptions. Target result: a listing description.
Source material I can provide: [source_material]. Typical source for this task is property facts, features, neighborhood context, photo notes, and compliance limits.
Audience or stakeholder: [audience]. The output must work for a buyer, seller, lead, or broker reviewer.
Task-specific focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as intake: ask the questions needed before writing, then wait for answers if the source material is missing.
Stop rule: Stop before creating the final asset if the audience, source material, or review owner is unclear.
Return a question list grouped by audience, source material, constraints, and review owner.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.
Check cue: The user should leave with a short context pack and a safe next prompt, not a finished answer.

[source_material]: The notes, facts, examples, or raw material behind write listing descriptions.Example: property facts, features, neighborhood context, photo notes, and compliance limits
[audience]: Who will read, use, approve, or act on the output.Example: a buyer, seller, lead, or broker reviewer
[goal]: The decision or work outcome the response should support.Example: make a listing description easier to review, adapt, and use in a real real estate agents workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: avoid claims about safety, schools, investment return, or legal facts without source support
[review_lens]: The most important thing a human should check after the answer.Example: listing description quality, property facts and feature hierarchy, and local-compliance restraint
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: property facts, feature hierarchy, buyer appeal, and compliance-safe claims

Expected output

Expect a question list grouped by audience, source material, constraints, and review owner that explicitly separates source-based content from assumptions and ends with a review pass for listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Follow-up prompt

Now improve this working version into a listing description by tightening listing description quality, property facts and feature hierarchy, and local-compliance restraint, emphasizing property facts, feature hierarchy, buyer appeal, and compliance-safe claims, removing unsupported claims, and giving me one stronger version for a buyer, seller, lead, or broker reviewer.

Human review

Check whether the answer uses only provided context, handles source notes, examples, constraints, and reviewer judgment, fits a buyer, seller, lead, or broker reviewer, reflects property facts, feature hierarchy, buyer appeal, and compliance-safe claims, and respects this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.

Best for: Starting write listing descriptions when the source material still needs shape. Use when: Use before asking ChatGPT for write listing descriptions so the model has enough task-specific context.

advanced

Write listing descriptions Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become a listing description.

Act as a careful assistant for Real Estate Agents.
Task: help me write listing descriptions. Target result: a listing description.
Source material I can provide: [source_material]. Typical source for this task is property facts, features, neighborhood context, photo notes, and compliance limits.
Audience or stakeholder: [audience]. The output must work for a buyer, seller, lead, or broker reviewer.
Task-specific focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return copy options grouped by angle, audience, proof point, and revision note.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.
Check cue: The user should get a working version they can inspect against the supplied notes.

[source_material]: The notes, facts, examples, or raw material behind write listing descriptions.Example: property facts, features, neighborhood context, photo notes, and compliance limits
[audience]: Who will read, use, approve, or act on the output.Example: a buyer, seller, lead, or broker reviewer
[goal]: The decision or work outcome the response should support.Example: make a listing description easier to review, adapt, and use in a real real estate agents workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: avoid claims about safety, schools, investment return, or legal facts without source support
[review_lens]: The most important thing a human should check after the answer.Example: listing description quality, property facts and feature hierarchy, and local-compliance restraint
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: property facts, feature hierarchy, buyer appeal, and compliance-safe claims

Expected output

Expect copy options grouped by angle, audience, proof point, and revision note that explicitly separates source-based content from assumptions and ends with a review pass for listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Follow-up prompt

Human review

Best for: Turning prepared context into a listing description. Use when: Use before asking ChatGPT for write listing descriptions so the model has enough task-specific context.

workflow

Write listing descriptions Repeatable Workflow Prompt

Use this when write listing descriptions repeats often enough to become listing description prompt pattern with source notes, constraints, and review checklist.

Act as a careful assistant for Real Estate Agents.
Task: help me write listing descriptions. Target result: a listing description.
Source material I can provide: [source_material]. Typical source for this task is property facts, features, neighborhood context, photo notes, and compliance limits.
Audience or stakeholder: [audience]. The output must work for a buyer, seller, lead, or broker reviewer.
Task-specific focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as a repeatable workflow: separate one-time facts from fields that should change next time.
Stop rule: Stop if the reusable version would preserve private details or hide a human approval step.
Return a reusable step-by-step workflow with inputs, checks, and follow-up prompts.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.
Check cue: The user should get reusable fields, a run order, and a reject-if rule for the next use.

[source_material]: The notes, facts, examples, or raw material behind write listing descriptions.Example: property facts, features, neighborhood context, photo notes, and compliance limits
[audience]: Who will read, use, approve, or act on the output.Example: a buyer, seller, lead, or broker reviewer
[goal]: The decision or work outcome the response should support.Example: make a listing description easier to review, adapt, and use in a real real estate agents workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: avoid claims about safety, schools, investment return, or legal facts without source support
[review_lens]: The most important thing a human should check after the answer.Example: listing description quality, property facts and feature hierarchy, and local-compliance restraint
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: property facts, feature hierarchy, buyer appeal, and compliance-safe claims

Expected output

Expect a reusable step-by-step workflow with inputs, checks, and follow-up prompts that explicitly separates source-based content from assumptions and ends with a review pass for listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Follow-up prompt

Human review

Best for: Creating a reusable process for repeated write listing descriptions work. Use when: Use when write listing descriptions repeats often enough to need a standard process.

review

Write listing descriptions Human Review Prompt

Use this after there is already working copy and the main need is listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Act as a careful assistant for Real Estate Agents.
Task: help me write listing descriptions. Target result: a listing description.
Source material I can provide: [source_material]. Typical source for this task is property facts, features, neighborhood context, photo notes, and compliance limits.
Audience or stakeholder: [audience]. The output must work for a buyer, seller, lead, or broker reviewer.
Task-specific focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as a review of existing copy: score the answer, name the weak sections, and propose repairs.
Stop rule: Stop if the copy cannot be traced back to the supplied source material or the reviewer is not named.
Return a scored review table with issues, fixes, and what still needs human judgment.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.
Check cue: The user should get a decision about accept, repair, or reject before polishing the wording.

[source_material]: The notes, facts, examples, or raw material behind write listing descriptions.Example: property facts, features, neighborhood context, photo notes, and compliance limits
[audience]: Who will read, use, approve, or act on the output.Example: a buyer, seller, lead, or broker reviewer
[goal]: The decision or work outcome the response should support.Example: make a listing description easier to review, adapt, and use in a real real estate agents workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: avoid claims about safety, schools, investment return, or legal facts without source support
[review_lens]: The most important thing a human should check after the answer.Example: listing description quality, property facts and feature hierarchy, and local-compliance restraint
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: property facts, feature hierarchy, buyer appeal, and compliance-safe claims

Expected output

Expect a scored review table with issues, fixes, and what still needs human judgment that explicitly separates source-based content from assumptions and ends with a review pass for listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Follow-up prompt

Human review

Best for: Finding weak spots in existing working copy. Use when: Use after real estate agents already have working copy and need to check listing description quality, property facts and feature hierarchy, and local-compliance restraint.

format

Write listing descriptions Format Conversion Prompt

Use this when the substance is right but the output needs to fit a table, checklist, email, outline, or script.

Act as a careful assistant for Real Estate Agents.
Task: help me write listing descriptions. Target result: a listing description.
Source material I can provide: [source_material]. Typical source for this task is property facts, features, neighborhood context, photo notes, and compliance limits.
Audience or stakeholder: [audience]. The output must work for a buyer, seller, lead, or broker reviewer.
Task-specific focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as format conversion: preserve the facts and change only the structure, order, or channel fit.
Stop rule: Stop if the requested format would require adding facts that were not in the original answer.
Return the same content reshaped without adding new facts.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.
Check cue: The user should get a reshaped version plus a note showing what stayed unchanged.

[source_material]: The notes, facts, examples, or raw material behind write listing descriptions.Example: property facts, features, neighborhood context, photo notes, and compliance limits
[audience]: Who will read, use, approve, or act on the output.Example: a buyer, seller, lead, or broker reviewer
[goal]: The decision or work outcome the response should support.Example: make a listing description easier to review, adapt, and use in a real real estate agents workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: avoid claims about safety, schools, investment return, or legal facts without source support
[review_lens]: The most important thing a human should check after the answer.Example: listing description quality, property facts and feature hierarchy, and local-compliance restraint
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: property facts, feature hierarchy, buyer appeal, and compliance-safe claims

Expected output

Expect the same content reshaped without adding new facts that explicitly separates source-based content from assumptions and ends with a review pass for listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Follow-up prompt

Human review

Best for: Changing the output format without changing the facts. Use when: Use when the answer needs a precise structure before real estate agents can review it.

privacy

Write listing descriptions Privacy-Safe Prompt

Use this when the source material contains private, sensitive, or account-specific details.

Act as a careful assistant for Real Estate Agents.
Task: help me write listing descriptions. Target result: a listing description.
Source material I can provide: [source_material]. Typical source for this task is property facts, features, neighborhood context, photo notes, and compliance limits.
Audience or stakeholder: [audience]. The output must work for a buyer, seller, lead, or broker reviewer.
Task-specific focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as a sanitizing pass: replace private details with role-safe descriptions before writing.
Stop rule: Stop if names, identifiers, account details, confidential strategy, or one-time records are still present.
Return a sanitized prompt-ready summary plus a list of removed details.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.
Check cue: The user should get a safe summary, removed-detail list, and a reusable version without sensitive data.

[source_material]: The notes, facts, examples, or raw material behind write listing descriptions.Example: property facts, features, neighborhood context, photo notes, and compliance limits
[audience]: Who will read, use, approve, or act on the output.Example: a buyer, seller, lead, or broker reviewer
[goal]: The decision or work outcome the response should support.Example: make a listing description easier to review, adapt, and use in a real real estate agents workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: avoid claims about safety, schools, investment return, or legal facts without source support
[review_lens]: The most important thing a human should check after the answer.Example: listing description quality, property facts and feature hierarchy, and local-compliance restraint
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: property facts, feature hierarchy, buyer appeal, and compliance-safe claims

Expected output

Expect a sanitized prompt-ready summary plus a list of removed details that explicitly separates source-based content from assumptions and ends with a review pass for listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Follow-up prompt

Human review

Best for: Sanitizing context before asking ChatGPT for help. Use when: Use before adding sensitive context so private details stay out.

short

Write listing descriptions Fast Checklist Prompt

Use this for a quick pass when the user only needs the next few decisions for write listing descriptions.

Act as a careful assistant for Real Estate Agents.
Task: help me write listing descriptions. Target result: a listing description.
Source material I can provide: [source_material]. Typical source for this task is property facts, features, neighborhood context, photo notes, and compliance limits.
Audience or stakeholder: [audience]. The output must work for a buyer, seller, lead, or broker reviewer.
Task-specific focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as a fast decision pass: give only the next actions, the missing input, and the main risk.
Stop rule: Stop if the user needs a full artifact, a legal answer, a policy decision, or unsupported factual claims.
Return a concise checklist with the next action and the main risk.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on listing description quality, property facts and feature hierarchy, and local-compliance restraint; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: avoid claims about safety, schools, investment return, or legal facts without source support.
Check cue: The user should get a narrow next step they can complete before opening a longer prompt.

[source_material]: The notes, facts, examples, or raw material behind write listing descriptions.Example: property facts, features, neighborhood context, photo notes, and compliance limits
[audience]: Who will read, use, approve, or act on the output.Example: a buyer, seller, lead, or broker reviewer
[goal]: The decision or work outcome the response should support.Example: make a listing description easier to review, adapt, and use in a real real estate agents workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: avoid claims about safety, schools, investment return, or legal facts without source support
[review_lens]: The most important thing a human should check after the answer.Example: listing description quality, property facts and feature hierarchy, and local-compliance restraint
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: property facts, feature hierarchy, buyer appeal, and compliance-safe claims

Expected output

Expect a concise checklist with the next action and the main risk that explicitly separates source-based content from assumptions and ends with a review pass for listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Follow-up prompt

Human review

Best for: Getting a quick decision checklist before spending more time. Use when: Use when time is short and the user needs the next action, not a full answer.

Variables

[source_material]: property facts, features, neighborhood context, photo notes, and compliance limits
[audience]: a buyer, seller, lead, or broker reviewer
[goal]: make a listing description easier to review, adapt, and use in a real real estate agents workflow
[constraints]: avoid claims about safety, schools, investment return, or legal facts without source support
[review_lens]: listing description quality, property facts and feature hierarchy, and local-compliance restraint
[task_focus]: property facts, feature hierarchy, buyer appeal, and compliance-safe claims

Quality Rubric

Output quality check: Can the user see when to use the prompt, when not to use it, what input to paste, and what result to expect?
Context: Does the prompt give enough property facts, features, neighborhood context, photo notes, and compliance limits to avoid guessing?
Specificity: Does the answer produce a listing description rather than broad advice?
Task focus: Does it handle property facts, feature hierarchy, buyer appeal, and compliance-safe claims instead of drifting into a neighboring workflow?
Reviewability: Can a human quickly check listing description checkpoint and source notes, examples, constraints, and reviewer judgment?
Fit: Does the wording match a buyer, seller, lead, or broker reviewer and the real channel?
Safety: Are private details, unsupported claims, and policy-sensitive assumptions controlled?

Common mistakes

Asking ChatGPT to write listing descriptions without giving property facts, features, neighborhood context, photo notes, and compliance limits.
Accepting polished wording before checking source notes, examples, constraints, and reviewer judgment.
Using the same prompt for every real estate agent task instead of changing the output shape and review lens.
Forgetting to name a buyer, seller, lead, or broker reviewer, which makes tone and detail level drift.
Ignoring the task-specific focus: property facts, feature hierarchy, buyer appeal, and compliance-safe claims.
Skipping the review pass for listing description quality, property facts and feature hierarchy, and local-compliance restraint.
Pasting private or sensitive details when a summarized version would work.

Risk Controls

Avoid unsupported claims about pricing, safety, schools, or investment outcomes.
Ask ChatGPT to label assumptions and verification needs before using a listing description.
Do not paste private names, identifiers, account details, student records, customer records, or confidential strategy when a summarized version is enough.
Check that property facts, feature hierarchy, buyer appeal, and compliance-safe claims is supported by the source material and not invented.
Have a human review listing description checkpoint before sharing the output with a buyer, seller, lead, or broker reviewer.

FAQ

What is the best prompt for real estate agents to write listing descriptions?

Use a prompt that names property facts, features, neighborhood context, photo notes, and compliance limits, asks for copy options grouped by angle, audience, proof point, and revision note, and ends with a review pass for listing description quality, property facts and feature hierarchy, and local-compliance restraint.

What should I paste into ChatGPT first?

Paste sanitized source notes, the intended audience, constraints, and the decision the output must support. For this task, the key input is property facts, features, neighborhood context, photo notes, and compliance limits.

How do I make the answer less generic?

Ask ChatGPT to use only the supplied material, show assumptions, and revise the answer against source notes, examples, constraints, and reviewer judgment and a buyer, seller, lead, or broker reviewer.

What should a human check before using the output?

Check facts, tone, privacy, unsupported claims, and the task-specific lens: listing description quality, property facts and feature hierarchy, and local-compliance restraint.

Next workflows

ChatGPT Prompts for Real Estate AgentsReturn to the role guide to choose by situation, output, and reviewer.
Write buyer emailsUseful next step when this workflow needs a related real estate agents output or review pass.
Write seller scriptsUseful next step when this workflow needs a related real estate agents output or review pass.
Follow up after open housesUseful next step when this workflow needs a related real estate agents output or review pass.
Outline neighborhood guidesUseful next step when this workflow needs a related real estate agents output or review pass.
Write market updatesUseful next step when this workflow needs a related real estate agents output or review pass.

Write Listing Descriptions: make listing copy map with fact-only feature notes reviewable

Start with the note you actually have

Copy this after checking the notes

Check the answer before saving it

Pick accept, repair, or reject before reuse

Save the final answer, human edit, and variables

Set up the first run

Write listing descriptions Evidence-Aware Working Copy Prompt

Variable Builder

Copy this filled version

Run this page in four moves

Start from the real note, not a blank prompt

Check the answer against your note

Real use plan for treating the prompt like a work note

Before copying

After ChatGPT answers

Reject the answer if

Choose the next move

Build The Asset

Know when the answer is ready

Ready signal

First run action

Second pass before the answer becomes reusable

Source line

Reviewer voice

the rough note "Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit" as the visible source line for a listing description

any confident claim about source notes, examples, constraints, and reviewer judgment that the pasted note does not prove

the missing audience, owner, or review detail needed before a buyer, seller, lead, or broker reviewer uses the answer

the first polished paragraph so it shows property facts, feature hierarchy, buyer appeal, and compliance-safe claims before tone improvements

Why this feels hand-edited

Run the margin pass

Task actions for the next useful move

Before you use the answer, make the call

Working case file: Write Listing Descriptions working case for Real Estate Agents

Rough note

Constraint to keep visible

What the user brought

What is still missing

Who accepts the answer

What gets saved

Before copying

Checks before sharing

Run this case first

Input triage before running ChatGPT

Missing context

Notes to save before reusing this prompt

Known material to preserve

Missing inputs to ask about

Non-negotiable constraints

Case-only material to remove

Repeatable prompt controls

Iteration loop: run the prompt as a working thread

Thread goal

First run

Gap fill

Skeptic pass

Handoff

Prompt readiness check before you copy

Collect context first

Session handoff: finish the run without losing the thread

Collect working context

Work note: what the rough note changes

Original working note

Questions before reuse

Who checks it

Usable output

Prompt run from pasted notes

Pasted notes

Why this input is messy

First prompt move

Questions ChatGPT should ask

Usable answer shape

Human revision

Save or discard

Why this page is not interchangeable

Work moment

Why this page

Do first

Next best workflow

What to look for