Research and Source Management
Research Question Planner
Turn a broad topic into answerable research questions, define the evidence each answer needs, and set boundaries, priorities, and stopping rules.
Free editable Markdown · Researchers, content strategists, and writers ·
Accessible HTML preview
Blank template
The downloaded file contains the same fields in editable Markdown.
Project framing
- Broad topic
- [Neutral topic]
- Primary reader
- [Role, context, and knowledge]
- Reader decision or task
- [What the answer supports]
- Primary research question
- [One bounded, answerable question]
- Population or object
- [Who or what]
- Place or jurisdiction
- [Where relevant]
- Period
- [Current, historical, or defined dates]
- Key terms to define
- [Potential ambiguity]
- Explicit exclusions
- [What this project will not answer]
Question and evidence map
- Question 1
- [Essential question]
- Answer shape
- [Definition, description, comparison, explanation, or recommendation]
- Required evidence
- [Source type and quality]
- Question 2
- [Supporting question]
- Required evidence
- [Source type and quality]
- Question 3
- [Contrary or boundary question]
- Required evidence
- [Source type and quality]
- Dependency
- [Question that must be answered first]
- Likely limitation
- [What evidence may not establish]
Readiness checks
- Questions do not assume the conclusion.
- Scope names relevant population, period, and context.
- Important terms have operational definitions.
- Evidence requirements match the type of answer.
- Contrary evidence and affected perspectives are included.
- Essential and optional questions are distinguished.
- Unethical or infeasible collection plans were removed.
- The stopping rule is based on evidence coverage and known uncertainty.
How to use this template
- Write the reader's situation, the intended use of the answer, and the broad topic in neutral language.
- Break the topic into one primary question and smaller definition, context, evidence, and action questions.
- Add scope boundaries and define what evidence would be sufficient for each answer.
- Rank questions, identify dependencies and contrary perspectives, and assign research owners.
- Apply the stopping rule, documenting unresolved questions that require qualification or removal.
Convert the topic into a bounded decision
A topic names an area; a research question defines what the project needs to establish. Start with the intended reader and the decision, explanation, or action the content should support. Add the population or object, place, period, and key terms that determine scope. “Remote work productivity” is a topic. “What scheduling practices help a distributed support team maintain handoff quality across three time zones?” is closer to an answerable editorial question. Avoid combining description, explanation, prediction, and recommendation in one sentence.
Match questions to feasible evidence
For each question, write what a satisfactory answer would look like and what evidence can support it. A definition may need an authoritative standard; a current product detail needs versioned documentation; an experience question may need interviews with appropriate perspectives; an outcome claim may require reliable data and methodology. Distinguish what you can observe from what you can infer. If the desired claim requires evidence you cannot ethically or practically obtain, narrow the claim now instead of filling the gap later with confident language.
Prioritize and define when to stop
Label questions as essential, helpful, or out of scope. Resolve dependencies first: a recommendation cannot be evaluated until terms, context, and alternatives are understood. Note expected disagreement and which voices or documents might challenge the early framing. Set a stopping rule based on coverage and confidence rather than the number of tabs opened. Research may be ready for drafting when essential questions have appropriate support, significant contradictions are understood, and remaining uncertainty can be stated honestly.
See the fields in context
Fictional example: late equipment returns
River Room Library and its lending records are invented to demonstrate question refinement.
- Broad topic: Late returns from a fictional community tool library.
- Primary question: Which documented friction points prevent first-time members from returning borrowed tools by the stated due date?
- Evidence: Approved, anonymized process logs; current reminder wording; and voluntary interviews covering different member experiences.
- Boundary: The project can describe reported friction but cannot infer every member's motivation from return timestamps.
- Stopping rule: Draft when each process stage is documented, recurring themes have more than one source, and contradictions are preserved.
Frequently asked questions
What makes a research question answerable?
It has defined terms and boundaries, and there is a feasible, ethical form of evidence capable of supporting the kind of answer requested.
Can a project have several primary questions?
It can, but multiple independent questions often signal that the assignment needs separate deliverables. Choose one organizing question and treat the rest as supporting or out of scope.
Should the question include a keyword?
Use the language readers and sources use when it fits accurately. Do not distort a research question to repeat a search phrase or assume a conclusion.
What happens when essential evidence cannot be found?
Seek an appropriate alternative source, narrow the question, state the uncertainty, or remove the claim. Lack of evidence is not permission to guess.