Direct answer
Save your search as a dynamic list and turn on monitoring. From then on the list rechecks its criteria as property records update, adds the properties that start to match, and drops the ones that stop. In PropertyRadar, two triggers bring those changes to you. New matches fires when a property joins the list. Status changes fires when a property already on the list gets a new transfer, loan, listing or foreclosure, and a new owner arrives as a new transfer.
A dynamic list already reflects its criteria each time you open it. Monitoring means you no longer have to open it. PropertyRadar's monitoring article says a monitored list adds and removes properties automatically as records change. It also keeps a New Since count and filter, so you can see what arrived after a date you pick, and it makes alerts and automations available. A static list can be monitored too. It keeps its membership and still receives status changes on the properties in it.
Setup is short. Save your search as a dynamic list, then choose Add Monitoring in My Lists. Monitoring commits the list for at least five days. Next, open the list's Automations settings, turn on the triggers you want, choose a notification for each, and save. Recent Events then shows what has fired. A day with no events can mean nothing on the list changed, so judge the setup after an event you can verify in the property record.
New matches covers properties entering the list. It fires when a property begins to meet your saved criteria, or when you add one by hand.
Status changes covers events on properties already in the list. The alerts and automations article puts new transfers, new loans, new listings and new foreclosures under this one trigger, along with listing price and status changes and foreclosure status changes. There is no separate owner-change trigger. A new owner reaches you as a new transfer.
One event has no trigger. When a property stops meeting your criteria, a monitored dynamic list removes it and neither trigger fires.
Which trigger catches which event
| Event | Trigger |
|---|---|
| A property starts meeting your saved criteria | New matches |
| A new owner on a property you already track | Status changes, as a new transfer |
| A new loan | Status changes |
| A new listing, or a listing price or status change | Status changes |
| A foreclosure filing, or a change in foreclosure status | Status changes |
| A property stops meeting your criteria | Neither. Monitoring removes it from a dynamic list |
Each trigger can notify you three ways: a mobile push per event, an immediate email per event, or a daily summary email that groups the day's events. PropertyRadar recommends push when timing matters, and it warns that immediate email on a busy list produces a lot of notifications. A daily summary suits a broad list where a morning review is enough.
A trigger can also act on the record. It can set the property's status or star rating, which flags records a person should review, and it can copy the property to a static list. Outreach actions start a direct mail piece or a marketing email to the owner. For other systems, the record can go to another app through Zapier or to a URL you control through a webhook. The webhook payload includes TriggerType, NewRecordType and up to three change fields, which is enough to route a transfer differently from a loan.
One action spends money. A trigger can buy and attach phones or emails once you have accepted the purchase terms for automated buying, and each purchase draws on your contact allowance. On the pricing page, Solo includes 250 phone contacts a month, and additional phone contacts are $0.08 each. Suppose a list produces 400 new matches in a month and the automation buys one phone contact for each. That is 150 contacts beyond the allowance, or $12.
A dynamic list is good at discovery and awkward for a campaign, because a property can drop off it partway through your mailings. Pairing it with a static list solves that.
Suppose a two-person team mails absentee owners in one county. Their discovery list is a monitored dynamic list of 6,000 properties. New matches is set to the daily summary, with an action that copies each match to a static campaign list. They seeded the campaign list with the properties already being mailed, because the copy action applies only to matches from that point on. The campaign list is monitored too, and it is the only list with Status changes turned on. Those alerts go to mobile push, set a review status on the record, and post it to the team's CRM. Running Status changes on one list keeps a single event from producing two notifications.
A few events show how the setup behaves. First, an owner's mailing address changes so that it differs from the property address, and the property now meets the absentee criteria. New matches fires, the property is copied to the campaign list, and it appears in the next daily summary. The team runs its pre-contact checks and adds the owner to that week's mailing.
Later, a deed is recorded on a campaign-list property. Status changes fires as a new transfer, and the team gets a push. Before changing the mailing, they read the transfer type, the document type, the amount and the grantee in the fields PropertyRadar's criteria glossary defines. Then they confirm the grantee on the recorded deed against the county's current ownership record. Some deeds move title without a sale, as when an owner puts a house into a trust, and some transfers carry no amount. A transfer with no sale can still change who to contact, since a trustee may now hold title in place of an individual.
Then a campaign-list property is listed for sale. Status changes fires as a new listing, and the owner comes out of the off-market mailing. A foreclosure filing arrives the same way, and the team pulls the recorded notice at the county before acting on a sale date.
The static list also covers the event that has no trigger. A property whose records no longer meet the absentee criteria leaves the discovery list and stays on the campaign list, where the team can review it and remove it by hand. The campaign list shows the latest owner in PropertyRadar's data, and that can change after a letter goes out. A dated export preserves the list as it stood that day. The mail or contact history for each piece is the record of who was written to.
Three separate delays sit between a county recording and your phone. The first runs from the recording to the day the record reaches PropertyRadar. The glossary tracks it with two fields: the county's recording date and Transfer Published Date, the day PropertyRadar received the record. PropertyRadar publishes no fixed figure for that gap. Comparing the two dates on recent transfers in your county shows the range you have seen so far.
The second delay is the automation. The webhook article says an automation can take up to 30 minutes to run after a trigger, and usually takes less. The third is your own notification choice, since a daily summary holds events for the digest. For anything with a deadline, such as a foreclosure sale date, use a per-event notification and read the dates from the recorded notice at the county.
A single monitored list holds at most 10,000 properties. PropertyRadar's monitoring article says add-ons raise the account's total and can't raise that per-list cap. The account total is set by the plan. The pricing page lists 10,000 monitored properties on Solo, 25,000 on Team and 50,000 on Business. Solo is $119 a month, or $99 a month on annual billing. A property that sits on two monitored lists counts once toward the total, so the discovery and campaign lists above don't double the count.
Suppose a county-wide search returns 14,000 properties. It has to be split into two lists, by ZIP code for example, with each under 10,000. The combined 14,000 is over Solo's allowance, so the account needs Team's 25,000 or a monitoring add-on. Each list carries its own automations, so set the same triggers and actions on both.