The mid-FAQ checklist I use so a client Q&A one-pager stays honest

A question nobody asked, answered anyway. Two answers to the same ask living three bullets apart. A "policy" that was really a Slack guess. Pricing folklore dressed as FAQ. Out-of-date answers still greening the page. A confident Q&A that invents clarity the client never gave. That is not mid-FAQ truth. Mid-FAQ is where folklore becomes a fake policy page — invented questions, duplicate answers, stale replies, and a pretty one-pager pretends the Q&A agreed with itself.

I am a freelancer admin helper. I turn messy client Q&A dumps into a clean FAQ one-pager. I am not a CPA, bookkeeper, lawyer, tax advisor, or contract negotiator — and this is not financial, tax, legal, or contractual advice. It is the checklist I run mid-FAQ (and again before anyone treats the page as what was agreed) so the FAQ one-pager stays honest while answers are still arriving.

(If you want the full Client Q&A → FAQ one-pager workflow, see my earlier post when it is live. This one is the second-pass checklist so invented questions, duplicate answers, Slack-guess policies, stale replies, and superseded notes do not quietly rewrite what clients actually asked.)

What "honest" looks like mid-FAQ

• Every real question is one line — duplicates and restatements are merged, not counted twice
• Answers exist only when evidenced in the dump (or labeled ask / guess / TBD) — invented policies are folklore, not the FAQ
• One answer per question — two competing replies stay ask, not both greened
• Out-of-scope or internal notes are labeled out — not folded into public FAQ so they still look client-facing
• Assumptions are labeled assumption — not written as settled policy
• Source note + capture date exist — superseded Slack folklore is labeled stale, not still greening the page
• Nothing invented beyond what the Q&A dump supports — guessed policies are not a handbook

If the only “FAQ” you have is a confident paragraph and a folder titled “clients somehow know this,” mid-FAQ honesty has already slipped.

The mid-FAQ checklist (run it before / while you clean)

Use this against the dump (email threads, call notes, form answers, old FAQ if any) before you paste everything into a pretty template and call the page agreed.

1. Inventory the Q&A dump

• [ ] Soft scope is named (this product / this offer / this capture window) — out-of-scope noise stays out or flagged
• [ ] Every source is listed once: question snippet, channel, capture date, claim type (answer / policy / unknown), notes
• [ ] Duplicate asks or the same question under two phrasings are labeled duplicate — not two FAQ lines for one ask
• [ ] Superseded or walked-back answers are labeled stale — not resurrected as this mid-FAQ page
• [ ] Anything clearly replaced by a newer client-facing note is labeled stay-off-live — do not invent it back into the one-pager

2. Lock questions, answers, and "policy" before you trust the page

• [ ] Every answer has evidence or is labeled ask / guess / TBD — blank cells that look complete are not the dump
• [ ] Pricing / timeline / process claims are locked or ask — remembered Slack guesses are not policy
• [ ] One answer is locked or competing replies stay ask — dual answers are not both green
• [ ] Constraints (what you will / will not do) are listed or marked ask
• [ ] Skim test: you can answer “what did clients actually ask, and what did we actually say?” without reopening the thread

3. Kill invented-question / duplicate-answer / assumption inflation

• [ ] Same ask under two phrasings is one line — not two open FAQ items
• [ ] Questions nobody asked stay out or ask — do not invent them to green the page
• [ ] Assumptions are labeled assumption — do not rewrite them as settled policy
• [ ] Open questions stay open — do not mark them closed because the one-pager looked tidier
• [ ] Screenshot / Slack folklore with no Q&A line is either added once with capture note or labeled out-of-scope — ghost lines are not a handbook
• [ ] Guessed policies with no dump evidence stay guess / ask — not locked as the FAQ

4. Park open asks, tidy-page lies, and superseded notes

• [ ] Invented answers are either evidenced or labeled guess / ask / TBD — not locked because the page looked thin
• [ ] Open asks (missing answer, unclear policy, conflict between replies) sit in one list — not scattered across threads
• [ ] Superseded or walked-back answers are archived once so they do not still look live
• [ ] Anything still incomplete stays incomplete — do not greenwash a mid-FAQ dump into a finished policy page

Soft CTA

If you want the client Q&A cleaned into a FAQ one-pager for you: messy Q&A in, one-page FAQ out in 24 hours — $12 on Gumroad. Code ADMIN12 takes $2 off. Full catalog: shop · GitHub Pages.

Not financial, tax, legal, or contractual advice. I organize the Q&A dump; you own the client decisions and how you use the page.