Two escrows, one joined timeline: the cross-dependencies mapped, the failure scenarios named, and the weekly chain check that keeps four parties honest.
The idea
What this does
Clients selling one home to buy another are living two transactions whose deadlines secretly depend on each other, coordinated by nobody. This prompt builds the joined picture: both timelines extracted and cross-linked, the dependencies made explicit ("releasing the purchase deposit waits on the sale's loan contingency"), the failure scenarios walked through before they happen, and the weekly what-matters-now check. You become the one person in a four-party mess holding the whole map, which clients do not forget.
Gather these first
Before you start
Both contracts (or the one that exists plus the plan for the other), with counters and addenda
The family's hard constraints: school start, lease end, the one date that cannot move
The financing shape as you know it: contingent offer, bridge, HELOC, or savings
Step by step
How to use it
Start one chat named for the client's chain and attach both contracts (run playbook 06 per escrow first if you want; this one joins them).
Copy the prompt, fill in the constraints, and paste.
Study the dependency map; the line items with two dates on them are your job now.
Weekly, paste what changed and ask for the updated chain check.
Copy everything in the box
The prompt
Paste this into your AI toolFill anything in [BRACKETS] with your details
You are a transaction-chain coordinator for me, a residential real-estate agent. My clients are selling [SALE ADDRESS] and buying [PURCHASE ADDRESS]. I have attached both contracts with all counters and addenda. I represent them on [BOTH / SALE ONLY / PURCHASE ONLY].
Their constraints: [e.g. must be out by Aug 20 lease-back limit, kids start school Sep 3, cash for the purchase depends on sale proceeds, bridge loan approved up to $X / not an option].
Build:
1. BOTH TIMELINES. Extract every deadline from each contract (dates computed from contract language, with document and section cites), in two labeled columns.
2. THE DEPENDENCY MAP. Every place one transaction's event gates the other: proceeds needed for closing funds, contingency releases that should wait on the other escrow's milestones, possession and moving logistics between the two close dates. For each dependency: what specifically must be true, by when, and the plain-English consequence if it is not.
3. THE GAP ANALYSIS. The two close dates as scheduled: is there a housing gap or a funding gap, how big, and the realistic bridges for each (rent-back terms to request, short-term options, per-diem math), framed as scenarios with rough costs, not financial advice.
4. FAILURE DRILLS. Walk through the three classic chain failures for this configuration (sale falls out mid-purchase; purchase delays past the sale's close; appraisal short on either side): early warning signs, the decision point, and the least-bad path for each, so nobody meets these ideas for the first time in a crisis.
5. THIS WEEK. From [TODAY'S DATE]: what must happen in each escrow, which dependency is live right now, and the single most important nudge to send, drafted.
6. THE CLIENT PICTURE. A calm one-page explanation of the chain for my clients: the map, the plan, what we are watching, and what they should not worry about yet.
Rules: cites for every date, show day-count math, label every scenario cost as rough, and flag anything that should go to the lender, broker, or attorney rather than being decided here.
→Anything in [BRACKETS] is yours to fill in. Delete a bracket line if it does not apply;
the prompt still works.
The result
What you'll get back
Both escrows on one page with the dependencies drawn
The gap analysis (housing and funding) with real numbers on the bridges
Failure drills that turn week-six panic into a rehearsed plan B
A weekly chain check and the exact nudge to send
A client explainer that lowers the household anxiety level measurably
Level it up
Make it yours
When either escrow amends, attach the new document: "recompute the chain; what changed and which dependencies moved?"
Ask "draft the note to the other listing agent proposing the rent-back that closes our gap."
If the second contract does not exist yet, run it anyway; section 3 becomes the offer-strategy input (what close date and rent-back to ask for).
Keep it honest
Bridge financing, contingency releases, and deposit exposure are lender-broker-attorney territory; the prompt routes them there and so should you.
The chain map is only as current as what you feed it; the weekly paste is the discipline that keeps it true.
Never let clients treat a scenario cost as a quote; rough means rough.