How does an agent draft MLS comp summaries with listing-agent sign-off?
A listing agent points the agent at a new MLS listing. The agent pulls active, pending, and sold comps, drafts a pricing summary, and writes a Dock row tied to the MLS listing key. The listing agent reviews, edits if needed, and signs off. MLS keeps the listing. BoldTrail keeps the lead history. Dock holds the agent's interpretation and the review attached to it. See the broader pattern in Dock for real estate.
[Platforms appropriate to this sub] stay the system of record for the raw data. Dock is the system of record for what the AGENT INTERPRETS. Each Dock row carries a pointer back to the platform record, agent identity, decision, reviewer, and timestamp. The agent re-fetches platform data via fresh API reads when it needs current state.
Surface: Listing comp reviews
| listing_key | address | agent_summary | suggested_price | reviewer | status |
|---|---|---|---|---|---|
| MLS-884213 | 412 Magnolia Ave | 3 active within 0.4 mi cluster at $612-$648/sqft; 2 sold in 30 days at $625 avg. Lot premium offsets dated kitchen. | $619,000 | jordan.h@brokerage | signed |
| MLS-884401 | 78 Cypress Ln | Pending comp at $545 sets ceiling. Active inventory thin. Recommend list at ceiling minus 1.5%. | $537,000 | priya.s@brokerage | edited+signed |
| MLS-884502 | 1209 Birch Ct | Sold comps span $410-$498; condition gap unclear from photos. Flagged for walkthrough before pricing. | hold | priya.s@brokerage | needs_walkthrough |
Worked workflow
Priya lists 78 Cypress Ln. The agent reads the MLS listing via RESO-standard fields, pulls six comps within a quarter mile and ninety days, drafts the summary, and writes a row. Priya sees the pending comp at $545, edits the suggestion to $537,000, and signs. The signature writes back to BoldTrail as a listing note with a Dock row link. If a buyer-side agent later asks how the price was set, the row shows the comps used, Priya's edit, and the timestamp. See agent audit and compliance for how that trail is structured.
Pricing changes after sign-off require a fresh review. Dock treats the original sign-off and the price-change approval as a two-key handshake, so a stale agent summary never silently drives a new list price.
Why it matters
MLS data is governed. The NAR Handbook on Multiple Listing Policy treats participation as conditional on rule compliance, and RESO's Data Dictionary fixes the field shapes the agent reads from. A summary that paraphrases an MLS field without attribution is a liability. A row that names the agent, the comps, the reviewer, and the timestamp is defensible. The same pattern that supports sales review supports listing review: agent drafts, human signs, identity is preserved.
The agent is a named principal in this loop. It is not a service account writing on Priya's behalf. See agent identity for why that distinction shows up in the signature on every row.
Start with one Dock surface for comp reviews tied to your MLS feed. See the Dock for sales pattern for adapting it to buyer-side workflows.
FAQ
Does Dock store MLS listing data? No. The MLS is the system of record. Dock stores the agent's interpretation, the human review, and a pointer to the listing key. The agent re-reads the MLS for current price, status, and photos on demand.
What happens if the MLS listing changes after sign-off? The next agent read detects the field delta and opens a new review row. The prior signed row stays as a historical record. The agent never silently updates a signed summary.
Can the agent push the summary back into BoldTrail? Yes, as a listing note with a link to the Dock row. The note carries the agent's name and the reviewer's name. BoldTrail remains the CRM; Dock remains the review record.
Who can sign off on a comp summary? Only the listing agent assigned to the MLS record. Dock checks the reviewer email against the listing's agent of record before accepting a signature.
External references: NAR Handbook on Multiple Listing Policy (2026 edition); RESO Data Dictionary 2.0 field definitions.
