03 · What You Need to Know
The important question is not how small the study is, but what the study requires
Researchers often use size as shorthand for simplicity:
Small sample = simple study = little planning needed.
That reasoning can fail quickly.
A study involving six participants could involve vulnerable individuals, sensitive personal information, invasive procedures, substantial privacy risks, or a difficult consent process. A study containing 100,000 observations might involve nothing more than a reproducible analysis of an openly available dataset.
The number of participants, cases, records, documents, specimens, or observations is therefore only one characteristic of a study. It does not by itself determine how much protocol documentation is appropriate.
First, separate the need for a study plan from the need for a formal protocol document
Every defensible research project needs a plan. Not every project necessarily needs the same kind of formal protocol document.
Study plan
The substantive decisions governing what the research will investigate and how it will be conducted, analyzed, managed, and documented.
Formal protocol
A structured document recording those decisions in the format and level of detail appropriate to the study or required by a responsible institution or authority.
This distinction matters because researchers sometimes conclude that if nobody requires a particular protocol template, they do not need to document the study systematically at all.
The better approach is to determine what decisions the study requires first, then decide how formally those decisions need to be documented.
External requirements come before your judgment about whether the study is too small
If an ethics committee, university, funder, research site, sponsor, regulator, or other authority requires a protocol, the question is largely settled.
For example, the World Health Organization's Research Ethics Review Committee reviews research projects involving human participants that are supported financially or technically by WHO. Its recommended protocol format covers the study rationale, objectives, design, methodology, data management and analysis, quality assurance, timeline, project management, ethics, and related matters.
That WHO process should not be generalized into a universal requirement for every small research project. Institutions have their own rules. The relevant lesson is that formal documentation requirements come from the system governing the study, not from the researcher's impression that the project is modest.
Before deciding that you do not need a protocol, check the requirements of every relevant authority.
Small human-participant studies can still require substantial planning
Imagine a qualitative study involving eight survivors of a traumatic event.
The sample is small, but the study may need careful decisions about recruitment, informed consent, participant distress, privacy, interview procedures, withdrawal, recordings, access to identifiable information, data retention, and the handling of potentially sensitive disclosures.
WHO's protocol guidance emphasizes that participant safety and ethical considerations should be addressed within the protocol and notes that even questionnaire research can potentially have adverse effects on individuals. It also expects protocols involving participants to address informed consent and relevant follow-up.
The amount of documentation should therefore be driven partly by what can happen to participants and their information, not simply by how many people participate.
A low-risk study may justify lighter documentation when no formal template is required
At the other end of the spectrum, consider a researcher analyzing an openly available dataset containing no information requiring special access or participant interaction.
The project still needs a research question, dataset definition, eligibility or filtering rules, variable definitions, analysis plan, data-processing workflow, and enough documentation for the researcher to understand and reproduce what was done.
However, if no ethics, institutional, funder, contractual, or other formal protocol requirement applies, a concise internal protocol may be entirely adequate.
It might be only a few pages. Length is not the relevant criterion. The document is adequate if it captures the consequential decisions needed to conduct and interpret that particular study.
Use complexity rather than sample size as one test of protocol detail
A project becomes harder to manage when many procedures, people, sites, measurements, time points, data sources, or analytical steps must remain coordinated.
A small experimental study, for example, may involve random assignment, several measurement occasions, standardized instructions, equipment settings, exclusion rules, adverse-event procedures, and multiple researchers. The sample may be modest while the operational complexity remains substantial.
By contrast, a larger one-time anonymous survey may have a relatively straightforward operational workflow.
| Study characteristic |
Likely documentation implication |
| Few procedures and one researcher |
A concise protocol may be sufficient if no formal requirement dictates otherwise. |
| Several researchers or data collectors |
More explicit procedures and responsibilities help maintain consistency. |
| Multiple sites |
Procedures, roles, permissions, and site-specific requirements may need greater specification. |
| Several measurement occasions |
Timing, follow-up, tracking, and missing-data procedures become more important. |
| Complex intervention or experiment |
Detailed implementation and quality-control procedures may be necessary even with a small sample. |
| Simple secondary analysis |
Documentation may focus more heavily on data provenance, eligibility, variable construction, and analysis. |
WHO's protocol guidance similarly expects study design, methodology, instruments, data management, quality assurance, duration, and responsibilities to be specified as relevant, and specifically notes the need for standardized and clearly defined methodology when multiple sites conduct the same protocol.
Risk should influence documentation
Protocol detail should also respond to what could go wrong.
A small study collecting names, health information, recordings, or other sensitive material may need explicit procedures for access, storage, coding, confidentiality, retention, and eventual disposal. A study involving an intervention may need safety procedures. Research with vulnerable populations may require additional protections.
The protocol provides a place to make these protections operational rather than leaving them as general intentions such as “confidentiality will be maintained.”
For example, instead of writing only that data will be confidential, the study plan might specify:
- which identifiers will be collected;
- why they are necessary;
- where the identifiable information will be stored;
- who will have access;
- whether identifiers will be separated from research data;
- how recordings will be handled; and
- when identifiable material will be deleted or otherwise managed according to applicable requirements.
The smaller sample does not make these questions disappear.
Methodological flexibility does not eliminate the need for a protocol
Researchers sometimes worry that a protocol is incompatible with qualitative or exploratory research because not every decision can or should be frozen in advance.
A protocol does not need to pretend otherwise.
A qualitative protocol can establish the research question, methodological approach, setting, population, sampling logic, recruitment, consent, broad interview or observation procedures, data handling, analytic approach, and ethical protections while identifying where iterative decisions are methodologically appropriate.
WHO's protocol guidance explicitly accommodates qualitative research and asks investigators to specify in sufficient detail how qualitative data will be analyzed.
The objective is not to remove legitimate flexibility. It is to distinguish what can appropriately remain flexible from decisions that should already be clear.
A small study can still benefit from a protocol even when nobody requires one
Formal requirements are not the only reason to create a protocol.
A concise protocol can help you discover whether the research question, sampling, instrument, data collection, analysis, and timeline actually fit together.
Consider a student planning twelve interviews. The project sounds straightforward until the protocol requires answers to questions such as:
- Who exactly qualifies to participate?
- How will those people be identified and approached?
- Why are twelve interviews being proposed?
- What will the interview guide cover?
- Will interviews be recorded?
- How will recordings and transcripts be protected?
- What analytical approach will be used?
- How will the researcher know when the intended sampling strategy has been adequately implemented?
If those questions cannot yet be answered, the project may be small without yet being ready.
The protocol can be shorter without becoming vague
Proportionality does not mean deleting important sections. It often means giving simple parts of the study appropriately concise treatment.
Suppose a single researcher will analyze publicly available policy documents. The project-management section might require only a short explanation because there is no multi-person team to coordinate. A clinical trial could require considerably more.
Likewise, a simple project may have few foreseeable safety issues, while another needs extensive monitoring procedures.
The guiding question is:
What does someone need to know to understand, evaluate, and correctly conduct this particular study?
Write enough to answer that question. Do not expand simple issues merely to make the document look substantial.
Do not omit analysis because the study is exploratory
Even a small exploratory project should have some account of how the resulting evidence will be interpreted.
For quantitative research, the plan might identify the variables, descriptive or inferential procedures, important comparisons, and how foreseeable data problems will be handled.
For qualitative research, it should identify the analytic approach and how material will move from raw interviews, observations, documents, or other sources toward the eventual interpretation.
WHO's recommended format asks quantitative protocols to outline proposed statistical methods and calls for qualitative projects to specify their analysis in sufficient detail.
This does not require pretending that exploratory analysis is confirmatory. It requires enough advance thought to establish that the data being collected can actually address the research question.
Do not omit data management because there will not be much data
A dataset does not need to be large to be sensitive, confusing, or vulnerable to loss.
Ten interview recordings can contain far more identifiable information than thousands of anonymous numerical observations. A small spreadsheet can still be overwritten accidentally. A modest qualitative project can still accumulate multiple transcript versions and inconsistent participant identifiers.
WHO's protocol guidance asks researchers to explain data handling, coding, monitoring, verification, and analysis.
For a small project, the resulting plan may be simple. You should nevertheless know where the data will be stored, how they will be organized, who can access them, how versions and identifiers will be managed, and what applicable retention or sharing requirements exist.
Do not omit a timeline because the study looks manageable
Small projects can still miss deadlines.
In fact, they are sometimes particularly vulnerable because researchers assume that every stage will be quick. A ten-interview project can still wait several weeks for approval, struggle with recruitment, require transcription, involve iterative analysis, and go through several rounds of supervisory revision.
WHO's recommended protocol format asks researchers to specify the expected duration of project phases and a timeline for activities.
Your own small study may need nothing more complicated than a simple sequence of major milestones. The important point is to check whether the work fits the available time rather than treating “small” as a duration estimate.
A pilot study is still a study
The word pilot can make a project sound exempt from ordinary planning requirements.
A pilot or feasibility study may be smaller than the intended main study, but it still needs a clear purpose. Are you testing recruitment feasibility? Instrument comprehension? Procedural timing? Intervention delivery? Data completeness?
The design should match that purpose.
If the pilot involves human participants or activities subject to ethics or institutional requirements, calling it a pilot does not by itself remove those requirements. Researchers should obtain an authoritative determination from the responsible body rather than deciding informally that the study is too small to require review.
Student research is not automatically exempt from protocol requirements
A project conducted for a thesis, dissertation, coursework requirement, or student research program may be small and educational in purpose. That does not automatically determine whether it is research requiring ethics review, a protocol, site permission, or another institutional process.
Universities differ in how they classify and review student activities. The responsible institution should determine which rules apply.
Where a protocol is required, student status is not a reason to omit methodological or ethical information. In practice, protocol development can be especially useful for student researchers because it exposes assumptions before they become data-collection problems.
One researcher still benefits from writing down what they intend to do
Protocols are sometimes viewed primarily as coordination documents for teams.
They do serve that function, but memory is a surprisingly unreliable version-control system even for a team of one.
During a project, you may revise an instrument, alter a coding rule, change a data-cleaning decision, or refine an analysis. Without an explicit baseline plan, it becomes difficult to reconstruct which decisions were made before data collection and which emerged afterward.
A concise dated protocol provides that baseline.
Formal does not have to mean bureaucratically elaborate
For a small study, formality may simply mean that the plan is:
- written rather than remembered;
- structured enough to locate important decisions;
- dated and versioned;
- consistent across the protocol and study materials;
- reviewed where appropriate; and
- updated transparently when consequential changes occur.
That can be accomplished without producing a document that resembles the operating manual of an international clinical trial.
The purpose is disciplined clarity, not page count.
Some small studies need more formalization precisely because there is little room for error
Small studies can be especially sensitive to procedural inconsistency.
If a study contains only ten interviews and the first three are conducted using substantially different eligibility criteria or interview procedures, a large portion of the dataset may already be affected.
Similarly, losing two observations from a study of twelve cases may have greater practical consequences than losing two from a study of several thousand, depending on the design.
Smallness therefore does not necessarily reduce the importance of consistent procedures. In some circumstances, it increases the proportion of the study affected by each mistake.
Use the protocol as a readiness check
Before deciding that a small study is ready, try to write down its essential protocol.
You should usually be able to explain:
Question What exactly is the study trying to answer?
Evidence Who or what can provide the information needed?
Selection How will participants, cases, documents, records, or observations enter the study?
Procedure What exactly will happen during data collection or acquisition?
Data What will be created or obtained, and how will it be organized and protected?
Analysis How will that evidence be interpreted to answer the question?
Ethics and permissions What review, consent, access, privacy, or institutional requirements apply?
Feasibility Can the study actually be completed with the available time and resources?
If those questions can be answered clearly in a concise document, the protocol may not need to become much longer unless an external requirement demands it.
If they cannot be answered, reducing the document length will not solve the underlying planning problem.
Check whether the study needs a specific institutional template
Before creating your own protocol format, check the responsible institution.
NIH's Intramural Research Program provides different protocol templates for several categories of research, including behavioral and social science studies, observational research, prospective data collection, repositories, retrospective review, and secondary research. This illustrates that protocol requirements can vary according to the type of study rather than simply its size.
If your university, ethics committee, sponsor, or research office supplies a template, use it. Do not shorten or restructure a required protocol merely because the study seems small unless the responsible authority permits that approach.
When no formal protocol is required, create the lightest document that still controls the study
If you have confirmed that no specific protocol format is required, proportionality becomes useful.
A concise protocol for a straightforward study might contain:
- research question and objectives;
- brief rationale;
- study design;
- population, cases, or data source;
- eligibility and sampling or selection;
- data collection or acquisition procedures;
- instruments or measures;
- data-management procedures;
- analysis plan;
- ethical and access considerations;
- major timeline and responsibilities; and
- protocol version and date.
Some studies will need additional sections. Others may combine several of these into short paragraphs.
The objective is to document the consequential choices without manufacturing complexity that the study does not possess.
The protocol should become more detailed as the study approaches implementation
Early in planning, some decisions can remain provisional. By the time the study approaches data collection, more of them need to be settled.
If you are still deciding between two recruitment populations, several instruments, and fundamentally different analysis strategies, a polished formal protocol may be premature.
If recruitment is about to begin, however, the relevant population, eligibility, procedures, participant materials, data handling, and applicable approvals should not remain vague.
The protocol should therefore mature with the project. This aligns with the broader principle that the level of planning detail should increase as decisions become consequential.
Small studies still need version control when the plan changes
A two-person research team can change a protocol just as easily as a fifty-person team. The difference is that informal changes may be easier to make without anyone noticing that the written plan is now outdated.
Keep a version number or date on the working protocol. When a consequential change occurs, document what changed and why. If the study is governed by ethics, institutional, funder, regulatory, or other requirements, determine whether review or approval is required before implementation.
The protocol should remain a record of the study being conducted rather than a document that describes an earlier version nobody follows anymore.
Watch Out
Do not use the label “small study” as a reason to bypass required ethics review, site permission, data-access conditions, consent procedures, or other institutional requirements. Study scale and formal requirements are separate questions. Verify the rules that apply to the actual project.
