Regrid tracks when it most recently refreshed parcel data from its source through ll_last_refresh and publishes geography-level refresh information at the county or county-equivalent level.

That is an important starting point.

But it should not automatically be interpreted as every field in this parcel record was updated on this date.

Different elements of parcel data may represent different reporting periods or update processes.

That is why evaluating currency should go beyond a coverage or refresh report and include the data itself.

Important attributes can provide additional context about currency.

For example, fields such as tax year or transaction dates tell you something different from a general source-refresh date.

If tax information matters to your workflow, ask: Which tax year does this record represent?

If transactions matter, examine the transaction dates themselves.

A sophisticated evaluation therefore looks at both:

Source currency: When did the provider most recently refresh the source data?

Attribute-level currency: What period or event does the specific field you depend on represent?

Those two answers are related, but they are not necessarily the same.

Parcel records can contain information produced through different source processes.

That means important elements within the same record may not all reflect the same point in time.

When evaluating a dataset, ask:

• • • Which fields matter most to our workflow?
    • What date or reporting period does each one represent?
    • Could some fields be older than the overall source refresh suggests?
    • How is that difference represented in the data?

This is more useful than assigning one universal “freshness” date to the entire parcel record.

Related datasets may have their own sources and refresh schedules.

A matched or enriched dataset should therefore not automatically be assumed to have the same currency as the underlying parcel record.

If an enrichment is important to your workflow, ask:

• • • When was the parcel source refreshed?
    • When was the matched or enriched dataset refreshed?
    • Does that dataset expose its own currency information?
    • Which of those dates is most relevant to the decision you are making?

A newer date is useful only in context.

Some parcel attributes can change frequently, while others may remain stable for long periods.

The most recent date is only useful when you understand what it represents. Some parcel attributes change frequently, while others may remain stable for long periods. Currency should therefore be judged against the needs of the workflow rather than treated as a standalone quality score.

That keeps currency evaluation focused on the actual workflow rather than treating the newest timestamp as a quality score on its own.

When comparing providers, ask:

• • • When was data for the geographies we care about last refreshed?
    • What does that refresh date actually represent?
    • Which attributes have their own dates or reporting periods?
    • Do key fields such as tax year or transaction dates provide additional currency context?
    • Do matched or enriched datasets update separately?
    • If different elements update at different times, how is that represented?
    • Is the level of currency appropriate for our use case?

The goal is to understand the currency of the information that matters, not simply to identify the newest date in the dataset.

For base parcel data, Regrid uses ll_last_refresh to show when it most recently refreshed data from the source and publishes refresh information at the county or county-equivalent level. Attributes such as tax year and transaction dates can provide additional time context within the data itself, while separate matched datasets have their own currency information where relevant.

Together, those signals let teams evaluate the currency of the particular fields and datasets their workflow depends on rather than relying on a single freshness date.

The broader lesson is that parcel-data quality depends on understanding not just how recently data was refreshed, but whether the information that matters to your workflow is current enough, complete enough, and transparent enough to support the decisions you need to make.

🔗 Learn more: How to evaluate parcel data quality: A buyer’s guide

📄 See which counties Regrid updated in recent releases