You have a short announcement and a request to turn it into a FAQ. AI can supply ten tidy questions in seconds. The harder job is deciding which questions matter, which answers the notice actually supports, and which apparent answers are policies nobody has approved. A polished answer about refunds or access can create a promise that was never in the original.

This worked example turns an invented community venue announcement into a small, source-backed question-and-answer section. It complements our source-of-truth editing guide by showing how to handle a specific change of format. All venue details below are fictional practice material.

Start with a bounded source notice

Here is the complete practice notice: “The upstairs reading room will close from 5 to 9 October for repainting. The ground-floor lending desk will stay open during its usual hours. Reserved books can be collected at that desk. The Tuesday reading circle will meet in the garden room. Please use the venue contact form for questions about existing room bookings.”

List what this establishes: a room closure, a date range, an open lending desk, a collection location, a meeting location, and a contact route for existing bookings. It does not establish opening hours, refunds, building access arrangements, a reopening time, or what happens if the painting overruns. Missing facts remain missing when the format changes.

Before using real material, check that the notice is approved and current. If a schedule and an announcement disagree, resolve the disagreement with the owner. Do not ask a model to choose whichever detail sounds more plausible.

Choose questions around reader decisions

A useful first question is “Can I still collect a reserved book?” It reflects a concrete task. “What exciting improvements are coming?” reflects the writer's promotional angle and has no supported answer here. An AI-generated question is a candidate, not evidence that people ask it frequently.

If available, use recurring reader enquiries to choose the questions, without uploading private messages or personal details. Otherwise call the section “Questions about the reading-room closure” rather than claiming the questions are frequent. For this example, three practical questions are enough. There is no need to fill an arbitrary ten-question template.

Also consider whether an FAQ belongs on the page at all. In its 2013 explanation of avoiding FAQs, the UK Government Digital Service describes the problems of slow scanning and duplicated content. That is a useful design challenge, not a universal ban: if a direct notice already answers everything clearly, improving that notice may serve readers better than adding another section.

Write the direct answer, then its boundary

Question: Can I still collect a reserved book?
Weak draft: “Absolutely! Our services remain fully available throughout the improvements.”
Edited answer: “Yes. Collect reserved books at the ground-floor lending desk during its usual hours.”

The edit answers the question and preserves the actual location. The weak version expands one continuing service into a claim about all services. Do not add an opening time unless a checked schedule supplies it. In a real publication, link to the current opening-hours page if one exists and is accurate.

Question: Is the whole venue closed?
Weak draft: “No, only a small area is affected, so your visit will continue as normal.”
Edited answer: “No. The upstairs reading room is closed from 5 to 9 October. The ground-floor lending desk remains open during its usual hours.”

The size of the affected area and the promise of a normal visit were not in the notice. A direct “No” is useful here, but it needs the limit immediately after it. Readers should not have to discover the closure exception several paragraphs later.

Question: Where will the Tuesday reading circle meet?
Edited answer: “The Tuesday reading circle will meet in the garden room.” This needs no enthusiastic preamble. Keep the event name so the answer still makes sense when copied into a message on its own.

Route unanswered questions without inventing rules

Suppose AI adds “Will I receive a refund for a room booking?” and answers “Yes, affected bookings will be refunded automatically.” Delete that answer. The notice supplies a contact route, not a refund policy. Nor does silence justify answering “No.” Both conclusions would invent a rule.

A supported alternative question is “Who should I contact about an existing room booking?” Its answer can say, “Use the venue contact form for questions about an existing room booking.” In the real page, link the words “venue contact form” to the verified form. Keep a separate editorial query asking the booking owner whether refund information needs to be added.

Some missing details are important enough to delay publication of that answer. Access arrangements, for example, cannot be inferred from the existence of a ground-floor desk. Ask the appropriate owner for an approved statement rather than improvising reassurance.

Give AI a brief that permits gaps

Try: “Use only this approved notice to propose up to four reader questions and answers. For each answer, identify the exact supporting sentence. Put unsupported questions in a separate editor-only list. Do not infer policies, times, access arrangements, or guarantees. Answer directly and preserve every limitation. Recommend no FAQ if the notice already serves the reader.”

Check each proposed source mapping yourself. If you use the AIUndetectable humanizer to refine wording, compare the revised answers with the notice again. More natural phrasing does not confirm a policy, and a detector score cannot verify the facts.

W3C's writing guidance recommends clear instructions and concise, understandable content. Apply that here with short answers, familiar words, and descriptive links. Our worked guide to link labels covers that last detail.

Publish one maintained answer to each question

Read each answer without its neighbours: does it still identify the service and its limits? Check the dates and destinations, remove the editor-only gap list from public copy, and assign someone to update the section when the closure ends. Avoid maintaining conflicting copies across the notice and FAQ. The finished result should help someone decide what to do while making no promise beyond the approved source.