A public business dataset can have clean columns, credible provenance, and thousands of records—and still offer a misleading picture of a market.
The problem is often selection bias. It begins before anyone calculates an average, ranks industries, or maps a geographic pattern. Some businesses had a better chance than others of appearing in the file.
The practical question is not only, “What does this dataset say?” It is also: What had to be true for a business to get into it?
That admission rule may be obvious. A file might cover grant recipients, registered firms, businesses with employees, or survey respondents. In other cases, it is less visible: an online directory may depend on a business maintaining a web listing, while a company list may depend on voluntary disclosure.
A dataset can accurately describe the businesses it contains while failing to represent all businesses a reader has in mind.
The list is not necessarily the market
Suppose a city has 80 businesses in a target market: 20 retailers and 60 service firms. An online directory includes 15 retailers and 15 service firms.
Within the directory, retail makes up 50% of listed businesses. In the actual target market, retail represents 25%.
Nothing needs to be wrong with the individual records for this result to mislead. The directory may list retailers at a much higher rate than service firms. Cleaning names, removing duplicates, and building a better chart will not fix that underlying coverage difference.
This is the central risk of selection bias: the observed group differs from the population a decision is meant to describe.
The relevant population must also be defined carefully. “Businesses” can mean legal entities, tax-reporting units, employer firms, physical establishments, storefronts, or nonemployer businesses. Those units produce different counts and different market stories.
Even large official programs have scope boundaries. The Census Bureau’s Statistics of U.S. Businesses program, for example, is based on employer establishments and excludes several categories, including self-employed individuals and most government employees. Its documentation also identifies possible undercoverage of smaller establishments in multi-unit companies.
That does not make the data poor. It means the right claim is specific to its defined universe.
When missing records become a serious problem
No public dataset captures everything at every moment. A business may be absent because it opened recently, filed late, changed names, was difficult to match, or has not yet been processed.
Selection bias becomes more consequential when the chance of inclusion is related to the attribute being measured.
If larger firms are more likely to be listed and the analysis concerns revenue, employment, or growth, the observed average may be too high for the broader market. If smaller businesses are less likely to answer a survey, an unadjusted respondent average can overstate typical performance among all invited firms.
A high survey response rate does not settle this question. The respondents and nonrespondents may still differ in ways that matter. More responses improve representation only when they reduce meaningful gaps, rather than adding more records from groups already well represented.
The same issue appears in rankings. A list of companies that publish headcount may be useful for studying firms with disclosed headcount. It is weaker evidence for claims about which industries employ the most people overall, especially if disclosure habits vary by sector.
Five questions before using the numbers
Before treating a public file as a market picture, ask:
1. What exact population is the decision about? Is it all operating businesses, employer establishments, registered entities, or a narrower group? 2. What had to be true for a record to enter this source? It may have needed to file a form, receive funding, answer a survey, maintain a listing, or be active on a particular date. 3. Who was excluded or harder to capture? Look for stated exclusions, timing lags, geography limits, industry limits, and businesses without employees or online visibility. 4. Could inclusion be related to the metric being compared? This is the key test. Consider whether size, industry, age, location, or performance affects the likelihood of appearing. 5. Can the file be checked against an external benchmark? Compare distributions by geography, industry, size class, or employer status when another credible source provides those measures.
A benchmark comparison will not prove that a file is fully representative. It can, however, reveal visible imbalances. If a directory is heavily concentrated in one industry or area compared with a relevant benchmark, broad market claims deserve more caution.
Weights can sometimes reduce known imbalances, but only when a credible benchmark exists and the adjustment fits the intended use. Weighting does not demonstrate that every unobserved difference has disappeared.
Use narrower labels, make stronger decisions
A selective dataset is not useless. A directory can be effective for discovering prospective businesses within its listed population. A grant-recipient file can answer useful questions about recipients. A survey can identify patterns among respondents.
The trouble starts when the label disappears and the dataset is presented as the whole market.
Plain language helps preserve the distinction: “directory-listed businesses,” “survey respondents,” “employer establishments in scope,” or “registered firms meeting the program criteria.” Those phrases may be less sweeping, but they are more informative.
Where coverage evidence is limited, narrow the claim rather than overstating certainty. For example: “These results describe employer establishments included in the source’s defined coverage, not every business operating in the area.”
Before counting a business dataset, identify who had a chance to appear in it. That small step can prevent a tidy list from becoming an untidy conclusion.
Morrow Creek Data Services handles paid research, cleanup, verification, and structured delivery projects.
Start a data project