Buyer-side work

Every deadline out of the contract

Feed it the executed contract and counters; get back every deadline, who owes what, and a plain-English "what happens if nothing happens today."

The idea

What this does

Between acceptance and keys, the calendar is the contract. This prompt extracts every deadline and obligation from the actual documents (including the ones a counter offer quietly moved), lays them out in order, tells you which party owes what, and writes the consequence of inaction next to each date. When an amendment lands mid-escrow, you paste it in and ask what changed. It is the second set of eyes on the dates your deposit-holding clients care about most.

Gather these first

Before you start

The executed purchase agreement plus every counter and addendum, as PDFs
The acceptance date and scheduled close date
Thirty seconds when any amendment lands, to keep the timeline current

Step by step

How to use it

Start a new chat named after the escrow and attach the contract documents.
Copy the prompt, fill in the dates bracket, and paste.
Check the two or three dates you already know by heart; if those are right, trust rises for the rest.
When anything changes, attach the new document in the same chat: "here is an amendment, recompute the timeline and tell me exactly what changed."

Copy everything in the box

The prompt

Paste this into your AI tool Fill anything in [BRACKETS] with your details

You are a transaction-deadline analyst for me, a residential real-estate agent. I have attached the executed purchase contract and all counters and addenda for an escrow. Acceptance date: [DATE]. Scheduled close: [DATE]. I represent the [BUYER or SELLER]. Extract and build: 1. THE MASTER TIMELINE. Every deadline and time-boxed obligation in these documents, in date order: contingency periods and removals, disclosure deliveries, deposit deadlines, notices, loan and appraisal milestones, possession and rent-back terms. For each: the date (compute it from the contract language and acceptance date, and show the math when it is day-count based), which document and section it comes from, who must act, and what happens if they do not, in one plain sentence. 2. MOVED BY COUNTERS. Anywhere a counter or addendum changed a default: show the original, the change, and the document that did it. 3. MY SIDE'S WEEK. The next 7 days from [TODAY'S DATE]: what my side must do, what the other side owes us, and the single item with the worst consequence if missed. 4. WATCH ITEMS. Dates that commonly slip in escrows like this and are worth a proactive nudge to the lender, escrow, or the other agent, with a one-line draft nudge for each. 5. CALENDAR LIST. The full timeline as a simple list I can paste into a calendar: date, item, owner. Rules: cite document and section for every date. If contract language is ambiguous about how a period is counted, flag it as a question for the broker or attorney rather than deciding. Never silently assume a date; show your basis.

→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

A dated, sourced master timeline with the day-count math shown
The counter-offer changes made visible instead of remembered
A "this week" view with consequences in plain English
Draft nudges for the dates that usually slip
A paste-ready calendar list

Level it up

Make it yours

Also add the wire-safety habit to your closing checklist: verify wire instructions by phone on a number you already had, never from an email, and treat any "updated instructions" mid-escrow as fraud until proven otherwise. Ask the AI to include this in the client's closing-week checklist.
Sell-and-buy client? Run one chat per escrow, then see playbook 19 to join the two timelines.
Ask "draft the weekly status email to my client from this timeline" for effortless communication.

Keep it honest

The contract is the authority and ambiguities go to your broker or an attorney; the flag-instead-of-decide rule in the prompt is doing real work.
Verify the computed dates against your own count on the first run; after that, spot-check.
This maintains a timeline when you feed it documents; it does not watch your inbox. The paste-when-things-change habit is what keeps it alive.