What is Data Refresh?

Company data & APIs
Data freshness & historical state
3 min read

The short answer

A data refresh retrieves or recomputes information to update a retained dataset or view.

Data Refresh: why it matters

Automated company-data workflows need clear meanings and traceable transformations. An operation that runs successfully can still produce a result that is unsuitable for the intended business question.

How to assess it in practice

For data refresh, retain the specific source, scope and effective date, and distinguish verified facts from assumptions before using the result in a decision. Start by defining the question the team needs to answer. Identify the relevant record or evidence, check its scope and date, and retain the reasoning behind the result. If evidence conflicts, keep that conflict visible for review.

Worked example

Illustrative workflow: a team reviewing a business adds a separate check for data refresh. The reviewer’s task is to for data refresh, retain the specific source, scope and effective date, and distinguish verified facts from assumptions before using the result in a decision. The outcome is recorded together with the supporting evidence; an unresolved question stays open rather than being converted into a positive result.

Illustrative scenario

A refresh retrieves new status information but fails to retrieve accounts. Mark those field states separately instead of stamping the entire record as fully refreshed.

Distinctions that matter

Data Refresh belongs to the data freshness & historical state topic family. Read Point-in-Time Data alongside it to understand the adjacent question. Each page has its own intended scope; shared context does not make the concepts equivalent.

Evidence and review output

Review these

Event and effective timestamps
Publication and ingestion context
Corrections and refresh outcomes

The review should produce

A time-aware record that supports both current use and reconstruction of earlier evidence states.

Across this family

Time has several meanings in company data: occurrence, effectiveness, publication, ingestion and retrieval. Historical analysis and current freshness need different views of those dates. Preserve corrections and delivery gaps so later information does not silently rewrite what was known earlier.

A note from practice

Refresh policies should prioritise the age and importance of specific attributes rather than update every field blindly. Retain successful updates and explicit failures so an attempted refresh is not mistaken for current evidence.

Limits and common mistakes

The practical boundary is important: For data refresh, retain the specific source, scope and effective date, and distinguish verified facts from assumptions before using the result in a decision. Do not substitute a related label for this check or assume that missing information is a negative finding. Source-specific and jurisdiction-specific rules require their own review.

Frequently asked questions

Which evidence should I review?

For this topic, focus on event and effective timestamps, publication and ingestion context, corrections and refresh outcomes. The relevant source and dates should be retained with the finding.

How is Data Refresh different from Data Latency?

Data latency is the delay between an event or source change and its availability to a consumer. The distinction matters because the evidence needed for that concept may not resolve the question addressed on this page.

What should the result of the review contain?

A time-aware record that supports both current use and reconstruction of earlier evidence states. Preserve material conflicts instead of replacing them with an unexplained success flag.

Continue learning

Explore Data freshness & historical state

See the registry record behind every answer.

Primary, government-sourced data on 600M+ companies in 200+ countries, with full source attribution.

Book a demo Talk to us