Provenance is the history behind a data value. A company website, a professional profile, a licensing record and a supplier enrichment process can establish different facts. Understanding that history makes a sample easier to audit and a disputed record easier to resolve.
A source link supports inspection; it does not by itself prove current accuracy, permission or complete coverage.
For a national starting point, explore our USA real estate email list and choose the audience and market for your brief.
Match evidence to the field
A licensing source may establish a recorded credential but not a current business email. A brokerage biography may describe employment and a contact route but leave license status unstated. Ask which evidence supports each important attribute.
A single row can combine several sources. Request a source category or field-level explanation where possible, rather than treating one URL as support for every populated column.
Understand collection and transformation
Ask whether an address was published, supplied by a licensed provider, inferred from a pattern or generated through another method. Preserve that distinction even if a later technical check passes.
Also ask about normalization: parsed names, role mapping, county assignment and company matching. A derived field can be useful, but buyers should be able to distinguish it from a value explicitly stated by the professional.
Keep time and access in context
A source may change or disappear after collection. Record the observation date and any later review. A current page that no longer mentions an attribute does not automatically explain what was true earlier, so preserve the history needed for investigation.
Public visibility alone does not settle all use rights, contract terms or outreach obligations. Review the provider’s stated sourcing and usage terms independently of whether a link is accessible.
Use provenance to resolve a mismatch
When a sample contains a conflicting role or company, compare the source wording, collection date and transformation rule. Classify the issue as an outdated observation, matching error, unsupported inference or unresolved conflict.
Ask how corrections affect the final file and future editions. A provider that can explain the path from source to field is easier to evaluate than one that responds only with a broad accuracy percentage.
- Original source or source category.
- Date observed and date last reviewed.
- Published versus inferred values.
- Normalization and conflict-resolution rules.
Make source questions part of the review.
Ask which source and observation information applies to the proposed selection, alongside the actual checks and permitted use.
Explore the quality checklist