What Belongs in Your FAQ? Four Ways to Sort Questions

Choose content by the job

Before building an approved FAQ for a website or chat assistant, decide which questions belong in it. A repeated question may need a clearer service page, a current availability check, or a private conversation. Putting every question in a single answer list can hide those differences.

This guide provides an original sorting worksheet for small businesses and adult-learning providers. Its purpose is to choose a suitable public answer and destination before writing or connecting a chatbot. The examples are fictional, and the suggested method is editorial guidance rather than a claim about business results.

Start with one audience and one decision: for example, an adult deciding whether to enquire about a beginner evening course. Keep that task visible while sorting possible content.

Four destinations for a question

Use these four destinations. The labels are working categories, not a required site structure.

A question may justify both a public explanation and a private follow-up. “How do changes work?” can have a general answer; “Has my change been approved?” needs the actual record. Do not join those two meanings into one confident response.

Four questions from one fictional course

Imagine a fictional provider offers an introductory spreadsheet class for adults. Its approved course sheet says learners use their own laptop and complete a short setup check before the class. Nothing in the sheet guarantees a particular device will work.

“Do I need a laptop?”

This belongs beside the course description and registration instructions. Draft the equipment requirement from the sheet, with the setup-check route. A separate FAQ can point there if that helps navigation, but it should not become a second competing specification.

“Are there places left on Thursday?”

This depends on the current booking record. The public content should show how to check availability. An old list of available dates cannot establish a place is available now.

“Can you make an exception for my situation?”

This needs staff review. Publish a general contact route without asking someone to describe private circumstances in an open chat. Do not let AI invent an exception policy from similar businesses.

“What happens during the setup check?”

This is a candidate public answer, but the fictional source does not explain it. Mark it “needs clarification” and ask the course owner. The worksheet has uncovered missing information before an assistant can turn a guess into an answer.

Route the question before drafting the answer

Take one of the fictional questions and answer five checks: Are its facts approved? Is any policy unsettled? Does the answer need personal context? Does it depend on a current record? Where does the reader need the information to make a decision? Use the four destinations above and record your reasons.

Missing or conflicting authority keeps the item at “needs clarification.” A current-system destination identifies the route to check; it does not establish availability. A staff destination can still have a separate approved general explanation. Write a short content brief that keeps the proposed destination, source-owner role, general source reference and next action together. Use no customer details.

Change one fact and repeat: if the equipment requirement is no longer approved, the question needs clarification before drafting. If a booking record is needed, a stable FAQ alone cannot answer it. The decision exercise works on paper. If the interactive sorter is available on this page, use the fictional examples and “Find the destination” to inspect the suggested route, missing evidence and next action; the result is not approval to publish.

Collect questions without copying conversations

Ask staff to paraphrase recurring questions into a short list. Record the question, the task behind it, where people currently look, and what evidence suggests the problem recurs. Do not copy private messages, learner records, or identifying details into a brainstorming document or an AI tool.

The GOV.UK guidance on identifying user needs recommends examining existing evidence and defining content around the task a person wants to complete. That is a useful design reference for this exercise; its government publishing rules do not become obligations for your business.

Separate observed questions from suggestions. An AI-generated list can supply ideas to investigate, but it cannot establish what your own customers frequently ask. Label each candidate “observed”, “staff suggestion”, or “untested idea”. Avoid calling a list frequently asked questions when there is no supporting evidence.

The evidence behind the destination

Create one row per candidate with these fields:

Need and authority

1. Question in the audience’s words

2. Task the person is trying to complete

3. Evidence that the need exists and whether it has been observed

4. Answer source and the person authorised to settle its meaning

Placement and next action

1. Whether the answer is stable, current-system dependent, or individual

2. Chosen destination and a reason

3. Conditions that must stay attached to the answer

4. Useful next action and the destination responsible for it

Drafting decision

1. Decision: ready to draft, needs clarification, or unsuitable for public answering

Do not use a numerical score to override a missing source. A popular question with an unsettled policy stays unresolved until the owner decides. A rare but essential question may still deserve prominent placement because someone cannot complete their task without it.

Can a colleague find the next step?

1. Observe a colleague

   Give a colleague a fictional task and the proposed page arrangement. Ask them to find the requirement, identify what remains unknown, and show where they would go next. Observe the route they choose rather than explaining it immediately.

2. Repair the route

   If people miss essential information, improve its location or wording before expanding the FAQ. Check that any contact link leads to a route the team actually supports. For an assistant, preserve the distinction between a general explanation and a live or personal answer in its approved content.

The Canada.ca Content Style Guide advises organising content around audience needs and using clear headings. Apply those principles to the chosen destination: “Equipment for the evening class” tells a reader more than an undifferentiated “Other questions” heading.

Finish with a short list of supported answers, unresolved source questions, and specific page improvements. That is enough to start a useful content review.

Sources rechecked 4 October 2026

• GOV.UK: Identify user needs
• Canada.ca Content Style Guide

A practical next step

Discuss a clearer FAQ and service-page structure.

Related reading: Review website clarity and enquiry routes, Choose the right assistant channel.