What Should You List In Your Research Plan? | No Misses

If you’re staring at a blank page and asking, what should you list in your research plan? think like a reviewer. They want to see what you’ll do, how you’ll do it, what you’ll need, and what you’ll deliver.

This article gives you a clean list you can use for a thesis proposal, a capstone plan, or a grant-style project write-up. It also gives you a simple way to spot gaps before you submit.

What Should You List In Your Research Plan?

A research plan works when each section answers one reviewer question. Section names vary by program, yet the building blocks stay similar.

Section To Include	What To Write	What Makes It Credible
Working title and aim	Name the topic and state the main aim in one sentence.	Aim is specific and matches the rest of the plan.
Research question set	Write 1 main question, then 2–5 sub-questions that break it down.	Each sub-question maps to a data source or a task you can run.
Background and gap	Summarize what the field knows, then state the gap your project targets.	Your gap is concrete and backed by a tight set of sources.
Scope and definitions	State boundaries (place, time window, population) and define core terms.	Boundaries match time and access; definitions can be used to code data.
Design choice	Name the design (survey, experiment, interview study, mixed methods) and why it fits.	Design matches the evidence needed to answer the question.
Participants or sources	Describe who or what you’ll study, plus inclusion and exclusion rules.	You can reach the sources you name, and the sample logic is clear.
Data collection plan	List instruments, procedures, and the order you’ll follow each time.	You note versions, piloting plans, and checks for missing data.
Analysis plan	Spell out how you’ll turn raw data into answers for each question.	Each question has a matching analysis step and a clear output.
Ethics and data protection	State approvals needed, consent flow, privacy steps, and risk handling.	Steps are concrete enough for ethics review and publication.
Timeline, resources, outputs	Break work into phases, list tools and costs, and name deliverables.	Milestones are measurable and fit the calendar you’re working in.

Start With A Question That Can Be Judged

Strong plans don’t open with a broad topic. They open with a question that can be answered with evidence. If your question feels fuzzy, your later sections will feel fuzzy too.

Write One Main Question

Keep the main question to one sentence. If it’s doing two jobs, split it. A clean split makes sampling and analysis easier to defend.

Add Sub-Questions That Force Clarity

Sub-questions keep you honest. Each one should point to a data source you can name. If you can’t name a source, the sub-question isn’t ready.

What To List In Your Research Plan For A Clear Scope

Scope is where good plans stay sane. Reviewers can spot an overreach fast, and they’ll doubt feasibility even if the idea is strong.

Define What You Won’t Do

Write one paragraph that names what’s out of bounds. Typical boundaries include one region, one age range, one organization type, or one time window. This is you proving you can finish.

List Constraints You Can’t Change

Constraints include access limits, a fixed semester schedule, a cap on participants, or a dataset with missing fields. Put constraints early so your method works with reality.

Build A Background Section That Earns Trust

Your background has one job: show what’s already known, then show the gap your project will fill. Use fewer sources, chosen well, and link each one to your question.

Use A Simple Source Ladder

• Start with 1–2 review sources that map the topic.
• Add primary studies closest to your question.
• End with the source that shows the gap you’ll target.

If your plan follows a grant format, align headings to what reviewers scan for. NIH applications commonly expect a Research Strategy organized under the headers NIH Research Strategy structure.

Choose A Design That Matches Your Evidence

A design is a promise about the evidence you’ll produce. Pick one that fits your question and your resources, then state the choice in one clean paragraph.

Quantitative Plans

If your question is about differences between groups or relationships between variables, a quantitative design often fits. Name your variables, your sampling approach, and the tool you’ll use for analysis.

Qualitative Plans

If your question is about meanings, decisions, or how people interpret a process, a qualitative plan can fit. Name recruitment, data type, and how you’ll keep coding consistent.

Mixed Methods Plans

Mixed methods works when you need both numbers and narrative. Add one extra line that states where the two strands meet: sampling, analysis, or interpretation.

Show Feasibility With Access And Sampling Details

Feasibility often comes down to access. If you need people, name where they are, how you’ll reach them, and what you’ll offer for their time. If you need documents or records, name the owner, the gatekeeper, and what permission looks like.

Spell Out Sampling In One Clean Block

Sampling is your “who counts” rule. State inclusion rules, exclusion rules, and the target count. Then add a line on what happens if the first recruitment route runs dry. A backup route can be as simple as adding a second site, widening the window, or switching from interviews to a structured questionnaire.

Define Success Criteria Up Front

Write one sentence that states what a usable dataset looks like. For a survey, that could be a minimum response count plus a rule for incomplete forms. For interviews, it could be a target number plus a stopping rule when new codes stop appearing. This gives you a clear finish line.

Write For Fast Skimming

Reviewers skim first, then read. Help them. Use headings, keep paragraphs tight, and put specifics early in each section. If a section has a list of steps, use a numbered list. If a section has choices, state the choice, then the reason.

Spell Out Data Collection So It’s Repeatable

Reviewers worry about fuzzy collection plans because fuzziness becomes unusable data. Your goal is repeatability: another person could follow your steps and collect data the same way.

List Instruments With Status Notes

Name each instrument and its status: draft, piloted, adapted, or already validated. If you adapt a scale, say what you changed.

Write Procedures As A Short Sequence

1. Recruit or identify sources
2. Run consent and screening
3. Collect data in a set order
4. Check for missing or inconsistent entries
5. Store data and label files the same way each time

If you’re writing for a grant template, check the submission rules for required documents and page limits. NSF gives an overview of common proposal parts on its page about NSF proposal parts.

Make The Analysis Plan Match The Questions

Many plans lose points here because mismatches show quickly. A simple trick: list each research question, then write the analysis step right under it.

Quantitative Analysis Notes

• Cleaning rules for missing data and outliers
• Descriptive stats that summarize the sample
• Tests or models tied to each question
• Assumption checks when relevant

Qualitative Analysis Notes

• Stages for coding and theme building
• An audit trail with memos and codebook updates
• A consistency check, like a second coder on a subset

Handle Ethics And Data Protection In Plain Language

Ethics is a set of choices that keep participants safe and keep your work publishable. Write this section in concrete steps, not slogans.

Consent Flow

State when consent happens, what people are told, and how they can exit. If minors are involved, include guardian consent plus assent.

Risk And Mitigation

Name likely risks, such as privacy leaks or time burden, then state what you’ll do to reduce them. If sensitive topics appear in prompts, plan a referral list your institution already uses.

Storage And Access

Write where data will live, who can access it, and how access is controlled. Keep file naming consistent so nothing gets lost.

Include A Timeline That Shows You Can Finish

A timeline is a feasibility test. Use milestones so you can measure progress, not just hope for it.

Use Milestones With Outputs

Good milestones include “instrument piloted,” “first 20% of data collected,” “analysis scripts running,” and “draft results section done.”

Plan For Bottlenecks

Bottlenecks include ethics review, recruitment delays, transcription time, and lab scheduling. Put those steps early and leave buffer time around them.

Quality Checks Before You Submit

Run this quick audit after your first full draft. It helps you catch holes that reviewers catch fast.

Check	What Often Goes Wrong	Fix That Works
Question to method fit	The question asks for cause, yet the design can only show association.	Change question wording or choose a design that can test cause.
Sampling reality	The plan assumes access to participants you can’t reach.	Add a recruitment channel or switch to a reachable source type.
Instrument clarity	Measures are named, yet prompts or items aren’t shown.	Attach instruments in an appendix or include a short item list.
Data storage detail	Files and backups are vague, so privacy and loss risk rise.	Write storage, backup cadence, access list, and retention plan.
Analysis mapping	Analysis steps don’t line up with sub-questions.	Add one matching analysis step under each sub-question.
Ethics detail	Consent and risk handling are too thin for review.	Write the consent flow and mitigation steps as numbered items.
Timeline realism	Every task is scheduled back-to-back with no slack.	Add buffer weeks around approvals, recruitment, and cleaning.
Outputs match aim	The plan promises outputs that don’t follow from the data.	Restate outputs as what your method can deliver in your timeframe.

A Copy Ready Research Plan Mini Template

Paste this outline into your document and fill each line with one tight paragraph. Keep headings, then write like you’re answering a reviewer.

Project Snapshot

• Working title:
• Main aim in one sentence:
• Main research question:
• Sub-questions:
• Scope boundaries:

Background

• What the field knows (chosen sources):
• The gap your project fills:
• Definitions of core terms:

Method

• Design and justification:
• Participants or sources and sampling:
• Data collection steps and instruments:
• Data storage and sharing plan:
• Analysis plan mapped to each question:

Ethics And Practicalities

• Approvals needed and when you’ll apply:
• Consent flow and privacy measures:
• Risks and mitigation steps:

Plan To Finish

• Timeline with milestones:
• Resources and costs:
• Outputs you’ll deliver:

When you revise, re-read your opening question and check that every later section still earns it. If you still find yourself asking, what should you list in your research plan? run the tables above like a checklist and patch the first mismatch you spot.