Research Table Design for Claims

Key stats

• A table should answer one comparison question.
• Every number needs a unit, period, and source context.
• Short labels improve scanning without removing necessary qualifications.

Key takeaways

• Put the decision field first.
• Keep definitions close to the table.
• Do not imply precision beyond the source.

Table routine

Start with the claim register and turn only comparable fields into columns. Link to the content fact checking evidence matrix for review.

Methodology and limitations

This guidance applies public research, statistics, accessibility, search, and plain-language principles. Tables cannot resolve incompatible source definitions by themselves.

Related research

• Content fact checking evidence matrix
• Content evidence matrix for claims
• Source register fields for article production

FAQs

How many columns should a table have?

Use only the columns needed for the reader decision. Move explanation into notes when the table becomes difficult to scan.

Should estimates be shown?

Only when the method and uncertainty are clearly labeled.

Sources

1. BLS data
2. U.S. Census data
3. Pew Research methods
4. Google Search Essentials
5. Google helpful content guidance
6. W3C WCAG 2.2
7. PlainLanguage.gov guidelines
8. NIST Privacy Framework
9. ISO 9001 quality management
10. Digital.gov content guidance