03 · What You Need to Know
How to Establish and Maintain Effective Research SOP Compliance
What Does SOP Compliance Mean in Research?
SOP compliance means that personnel perform applicable research activities according to the requirements of the approved procedures in effect at the time.
Compliance may involve following specified steps, using approved instruments, maintaining required records, observing decision boundaries, and escalating situations that cannot be resolved under existing instructions.
However, compliance does not necessarily mean that every researcher must behave identically in every circumstance.
For example, a semi-structured interviewer may legitimately vary follow-up questions while maintaining the approved consent, confidentiality, and methodological requirements.
Compliance should therefore be evaluated against the actual requirements of the procedure, including any permitted flexibility.
Why Are Approved SOPs Sometimes Not Followed?
Procedural noncompliance may arise from several sources. Personnel may misunderstand instructions, lack practical training, use outdated documents, encounter unsuitable equipment, or work under conditions that make the approved procedure difficult to implement.
Some deviations reflect individual mistakes. Others arise from organizational weaknesses, such as unrealistic workloads, conflicting instructions, inadequate supervision, or poorly designed systems.
For example, repeated failure to upload data within a specified period may reflect unreliable internet connectivity rather than deliberate disregard of the SOP.
Researchers should therefore investigate the circumstances of noncompliance before deciding what corrective action is appropriate.
Simply reminding personnel to follow the SOP may be ineffective when the underlying problem is an impractical procedure.
What Is the Difference Between SOP Availability, Understanding, and Compliance?
These are related but distinct conditions.
SOP availability
Personnel can access the current approved instructions relevant to their responsibilities.
SOP understanding
Personnel know what the instructions require and can explain consequential decisions.
Procedural competence
Personnel can demonstrate the skills necessary to implement the procedure.
Actual compliance
Personnel implement the applicable requirements during real research activities.
A signed acknowledgment may establish that a document was received. It does not necessarily establish understanding, competence, or actual adherence.
1. Make SOPs Accessible and Operationally Usable
Personnel cannot reliably follow procedures that are difficult to locate, ambiguous, or unnecessarily complicated.
Research teams should maintain an accessible collection of current approved SOPs, with clear document identifiers, version numbers, and effective dates.
Instructions should be organized around the actual workflow and written at a level appropriate for their intended users.
For example, an assessment administration SOP should make the requirements for participant identification, instructions, timing, interruptions, and recording easy to find.
Where detailed software instructions are necessary, a controlled work instruction may be more practical than embedding numerous screenshots in the main SOP.
The principles for determining how detailed a research SOP should be can help avoid both ambiguity and unnecessary complexity.
2. Assign Clear Responsibility for Implementation
Every critical procedure should have an identifiable person or role responsible for implementation and oversight.
For example, research assistants may administer assessments, site coordinators may review administration logs, and a data manager may investigate discrepancies in transferred records.
Responsibilities should distinguish performing a task from reviewing its implementation and authorizing corrective action.
Where several people share responsibility, the SOP should clarify how information moves between them.
Unclear accountability can allow problems to remain unresolved because each person assumes someone else is responsible.
3. Provide Training Before Independent Implementation
Personnel should receive training appropriate to the procedures they will perform.
Training should address the purpose of the procedure, required steps, critical decision rules, documentation, and responses to foreseeable problems.
For example, an assistant administering a standardized assessment should understand not only the approved instructions but also what to do when a participant requests clarification or the assessment platform becomes unavailable.
Training should include practical demonstrations when written instructions alone are insufficient.
Where errors could have consequential effects, supervised practice and competency assessment may be justified.
These arrangements should align with standardized training for research data collectors.
4. Verify Competence Rather Than Relying on Attendance
Attendance at a training session does not necessarily establish the ability to perform a procedure correctly.
Competency assessment may involve simulated participant encounters, observed demonstrations, scoring exercises, or practical data management tasks.
For example, an assistant may be asked to administer a mock assessment while an evaluator checks whether critical procedural requirements are satisfied.
Performance criteria should reflect the consequences of error and be defined before assessment.
Not every task requires formal certification. However, personnel should not independently perform critical procedures when required competence has not been established.
The distinction between training and study-specific authorization or certification should remain clear.
5. Monitor Actual Performance During Data Collection
Training establishes initial readiness, but it does not guarantee continued compliance.
Researchers may need to monitor whether personnel maintain the required procedures during actual implementation.
Monitoring methods can include direct observation, review of completed records, system-generated logs, selected source verification, and examination of procedural deviations.
For example, an electronic assessment system may record administration duration, submission timestamps, and technical interruptions.
These records can help identify unusual patterns, although they may not reveal every form of noncompliance.
Monitoring should focus on critical requirements rather than every minor administrative action.
Which Monitoring Methods Are Appropriate?
Different methods provide evidence about different aspects of implementation.
| Monitoring method |
What it can establish |
Important limitation |
| Direct observation |
Whether selected procedural steps are performed as required. |
Personnel may behave differently while being observed. |
| Record review |
Whether required documentation is complete and internally consistent. |
Complete records do not necessarily prove correct performance. |
| Electronic system logs |
Timing, access, transactions, and selected recorded actions. |
Logs may not capture the full context of an activity. |
| Source data verification |
Whether selected database entries correspond to authoritative source records. |
Does not establish the validity of the original measurement. |
| Staff interviews or debriefings |
Operational difficulties, misunderstandings, and informal workarounds. |
Accounts may be incomplete or affected by recall and social desirability. |
| Deviation trend analysis |
Recurring procedural problems across time, personnel, or sites. |
Reported deviations may underestimate actual occurrences. |
Using complementary methods may provide a more informative picture than relying on a single compliance indicator.
6. Prioritize Critical SOP Requirements
Not every procedural step carries the same scientific or ethical consequences.
Monitoring should prioritize requirements that protect participants, determine eligibility, generate primary measurements, govern intervention delivery, or maintain data integrity.
For example, verifying that assessors follow standardized scoring rules may be more consequential than checking whether administrative files use a preferred naming convention.
However, apparently minor steps may become important when they support record linkage or traceability.
Risk assessment should therefore consider the function of each requirement rather than its apparent complexity.
The broader principles of proportionate research quality control can inform monitoring intensity.
7. Establish Practical Compliance Indicators
Compliance indicators should reflect observable requirements and provide information that can support corrective decisions.
Examples include the proportion of assessments administered within approved conditions, completion of required eligibility checks, frequency of unauthorized data corrections, and number of unresolved critical deviations.
A simple compliance proportion may be calculated when the procedure defines a clear set of applicable opportunities.
The result describes the reviewed activities, not necessarily all activities conducted in the study.
Its interpretation depends on how observations were selected, which requirements were assessed, and whether the consequences of different deviations are comparable.
A high overall rate should not obscure a small number of serious failures.
8. Distinguish Compliance Monitoring From Research Auditing
Routine monitoring and formal auditing serve related but different purposes.
Monitoring is an ongoing process for evaluating implementation, identifying problems, and supporting timely correction.
Auditing generally involves a more systematic evaluation against specified requirements, potentially conducted by personnel independent of the activities being examined.
Not every nonregulated study requires a formal independent audit.
However, complex, high-risk, multisite, or regulated research may benefit from stronger review arrangements or be subject to specific auditing obligations.
Researchers should select the level of oversight according to the study's risks and applicable governance requirements.
9. Create a Process for Reporting Deviations
Personnel should know how to report departures from approved procedures and which events require immediate escalation.
For example, a minor administrative error may be addressed through a routine log, while a deviation affecting consent or primary outcome measurement may require prompt investigation.
The reporting process should identify what information must be recorded, who reviews the event, and how decisions are documented.
Researchers should avoid creating conditions in which staff conceal problems because reporting is automatically associated with punishment.
The purpose of documenting research SOP deviations is to support accountability, impact assessment, and improvement.
10. Investigate Why Noncompliance Occurred
When a deviation is identified, the team should examine its underlying causes.
Possible explanations include unclear instructions, inadequate training, excessive workload, equipment failure, insufficient resources, or deliberate departure from approved requirements.
For example, repeated failures to complete a required verification step may indicate that the workflow places the verification after a point where the necessary source information is no longer available.
In such circumstances, redesigning the workflow may be more effective than issuing repeated reminders.
Investigations should distinguish individual performance problems from systemic weaknesses.
11. Use Corrective and Preventive Action Appropriately
Corrective action should address the cause of an identified problem rather than only its immediate manifestation.
For example, correcting several mislinked participant records resolves the affected entries, but improving the identifier verification procedure may reduce future errors.
Preventive action may be justified when monitoring reveals a plausible risk before another failure occurs.
For consequential problems, the research team should document the proposed action, responsible person, implementation date, and evidence of effectiveness.
Not every minor error requires an extensive formal corrective and preventive action process.
The response should be proportionate to the risk and likelihood of recurrence.
12. Verify Whether Corrective Actions Actually Work
Implementing corrective action does not automatically establish that the problem has been resolved.
Researchers should examine whether the revised procedure, additional training, or technical correction produces the intended improvement.
For example, after retraining personnel on participant identifier verification, the team may review subsequent records to determine whether mismatches continue.
If the problem persists, the underlying explanation may be incomplete.
Effectiveness checks should be planned according to the nature of the corrective action and the consequences of failure.
13. Manage SOP Compliance Across Multiple Sites
Multisite studies may require common compliance criteria for critical procedures, even when local operational arrangements differ.
A coordinating center may establish monitoring requirements, reporting formats, and escalation criteria.
Local supervisors can review implementation and provide contextual explanations for unusual patterns.
However, comparing sites solely by the number of reported deviations may be misleading. A site with more reports may have stronger detection and reporting practices rather than worse implementation.
Cross-site evaluation should consider monitoring coverage, participant characteristics, procedural complexity, and the severity of identified problems.
14. How Should Compliance Be Evaluated in Qualitative Research?
Qualitative research may involve procedures that legitimately permit responsive questioning, iterative sampling, or contextual adaptation.
Compliance should therefore be assessed against the methodological and ethical commitments of the study rather than a universal requirement for identical behavior.
For example, interviewers may vary their probes while consistently observing approved consent procedures, confidentiality safeguards, and recording requirements.
Reflexive thematic analysis does not ordinarily require analysts to produce identical codes as evidence of compliance.
Monitoring should preserve the distinction between justified methodological flexibility and departures from essential requirements.
15. What If the SOP Is Impractical or Outdated?
Repeated noncompliance may indicate that the SOP itself needs review.
For example, an instruction may refer to software that has been replaced or require a workflow that cannot be completed with available equipment.
Personnel should report these problems rather than silently invent permanent workarounds.
The responsible authority should evaluate whether a controlled revision is necessary.
Changes should follow the applicable process for approving research SOP revisions, including additional governance review when required.
Approval of a revised SOP does not automatically erase earlier deviations.
16. How Much SOP Monitoring Is Enough?
There is no universal monitoring frequency or compliance threshold suitable for every study.
A small, low-risk research project may use periodic supervision and selected record reviews. A complex intervention involving several sites and critical outcomes may require more frequent and structured monitoring.
The appropriate intensity depends on procedural risks, existing controls, collection duration, personnel experience, and the consequences of undetected failures.
Monitoring should also be feasible. A procedure requiring daily review is of limited value if the responsible person cannot complete it.
The objective is credible assurance about consequential implementation requirements, not maximum surveillance of research personnel.
Watch Out
Do not equate a completed checklist, signed training acknowledgment, or high overall compliance percentage with evidence that every critical procedure was performed correctly. Compliance monitoring should examine actual implementation and give particular attention to serious or recurring deviations that may be hidden by favorable aggregate indicators.