Verification starts with defining what counts as evidence

“Verify this” sounds clear until the project has to decide what verification actually means.

A phone number appearing on three directory pages may look convincing. But if all three copied the same old listing, the repetition does not make the number current.

The same problem appears with addresses, company names, product details, and almost any other business field.

Before checking a value, define what kind of evidence would be strong enough to support it.

For one project, the company’s own website may be enough. Another may require an official registry, an original manufacturer page, a government record, or agreement between independent sources.

The standard should match the consequence of being wrong.

A low-stakes research list may tolerate more uncertainty than a dataset being used for financial reporting, compliance work, or a costly outreach campaign. Treating both projects as if they need the same proof can waste effort in one direction and create risk in the other.

It also helps to distinguish “verified” from “found.” Finding a value means the information appeared somewhere. Verification means the evidence met the standard chosen for the project.

That definition should exist before the research begins, not after the spreadsheet is filled.

When the evidence rule is clear, verification becomes a repeatable decision instead of a vague feeling that a record looks right.