A standard operating procedure (SOP) in research is a detailed, written set of instructions that tells everyone on a team exactly how to perform a specific task the same way every time. Whether the setting is a chemistry lab, a clinical trial site, or a data management office, SOPs exist to eliminate guesswork, reduce errors, and make results reliable enough that another researcher could repeat the same process and get the same outcome.
Why Research Teams Use SOPs
The core function of an SOP is to prevent deviations. When multiple people handle samples, recruit participants, or record data, small differences in technique can introduce variability that undermines an entire study. A well-written SOP locks in a single, optimized process so that results don’t shift depending on who performed the task or what day it was done.
Beyond consistency, SOPs serve several practical purposes at once. They speed up the onboarding of new staff because a newcomer can read the document and understand the expected process without relying solely on verbal instruction. They create a paper trail that proves work was done correctly, which matters during audits and inspections. They also improve traceability and transparency of research findings, which has a direct impact on whether other scientists can reproduce or build on published results. In clinical settings, SOPs can even accelerate patient care by making treatment protocols immediately clear to every member of the team.
Where SOPs Are Required
In clinical trials, SOPs aren’t optional. The International Council for Harmonisation’s Good Clinical Practice guidelines define SOPs as “detailed, documented instructions to achieve uniformity of the performance of a specific activity.” Sponsors running a trial must establish, implement, and maintain documented procedures that ensure the trial complies with the protocol, GCP standards, and all applicable regulations. Failure to follow SOPs can trigger corrective action, and in serious cases, a sponsor is required to stop shipping an investigational drug to any site that can’t maintain or make its records available.
The FDA reinforces this by requiring that both sponsors and investigators keep records available for inspection. Authorized FDA employees can access, copy, and verify any records related to a clinical investigation. Those records, including SOPs, must be retained for at least two years after a drug receives marketing approval, or two years after the investigation is discontinued if no approval is sought.
Laboratory research has its own SOP requirements. At institutions like UC Berkeley, written SOPs are mandatory for all hazardous operations, whether the hazard is chemical, physical, biological, or radiological. Chemical SOPs are typically organized by hazard class (flammables, carcinogens, oxidizers), and biological research SOPs cover procedures ranging from cell culture to biohazard disposal.
What a Research SOP Typically Includes
While formats vary by institution, most research SOPs share a common structure. The document opens with a title, version number, and effective date. It then states the purpose (what the procedure accomplishes) and the scope (which tasks, people, or situations it covers). A responsibilities section identifies who performs each role. The body of the document lays out step-by-step instructions, often supplemented with flowcharts, tables, or checklists. Finally, most SOPs include references to related documents, a revision history, and a signature block where authorized personnel approve the final version.
Version control matters more than you might expect. Each revision gets a new whole-number version (V1, V2, V3) paired with an effective date. Decimal versions like V1.1 or V2.3 are discouraged in many regulatory environments because they don’t create a clean audit trail. Previous versions and tracked-changes drafts are archived in the study master file so that inspectors can see exactly what changed and when.
How an SOP Gets Created
Developing an SOP is a collaborative process, not a solo writing exercise. The typical lifecycle follows seven steps: develop a template, define the scope and purpose, determine the audience and authors, write and format the document, test and adjust it, distribute it with training, then review and update it on a regular schedule.
During drafting, the guiding questions are straightforward: who does this task, what exactly do they do, when and where do they do it, and how? Language should be simple and direct. Flowcharts and numbered lists work better than dense paragraphs when the goal is for someone to follow the steps in real time.
Testing is where many teams cut corners and regret it later. The person who wrote the SOP should not be the one who tests it. Instead, representatives from every role that will use the document should try to follow it in a realistic setting. Any instruction that causes confusion, doesn’t work in practice, or can’t be reproduced gets revised before the SOP is finalized. Once it passes testing, all staff within the SOP’s scope sign off to confirm they’ve reviewed and understood the procedure.
Training and Documentation
Writing an SOP is only half the job. Every person expected to follow the procedure needs documented training, and that documentation lives in the study’s regulatory binder. Training can happen during a site initiation visit, through face-to-face sessions, by email, or even by reviewing slides and protocol materials independently. Regardless of the format, the key requirement is the same: there must be a record that each team member was trained, what materials they received, and when the training took place. A site training log captures this information for every study team member.
Staff who miss a group training session still need to be brought up to speed individually, with the same materials and the same documentation. This ensures that no one is performing a regulated task based on secondhand instructions or memory alone.
Keeping SOPs Current
An SOP that sits untouched for years can become a liability rather than an asset. Best practice is to review each SOP at least once a year to catch logistical changes, updated regulations, or improved techniques that should be incorporated. Different SOPs may need different review cycles depending on how quickly the underlying process evolves. When a revision is made, the same lifecycle applies: re-test, re-adjust, redistribute, and retrain everyone who uses it. The goal is a living document that always reflects what the team actually does, not what it did two years ago.