Authority Claims Without Evidence: Spotting Unsupported Assertions in Documents

Some of the most consequential statements in professional documents are the ones presented as settled fact when the evidence does not support them.

What is an authority claim?

An authority claim is a statement that presents a conclusion as established without citing the evidence or reasoning that supports it. The classic forms are:

**Bare assertions.** "This approach is industry best practice." "The system is fully compliant." "The data is accurate and complete." None of these statements are argued — they are simply declared.

**Implicit expertise.** "As is well known..." "It is widely accepted that..." "Research shows..." without specifying which research, or what it actually shows.

**Circular reasoning.** "The methodology is reliable because it produces reliable results." "The process is robust because it has been thoroughly tested." The conclusion supports itself.

**Normative claims disguised as descriptive ones.** "All leading organisations use this approach." This may be true or false, but it is presented as a fact about the world rather than an argument.

Why they appear

Authority claims appear in documents for several reasons.

Writers under time pressure reach for assertions because marshalling evidence takes time. Hedged or qualified statements require more careful thought than confident ones. And confident assertions carry a rhetorical force that supports the overall argument, even if they weaken the document's intellectual integrity.

In organisations with strong hierarchies, authority claims also function as a form of status signalling. A confident statement implies the writer has access to knowledge that justifies the claim.

The legal and reputational risk

In regulatory filings, unsupported compliance claims create liability. If a filing states that a system "meets all applicable requirements" and that statement turns out to be incorrect, the bare assertion is evidence of negligence or misrepresentation.

In procurement, a proposal that claims "best in class" performance without evidence gives the buyer grounds to challenge the contract if performance falls short.

In litigation, documents with unsupported assertions are vulnerable to cross-examination. The absence of supporting evidence turns what seemed like a strength — confident language — into a weakness.

The difference between a claim and a conclusion

A claim is a statement. A conclusion is a claim supported by reasoning and evidence. Professional documents should consist of conclusions, not claims.

The test: if challenged on the statement, could you produce the evidence or reasoning that supports it? If not, the statement is a bare claim and should be revised to either include the support or qualify the statement appropriately.

How automated detection works

Detection works by identifying linguistic patterns associated with unsupported authority: epistemic verbs without attribution ("research shows," "studies indicate," "experts agree"), superlatives without qualification ("the best," "the most," "the only"), and compliance assertions without citation ("fully compliant," "meets all requirements").

Each flagged statement is a prompt for a review question: what is the evidence for this, and is it cited in the document?

Revising authority claims

The revision approach depends on the nature of the claim.

If the evidence exists and is strong, cite it explicitly. "The system meets all requirements of ISO 27001 (certified by Bureau Veritas, certificate number 12345)."

If the evidence exists but is uncertain, qualify appropriately. "Based on testing conducted in March 2024, the system meets the performance requirements in Schedule 2."

If no evidence exists, the claim should be removed or converted to an aspiration: "The system is designed to meet all applicable requirements."

A document that only asserts what it can support is harder to write but significantly more defensible.