Absence of evidence is not evidence of absence

Not finding it does not mean it is not there.

Fallacy vs. flaw, on this site. This has no dedicated fallacy page, because it is a test-specific pattern rather than a classic named fallacy. On the LSAT it usually appears as "the argument concludes X does not exist because no evidence of X was found." Learn the shape; it recurs.

This one has no fallacy page. It is an LSAT-specific pattern, which is exactly why it is worth learning.

What it is

This flaw treats a failed search as proof that nothing exists to find. "We looked and did not find X, therefore X does not exist." That only follows if the search was thorough enough to have found X for sure.

The strength of the move depends entirely on how good the search was. A quick glance proves nothing. An exhaustive search proves a lot. Flawed arguments never establish which one happened.

An LSAT-style example

This example is original. It is not a real LSAT question.

The inspection found no structural damage to the bridge, so the bridge is definitely safe.

The flaw: An inspection that finds nothing proves the inspection found nothing. Unless the inspection is shown to catch every possible defect, "no damage found" does not equal "no damage exists."

How to spot it on test day

The right answer vs. the trap

The right answer

Usually "treats the failure to find evidence as proof that no evidence exists" or "confuses absence of evidence with evidence of absence."

The trap

"The argument relies on a sample that is too small." The search is not a sample of a population here. Keep the flaw categories straight.

Find your weak flaws

The free diagnostic scores flaw questions separately and shows whether this pattern is costing you points.

Take the free diagnostic All 12 flaws

Related flaws

Last updated October 12, 2026