Answer the question a reader actually brought to the page
A helpful FAQ is not a storage cupboard for spare information. It begins with real questions, groups them around the reader’s journey, uses the reader’s words without copying misconceptions, gives a direct answer first, explains conditions and exceptions, links to the canonical detail, and has an owner who retires stale entries. English matters because question shape, answer order and modal verbs determine whether a reader can decide, act or ask for help.
Choose the route closest to your task, or read straight through for the complete system.
People search for how to write FAQs because repeated questions consume time and reveal where a service, assignment, event or process is hard to understand. A useful FAQ turns that evidence into a shorter route, but it does not hide weak information architecture behind a fashionable component.
The practical mechanism is question-to-decision design. Gather real questions, identify the user’s stage, write a natural question title, answer it immediately, show conditions and exceptions, give the next action and connect the reader to the authoritative detail.
Good FAQs respect both language and choice. They do not manufacture questions to advertise features, bury “no” beneath a long preface, or imply that English is the only support a multilingual reader may use. Translation, diagrams, contact routes and better core pages may be the right response.
This guide was checked on 13 October 2026. Actual FAQ content should follow current school, workplace, privacy, accessibility, legal and policy requirements. The page owner must reopen authoritative sources before publishing claims that can change.
Did You Know? The GOV.UK Design System guidance on accordions says well-written, structured content can remove the need for an accordion and specifically advises against using accordions to split up a series of questions. An FAQ is therefore a content problem first, not an expand-and-collapse design pattern.
Find the section you need
Find the real questions · 2 chapters
Shape useful answers · 2 chapters
Design the route · 2 chapters
Check the effect · 2 chapters
An FAQ should answer questions people genuinely ask or are likely to need before a consequential step.
Collect anonymised questions from support, class discussions, search terms, forms, interviews and task observation. Separate high-frequency questions from rare but high-impact ones.
Several students ask whether a draft must include citations; the repeated question points to an unclear requirement, not a marketing opportunity.
What to check
- Collect questions
- Protect privacy
- Note frequency
- Note consequence
Try this chapter on an assignment FAQ. Write the audience, present state, desired result, exact evidence, uncertainty, safe boundary and next action before polishing the sentences.
Now create an ordinary case, a difficult case and a missing-information case. Keep the governing meaning stable while adapting examples, detail and support for the reader.
Ask an independent reader to explain what they understood, what they would do next and where they hesitated. Revise the communication, preserve the source evidence and keep the first version beside the improvement.
Boundary: Do not invent search volume or present one anecdote as representative demand.
Learning transfer: Evidence gathering supports inquiry and content design.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
Repeated questions can signal that the main page, form, instruction or policy needs repair.
Trace each question to its source. Fix missing labels, contradictory pages and confusing steps first; keep an FAQ when readers still benefit from a concise question-led route.
If every user asks where to submit, moving the submission link into the task page is better than adding a distant FAQ.
What to check
- Trace source
- Fix core page
- Choose format
- Avoid duplication
Try this chapter on a school event FAQ. Write the audience, present state, desired result, exact evidence, uncertainty, safe boundary and next action before polishing the sentences.
Now create an ordinary case, a difficult case and a missing-information case. Keep the governing meaning stable while adapting examples, detail and support for the reader.
Ask an independent reader to explain what they understood, what they would do next and where they hesitated. Revise the communication, preserve the source evidence and keep the first version beside the improvement.
Boundary: An FAQ should not become a permanent patch over preventable confusion.
Learning transfer: Problem diagnosis supports design and learning.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
3. Write the question in the reader’s language
Back to contentsA question heading should be recognisable at a glance and specific enough to distinguish its answer.
Use first- or second-person wording where natural, include the key object and condition, and replace internal labels with the public term while preserving necessary official names.
“Can I change my file after I submit it?” is easier to scan than “Post-submission amendment protocol.”
What to check
- Use user words
- Name object
- Add condition
- Keep official term
Try this chapter on a volunteer onboarding FAQ. Write the audience, present state, desired result, exact evidence, uncertainty, safe boundary and next action before polishing the sentences.
Now create an ordinary case, a difficult case and a missing-information case. Keep the governing meaning stable while adapting examples, detail and support for the reader.
Ask an independent reader to explain what they understood, what they would do next and where they hesitated. Revise the communication, preserve the source evidence and keep the first version beside the improvement.
Boundary: Do not repeat an offensive, dangerous or false premise without correction.
Learning transfer: Question framing supports comprehension and search.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
Readers should not cross a paragraph of background to discover yes, no, sometimes, not yet or contact us.
Open with the narrow answer, then explain the rule, condition, reason, example and next step. Keep the wording proportionate to the evidence and authority.
“Yes, until the deadline shown on your assignment page. Replace the file through the same submission screen and check the new receipt.”
What to check
- Answer first
- State condition
- Give reason
- Give action
Try this chapter on a family technology FAQ. Write the audience, present state, desired result, exact evidence, uncertainty, safe boundary and next action before polishing the sentences.
Now create an ordinary case, a difficult case and a missing-information case. Keep the governing meaning stable while adapting examples, detail and support for the reader.
Ask an independent reader to explain what they understood, what they would do next and where they hesitated. Revise the communication, preserve the source evidence and keep the first version beside the improvement.
Boundary: Directness is not permission to omit an exception that changes the decision.
Learning transfer: Answer-first writing supports exams and work.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
Many FAQ answers are true only for a role, date, location, version or status.
Use if, unless, before, after, only and may carefully. Name the applicable group, time zone, cut-off source and exception owner near the claim.
Late changes require teacher approval; the FAQ links the current assignment page rather than copying a date that may change.
What to check
- Name who
- Name when
- Name condition
- Name exception
Try this chapter on an assignment FAQ. Write the audience, present state, desired result, exact evidence, uncertainty, safe boundary and next action before polishing the sentences.
Now create an ordinary case, a difficult case and a missing-information case. Keep the governing meaning stable while adapting examples, detail and support for the reader.
Ask an independent reader to explain what they understood, what they would do next and where they hesitated. Revise the communication, preserve the source evidence and keep the first version beside the improvement.
Boundary: Never turn a historical deadline or example into a guarantee for the next cycle.
Learning transfer: Conditional reasoning supports policy and mathematics.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
An FAQ can clarify an official rule without silently becoming the rule.
Identify the authoritative source, paraphrase only what the reader needs, link the current detail and label examples as examples. Route conflicts back to the policy owner.
The club FAQ explains the registration steps and links the approved safety policy for the binding requirements.
What to check
- Identify owner
- Link source
- Label example
- Handle conflict
Try this chapter on a school event FAQ. Write the audience, present state, desired result, exact evidence, uncertainty, safe boundary and next action before polishing the sentences.
Now create an ordinary case, a difficult case and a missing-information case. Keep the governing meaning stable while adapting examples, detail and support for the reader.
Ask an independent reader to explain what they understood, what they would do next and where they hesitated. Revise the communication, preserve the source evidence and keep the first version beside the improvement.
Boundary: Do not invent permissions, rights, penalties or commitments.
Learning transfer: Source control supports research and citizenship.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
Readers usually arrive before, during or after a task, not with the organisation’s department chart in mind.
Cluster by goal or stage, order common and consequential questions first, use clear H2 and H3 headings, and keep related questions close enough to compare.
An event FAQ groups eligibility, registration, preparation, attendance and follow-up rather than administration, finance and operations.
What to check
- Map journey
- Group goals
- Order priority
- Use headings
Try this chapter on a volunteer onboarding FAQ. Write the audience, present state, desired result, exact evidence, uncertainty, safe boundary and next action before polishing the sentences.
Now create an ordinary case, a difficult case and a missing-information case. Keep the governing meaning stable while adapting examples, detail and support for the reader.
Ask an independent reader to explain what they understood, what they would do next and where they hesitated. Revise the communication, preserve the source evidence and keep the first version beside the improvement.
Boundary: A catch-all page with dozens of unrelated questions may need separate task pages.
Learning transfer: Information architecture supports digital reading.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
Hidden answers can reduce scanning clutter but may also make comparison and find-in-page behaviour harder.
Start with visible headings and concise answers. If an accordion is justified, test keyboard access, screen-reader labels, open-state behaviour, printing, linking and search.
Three long eligibility answers are moved to separate pages with a short list of links instead of nested accordions.
What to check
- Prefer structure
- Test keyboard
- Test search
- Avoid nesting
Try this chapter on a family technology FAQ. Write the audience, present state, desired result, exact evidence, uncertainty, safe boundary and next action before polishing the sentences.
Now create an ordinary case, a difficult case and a missing-information case. Keep the governing meaning stable while adapting examples, detail and support for the reader.
Ask an independent reader to explain what they understood, what they would do next and where they hesitated. Revise the communication, preserve the source evidence and keep the first version beside the improvement.
Boundary: The interface component cannot repair unclear content.
Learning transfer: Accessibility thinking supports inclusive communication.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
A reader often needs a document, form, owner, deadline or escalation route after understanding the answer.
Name the action, link, owner, evidence to prepare, expected response path and emergency or high-stakes boundary where relevant. Avoid vague endings such as contact support without a route.
If the receipt is missing, the answer tells the student which screenshot and file name to send to the assignment owner.
What to check
- Name action
- Give route
- Prepare evidence
- Set boundary
Try this chapter on an assignment FAQ. Write the audience, present state, desired result, exact evidence, uncertainty, safe boundary and next action before polishing the sentences.
Now create an ordinary case, a difficult case and a missing-information case. Keep the governing meaning stable while adapting examples, detail and support for the reader.
Ask an independent reader to explain what they understood, what they would do next and where they hesitated. Revise the communication, preserve the source evidence and keep the first version beside the improvement.
Boundary: Do not promise a response time or outcome that the owner has not approved.
Learning transfer: Action writing supports self-management.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
The writer’s familiarity can hide whether another reader recognises the right question and acts correctly.
Give representative users realistic tasks. Observe the search words they use, which heading they choose, what they infer, whether they complete the action and where they still seek help.
A user searches “edit submission” while the FAQ says “amendment,” revealing a heading mismatch.
What to check
- Test terms
- Test scan
- Test inference
- Test action
Try this chapter on a school event FAQ. Write the audience, present state, desired result, exact evidence, uncertainty, safe boundary and next action before polishing the sentences.
Now create an ordinary case, a difficult case and a missing-information case. Keep the governing meaning stable while adapting examples, detail and support for the reader.
Ask an independent reader to explain what they understood, what they would do next and where they hesitated. Revise the communication, preserve the source evidence and keep the first version beside the improvement.
Boundary: A satisfaction rating alone does not prove that the answer was understood or correct.
Learning transfer: Usability testing supports evaluation.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
An answer that was once correct can become harmful after a policy, interface or date changes.
Record owner, source, review date, trigger, last change and retirement rule. Monitor unresolved contacts and consolidate duplicate answers into one canonical page.
The page owner reviews registration answers whenever the form changes and removes last year’s temporary exception.
What to check
- Name owner
- Date review
- Set trigger
- Retire duplicate
Try this chapter on a volunteer onboarding FAQ. Write the audience, present state, desired result, exact evidence, uncertainty, safe boundary and next action before polishing the sentences.
Now create an ordinary case, a difficult case and a missing-information case. Keep the governing meaning stable while adapting examples, detail and support for the reader.
Ask an independent reader to explain what they understood, what they would do next and where they hesitated. Revise the communication, preserve the source evidence and keep the first version beside the improvement.
Boundary: Adding a new answer is not always safer than revising or deleting an old one.
Learning transfer: Maintenance literacy supports reliable knowledge bases.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
How to build this kind of English before the job title arrives
Back to contentsStudents do not need professional authority to practise the underlying language. They can learn to define scope, annotate conditions, compare versions, rebuild a timeline, match a number to its unit and explain uncertainty without embarrassment. Parents can ask calm questions: What decision is this document supporting? Which sentence carries the strongest claim? What would make that claim false? Which source would you open next?
Use a three-pass routine. First, map the document: title, owner, audience, date, sections and decision. Second, trace one claim from source to conclusion. Third, explain the limit and next action. This routine strengthens comprehension, science, mathematics, humanities and workplace readiness because it turns English into an evidence tool.
A student should never imitate professional authority. The useful goal is to recognise when a text needs a qualified reviewer, current rule or official decision. Knowing when to pause is part of literacy.
Evidence
Students repeatedly ask whether a submitted file can be replaced.
Direct answer
The first sentence says yes or no for the current assignment and names the governing condition.
Route
The answer gives the approved steps, receipt check and link to the canonical assignment page.
Exception
Late or locked submissions go to the named owner; the FAQ does not invent approval.
Maintenance
A review trigger is tied to assignment settings and deadline changes.
Question evidence
Where the question came from, frequency, consequence and user stage.
Answer core
Direct answer, authority, condition, exception and date.
Reader route
Next action, canonical link, owner and escalation.
Structure
Journey group, heading terms, visible comparison and accessibility.
Validation
Source check, user test, unresolved query and correction.
Maintenance
Owner, review date, revision trigger, duplicate and retirement decision.
Use this roadmap to see how the chapters connect. Each decision names a purpose, action, observable example and limit rather than repeating a generic writing rule.
1. Begin with evidence of reader need
An FAQ should answer questions people genuinely ask or are likely to need before a consequential step. The practical move is to collect anonymised questions from support, class discussions, search terms, forms, interviews and task observation. Separate high-frequency questions from rare but high-impact ones.
A reader can test the chapter through this example: Several students ask whether a draft must include citations; the repeated question points to an unclear requirement, not a marketing opportunity. Keep the boundary visible: Do not invent search volume or present one anecdote as representative demand.
2. Decide whether an FAQ is the right fix
Repeated questions can signal that the main page, form, instruction or policy needs repair. The practical move is to trace each question to its source. Fix missing labels, contradictory pages and confusing steps first; keep an FAQ when readers still benefit from a concise question-led route.
A reader can test the chapter through this example: If every user asks where to submit, moving the submission link into the task page is better than adding a distant FAQ. Keep the boundary visible: An FAQ should not become a permanent patch over preventable confusion.
3. Write the question in the reader’s language
A question heading should be recognisable at a glance and specific enough to distinguish its answer. The practical move is to use first- or second-person wording where natural, include the key object and condition, and replace internal labels with the public term while preserving necessary official names.
A reader can test the chapter through this example: “Can I change my file after I submit it?” is easier to scan than “Post-submission amendment protocol.” Keep the boundary visible: Do not repeat an offensive, dangerous or false premise without correction.
4. Put the direct answer first
Readers should not cross a paragraph of background to discover yes, no, sometimes, not yet or contact us. The practical move is to open with the narrow answer, then explain the rule, condition, reason, example and next step. Keep the wording proportionate to the evidence and authority.
A reader can test the chapter through this example: “Yes, until the deadline shown on your assignment page. Replace the file through the same submission screen and check the new receipt.” Keep the boundary visible: Directness is not permission to omit an exception that changes the decision.
5. Make conditions, exceptions and time visible
Many FAQ answers are true only for a role, date, location, version or status. The practical move is to use if, unless, before, after, only and may carefully. Name the applicable group, time zone, cut-off source and exception owner near the claim.
A reader can test the chapter through this example: Late changes require teacher approval; the FAQ links the current assignment page rather than copying a date that may change. Keep the boundary visible: Never turn a historical deadline or example into a guarantee for the next cycle.
6. Separate explanation from policy authority
An FAQ can clarify an official rule without silently becoming the rule. The practical move is to identify the authoritative source, paraphrase only what the reader needs, link the current detail and label examples as examples. Route conflicts back to the policy owner.
A reader can test the chapter through this example: The club FAQ explains the registration steps and links the approved safety policy for the binding requirements. Keep the boundary visible: Do not invent permissions, rights, penalties or commitments.
7. Group questions around the user journey
Readers usually arrive before, during or after a task, not with the organisation’s department chart in mind. The practical move is to cluster by goal or stage, order common and consequential questions first, use clear H2 and H3 headings, and keep related questions close enough to compare.
A reader can test the chapter through this example: An event FAQ groups eligibility, registration, preparation, attendance and follow-up rather than administration, finance and operations. Keep the boundary visible: A catch-all page with dozens of unrelated questions may need separate task pages.
8. Use disclosure components only when they help
Hidden answers can reduce scanning clutter but may also make comparison and find-in-page behaviour harder. The practical move is to start with visible headings and concise answers. If an accordion is justified, test keyboard access, screen-reader labels, open-state behaviour, printing, linking and search.
A reader can test the chapter through this example: Three long eligibility answers are moved to separate pages with a short list of links instead of nested accordions. Keep the boundary visible: The interface component cannot repair unclear content.
9. End each answer with the next responsible action
A reader often needs a document, form, owner, deadline or escalation route after understanding the answer. The practical move is to name the action, link, owner, evidence to prepare, expected response path and emergency or high-stakes boundary where relevant. Avoid vague endings such as contact support without a route.
A reader can test the chapter through this example: If the receipt is missing, the answer tells the student which screenshot and file name to send to the assignment owner. Keep the boundary visible: Do not promise a response time or outcome that the owner has not approved.
10. Test questions, answers and findability
The writer’s familiarity can hide whether another reader recognises the right question and acts correctly. The practical move is to give representative users realistic tasks. Observe the search words they use, which heading they choose, what they infer, whether they complete the action and where they still seek help.
A reader can test the chapter through this example: A user searches “edit submission” while the FAQ says “amendment,” revealing a heading mismatch. Keep the boundary visible: A satisfaction rating alone does not prove that the answer was understood or correct.
11. Assign an owner and retire stale answers
An answer that was once correct can become harmful after a policy, interface or date changes. The practical move is to record owner, source, review date, trigger, last change and retirement rule. Monitor unresolved contacts and consolidate duplicate answers into one canonical page.
A reader can test the chapter through this example: The page owner reviews registration answers whenever the form changes and removes last year’s temporary exception. Keep the boundary visible: Adding a new answer is not always safer than revising or deleting an old one.
The completed route should let another person reconstruct what the communication is for, what evidence supports it, what remains uncertain and what happens next.
Each case asks the learner to compare a quick answer with a version another person can actually use.
Case 1: Begin with evidence of reader need
Start with the worked situation: Several students ask whether a draft must include citations; the repeated question points to an unclear requirement, not a marketing opportunity. Write the most tempting shortcut, then mark the missing reader need, condition, source, authority or next action.
Repair the communication by applying this method: Collect anonymised questions from support, class discussions, search terms, forms, interviews and task observation. Separate high-frequency questions from rare but high-impact ones. Finish by stating why this boundary still matters: Do not invent search volume or present one anecdote as representative demand.
Case 2: Put the direct answer first
Start with the worked situation: “Yes, until the deadline shown on your assignment page. Replace the file through the same submission screen and check the new receipt.” Write the most tempting shortcut, then mark the missing reader need, condition, source, authority or next action.
Repair the communication by applying this method: Open with the narrow answer, then explain the rule, condition, reason, example and next step. Keep the wording proportionate to the evidence and authority. Finish by stating why this boundary still matters: Directness is not permission to omit an exception that changes the decision.
Case 3: Group questions around the user journey
Start with the worked situation: An event FAQ groups eligibility, registration, preparation, attendance and follow-up rather than administration, finance and operations. Write the most tempting shortcut, then mark the missing reader need, condition, source, authority or next action.
Repair the communication by applying this method: Cluster by goal or stage, order common and consequential questions first, use clear H2 and H3 headings, and keep related questions close enough to compare. Finish by stating why this boundary still matters: A catch-all page with dozens of unrelated questions may need separate task pages.
Case 4: Test questions, answers and findability
Start with the worked situation: A user searches “edit submission” while the FAQ says “amendment,” revealing a heading mismatch. Write the most tempting shortcut, then mark the missing reader need, condition, source, authority or next action.
Repair the communication by applying this method: Give representative users realistic tasks. Observe the search words they use, which heading they choose, what they infer, whether they complete the action and where they still seek help. Finish by stating why this boundary still matters: A satisfaction rating alone does not prove that the answer was understood or correct.
A parent, tutor, teacher or colleague can ask questions, but the learner should make the final revision in their own words and keep evidence of what changed.
Clear English is reliable when the reader can see not only what the sentence says, but also where it stops.
Boundary 1: Write the question in the reader’s language
A question heading should be recognisable at a glance and specific enough to distinguish its answer. Before treating the wording as complete, identify an exception, a missing fact, a reader who may need another route and a change that would force revision.
Apply the chapter’s observable signal—“Can I change my file after I submit it?” is easier to scan than “Post-submission amendment protocol.”—and underline the exact words carrying scope, time, permission, comparison or uncertainty. Do not repeat an offensive, dangerous or false premise without correction.
Boundary 2: Separate explanation from policy authority
An FAQ can clarify an official rule without silently becoming the rule. Before treating the wording as complete, identify an exception, a missing fact, a reader who may need another route and a change that would force revision.
Apply the chapter’s observable signal—The club FAQ explains the registration steps and links the approved safety policy for the binding requirements.—and underline the exact words carrying scope, time, permission, comparison or uncertainty. Do not invent permissions, rights, penalties or commitments.
Boundary 3: End each answer with the next responsible action
A reader often needs a document, form, owner, deadline or escalation route after understanding the answer. Before treating the wording as complete, identify an exception, a missing fact, a reader who may need another route and a change that would force revision.
Apply the chapter’s observable signal—If the receipt is missing, the answer tells the student which screenshot and file name to send to the assignment owner.—and underline the exact words carrying scope, time, permission, comparison or uncertainty. Do not promise a response time or outcome that the owner has not approved.
Boundary 4: Assign an owner and retire stale answers
An answer that was once correct can become harmful after a policy, interface or date changes. Before treating the wording as complete, identify an exception, a missing fact, a reader who may need another route and a change that would force revision.
Apply the chapter’s observable signal—The page owner reviews registration answers whenever the form changes and removes last year’s temporary exception.—and underline the exact words carrying scope, time, permission, comparison or uncertainty. Adding a new answer is not always safer than revising or deleting an old one.
A bounded statement is useful because a reader can test it, ask a focused question and act without treating confidence as proof.
Audience adaptation changes emphasis, vocabulary and next steps; it does not authorise a different truth.
Learner
An FAQ should answer questions people genuinely ask or are likely to need before a consequential step. This reader may need a different level of detail or a different next action.
Preserve collect questions, protect privacy, note frequency, note consequence while adapting examples and support. Do not change the underlying fact, decision or limit simply to make the short version easier.
Teacher or mentor
A question heading should be recognisable at a glance and specific enough to distinguish its answer. This reader may need a different level of detail or a different next action.
Preserve use user words, name object, add condition, keep official term while adapting examples and support. Do not change the underlying fact, decision or limit simply to make the short version easier.
Parent or colleague
Many FAQ answers are true only for a role, date, location, version or status. This reader may need a different level of detail or a different next action.
Preserve name who, name when, name condition, name exception while adapting examples and support. Do not change the underlying fact, decision or limit simply to make the short version easier.
Reviewer
Readers usually arrive before, during or after a task, not with the organisation’s department chart in mind. This reader may need a different level of detail or a different next action.
Preserve map journey, group goals, order priority, use headings while adapting examples and support. Do not change the underlying fact, decision or limit simply to make the short version easier.
Future reader
A reader often needs a document, form, owner, deadline or escalation route after understanding the answer. This reader may need a different level of detail or a different next action.
Preserve name action, give route, prepare evidence, set boundary while adapting examples and support. Do not change the underlying fact, decision or limit simply to make the short version easier.
Successful transfer preserves identity, source, status, uncertainty, boundary and responsible action while making the route easier for this reader to follow.
A polished paragraph can still conceal an unclear purpose, missing condition, invisible assumption or stale source.
Purpose test
State in one sentence what the reader should understand, decide or do. Delete a detail only if its removal does not change that outcome or a necessary boundary.
Write the expected interpretation, the reader’s actual interpretation, the difference and one precise revision. Keep the earlier version so the learning remains visible.
Condition test
Circle words such as if, unless, before, after, may, must and only. Add the missing role, date, version or exception beside each one.
Write the expected interpretation, the reader’s actual interpretation, the difference and one precise revision. Keep the earlier version so the learning remains visible.
Independent-reader test
Give the communication to someone who was not present. Ask what they think is true, what is still unknown and what action they would take next.
Write the expected interpretation, the reader’s actual interpretation, the difference and one precise revision. Keep the earlier version so the learning remains visible.
Change test
Imagine that a deadline, interface, source, role or policy changes tomorrow. Mark every sentence needing review and name who will update it.
Write the expected interpretation, the reader’s actual interpretation, the difference and one precise revision. Keep the earlier version so the learning remains visible.
Close reading is practical care: it keeps language from outrunning the reader, the evidence or the authority behind it.
Answer each prompt in a complete sentence tied to the current task, source, reader or authorised clarification. Write “unknown” when the available information does not support an answer.
- Collect questions? State the evidence, the limit and the narrow next action it supports.
- Protect privacy? State the evidence, the limit and the narrow next action it supports.
- Note frequency? State the evidence, the limit and the narrow next action it supports.
- Note consequence? State the evidence, the limit and the narrow next action it supports.
- Trace source? State the evidence, the limit and the narrow next action it supports.
- Fix core page? State the evidence, the limit and the narrow next action it supports.
- Choose format? State the evidence, the limit and the narrow next action it supports.
- Avoid duplication? State the evidence, the limit and the narrow next action it supports.
- Use user words? State the evidence, the limit and the narrow next action it supports.
- Name object? State the evidence, the limit and the narrow next action it supports.
- Add condition? State the evidence, the limit and the narrow next action it supports.
- Keep official term? State the evidence, the limit and the narrow next action it supports.
Read it aloud
Listen for sentences that postpone the answer, hide the actor, overload one step or imply certainty that the source does not provide. Revise for meaning before tone.
Ask a real reader
Invite a learner, parent, colleague or mentor to identify the purpose, strongest claim, important condition and next action. Treat hesitation as useful evidence about the text.
Keep a small revision note
Record the source, date, change and reason. A short history helps the next writer avoid restoring an earlier ambiguity.
How many questions should an FAQ contain?
Enough to serve one coherent reader journey; split or redesign when unrelated questions make the page hard to scan.
Should every answer begin with yes or no?
Only when the question genuinely has that form. Otherwise begin with the most direct accurate answer.
Are accordions best for FAQs?
Not automatically. Clear headings, separate pages or anchor links may be more usable.
Can an FAQ replace the official policy?
No. It can explain and link the policy but should not invent or override authority.
How can I find useful questions?
Use anonymised support queries, task observation, search terms and conversations, then repair the source of repeated confusion.
When should an answer be deleted?
When it is obsolete, duplicated, misleading or better answered at the point of need.
- GOV.UK Design System: Accordion
- W3C: Headings
- Digital.gov Plain Language Guide Series
- Why English? Reporting a Problem Clearly
Cycle-sensitive facts were checked against current official pages on 13 October 2026. Always reopen the authority’s live page before a real decision.