Knock on Door
← Back to hub
DRAFTA working draft — not yet checked against reality by a person. Read it, but confirm before you rely on it.

Lead Intake / Foreclosure-Notice Scrape

Lead lifecycle — from foreclosure-notice scrape through cleaning and bucketing into the route. · tap to zoom & pan
Pulls the day's fresh foreclosure notices, turns them into clean leads, and dedups so nothing gets knocked twice or missed.
WhoJason
WhenEvery morning before the day's route is built, or as a catch up pass after a source outage
Time~20 min
THE ONE RULESpeed to lead is the whole game, being first to a same day notice beats almost everything else

The steps · 7

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7

Tap a step to open its detail.

ALWAYSDedup against existing records by address with parcel number as a fallback
ALWAYSSend new addresses on to enrichment rather than pulling owner, equity, or phones here
Why this matters

Pull the day's fresh foreclosure notices before anyone else does, turn raw notices into clean working leads, and make sure nothing gets knocked twice or missed. Speed to lead is the whole game — being first to a same-day notice is worth more than almost anything else in the pipeline.

When to use this

Every morning before the day's route is built (see sop-kod-daily-route). Also any time a source has been down and needs a catch-up pass.

Before you start
  • Access to our foreclosure-notice sources set up and working.
  • Target cities/counties list confirmed current (the standing Rialto-area rotation across San Bernardino / Riverside counties).
  • The intake destination (our system) reachable so new notices can land.
How to know it worked
  • The day's sources were pulled (or a documented fallback was used for any that were down).
  • Every new notice produced exactly one lead/property/case — spot-check for duplicates on a shared address.
  • Any case that changed status shows the correct new state.
  • New or gold-bucket leads fired a same-day alert.
If it goes sideways
  • A source is down or blocking. Don't force it — use a fallback source for the same underlying data and move on.
  • The same property keeps creating a "new" lead. The dedup is address-first with parcel-number fallback; normalize the address (unit numbers, abbreviations) if slight variations slip through.
  • A must-hit lead didn't get a same-day alert. Treat a missing same-day alert as a gap to flag — same-day is the entire point of this step.
  • Paid-list data looks stale. Paid lists can run ~2 weeks behind, which is dangerous in short-timeline states. Check any paid lead against a live source before trusting it.

Linked resources