A record can be perfectly formatted and still be too old to trust

A polished record earns confidence quickly. The company name is consistently capitalized. The address parses cleanly into street, city, region, and postal code. The phone number follows a valid pattern. Dates sort correctly. Nothing looks broken.

But formatting answers a narrow question: can people and systems read this field consistently? It does not answer whether the field still describes reality.

A headquarters address verified 30 months ago may be impeccably standardized and no longer correct. A contact record can have a properly cased name, a plausible title, and a valid-looking work email while describing someone who changed roles during a reorganization. A dashboard can refresh every morning while displaying revenue from a fiscal period that ended months ago.

Those are not formatting failures. They are freshness failures.

Data quality is often discussed through accuracy, completeness, and consistency. Timeliness belongs in that conversation too. More importantly, it has to be judged against the decision being made. A two-year-old annual revenue figure may be useful for historical context. That same figure may be unsuitable for ranking accounts for a current sales campaign.

The useful question is not just, “Is this row clean?” It is: “What does this row claim was true, as of when, and is that recent enough for this use?”

One date is rarely enough

A generic column called “Date” creates false clarity. A consequential record often needs several dates because each one answers a different question.

Fact as of identifies when the fact applied or was observed. For an address, it may be the day the location was confirmed. For revenue, it may be the end of the reporting period.

Source published identifies when a source made the information available. This matters, but publication is not proof that the underlying fact is new.

Verified on identifies when your organization last checked the information against appropriate evidence. It tells a reader something about the age of the organization’s confidence, not necessarily the age of the fact itself.

Review by identifies when the record should next be reconsidered for its intended use.

These labels may feel like extra administrative work until a record is used in a present-tense decision. Then they make uncertainty visible before it becomes an avoidable mistake.

Consider public financial filings. Data may be delivered or refreshed quickly after a filing is disseminated, while individual figures remain tied to different reporting periods. A recent download date means the copy is recent. It does not mean every fact in the copy describes the present. The reporting-period date must travel with the value.

The same distinction applies well beyond financial data. A profile page updated yesterday may still repeat an older executive title. A supplier file received this week may carry operating-status information that was last checked last year.

Do not let a download timestamp impersonate evidence

“Downloaded today” is useful provenance. It establishes when a copy entered a system. It does not establish when the source confirmed the address, contact, price, license, or operating status in the record.

This mix-up happens because system timestamps are easy to capture and easy to sort. Evidence dates are often harder. They may be missing, embedded in a document, or attached to one field but not another.

That inconvenience is a reason to preserve the uncertainty, not to erase it.

When no meaningful as-of or verification date is available, label freshness as unknown or unverified. That does not prove the record is wrong. It means no one can independently assess whether it is current enough for the proposed decision.

An unsupported “current” label is more dangerous than an explicit unknown because it encourages action without a visible basis for confidence.

Set freshness rules around consequences

There is no universal age at which data becomes stale. A sensible review window depends on what can change, how quickly it tends to change, the authority of the source, and the cost of acting on an outdated fact.

Executive contacts, operating status, pricing, and regulated facts usually deserve shorter windows because errors can quickly affect outreach, procurement, compliance, or eligibility decisions. Historical financial context and long-lived reference attributes may remain useful much longer.

A practical workflow can be modest:

1. Define the decision the field will support. 2. Identify the evidence date that matters for that field. 3. Set an acceptable age for that decision, with room for source-specific judgment. 4. Preserve the relevant dates beside the record. 5. Send records with missing, overdue, or contradicted evidence into review instead of treating them as current by default.

For a current outreach list, a team might sort records first by missing verification date and then by oldest verification date. That is often more useful than sorting by completeness. The most complete-looking rows can be the most misleading if their evidence is old.

Older records do not need to be discarded. They may retain real historical, analytical, or audit value. The key is to stop them from silently feeding present-tense claims, rankings, outreach lists, or automated decisions.

Good formatting still matters. It makes records easier to compare, join, filter, and use. It just cannot tell you whether the world described by the record has moved on. Make the age of evidence visible, and a clean row becomes easier to trust for the right reason.