Workflow card WC-11.1: Contract dates to draft timeline, with verification table
From AI for Real Estate Agents (2026 Edition). Facts in, draft out, licensee signs.

Time: estimate: about 20 minutes, most of it your counting

Trigger. An offer was accepted and you need every contract deadline in one table, with the clause behind each one, before the end of day 1.

Inputs.

- The fully executed purchase agreement and every addendum and counter, as text or PDF (financial terms redacted unless your broker has approved the tool for them; Chapter 4.5)
- The acceptance date and time, and whether your form defines acceptance as signature or delivery
- Your form's day-counting rules from your standing instructions: calendar or business days, whether the trigger day counts, weekend and holiday rollover, expiry time, which holidays apply
- A paper or wall calendar for your own count

Brief. (paste everything between the lines)

------------------------------------------------------------
Role: You are helping a licensed real estate agent build a deadline table for an escrow. You extract and organize. You do not decide dates. Use only facts I give you; if a date field or definition is missing, ask instead of guessing.
Facts: [paste the purchase agreement, addenda, and counters] Acceptance: [date and time, and whether that is signature or delivery per the form]. Counting rules for this form: [calendar or business days; trigger day counted or not; weekend and holiday rollover rule; expiry time; holiday list].
Audience: Me. This is a working table I will verify by hand.
Voice: Plain. No commentary.
Rules: Use only facts I give you; ask instead of guessing. List every deadline, contingency, delivery obligation, and date the contract or any addendum creates, including ones stated as a count of days. For each, quote the clause that creates it, with its paragraph number. Where you convert a count into a date, state in the same row which counting rule you applied and label the date DRAFT. Never label any date final. If two documents set the same deadline differently, list both and mark the row CONFLICT. No advice on whether to remove a contingency. No language about who should live here or who the neighbors are.
Format: A four-column table: Milestone; AI-drafted date (DRAFT, with the rule applied); Contract clause (quoted, with paragraph number); Verified date (leave blank). Rows in date order. Below the table, a list titled "Counting assumptions I made" and a list titled "Dates I could not derive and why." After the output, list every fact you used and which input it came from.
------------------------------------------------------------

Check.

- For every row, open the quoted clause in the contract and confirm the quote and paragraph number are right.
- Count each date yourself, on a calendar, using your form's rules. Write it in the Verified column and initial it, including the rows that match.
- Where your date differs, note the assumption the assistant made (acceptance as day 1, business days, no rollover) and add a rule forbidding it to your standing instructions.
- Read "Dates I could not derive." Each one is a date you still owe the file.
- Confirm no date came from anywhere but the documents you pasted.

Ship. The initialed table goes in the transaction file and the per-escrow project (Chapter 3.4). Calendar every verified date with a reminder two business days ahead. Save the brief, with the contract removed, to your brief library as "Contract to timeline, v1." Re-run on any addendum that changes a date.

Compliance check. Ch. 4.4 (disclosures and advice), 4.5 (privacy and client data). The assistant drafts; the licensee counts, verifies, and initials every date. Redact financial terms before pasting unless your broker has approved the tool for them.
