Report QA Checklist: Quotes, Numbers, Terminology, Consistency, Formatting (Plus Sign-Off)

A report QA checklist helps you catch the mistakes that hurt trust: misquoted statements, inconsistent numbers, drifting terminology, messy formatting, and broken links. Use the checklist below to run a fast, repeatable final review before you publish or share a report. It includes quote accuracy checks, numeric consistency steps, terminology alignment, formatting rules, link validation, a simple sign-off flow, and the most common last-mile errors.

Primary keyword: report QA checklist.

Key takeaways

• Verify quotes against the original source and keep meaning, context, and attribution intact.
• Reconcile every number across tables, charts, summaries, and headings before final export.
• Lock terminology early (names, product terms, metrics) and enforce it with a glossary.
• Run a formatting and link pass on the final file you will send, not an earlier draft.
• Use a simple sign-off process so someone other than the author checks high-risk items.

What “QA” means for a report (and what it does not)

Report QA is a final quality check that confirms your content is accurate, consistent, and easy to read. It focuses on the things readers will notice fast, like mismatched numbers, unclear labels, broken links, and quotes that do not match the source.

QA is not a full rewrite or a strategy review, so keep it scoped to verification and consistency. If you find repeated issues, capture them as fixes for your template or process next time.

Before you start: set up your QA pass in 10 minutes

A short setup makes the checklist faster and more reliable. It also reduces “I thought you checked that” confusion during approvals.

• Pick the source of truth for facts: dataset, spreadsheet, interview recording, meeting notes, or approved brief.
• Freeze the draft: stop content edits during QA or track them clearly in change comments.
• Define the final format: PDF, Google Doc, Word, slide deck, or web page, since QA differs by output.
• Create a quick glossary: key names, product terms, metric definitions, and preferred spellings.
• Decide who signs off: one content owner and one independent checker.

If you will publish online, plan to review the final rendered version too. Formatting and links can break during export or upload.

The final report QA checklist (copy/paste)

Use this as your last-step checklist before sending to a client, publishing to the web, or presenting to leadership. If you need to move faster, do the items marked “High risk” first.

1) Quote accuracy checklist (High risk)

• Match wording to the source: compare each quote to the recording, transcript, or notes and confirm it is verbatim if you present it as a direct quote.
• Check attribution: confirm speaker name, title, and organization, and verify you did not swap speakers.
• Confirm context: make sure surrounding sentences do not change the meaning of what was said.
• Verify punctuation that changes meaning: commas, ellipses, and brackets can alter intent, so use them carefully.
• Mark edits honestly: use brackets for clarifying words and ellipses only when you remove non-essential parts without changing meaning.
• Standardize quote formatting: consistent quotation marks, block quote style, and citation pattern across the report.
• Check permissions and sensitivity: remove or anonymize quotes that were not approved for sharing, if applicable.

Quick method: make a two-column table: “Quote in report” and “Source line/time stamp,” then confirm each row.

2) Numbers and units checklist (High risk)

• Reconcile repeats: every repeated number must match across executive summary, body, tables, charts, and captions.
• Confirm calculation logic: spot-check formulas for totals, averages, medians, and percentages.
• Check rounding rules: use one approach (for example, one decimal place) and keep it consistent.
• Verify units: $, %, days, hours, kg, miles, and currency symbols should be correct and consistent.
• Validate date ranges: ensure the stated period matches the data pull and chart axes.
• Watch sign and scale errors: negative vs positive, thousands vs millions, and “per month” vs “per year.”
• Confirm sample sizes and denominators: percentages must clearly state “of what,” especially in survey results.
• Check chart labels: axis titles, tick marks, and legend items must match the narrative.

Quick method: search the document for “%” and currency symbols, then review each instance for context and consistency.

3) Terminology alignment checklist (High risk)

• Lock proper nouns: product names, team names, locations, and program names spelled the same way every time.
• Standardize metric names: decide whether it is “conversion rate” or “CVR,” then apply consistently.
• Confirm definitions: if you define a term (like “active user”), verify the report uses that definition everywhere.
• Align acronyms: spell out on first mention, then use the acronym consistently.
• Remove “near-synonyms”: avoid switching between two terms if they are not truly identical.

Tip: put your glossary at the top of the QA doc so reviewers do not invent new terms during feedback.

4) Consistency checks (structure, logic, and narrative flow)

• Headings match content: each section should deliver what its heading promises.
• Summary matches body: executive summary claims must be supported in the main report.
• One idea per paragraph: tighten paragraphs that mix methods, results, and recommendations.
• Parallel structure: lists and subheadings follow the same pattern and level of detail.
• Cross-references work: “see Figure 3” should point to the right figure after edits.
• Methods are repeatable: if you describe a process, ensure someone could follow it without guessing.

5) Formatting and layout checklist (High risk in final export)

• Run QA on the final output: check the exported PDF, sent deck, or published page, not only the draft.
• Fix broken line breaks: widows/orphans, awkward page breaks, and split tables reduce readability.
• Ensure table readability: consistent alignment, header styling, and no clipped text.
• Standardize capitalization: title case vs sentence case for headings, and keep it consistent.
• Use consistent punctuation: Oxford comma choice, hyphenation, and dash style (– vs —).
• Check visuals: charts are readable, colors have enough contrast, and legends are not cut off.
• Verify numbering: page numbers, section numbers, and appendix labels update correctly.
• Confirm accessibility basics: add alt text for key images and ensure headings use real heading styles.

If accessibility is a requirement, use recognized guidance like the W3C WCAG overview to check basics that apply to your format.

6) Link validity checklist (High risk for web and PDFs)

• Click-test every link: do not rely on visual inspection, especially after PDF export.
• Confirm link text matches destination: the anchor should describe what the reader will get.
• Remove “naked URLs” where possible: use descriptive text instead of long raw links.
• Check tracking and redirects: ensure tracked links still land on the correct page.
• Validate citations: any external reference should point to the right document and section.

If you cite standards or regulations, link to an official or widely accepted source. For example, when discussing accessibility-related communication support, use an authoritative reference such as the ADA effective communication guidance when it applies to your context.

A simple sign-off process (fast, clear, and repeatable)

A sign-off process works best when it is small and specific. It should also separate “author checks” from “independent checks.”

Suggested roles

• Content owner (author): runs the full checklist, fixes issues, and confirms the report reflects the source of truth.
• Independent checker: verifies the high-risk items (quotes, numbers, links) and confirms fixes.
• Approver (optional): signs off on messaging or compliance needs, if your team requires it.

Suggested sign-off steps (copy/paste)

• Step 1: Author completes QA checklist and records any exceptions (what, where, why).
• Step 2: Independent checker reviews high-risk items and spot-checks the rest.
• Step 3: Author applies fixes and shares a clean “final” file plus a change summary.
• Step 4: Checker confirms fixes and signs off in writing (email or comment).
• Step 5: Approver signs off only if needed, then you publish or distribute.

What to record in your sign-off note

• Report title and version/date.
• What sources were used (dataset name, interview date, or file name).
• Who checked quotes, numbers, and links.
• Any known exceptions (for example, “Figure 2 uses preliminary data”).

Common last-mile errors (and how to catch them)

Many report issues appear after “final” changes, like last-minute edits, export problems, or copy-paste mistakes. Use this list as a last scan before you send.

• Numbers drift after edits: you update a chart but not the summary sentence, so values conflict.
• Percentages without a base: “up 20%” with no clear starting point or denominator.
• Quote clean-up that changes meaning: removing filler words can accidentally remove hedging or intent.
• Chart-label mismatch: the axis says “weekly” but the text says “monthly.”
• Broken cross-references: “Table 4” was deleted and the reference now points nowhere.
• Formatting breaks in PDF: links no longer clickable, tables split, or text overlaps.
• Terminology drift: the same metric appears with two names in different sections.
• Unintended track changes: comments or suggested edits remain in the delivered file.

Common questions

How long should a report QA pass take?

It depends on report length and risk, but a focused pass often works best in two stages: a fast high-risk check (quotes, numbers, links) and then a formatting and flow check on the final export.

Should the author do QA, or should someone else do it?

Have the author run the checklist, then use an independent checker for high-risk items. A second set of eyes catches mistakes the author’s brain skips.

What’s the fastest way to check numeric consistency?

Start with repeated numbers in summaries, headings, and callouts, then reconcile tables and charts. Search for “%” and currency symbols and confirm each instance has the right unit and base.

How do I handle quotes if I do not have a transcript?

Use the best available source of truth, like a recording or approved notes, and avoid presenting paraphrases as direct quotes. If quote accuracy is critical, create a transcript first so you can verify wording and attribution.

What should I do when a term means different things to different teams?

Define it in a glossary and use that definition consistently in the report. If needed, add a short note the first time the term appears to prevent confusion.

Do I need to click-test links if the report is a PDF?

Yes, because exporting to PDF can break link targets or click areas. Always test links in the final PDF you will send.

What’s the best way to prevent last-minute formatting issues?

QA the final output file and keep changes minimal after export. If you must edit after export, re-export and repeat the link and layout checks.

When transcripts help report QA (especially quotes and terminology)

If your report includes interviews, meetings, or recorded calls, a transcript can make QA faster and more accurate. You can search exact phrasing, confirm attribution, and keep terminology consistent across sections.

• For a fast first draft, you can start with automated transcription and then verify critical quotes.
• If you already have a draft transcript and need it cleaned up, consider transcription proofreading before you finalize quotes.

If you want help turning audio or video into reliable text you can cite and QA against, GoTranscript offers professional transcription services that fit into a straightforward report review workflow.