---
source: https://iinventedlight.com/library/notes/plain-language-avoid-faq-dumps.md
title: "Put answers in the main content instead of a FAQ dump"
license: CC-BY-4.0
license_url: https://creativecommons.org/licenses/by/4.0/
source_license: "US government work, public domain; original synthesis in our own words"
attribution: "Summary by iinventedlight (AI-assisted). Sources: GSA / PlainLanguage.gov archive, Avoid FAQs; GSA / PlainLanguage.gov archive, Make it easy to follow."
author: "iinventedlight (synthesis of cited sources); text drafted with AI assistance"
date: 2026-11-05
status: published
checked_on: 2026-11-05
as_of: 2026-11-05
confidence: high
untested: "Editorial checklist only; not tested with readers. Sources fetched and evidence checked."
category: coverage-gaps
topic_area: "write-comm: summarizing answers where readers already look"
tags: writing, plain-language, communication, avoid-faq-dumps
sources:
  - id: S1
    title: "Avoid FAQs"
    publisher: "GSA / PlainLanguage.gov archive"
    url: https://raw.githubusercontent.com/GSA/plainlanguage.gov/main/_pages/guidelines/web/avoid-faqs.md
    accessed: 2026-11-05
    license: "US government work, public domain"
  - id: S2
    title: "Make it easy to follow"
    publisher: "GSA / PlainLanguage.gov archive"
    url: https://raw.githubusercontent.com/GSA/plainlanguage.gov/main/_pages/guidelines/organize/make-it-easy-to-follow.md
    accessed: 2026-11-05
    license: "US government work, public domain"
---
# Put answers in the main content instead of a FAQ dump

If you write clear web content that is easy to navigate and answers your readers questions, you will not need to create a FAQ. [S1]
FAQs often cause your readers more frustration. [S1]
Often your best solution is a clear, well-organized main content page explaining a process. [S1]
Organize your writing so it is easy to follow along. [S2]

## Checklist
1. [ ] Prefer a clear, well-organized main content page explaining a process. [S1]
2. [ ] Supplement your main content with FAQs, but do not try to replace the main content. [S1]
3. [ ] Do not assume what kinds of questions people will have. [S1]
4. [ ] Monitor customer calls and emails to create helpful FAQs. [S1]
5. [ ] Limit the volume of content. [S1]
6. [ ] Think through the questions your users likely have and organize the material in a logical order. [S2]
7. [ ] Present the steps chronologically when you explain a process. [S2]

**Done when:** main content explains the process and FAQs only supplement it. [S1]

## Claims
- id: C1
  claim: Limit FAQ volume so content does not overwhelm.
  source: S1
  evidence: "Limit the volume of content."
- id: C2
  claim: FAQs often frustrate readers.
  source: S1
  evidence: "FAQs often cause your readers more frustration."
- id: C3
  claim: Prefer a well-organized main process page.
  source: S1
  evidence: "Often your best solution is a clear, well-organized main content page explaining a process."
- id: C4
  claim: FAQs should supplement, not replace, main content.
  source: S1
  evidence: "Supplement your main content with FAQs, but don’t try to replace the main content."
- id: C5
  claim: Organize writing so readers can follow it.
  source: S2
  evidence: "Organize your writing so it's easy to follow along."

## Sources
- [S1] Avoid FAQs. GSA / PlainLanguage.gov archive. https://raw.githubusercontent.com/GSA/plainlanguage.gov/main/_pages/guidelines/web/avoid-faqs.md . License: US government work, public domain. Accessed 2026-11-05.
- [S2] Make it easy to follow. GSA / PlainLanguage.gov archive. https://raw.githubusercontent.com/GSA/plainlanguage.gov/main/_pages/guidelines/organize/make-it-easy-to-follow.md . License: US government work, public domain. Accessed 2026-11-05.

License: this note is CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Summary by iinventedlight (AI-assisted).