When an addendum arrives by email

Addendums are a major silent-killer in real-estate coordination: a party emails an updated PDF, the closing date shifts by 2 weeks, nobody updates the task schedule, and 10 days later you realize the loan approval deadline passed.

BuyerFlo handles this.

What the app does automatically

When a PDF attachment lands on the deal's address:

1. Saved. The file goes to the deal's Documents tab.
2. Classified. A quick AI pass guesses what the document is (addendum / inspection report / lender letter / etc.).
3. Scanned. If it looks like an addendum or disclosure, a full AI scan diffs it against the current contract data — looking for date changes, money changes, contingency flips, new parties.
4. Surfaced. If any changes are detected, a "Review changes" card appears on the deal page with the diff.

The review card

Shows every detected change as a before → after pair:

• Closing date: May 15, 2026 → May 29, 2026
• EMD deadline: Apr 25 → Apr 27
• Inspection period: 10 days → 15 days

Plus a preview of the downstream effects — how many tasks would reschedule, how many new tasks would activate, which (if any) would become inapplicable and get skipped.

Two actions:

Apply — the deltas merge into the deal's contract data. Every downstream task re-plans using the new dates. An audit event records the full change. The scan card disappears.

Dismiss — the addendum stays stored, but the contract data doesn't change. Useful when the addendum is just a copy of what's already in your data, or when you disagree with what the AI detected.

What if the scan misses something

The AI is good at catching literal field changes (a new closing date, a different EMD amount). It's weaker at:

• Contingency waivers expressed as prose — "buyer hereby waives the appraisal contingency" may or may not get flagged depending on exact wording
• Computed-offset changes — "extend the inspection period by 5 days" needs to resolve against the acceptance date; the scanner currently treats these as literal dates and may miss
• Completely new document types — a lease-back rider the scanner doesn't have a template for

If you notice a scan missed a real change, open the addendum manually, then edit the affected fields on the deal's Edit page. The edit goes through the same reconciler as a scan-apply, so downstream tasks still re-plan.

When the apply is wrong

See Undoing an applied addendum for the revert path.

Party privacy

The addendum-scan process does NOT share the addendum content outside your deal. It runs on our own AI infrastructure (Claude Haiku for classification, Sonnet for deep scans) — the same pipeline as your original contract extraction.