Reading Complexity: When Your Document Is Too Hard for Its Audience

There is a persistent belief in professional writing that complexity signals expertise. Dense prose, long sentences, and specialised vocabulary are taken as evidence that the writer knows what they are talking about. The evidence does not support this belief.

Reading complexity defined

Reading complexity is the degree of cognitive effort required to process and understand a text. It is determined by several factors:

• **Sentence length.** Longer sentences require the reader to hold more information in working memory before they can parse the grammatical structure.
• **Word complexity.** Words with more syllables and lower frequency in everyday language are harder to process.
• **Syntactic complexity.** Nested clauses, passive voice, and inverted constructions slow processing speed.
• **Conceptual density.** How many distinct ideas appear in each sentence and paragraph.
• **Assumed knowledge.** How much specialised background the reader must bring to understand the text.

Standard readability metrics — Flesch-Kincaid, SMOG, Gunning Fog — operationalise the first two or three of these factors into a score correlated with US school grade level. A score of 12 means a reader needs a high school education to process the text comfortably. A score of 16 corresponds to a college degree.

The mismatch problem

The issue arises when document complexity exceeds audience reading level. This mismatch is pervasive:

• Consumer-facing terms and conditions are routinely written at a graduate level
• Employee handbooks often require more literacy than the roles they govern
• Medical information provided to patients is frequently inaccessible to the patients who need it
• Public consultations draw fewer meaningful responses when the consultation documents are too complex

The mismatch is not always intentional. Authors write for readers like themselves — and professionals typically have high reading fluency. They underestimate the cognitive cost of their prose for readers with less specialised training.

When complexity is appropriate

Complexity is not always a defect. Technical documentation for expert users, legal instruments where precision requires specificity, and scientific papers written for specialist audiences all appropriately use complex language.

The standard is fitness for purpose: the document should be as simple as the content permits for the intended audience.

Measuring complexity

Flesch-Kincaid is the most widely used metric. It combines average sentence length and average syllables per word into a grade-level score. It is fast to compute and directionally reliable, though it does not capture all aspects of difficulty.

SMOG (Simple Measure of Gobbledygook) counts polysyllabic words and is better calibrated for healthcare and legal writing. Gunning Fog weights both sentence length and complex words.

Running multiple metrics provides a more robust picture than any single score. A document that scores consistently high across all metrics is genuinely complex; one that scores high on one metric and low on others may have a specific addressable issue (very long sentences but simple vocabulary, for instance).

Practical reduction strategies

For most professional documents, complexity can be reduced without sacrificing precision:

**Sentence length.** If a sentence exceeds 25 words, it is a candidate for splitting. Look for coordinating conjunctions (and, but, or) and relative clauses (which, that, who) as natural split points.

**Passive voice.** Active constructions are faster to process. "The committee approved the proposal" is clearer than "The proposal was approved by the committee."

**Nominalisation.** Converting verbs to nouns adds syllables and reduces clarity. "We analysed the data" is clearer than "We conducted an analysis of the data." "Consider" rather than "give consideration to."

**Jargon.** Every piece of jargon should pass a test: is this the clearest available expression for this concept for this audience? If a simpler term exists, use it.

The business case for readable documents

Readable documents achieve their purpose more reliably. A data protection notice that recipients can understand generates better-informed consent than one they cannot. A procedure that staff can follow reduces errors. A contract that both parties understand reduces disputes.

The investment in reducing complexity returns in fewer misunderstandings, faster decision-making, and more effective compliance. The cost of revision is real but bounded; the cost of a document that fails to communicate is open-ended.