What is the difference between a dynamic property list and a static property list?

A dynamic property list stores search criteria rather than a fixed set of parcels, so the same list can return a different count each time it re-evaluates.[1] PropertyRadar's help center describes dynamic lists as updated automatically when monitored and static lists as created by manually adding properties, with no search criteria attached.[1] A static list holds whatever was put into it until somebody deletes a row, which means it cannot be re-derived inside the platform once the criteria that produced it are gone.

An unmonitored dynamic list updates according to its saved criteria only once you open it.[2] A monitored one adds and removes properties on its own and maintains a New Since count on the card.[2] Both reflect the properties meeting their criteria, so monitoring changes the timing rather than the membership rule. PropertyRadar marks the three shapes in the interface with a lightning bolt on dynamic lists, a diamond icon on static ones, and a download icon on imports.[3]

An imported list sits between the two, because it starts as a file you upload and each import matches those records against the platform's own data before anything lands in the account.[1] The file is frozen at the moment of upload while the match result reflects the platform's records on the day the import ran, which gives an import a static shape and a dated dependency at once.

Confusing the two costs money in both directions, and an export is the easiest place to see it. A PropertyRadar Solo plan includes 10,000 monthly exports and bills 2 cents a record past that ceiling, so re-pulling the same file every time a campaign needs it turns a free re-download into a recurring line item.[5] What decides the shape is whether the set has to keep changing after outreach starts, because a prospecting queue and a mail file reconciled against responses two months later want opposite behavior from the same records.

A monitored list moves on two triggers that PropertyRadar names. New matches fire when a property is added to the list, and status changes fire on new transfers and loans, on new listings and foreclosures, and on movement in listing status, listing price, or foreclosure status.[4] Neither trigger carries a published latency figure, and the monitoring documentation describes what the platform adds and removes without stating how long a county record takes to reach the list.[2]

The slowest source in the chain sets the refresh you actually experience, and that is usually the county rather than the platform. Harris County's real property search tells filers it may take 1 to 2 business days after a document is processed for the recording to appear in a search inquiry, and the same page states that the online database does not constitute the official repository of real property records and may not reflect their complete or unaltered contents.[6] A dynamic list keyed on new deeds inherits that delay before its criteria ever run.

HUD receives USPS address vacancy data on a quarterly basis.[7] An address counts as vacant only once delivery staff on urban routes have identified it as not collecting mail for 90 days or longer.[7] A monitored list filtered on vacancy can therefore re-evaluate every day and still surface a property that emptied out five months earlier, because the criterion moves no faster than the quarterly file behind it. Fields drawn from recorder documents run on a different clock than fields drawn from postal operations, which is why a single alert should never be read as a same-day signal about the property.

The criteria themselves change without leaving a mark on the record, because editing a saved search changes what every earlier count meant. A card showing 1,400 parcels in June and 900 in August might be reporting a shift in the market or a filter somebody tightened, with nothing on the list to say which. Copying a list before you edit it is the documented way to keep both versions,[3] and it is the closest thing to version control this workflow offers.

A static list is the only version of a campaign you can reproduce after the fact. A dynamic list re-derives itself, so a parcel that dropped out last week leaves no trace on the card. Anyone reconciling responses to a mail drop needs the set as it stood on the day the file went to print, since the live list six weeks later holds parcels that were never mailed and is missing ones that were.

The Telemarketing Sales Rule requires most sellers and telemarketers to keep records tied to their telemarketing activities for two years from the date the record is produced.[8] The FTC defines that category to include sales records and all verifiable authorizations or records of express informed consent.[8] A regenerating list satisfies none of that on its own, since criteria that produced a call file in March return a different set of parcels in August.

A frozen call file has a shelf life that the recordkeeping rule does nothing to extend. 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,[9] and the FCC's rules require an entity-specific do-not-call request to be honored within 10 business days of receipt and kept honored for 5 years from the date it was made.[10] The archived file answers what was worked and when, while a re-scrubbed copy answers who may be dialed this week, so a calling operation ends up keeping both and treating the archive as read-only.

A BiggerPockets thread on list stacking shows investors building the frozen half in spreadsheets.[14] The method runs a tab per source list, standardized formatting, a type tag on every row, and a merge sorted by address or owner name, which is a static list with a manual refresh cycle bolted on.[14] County governments publish the same shape, and Mecklenburg County's delinquent taxpayer list carries an explicit as-of date on each monthly release along with a note that any change in status appears in the next list.[11]

PropertyRadar meters monitored properties against a plan allowance, which makes monitoring the cost driver on the dynamic side. The allowance runs 10,000 properties on Solo at $119 a month, 25,000 on Team at $249, and 50,000 on Business at $599.[5] Monitoring the same property across several lists counts as one monitored record toward that allowance, and a single monitored list caps at 10,000 properties, a limit the documentation says cannot be expanded even with add-ons.[2] A dynamic list left unmonitored can run past 10,000 records, so the cap constrains automation rather than list size.

Exports are the metered resource on the static side, at 10,000, 25,000, or 50,000 records a month by plan.[5] Overage bills at 2 cents, 1.5 cents, or 1 cent a record.[5] Re-downloading an export you already purchased costs nothing and does not touch the monthly limit, while re-running the same export from scratch counts against the quota a second time.[3] Unused allowance does not roll over, since exports and included contacts reset on the renewal date.[5]

A team exporting 40,000 records one month and 2,000 the next pays for the peak twice. The bill lands once in the plan tier and once in overage, which is the arithmetic behind sizing a plan on the busiest month. Contacts sit on their own meter separate from exports, so heavy contact purchasing does not eat into the export pool.[5]

PropStream meters the same behavior as Lead Automator, which monitors 50,000 properties on the Pro plan and 120,000 on Elite.[12] The pricing page describes it as updating and refining lead lists based on custom filters.[12] PropStream also counts monthly saves and exports together at 25,000 on Essentials, 50,000 on Pro, and 100,000 on Elite, and unused saves and exports expire when the account resets each month.[12] Saving a property to watch it and exporting it to mail it draw down the same pool there, so a buyer who monitors heavily has less room to export.

Ongoing prospecting takes the dynamic version, because the point of saved criteria is catching parcels that failed to qualify last month and qualify now. A direct mail drop takes the frozen version, because responses arrive over weeks and the mail file has to still exist when a postcard comes back with a phone number written on it.

A calling campaign takes both at once, because the dynamic list decides who belongs in the queue this week. The exported file records who was dialed and what the phone column said at the time. Registry access runs on the seller's own Subscription Account Number, which the FTC requires each seller to hold separately from any telemarketer working on its behalf,[9] so the scrub and the 31-day resynchronization sit with you rather than with the data platform. An exported phone column that has been sitting in a spreadsheet for six weeks has aged past that window and needs a fresh pass before anyone dials it.

A list that leaves the platform for a mail house or a dialer vendor becomes static the moment it is exported. Handoffs therefore settle the question more often than campaign type does, and the copy the vendor holds stops matching the account within days. Naming every export with the date you pulled it keeps two people from arguing over which file a set of results belongs to.

The pattern that holds up under both cost and audit runs the criteria live and freezes only what leaves. A monitored list stays the working surface for as long as the market is worth watching,[2] while every campaign that touches an owner gets its own export saved with the date it was pulled.

PropertyRadar cautions users about immediate alerts, noting that lists generating large volumes of notifications are easy to create by accident.[4] That caution is the practical ceiling on how many criteria sets one person can monitor at once, and it argues for two tight criteria sets over one broad set that burns the allowance on parcels nobody will call.[2]

Records assembled from a driving route or a county portal have no criteria behind them, and that is the case that breaks the pattern. The file itself is the only copy, which puts the premium on where it is stored and who holds the current version. DealMachine builds that shape in the field, tagging properties along a driven route and showing a live map of the streets covered, the stops made, and the properties tagged.[13] A tagged route is a fixed set by construction, because a person chose each parcel by looking at a roof, and no criteria change will add or remove one afterward.

A dynamic list is not a real-time feed. Neither monitoring trigger carries a published latency figure, and the documentation describes what the platform adds and removes without stating how long a county record takes to reach the list.[2]

A dynamic list is also not an audit trail, since editing a saved search rewrites the meaning of every count the list produced before the edit. Nothing on the card records that the filter changed, which is why copying a list before editing it is the documented way to keep both versions.[3]

An imported list is not a dynamic list, even though it arrives through the platform and gets matched against the platform's records.[1] The uploaded file carries no criteria, so it behaves like a static set with a match result dated to the day the import ran. A copied list is the opposite case, because the copy inherits dynamic behavior and freezes nothing by itself.[3]