A real estate deal-pipeline workflow in Dock works like this. A named agent reads the active pipeline from BoldTrail, pulls contact and activity history from Salesforce, and re-fetches current listing state from the MLS feed. It drafts a one-page deal brief into a Dock row. A broker reviews the brief, approves or rejects the proposed pipeline-stage move, and signs. Only then does the agent push the stage change back to BoldTrail. The platform never moves a deal on its own initiative.
BoldTrail, Salesforce, and the MLS 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.
The Deal Briefs surface
| Deal | BoldTrail link | MLS # | Proposed move | Agent rationale | Broker | Status |
|---|---|---|---|---|---|---|
| 412 Oak Ave | bt://opp/8841 | RESO-44182 | Active to Under Contract | Buyer signed offer 5/28, EMD wired, MLS still Active | Priya Shah | Approved 5/29 |
| 88 Lakeview | bt://opp/8847 | RESO-44910 | Qualified to Nurture | No response 21 days, MLS shows price drop on competing listing | Priya Shah | Approved 5/29 |
| 1207 Mill St | bt://opp/8852 | RESO-45003 | Under Contract to Closed | Title cleared 5/30, funder confirmed, listing pending MLS update | Mark Boren | Pending |
Each row links back to the BoldTrail opportunity and the MLS record. The rationale is the agent's reading at the moment of draft. If the broker disagrees, they reject the row and the BoldTrail stage stays put.
One worked workflow
Monday 8:14 a.m. The agent runs its pipeline sweep. It reads 38 active opportunities from BoldTrail, joins them to Salesforce contact records, and re-queries the MLS for current listing status on each property. It finds 412 Oak Ave: BoldTrail says Active, MLS says Active, but Salesforce logged a signed offer Friday night and the EMD posted Saturday. The agent writes a Deal Brief row proposing Active to Under Contract, cites the offer document and the EMD confirmation, and pings broker Priya Shah. Priya opens the row at 9:02 a.m., reads the brief, approves. The agent writes the stage change to BoldTrail at 9:02:14 a.m. with the approval record attached. If Priya had rejected, the BoldTrail record would not have moved and the row would carry her note.
Why this matters
Pipeline hygiene is where real estate teams lose money. Stale stages mean missed follow-ups, double-booked showings, and commissions held up in reconciliation. An agent reading pipeline data continuously catches drift. Routing every status change through a signed broker handshake keeps a human accountable for the move. The result is a pipeline that is current AND auditable, which matters when a brokerage compliance review asks who moved what and why.
The same architecture covers buyer-side leads, listing-side updates, and referral splits. See the full real estate pillar for the surface inventory.
Set up your deal-brief surface in Dock.
FAQ
Does the agent ever change a BoldTrail stage without broker approval? No. The agent drafts to Dock, the broker signs in Dock, and only then does the agent write back to BoldTrail. This is the two-key handshake pattern.
How does Dock know which agent did what? Every row carries the agent's identity as a first-class field. See agent identity lifecycle for how identities are issued and rotated.
What if the MLS data is stale? The agent re-fetches MLS state at draft time, not from a cache. RESO Data Dictionary fields like StandardStatus and ModificationTimestamp tell the agent how fresh the listing record is (RESO).
Is this auditable for a brokerage compliance review? Yes. Every stage change has a row with the agent, the broker, the rationale, the source links, and the timestamp. See agent audit and compliance for the export format. Context: NAR's 2025 Profile of Home Buyers and Sellers reports first-time buyer share at a historic low of 21%, raising the stakes on every active deal (NAR). For broader sales-side patterns see Dock for sales.
