Issued, observed, updated: why permit dates matter.
Learn the difference between permit issue dates, observation dates, source updates, and historical backfills before using construction data for alerts or sales research.
“New” needs a definition
Imagine a permit issued in April appears in a dataset in September. Is it a new permit? It is new to that dataset, but its source issue date says something else. Both dates can be useful. Combining them into a single “new” label makes the record harder to interpret.
For teams researching construction activity, freshness is a sequence: an event happens, an authority records or publishes it, a system retrieves the record, and a customer receives it. A fast retrieval schedule cannot remove a delay at the source.
Keep the dates separate
An application date describes a submission stage. An issue date describes an authorization stage. A completion or final date, when the authority provides one, describes another stage. An observation date describes when a particular system first saw the record. An update timestamp may describe a source change or an internal processing event.
Always check the source’s definitions. A date-only field should remain a date instead of shifting a day when displayed in another time zone. Missing dates should remain missing. Substituting another date may make a table easier to sort while obscuring what the record actually says.
Compare issue and retrieval dates in a real permit walkthrough →
Corrections are useful, but different
An agency might correct an address, a business name, or a description. A data provider might improve its trade classification. Those changes can be important for record quality without representing a new project or a new sales opportunity.
A monitoring workflow should explain what changed and preserve enough context for a user to interpret it. For software consumers, a stable reference and an explicit change record can be more useful than silently replacing an entire snapshot.
Do not let backfills inflate the story
A historical backfill adds older records that were not previously available in a system. It may improve research coverage. It should not automatically enter a queue intended to show recent construction activity.
The same issue affects trends. If a platform adds another jurisdiction or extends history, observed permit counts can increase even when underlying market activity does not. Compare a consistent source scope and date definition before interpreting a change as growth.
Ask a few specific freshness questions
Which timestamp does this filter use? When did the source last publish successfully? When was the record retrieved? Does the update include newly discovered history? Can a source failure be distinguished from zero observed activity?
For an alert or export, ask what happens after a failed delivery and how repeated events are identified. Reliable delivery includes a clear retry behavior and a way to recognize duplicates. A label like “real time” does not answer any of these questions by itself.
Why it matters for ObservedWork
Source activity, observations, and corrections answer different questions. ObservedWork keeps those distinctions central to contractor intelligence. Explore our coverage approach and use the questions in this guide to evaluate the signals behind your next account.
Sources & further reading
The primary sources below support the definitions and jurisdiction-specific examples. Checklists, illustrative examples, and research workflows are ObservedWork’s editorial guidance. Sources reviewed September 7, 2026.