03 · What You Need to Know
Determining the Appropriate Level of Detail in Research SOPs
What Is the Purpose of Operational Detail in an SOP?
The purpose of an SOP is to translate an approved procedure into instructions that can be implemented consistently by the personnel responsible for it.
A research protocol may state that participants will complete a standardized achievement assessment. The corresponding SOP may explain how participants are identified, how instructions are delivered, how assessment timing is controlled, and how technical interruptions are handled.
Operational detail matters when differences in implementation could affect participant protection, measurement quality, data integrity, or compliance with approved procedures.
However, an SOP is not necessarily a complete training manual or a substitute for professional competence. Instructions should be written for the personnel expected to use them, with appropriate training and supervision provided separately.
The need for an SOP should first be established by considering which research procedures require formal operational instructions.
What Is the Difference Between Too Little, Sufficient, and Excessive Detail?
The appropriate amount of detail can be evaluated by examining whether a trained person could implement the procedure correctly without making consequential decisions that the research team intended to standardize.
| Level of detail |
Illustration |
Likely consequence |
| Insufficient |
Administer the assessment consistently. |
Leaves timing, instructions, assistance, and interruptions undefined. |
| Appropriate |
Verify the participant identifier, read the approved instructions, apply the specified time limit, and record interruptions using the designated procedure. |
Defines consequential actions and supports comparable administration. |
| Potentially excessive |
Describe every routine mouse movement, keyboard action, and screen transition despite a stable interface and trained users. |
May increase document length and maintenance without improving measurement quality. |
These distinctions depend on context. Detailed interface instructions may be essential for an unfamiliar, high-risk system but unnecessary for a routine task performed by trained personnel.
Which Information Should a Research SOP Normally Contain?
A practical SOP commonly identifies its purpose, scope, responsible personnel, prerequisites, procedure, acceptance criteria, documentation requirements, and actions to take when problems occur.
Document control information may include an identifier, version number, effective date, approval status, and responsible owner.
The exact requirements vary by institution and research context. Some regulated or accredited settings prescribe additional elements.
| SOP element |
Purpose |
Example |
| Purpose and scope |
Define what the procedure covers and when it applies. |
Administration of baseline and posttest achievement assessments. |
| Responsibilities |
Identify who performs, reviews, and authorizes activities. |
Research assistant administers; site coordinator reviews deviations. |
| Prerequisites |
Establish conditions necessary before work begins. |
Training completed and approved instrument available. |
| Operational steps |
Describe the required sequence of actions. |
Verify identity, provide instructions, administer, and record results. |
| Decision rules |
Specify what personnel should do under defined conditions. |
Pause the assessment when a qualifying technical failure occurs. |
| Acceptance criteria |
Define satisfactory completion or performance. |
All required assessment records pass specified validation checks. |
| Documentation |
Identify records that demonstrate implementation. |
Assessment log, incident record, and authorized corrections. |
| Escalation |
Identify situations requiring higher-level review. |
Unresolved participant identity or consent discrepancy. |
These elements should be adapted to the procedure rather than reproduced mechanically in every document.
How Detailed Should the Step-by-Step Instructions Be?
Steps should describe actions at the level necessary to prevent meaningful variation in implementation.
For example, an SOP for a performance assessment may need to specify the exact scoring rubric, the treatment of incomplete responses, and the procedure for resolving scoring discrepancies.
It may not need to explain how to operate a standard computer unless that action presents a genuine risk of error.
Instructions should use clear action verbs and identify the expected result of each consequential step.
Where a procedure involves several decisions, conditional instructions can clarify what happens when a particular condition is met.
Long paragraphs describing multiple actions may be harder to follow than a logically ordered sequence of concise instructions.
Should SOPs Explain Why Each Step Is Necessary?
Brief explanations can improve understanding, particularly when a step may otherwise appear arbitrary.
For example, explaining that assessors must not provide additional hints because doing so could compromise score comparability may reinforce procedural adherence.
However, extensive theoretical discussion generally belongs in the research protocol, training materials, or methodological documentation.
The SOP should prioritize what personnel need to do, when they need to do it, and how they should respond when the procedure cannot be followed.
Explanations are most useful when they support correct decisions rather than simply increase document length.
How Should Personnel Experience Influence the Level of Detail?
Instructions should be appropriate for the people expected to implement them.
Experienced laboratory technicians may require less explanation of routine instrument operation than newly recruited research assistants.
However, prior experience does not eliminate the need to specify study-specific requirements.
For example, an experienced interviewer may understand general interviewing techniques but still need clear instructions about the approved consent process, recording arrangements, and boundaries of the research questions.
The SOP should identify essential requirements while training and competency assessment address the skills needed to implement them.
How Should Risk Determine the Amount of Detail?
High-consequence procedures generally justify more explicit instructions than low-risk administrative tasks.
For example, a procedure governing the correction of primary outcome data should identify who can authorize changes, what source evidence is required, and how original values are preserved.
A routine procedure for naming internal working files may require only a short convention.
Researchers should consider the likelihood of error, the consequences of incorrect execution, and the possibility of detecting and correcting the problem afterward.
Where a mistake could affect participant safety or irreversibly compromise a measurement, the SOP should provide stronger safeguards and clearer escalation criteria.
Should SOPs Include Exact Timing and Numerical Limits?
Yes, when those details are consequential to the procedure.
An assessment SOP may need to specify a fixed duration, permitted administration window, or maximum number of attempts if those conditions affect measurement comparability.
A laboratory procedure may require defined temperatures, volumes, stabilization periods, or acceptable equipment performance limits.
However, numerical requirements should be derived from approved methods, technical specifications, or defensible scientific criteria.
Researchers should not invent arbitrary limits merely to make an SOP appear precise.
Where a range is acceptable, specify the range and explain what happens when observations fall outside it.
How Much Detail Is Necessary for Unexpected Problems?
An SOP should address foreseeable problems that could materially affect implementation.
For example, an electronic assessment procedure may specify what happens when internet connectivity is interrupted, a participant cannot be identified, or the system fails to save a response.
It is rarely practical to describe every conceivable event.
Instead, the SOP should establish general decision boundaries and identify who has authority to resolve circumstances not explicitly covered.
Where an unexpected event may affect participant protection or the approved research design, the procedure should require appropriate escalation rather than allowing collectors to improvise consequential changes.
Should SOPs Include Screenshots and Detailed Software Instructions?
They may be useful when personnel must interact with unfamiliar software or when incorrect selections could compromise data integrity.
For example, a screenshot may help distinguish an authorized data export function from another option that produces incomplete records.
However, screenshots can become outdated when software interfaces change.
Researchers should consider whether a separate work instruction or controlled technical appendix would be easier to maintain.
The main SOP can define the required process while referring to a current technical guide for interface-specific steps.
Should an SOP Repeat the Entire Research Protocol?
No. Repeating extensive protocol content can create unnecessary duplication and increase the risk of conflicting instructions.
The protocol establishes the scientific design and major methodological commitments. The SOP translates relevant procedures into operational actions.
For example, the protocol may explain why a particular achievement instrument was selected and how its scores will be analyzed.
The SOP should focus on how the instrument is administered, scored, recorded, and checked.
Where the SOP depends on a protocol requirement, it should reference the current approved document and remain consistent with it.
How Should SOPs Handle Methodological Flexibility?
Some procedures require consistent execution, while others depend on professional or interpretive judgment.
For example, a structured achievement assessment may require highly standardized instructions. A semi-structured qualitative interview may require flexibility in follow-up questions.
An appropriate SOP can identify essential interview domains, consent requirements, recording procedures, and ethical boundaries while allowing responsive probing.
Such flexibility should be intentional rather than the result of vague instructions.
The distinction between essential standardization and justified flexibility in research SOPs is particularly important for multisite and interpretive studies.
How Can You Test Whether an SOP Contains Enough Detail?
A useful approach is to ask a suitably trained person who did not write the SOP to perform the procedure under controlled or simulated conditions.
Observe whether the person can identify the required steps, make appropriate decisions, and complete the necessary records without repeated clarification.
Pay attention to points where the person hesitates, interprets instructions differently, or relies on undocumented knowledge.
These observations can identify missing operational detail.
Conversely, if personnel repeatedly skip irrelevant instructions or struggle to locate critical steps, the document may need simplification.
Testing should focus on usability and correct implementation rather than document length alone.
How Should SOP Detail Be Managed Across Multiple Sites?
Multisite studies may need common instructions for critical procedures and controlled local supplements for legitimate site differences.
For example, all campuses may follow the same assessment timing and scoring rules while using different approved rooms or secure storage systems.
The main SOP should specify requirements essential to comparability, while local instructions can address operational details that do not change the scientific procedure.
Researchers should ensure that local documents do not contradict the central SOP.
The question of whether all research sites should follow the same SOPs therefore requires attention to both consistency and context.
When Does an SOP Become Too Detailed?
An SOP may be excessively detailed when it duplicates other controlled documents, describes trivial actions unrelated to quality, or makes essential instructions difficult to find.
Excessive detail can also increase maintenance demands. Every minor software or administrative change may require revision even when the underlying scientific procedure remains unchanged.
Researchers should distinguish essential instructions from optional examples, training explanations, and interface-specific guidance.
Supporting documents may be appropriate when they allow the SOP to remain concise without sacrificing necessary detail.
The objective is a document that personnel can use accurately during real work, not an exhaustive narrative of every possible action.
How Should SOPs Be Reviewed and Updated?
Review should consider whether the instructions remain scientifically appropriate, operationally accurate, and consistent with the approved research protocol.
Changes in equipment, software, personnel responsibilities, or institutional requirements may justify revision.
Researchers should preserve appropriate version control and ensure that personnel use the current approved procedure.
Consequential changes may require additional training or governance approval.
Superseded versions should be retained when necessary to establish which instructions governed earlier research activities.
Watch Out
Do not confuse procedural detail with methodological validity. An SOP can describe an unsuitable research procedure with exceptional precision. Scientific justification must come from the research design, measurement evidence, and applicable ethical or technical requirements.
