How Move Detection Works

DeedPulse monitors public deed recordings at supported counties and converts raw filings into structured move events you can act on.

The pipeline, end to end

1. Ingest. We pull new deed recordings from the county register of deeds on a rolling schedule — typically within hours of recording.
2. Parse. Each recording is normalized: grantor, grantee, legal description, sale price, instrument type, recording date.
3. Classify. The event is tagged by type (Transfer, New Construction, Refinance, Foreclosure, Other) using a combination of document codes and content classifiers.
4. Enrich. We match the property to address, parcel, and owner data — and attach attributes like year built, square footage, and sale price when available.
5. Route. The event is matched against every active territory and campaign on your account. Matches appear in your dashboard and trigger outreach per your campaign rules.

Latency

For counties with a modern recording pipeline, events typically land in your dashboard within 4–12 hours of the recording being made public. Some counties run overnight batches and can be up to 24 hours behind. Latency per county is shown on the Supported counties page.

Accuracy

Classification is continuously audited. If a deed event is mislabeled, flag it from the event detail page and the correction feeds back into our classifier. We publish accuracy metrics per event type per county quarterly.

What DeedPulse does not do

• We do not scrape MLS or private listing data.
• We do not use skip tracing to surface non-public contact info beyond what's legally available in the record and standard enrichment.
• We do not use rented consumer data or credit data.

Everything DeedPulse works with is rooted in the public record.