How can monitored property lists automatically surface new matches and owner-status changes?

Monitoring is a switch on a dynamic list, and turning it on makes the platform add and remove properties automatically [2]. The same switch keeps a New Since count on the list card and opens the automation settings where triggers and actions are configured [2]. A dynamic list already reflects its saved criteria whether monitoring runs or not, so what monitoring adds is the trigger surface plus a running count of what arrived since your last look.

How the criteria get re-evaluated

Every parcel on a monitored list is re-evaluated against the whole criteria set on each pass. A parcel can therefore arrive for a reason you were not watching, and a criteria set combining absentee ownership with 50% estimated equity picks up a new match when the equity estimate crosses that line, when a mailing address stops matching the site address, or when a parcel excluded for an active listing sees that listing expire. The New Since count reports that something arrived without reporting which criterion moved, so your first step on any new match is opening the profile and finding the field that changed.

Removals run on the same evaluation and get no announcement at all. An owner who pays off a delinquent tax year drops out of a delinquency watchlist quietly, taking any note or star rating attached to that record out of your working view. Teams that mail from monitored lists keep a dated export of every campaign because a parcel that left the list still received the postcard.

What sits behind each event

The document behind an event decides whether it deserves an action. A recorded deed carries a filing date you can check at the county, while a modeled field moves whenever the vendor refreshes its model. The criteria glossary warns that listing data comes from third parties and may be incomplete [5].

An automation can also be set to purchase and append a phone number on every triggered event [1]. That purchase draws against a monthly allowance of 250 contacts on the Solo plan and bills $0.08 per contact past that limit [3].

A trigger can drive three kinds of action [1]. The alert side offers a mobile push notification, a daily summary email batching the day's events into one message, or an immediate email per event [1]. The data side can set a status, set an interest level in stars, add the parcel to a static list, or purchase and append a phone number or email address [1].

A webhook carries the event to software you build, and its payload names what fired the automation in a TriggerType field [4]. The payload describes the change itself through NewRecordType and NewAttribute values plus up to 3 numbered Change fields [4].

PropertyRadar also publishes a Zapier app with a property match or update trigger and an import action [6]. That route puts a row in a spreadsheet or a task in a CRM without any code, although the county criteria still have to be re-run somewhere upstream of both [6].

An automation that purchases and appends a phone number asks you to accept three statements of the purchase agreement first [1]. That gate is the platform's own guard against an unattended list spending your contact allowance [1]. Any appended number still needs a suppression pass before a dialer touches it, because sellers using the National Do Not Call Registry must synchronize their calling lists with an updated version of the registry at least every 31 days [8].

Delivery of a triggered automation can take up to 30 minutes, which PropertyRadar's webhook troubleshooting attributes to background alert agents and variable server load [4]. Nothing in the monitoring documentation states how often the records behind a list are re-evaluated, so the gap between a county update and a new match has no published figure behind it [2].

Any alert keyed on tax status inherits the county's publication cycle [9]. Mecklenburg County publishes its delinquent taxpayer list monthly and states that each release reflects the tax record as of one date, with any change in status appearing in the next list [9]. An owner who pays in full on the 6th stays on the published file until the following month, so a platform re-reading its own copy every hour would still show a stale status.

San Bernardino County's assessor-recorder takes the owner's mailing address from the Preliminary Change of Ownership Report filed at recording [10]. That address stays in use until the owner signs a request for a change of address, so an absentee owner who relocates twice without filing leaves the county file unchanged [10].

PropertyRadar's Solo plan monitors 10,000 properties at $119 a month, Team 25,000 at $249, and Business 50,000 at $599 [3]. A single monitored list is limited to 10,000 properties whichever plan pays for it, and the documentation says that ceiling cannot be expanded with add-ons [2]. If you watch a metro holding 60,000 absentee parcels, narrowing the criteria is the only move the plan tiers allow.

Watching the same parcel from more than one list counts once toward the monthly allowance [2]. A team running a tax-delinquent watchlist and a high-equity watchlist across the same ZIP codes pays for the overlap a single time, which favors several narrow lists over one broad one [2].

PropStream meters the same capability through Lead Automator, tracking 50,000 properties on the $199 Pro plan and 120,000 on Elite [7]. Its pricing page describes the feature as updating and refining lead lists against custom filters, and the $99 Essentials plan carries no Lead Automator allowance [7]. Continuous re-evaluation on PropStream therefore starts a tier up or through the Connect add-on [7].

Append automations spend a separate meter from the monitoring allowance [3]. Included contacts run 250 a month on Solo, 500 on Team, and 2,500 on Business before per-contact pricing of $0.08, $0.06, and $0.04 applies [3]. A monitored list producing 400 new matches in a month on the Solo plan therefore bills 150 appended contacts at 8 cents each on top of the subscription.

A status change on a transfer does not establish that the property sold [5]. The criteria glossary defines Purchase Amount as the amount of the most recent change of ownership and notes that not all changes of ownership carry an amount [5]. A deed moving a parcel into the owner's revocable trust, a quitclaim between spouses, or a transfer to an heir all record as ownership changes with no sale price attached.

San Bernardino County charges documentary transfer tax at $0.55 per $500 of value on taxable conveyances above $100 [11]. A recorded deed carrying little or no transfer tax therefore points at a conveyance that moved title without moving the property [11].

A new loan recorded against the parcel fires the same status-change trigger, and a refinance produces one every time [1]. An equity-keyed watchlist can therefore alert on a parcel whose estimated equity just fell, which inverts the signal your criteria were built to catch. Checking the transfer type and the recorded amount before a parcel enters an outreach queue is a short step, and it keeps a refinanced owner out of a high-equity mailing.

Immediate email alerts carry an explicit caution in the automation documentation, which notes how easily a list with lots of notifications gets created [1]. A monitored list firing 30 immediate emails a day trains you to archive them on sight, and the two or three that mattered get archived with the rest. The daily summary email exists for people who want to stay informed without acting the same hour [1].

Criteria drift shows up as a list that got quieter, and the cause can be a tightened filter or a cooling market. A saved search edited from 50% minimum equity to 60% surfaces fewer new matches every month afterward, so recording the date and the reason for every criteria edit is the cheapest way to tell the two apart later.

Immediate alerts against a daily digest

Foreclosure status changes and new transfers earn an immediate alert on most desks, since both carry a filing date and a deadline behind them [1]. New matches on a broad criteria set belong in the daily digest, where one person reviews them in a single pass [1].

List size against alert volume

A monitored list stops at 10,000 properties, and the plan allowance limits the total across every list your account runs [2][3]. Two narrow watchlists over the same ZIP codes draw the same allowance as one broad list covering both, so sizing is the second decision after the trigger rules.

Automatic appends against manual pulls

An append automation removes a person from the loop and spends $0.08 per contact past the Solo allowance of 250 a month [3]. Pulling contacts by hand from the New Since view costs about an hour a week and keeps a check between the trigger and the invoice.

Verification rules against trigger rules

Every event reaching an outreach queue should carry the document type and the recorded amount alongside it, which the webhook payload supports through its TriggerType and NewAttribute fields [4]. A CRM field holding those two values turns a status-change alert into something a caller can act on without reopening the property profile.

Ordering the queue after the alerts land is the part no automation settles, and it comes up repeatedly among investors discussing outbound calling on public forums [12]. Forum practice is evidence about how the work gets sequenced and carries nothing about conversion rates.

It is not a real-time feed

Delivery of a triggered automation can take up to 30 minutes, and no interval for re-evaluating the underlying records appears in the monitoring documentation [4][2]. A monitored list reports changes on the platform's own clock, which means anything with a same-day deadline still needs a separate check against the county record.

It is not the county record

A foreclosure status change or a new transfer on a list is a copy of a filing, and the recorder holds the document itself. Confirming a scheduled sale date with the county before you act takes a phone call, and the platform copy can trail the filing by the delivery window described above.

It is not a contact-data monitor

Nothing in the automation settings fires on a new mailing address, a new phone number, or a new email for an owner [1]. Those changes reach you only when they move a parcel into or out of your saved criteria, so anything narrower has to be caught by comparing a fresh export against the previous one.