Direct answer: verify that a question recurs in the creator's own defined evidence window, de-identify the records, state one Answer job, and complete a Fan-question brief containing the Verified recurring question, context, evidence IDs, response boundary, format rationale, Evidence note, owner, approval state, and next handoff.
This planner converts a verified recurring question into one content brief. It does not generate generic idea lists, answer sales objections, automate DMs, research a niche, schedule a recurring series, or decide a publishing cadence. One question produces one bounded brief.
If there is no verified question yet, the content ideas guide can support broader ideation. Do not label an internal brainstorm as fan evidence. This workflow begins with recorded questions.
Define what verified recurring means
Set the evidence window, included channels, question-unit definition, and recurrence threshold before reviewing records. A creator might require the same underlying question in at least three distinct interactions during a named window. That is a local working rule, not a universal standard.
Distinct means separate interactions or records, not three messages from one conversation. Similar questions can be grouped only when they seek the same answer. “How did you make this?” and “What equipment did you use?” may overlap but can require different answer jobs.
Show raw counts, unique interaction count, dates, and channel distribution. Do not infer that recurrence in the sample represents all fans. The gate merely confirms that the question was not invented for the brief.
Create a de-identified question log
Use one row per observed question: evidence ID, date, channel type, exact or tightly paraphrased question, context needed to interpret it, normalised question key, and reviewer. Remove usernames, contact details, purchase history, and unrelated personal information.
Keep private message content out of broadly shared planning views. Store only the minimum excerpt needed to establish the question and follow the creator's access controls. A content brief should never expose who asked.
Mark ambiguous, joking, rhetorical, and sales-related questions separately. A recurring objection belongs in another workflow. This planner is for informational or experience questions that can become useful content.
Normalise wording without erasing meaning
Create a normalised key after preserving the evidence wording. Group spelling variants and close paraphrases, but keep materially different intent separate. Write an inclusion and exclusion rule for every key that reaches the recurrence threshold.
For example, a process key may include “how did you set this up?” and “what were the steps?” It may exclude “how long did it take?” when duration is a distinct decision-relevant question. The distinction should follow the answer required.
Ask a second reviewer to classify a small sample. If grouping depends on hidden context, improve the rule or leave the records separate. A smaller accurate cluster is more useful than a large vague one.
State one Answer job
The Answer job describes what the content must help the audience understand, compare, recognise, or do. “Explain the three visible stages and why each matters” is clearer than “make an educational post.” It gives the writer an observable completion condition.
List the minimum facts needed, facts that require checking, and matters outside scope. If the creator cannot disclose a requested detail, reshape the answer around what can be explained accurately rather than implying access that is unavailable.
Choose one primary answer job. Related questions can be linked as future briefs. Combining setup, cost, timing, equipment, and personal history in one piece often leaves every answer shallow.
Complete the Fan-question brief
Fields: brief ID; Verified recurring question; normalised key; evidence window; evidence IDs; raw recurrence count; context; Answer job; audience starting point; required facts; response boundary; approved examples; format; rationale; creator input; Evidence note; owner; reviewer; status; and handoff.
The Evidence note explains why the records belong together and records any contrary example. It should not claim the topic is popular beyond the creator's sample. The status can be evidence ready, fact check, creator input needed, draft, review, approved, or stopped.
Set a stop condition for missing facts, privacy concerns, creator discomfort, duplicated content, or an answer that would exceed the approved boundary. A recurring question does not create an obligation to publish.
Choose a format that fits the answer
Match format to the audience job. A sequence may need a short demonstration or carousel. A comparison may need paired examples. A definition may need a concise written post. A nuanced experience may need a longer explanation.
Record why the format helps the answer, available approved assets, accessibility needs, and production dependency. Do not select a format simply because it performed well for an unrelated topic.
The brief can name one primary format and one feasible fallback. Scheduling and production allocation happen later, after facts and boundaries are approved.
Draft from evidence and source facts
Open with the question in recognisable, de-identified language. Give the direct answer, explain the necessary steps or distinctions, show a relevant example, state limits, and point to the next appropriate resource. Do not mention that a particular subscriber asked.
Separate creator experience from externally checkable facts. Date time-sensitive sources and link primary material where relevant. Do not use an invented statistic to make the answer seem stronger.
Review the draft against the Answer job. A reader at the defined starting point should be able to explain the answer after consuming the content. Extra promotion that distracts from the answer should be removed or handled elsewhere.
Approve one brief before creating a series
Check evidence IDs, recurrence rule, de-identification, factual support, scope, creator approval, format feasibility, and duplicate risk. Record changes and reviewer. Approval applies to the version reviewed, not every future adaptation.
If several approved questions form a coherent progression, hand them to the content series planner. Do not turn one recurring question into an endless series merely to fill slots.
If the question is time-sensitive, add an expiry or recheck date. An answer based on current interface or platform information can become stale even when the audience question remains useful.
Hand off without scheduling inside the brief
The approved brief moves to production with owner, assets, dependencies, and desired completion window. Final cadence belongs in the weekly content schedule template. Keep the question evidence attached by ID rather than copying private source material.
After publication, record the content ID and whether the original Answer job was delivered. New questions can become new evidence records. Do not treat views or sales as proof that the original question was representative.
If the published answer reveals a different recurring question, open a new log key and apply the same gate. This preserves one-question-one-brief traceability.
Copy the workflow checklist
Confirm: defined window; distinct evidence records; recurrence threshold met; records de-identified; normalised key reviewed; one Answer job; facts sourced; boundaries approved; format justified; owner named; status current; and next handoff separate.
Reject briefs based on one anecdote labeled recurring, generic idea lists with no evidence IDs, combined sales objections, hidden personal information, unsupported claims, or a format selected before the answer was defined.
Review whether the published answer stayed useful
After publication, review the final item against the approved brief rather than treating performance as the only quality signal. Confirm the direct answer appears, the necessary facts are accurate, the example supports the explanation, the boundary remains visible, and the question has not been replaced by an unrelated promotion.
Collect follow-up questions as new evidence rows. A follow-up may show that the original answer assumed too much starting knowledge or combined two steps. Revise the existing item when the answer is incomplete; open a new brief when the follow-up has a genuinely different Answer job.
Keep a version note containing publication date, content ID, brief version, factual recheck date, revision reason, and reviewer. If the content is retired, record why. Do not delete the connection to the original question log.
Measure answer quality with a small editorial rubric: directness, completeness for the stated job, evidence accuracy, understandable sequence, accessible format, and boundary clarity. The rubric supports revision; it does not predict reach or purchases.
Handle conflicting recurring questions
Two recurring questions can pull in opposite directions. One group may ask for a quick summary while another asks for a detailed process. Preserve both clusters and write separate briefs when their answer jobs differ. Do not average them into an unclear middle format.
When questions contain conflicting assumptions, answer the shared factual issue first and identify the distinction. A comparison format may be appropriate, but only if the evidence shows that comparison is the actual job.
Prioritisation belongs to the content owner using relevance, creator capability, freshness, factual readiness, and existing commitments. Recurrence is one input. A frequently asked question can still be unsuitable when answering it would cross a creator boundary.
Limitations and sources
Limitations: recurrence is specific to the creator's selected records and window. It does not measure market demand, importance to every subscriber, or likely performance. De-identification and narrow scope can also remove context, so uncertain records should remain uncertain.
The workflow adapts GOV.UK guidance to record observations and group evidence and start from a real user need. The recurrence gate, brief fields, and approval flow are original SirenCY editorial tools.