realtor-transaction-ops

v1.0.0 MIT real-estate updated 2026-09-27

Track a real estate deal from accepted offer to closing — feed a milestones CSV (milestone, due date, done, owner) and get days remaining to closing, overdue flags, and the next upcoming milestone. Use when managing any active escrow or transaction you need to keep on schedule.

$ skillbank install realtor-transaction-ops@1.0.0
# pins exactly 1.0.0 · README + changelog included

Realtor Transaction Ops

Overview

A plain-text contract-to-close tracker. You keep one CSV of milestones — inspection, appraisal, loan approval, final walkthrough, closing — each with a due date, a yes/no done flag, and an owner. The script reports how many days remain to closing, flags anything overdue and undone, and names the next upcoming milestone. All data stays local — nothing is uploaded.

Installation

1. Copy the realtor-transaction-ops/ directory anywhere convenient. 2. Make the script executable (Unix):


   chmod +x scripts/tracker.py

3. Write your milestones CSV (see Inputs). No pip install needed — standard library only.

Configuration

No config file. Runtime options:

| Flag | Default | Description | |-------------|-----------|---------------------------------------------------------| | --closing | Closing | Milestone name that marks the closing date. | | --today | real date | Override "today" (YYYY-MM-DD); useful for rehearsals. |

The CSV must have exactly these columns (order does not matter):

| Column | Format | |------------|--------------------------------------| | milestone| Any text, e.g. Inspection. | | due_date | YYYY-MM-DD. | | done | yes or no (also accepts y/n, true/false, 1/0). | | owner | Person responsible, e.g. Marcus. |

See references/contingency-playbook.md for the standard 30-day escrow milestone set and day offsets.

Inputs

tracker.py <milestones.csv> [--closing NAME] [--today YYYY-MM-DD]

Returns, on stdout: closing date with days remaining, completion count, overdue milestones (undone + past due date), the next three upcoming milestones, and the completed list. Missing/invalid input produces a clear Error: message on stderr and exit code 2 — never a raw traceback.

Worked example

A 30-day escrow (tested with --today 2026-09-27):


cat > escrow.csv <<'EOF'
milestone,due_date,done,owner
Offer accepted,2026-09-27,yes,Marcus
Earnest money deposited,2026-09-30,no,Marcus
Inspection,2026-10-02,no,Dana
Appraisal,2026-10-07,no,Marcus
Loan approval,2026-10-15,no,Dana
Final walkthrough,2026-10-26,no,Marcus
Closing,2026-10-27,no,Dana
EOF

./scripts/tracker.py escrow.csv --today 2026-09-27

Output:


Contract-to-close status (as of 2026-09-27)
Closing: 2026-10-27 — 30 day(s) remaining
Progress: 1 of 7 milestones complete

OVERDUE: none — everything is on track

NEXT UP:
  -> Earnest money deposited — due 2026-09-30 (in 3 days) [owner: Marcus]
  -> Inspection — due 2026-10-02 (in 5 days) [owner: Dana]
  -> Appraisal — due 2026-10-07 (in 10 days) [owner: Marcus]

COMPLETED:
  [x] Offer accepted — due 2026-09-27 [owner: Marcus]

Error handling example:


$ ./scripts/tracker.py missing.csv
Error: cannot read missing.csv: No such file or directory

Version history

Changelog

1.0.0 — 2026-09-27

  • Initial public release.
  • scripts/tracker.py: milestones CSV → contract-to-close status (days to closing, overdue flags, next upcoming milestones).
  • references/contingency-playbook.md: standard 30-day escrow milestone set with day offsets and rules of thumb.
  • Zero dependencies; tested with a 30-day escrow sample plus bad-input cases (missing file, bad date, bad yes/no).

← back to catalog