SOP-100

Writing, Approving and Controlling SOPs

Number
SOP-100
Category
Governance and Quality System
Edition
Reference Edition 1.3
Approx. pages
9

[YELLOW] the site fills in. [DEFAULT: green] a value the site may keep or change.

On this page

1. Purpose

This SOP describes how [SITE NAME] writes, reviews, approves, issues, trains on, revises and retires its standard operating procedures (SOPs), study-specific work instructions and controlled forms. It also sets the order of precedence between site SOPs and the regulatory, IRB, protocol and sponsor requirements that apply to each study, and describes how the site adopts this SOP library from the template.

2. Scope

This SOP applies to all controlled documents in the [SITE NAME] quality system: SOPs, work instructions, controlled forms and logs, and the SOP Master Index. It applies at every location operated by [SITE NAME].

It does not cover study documents written by sponsors or IRBs (protocols, manuals, consent form templates, IRB policies). The site follows those documents as issued and controls them through SOP-204 Essential Documents and the Investigator Site File.

Throughout this SOP library, follow the protocol, sponsor or IRB requirement where it is stricter than the SOP.

3. Responsibilities

RoleResponsibilities
Quality LeadOwns the SOP system. Maintains the SOP Master Index and review schedule, assigns authors, coordinates review and approval, issues effective versions, retires obsolete versions, tracks SOP training, approves planned SOP deviations and reviews unplanned ones.
Site DirectorApproves SOPs for operational fit and resources. Confirms the site can staff and fund each procedure before it becomes effective. Acts as Quality Lead where the roles are combined.
Principal Investigator (PI)Approves SOPs that affect investigator duties, participant safety, informed consent, investigational product or data integrity. Raises the need for a new or revised SOP when practice changes.
SOP AuthorDrafts or revises the SOP using the site template and this SOP. Consults the staff who perform the process.
Regulatory CoordinatorFiles SOP-related records that a sponsor or IRB requests for a study. Tells the Quality Lead about new IRB or sponsor requirements that may need an SOP change.
Network Quality Lead (Model N only)Owns the network SOP library and performs the Quality Lead duties in this SOP for network SOPs. Approves local addenda (F-900-01). Trends SOP deviations across member sites.
Site Quality Lead (Model N only)Performs the Quality Lead duties in this SOP for the member site: site training before the effective date, site-only SOPs and work instructions, local addenda drafts and site SOP deviations.
All Research StaffRead and acknowledge SOPs before the effective date or before performing the task. Follow the current effective version. Report any SOP deviation or any SOP that does not match how work is done.

4. Definitions

TermDefinition
Standard Operating Procedure (SOP)Detailed, documented instructions to achieve uniformity of the performance of a specific activity (ICH E6(R3) Glossary). At [SITE NAME], an SOP applies to all studies.
Work Instruction (WI)A controlled, site-written document that gives step-level detail for one study, one system or one location. It must not conflict with an SOP.
Controlled FormA form or log template issued under this SOP with a form code (for example, F-302-01).
Controlled DocumentAn SOP, WI or controlled form that has an identifier, version number, effective date and approval record.
Effective DateThe date from which staff must follow a version. Training is completed before this date.
Obsolete (Superseded) VersionA version replaced by a newer version or retired without replacement.
SOP DeviationAny departure from an effective SOP. Planned deviations are approved in advance; unplanned deviations are discovered after they happen.
must / should / mayUsed across this SOP library with fixed meanings. must = required by regulation or by this SOP library. should = expected practice unless a documented reason exists for doing otherwise. may = permitted but optional.
Site DecisionA choice this SOP library leaves to the site. Each is marked "Site decision" in the text and is recorded when the site adopts the library.
Operating ModelHow the library is run: Model S (single site: one legal entity, one leadership team, one or more locations) or Model N (a Network Office plus two or more member sites). Model N is either N-Integrated (the member sites and the network entity are one legal entity) or N-Affiliated (separate legal entities bound by a network or affiliation agreement). Model S records it in the SOP-100 operating model Site decision and on F-100-03; Model N records it on F-900-02.
Network OfficeIn Model N, the central organization that issues the network SOP library and provides the central functions assigned to it in Appendix B.
Member SiteIn Model N, a site that conducts studies under the network SOP library. In N-Affiliated, each member site is a separate legal entity.
Local AddendumA controlled site document, recorded on F-900-01, that adds site-specific detail or stricter requirements to a network SOP. It cannot lower a network requirement.
[DEFAULT: ...]A value set by this library that the site may change at adoption or later through revision under this SOP.

5. Procedure

5.1 Order of precedence

5.1.1
All Research Staff apply requirements in this order when they overlap:
  • applicable law and regulation (for example, 21 CFR 50, 54, 56, 312, 812, HIPAA, state law)
  • determinations and policies of the reviewing IRB for the study
  • the IRB-approved protocol and sponsor written instructions that apply to the study (for example, pharmacy manual, laboratory manual, clinical trial agreement terms)
  • [SITE NAME] SOPs
  • [SITE NAME] work instructions and job aids
5.1.2
Where a site SOP is stricter than the protocol or sponsor instruction and the two can both be met, staff follow both. Example: the protocol is silent on temperature log review and the SOP requires daily review; staff review daily.
5.1.3
Where a site SOP and a protocol or sponsor instruction cannot both be met, staff follow the protocol or sponsor instruction, provided it complies with regulation and IRB requirements. The CRC or Regulatory Coordinator documents the conflict on F-306-01 Note to File in the Investigator Site File (ISF) and informs the Quality Lead. If the conflict will recur across studies, the Quality Lead opens an SOP revision.
5.1.4
No SOP, work instruction or sponsor instruction overrides an action needed to eliminate an immediate hazard to a participant. Deviations taken for that reason are handled under SOP-308 Protocol Deviations and Noncompliance.

5.2 Document types and numbering

5.2.1
SOPs are numbered SOP-XXX by series:
  • 100 Governance and quality system
  • 200 Start-up and regulatory
  • 300 Study conduct
  • 400 Data, privacy and systems
  • 500 Safety
  • 600 Monitoring and closeout
  • 700 Quality assurance
  • 800 Investigator-initiated research
  • 900 Network (Model N only)
5.2.2
Forms carry the number of their parent SOP plus a sequence: F-XXX-NN (for example, F-103-01 belongs to SOP-103). Appendices to the library are lettered (Appendix A).
5.2.3
Work instructions are numbered WI-XXX-NN, where XXX is the parent SOP. A study-specific WI also carries the protocol number in its title.
5.2.4
Versions are numbered "major.minor". The first approved version is 1.0. A change to what staff do, who does it, or a timeline is a major change (1.0 to 2.0). An editorial change that does not change the procedure (spelling, formatting, a corrected cross-reference) is a minor change (1.0 to 1.1). The Quality Lead decides the category and records it on F-100-01 SOP Review and Approval Record.
5.2.5
Every controlled document shows its identifier, title, version, effective date and page numbering. The revision history and approval block are part of each SOP.

5.3 Writing a new SOP or work instruction

5.3.1
Any staff member may request a new or revised SOP or WI by sending the request and reason to the Quality Lead. Triggers include a new type of study or service, a regulatory or guidance change, an inspection, audit or monitoring finding, a CAPA (SOP-703 Corrective and Preventive Action), a change in systems or vendors, or a recurring SOP deviation.
5.3.2
The Quality Lead assigns an author and a target date and records the request on F-100-03 SOP Master Index and Review Schedule.
5.3.3
The author drafts in the site SOP template and follows these rules:
  • the procedure states who does what, when, and which record proves it
  • one process per SOP; cross-reference other SOPs instead of repeating them
  • must, should and may are used only with the meanings in Section 4
  • regulatory citations are checked against the current text of the regulation or guidance
  • site-specific values are shown as placeholders or [DEFAULT: ...] values until decided
5.3.4
The author consults at least one person who performs the process. For a WI, the author confirms it matches the parent SOP.

5.4 Review and approval

5.4.1
The Quality Lead routes the draft for review to the staff who perform the process and to the PI when the SOP affects investigator duties, participant safety, informed consent, investigational product or data integrity. Reviewers return comments by the date the Quality Lead sets.
5.4.2
The author resolves each comment. The Quality Lead keeps the comment record with F-100-01.
5.4.3
Approval signatures are recorded on F-100-01 and in the SOP approval block:
  • SOPs: Author, Quality Lead, Site Director, and the PI or Medical Director where 5.4.1 applies
  • Work instructions: Author and Quality Lead; add the PI for a study-specific WI that affects participant care or data
  • Controlled forms: Quality Lead, with the parent SOP or as a minor change
5.4.4
One person must not be the only approver of an SOP they wrote. Where the Quality Lead is the author, the Site Director and a second reviewer approve. Where one person is Quality Lead, Site Director and author, the PI or a qualified external reviewer approves.
5.4.5
Signatures may be wet ink or electronic. Electronic signatures used on SOP records meet the site's controls for computerized systems under SOP-401 Computerized Systems and Electronic Records (21 CFR 11 where it applies).

5.5 Effective date and training before effective

5.5.1
The Quality Lead sets the effective date when the SOP is approved. The effective date is at least [DEFAULT: 14 calendar days] after approval so staff can complete training.
5.5.2
The Quality Lead identifies which roles must be trained on the new or revised SOP and records the assignment on F-103-01 Staff Training Log or in the training system.
5.5.3
Each assigned staff member reads the SOP (for a major change, the changed sections at minimum, with a summary of changes) and signs F-100-02 SOP Training Acknowledgment before the effective date. For SOPs that need a demonstration (for example, IP handling or specimen shipping), training follows SOP-103 Staff Qualification, Training and Training Records.
5.5.4
A staff member who has not completed training on an SOP must not perform the tasks it covers after the effective date until trained. The Quality Lead checks training completion before the effective date and either moves the date or restricts tasks for untrained staff.
5.5.5
Minor changes may be released with a read-and-acknowledge notice at the Quality Lead's discretion.

5.6 Issue and access

5.6.1
The Quality Lead publishes effective versions in a single controlled location: [SOP REPOSITORY LOCATION, e.g., read-only folder or document management system]. Only the Quality Lead (and a named backup) has edit rights.
5.6.2
Printed copies are uncontrolled unless the Quality Lead issues them as numbered controlled copies. Each printed page carries the statement "Uncontrolled when printed. Check the SOP repository for the current version."
5.6.3
When a sponsor, monitor, auditor or inspector asks for SOPs, the Regulatory Coordinator or Quality Lead provides the version effective during the period under review and records what was provided (for inspections, on F-702-01 Inspection Request and Document Log).

5.7 Periodic review

5.7.1
The Quality Lead reviews each SOP at least every [DEFAULT: 2 years] from its effective date, and sooner when a trigger in 5.3.1 occurs. Due dates are tracked on F-100-03.
5.7.2
The reviewer checks the SOP against current regulations and guidance, recent audit and monitoring findings, CAPAs, SOP deviations and actual practice. The reviewer records the outcome on F-100-01 as one of:
  • no change needed: the version number stays the same; the review date is recorded and the next review date is set
  • minor change: revise under 5.2.4
  • major change: revise and approve under 5.3 and 5.4
5.7.3
An SOP past its review date stays effective. The Quality Lead completes the overdue review within [DEFAULT: 60 calendar days] and records the reason for the delay.

5.8 Obsolete versions

5.8.1
When a new version becomes effective, the Quality Lead removes the old version from the controlled location and from all points of use the same day, and collects or destroys numbered printed copies.
5.8.2
The Quality Lead keeps one archived copy of every obsolete version, marked "SUPERSEDED" with the date, together with its F-100-01 record and training records. Archived versions are kept for at least as long as the records of any study conducted while that version was effective must be kept (see SOP-402 Record Retention, Archiving and Destruction).
5.8.3
When an SOP is retired without replacement, the Quality Lead records the reason on F-100-01 and updates F-100-03.

5.9 Deviations from an SOP

5.9.1
A planned deviation is a decision made before the work to depart from an SOP for a stated reason (for example, a sponsor requires a different process, or a location lacks equipment for a period). The requester documents the deviation, the reason, the duration and any controls on F-306-01 Note to File. The Quality Lead approves it before the work starts, and the PI also approves it when 5.4.1 applies. Study-specific notes are filed in the ISF; others are kept with the SOP records.
5.9.2
An unplanned deviation is a departure discovered after the fact. The staff member who finds it reports it to the Quality Lead within [DEFAULT: 2 business days] of discovery. Where the departure is also a protocol deviation or a consent error, the same-day report to the CRC or PI under SOP-308 5.3.1 (and SOP-301 for consent) comes first; this report to the Quality Lead does not delay it.
5.9.3
The Quality Lead assesses each unplanned deviation:
  • whether it also is a protocol deviation or a regulatory noncompliance (if so, it is handled under SOP-308 as well)
  • whether participant safety, rights or data reliability were affected
  • whether the SOP is wrong, unclear or not trained, or whether the staff member did not follow it
5.9.4
The Quality Lead opens a CAPA on F-703-01 CAPA Record for any deviation that affected participant safety, rights or data reliability, or that recurs. Trends are reviewed at least [DEFAULT: quarterly].
5.9.5
Repeated planned deviations from the same SOP mean the SOP no longer fits practice. The Quality Lead opens a revision.

5.10 Adopting this SOP library from the template

5.10.1
The Site Director appoints the Quality Lead and approves an adoption plan with target dates.
5.10.1.1
As part of the adoption plan, leadership records the operating model: Model S, Model N-Integrated or Model N-Affiliated. In Model S, the Site Director records it in the Site decision below and on F-100-03 SOP Master Index and Review Schedule. In Model N, it is recorded on F-900-02 Network Operating Model and Appendix B Adoption Record; the Network Office leadership and the Site Director of each member site sign, and the record also states which Appendix B Central and Site Responsibility Matrix defaults the network adopts or changes.
5.10.2
The Quality Lead, with the PI and Regulatory Coordinator, completes these steps before the first effective date:
  • replace every bracketed placeholder (for example, [SITE NAME], [CENTRAL IRB NAME], [STATE]) with the site's information
  • resolve each "Site decision" box by writing the decision into the box, or replacing the box with the resulting procedure text
  • confirm or change each [DEFAULT: ...] value and remove the DEFAULT marker
  • complete Appendix A State Law Worksheet for every state where the site has a location or enrolls participants, with sources and the date checked
  • read the Regulatory Currency Note and confirm each listed item against current sources
  • delete or mark "not applicable" any SOP or section for activities the site does not perform (for example, SOP-800 if the site never holds an IND or IDE), and record that decision on F-100-03
  • compare each SOP with current practice, sponsor contract obligations and the reviewing IRB's policies, and list gaps that need resources or training
5.10.3
The Quality Lead loads the forms set, assigns each form to its parent SOP, and adds site details (logo, location fields) without changing form content except through this SOP.
5.10.4
Approval and training for the adopted library follow 5.4 and 5.5. All SOPs may share one effective date. Version numbering starts at 1.0 for the site's adopted versions.
5.10.5
Any SOPs the site used before adoption are retired under 5.8 on the effective date of the adopted library. The Quality Lead maps each retired SOP to its replacement on F-100-03 so auditors can trace the change.
5.10.6
The Regulatory Coordinator gives sponsors and the reviewing IRB the new SOP index when they ask, or when a contract requires notice of SOP changes.

5.11 SOP control in a network (Model N only)

This section applies only in Model N. Model S sites skip it.

5.11.1
The Network Office owns the network SOP library. The Network Quality Lead performs the Quality Lead duties in 5.2 to 5.9 for network SOPs, network work instructions and network forms: master index (F-100-03), authors, review routing, effective dates, the single controlled repository, periodic review and obsolete versions. Governance of the library, including approval of network SOPs by the Network Quality Committee, follows SOP-900 Network Governance, SOP Hierarchy and Local Addenda.
5.11.2
Each member site follows the network SOPs as issued. A member site may add a local addendum on F-900-01 Local Addendum to a Network SOP, under SOP-900, to add detail for its own locations, systems, state law (Appendix A), local IRB or hospital requirements, or to set a stricter requirement. A local addendum must not remove a step, lower a requirement, lengthen a timeline, or move a duty away from the role the network SOP names. It must never move an investigator duty away from the PI.
5.11.3
Approval signatures in Model N are recorded on F-100-01 and in the approval block:
  • network SOPs: Author, Network Quality Lead, the Network Executive (SOP-900), and the Network Medical Director or a PI named by the Network Office where 5.4.1 applies
  • adoption at each member site: Site Director and Site Quality Lead, recording that the site has adopted the version and trained staff before the effective date (5.11.5)
  • local addenda: Author, Site Quality Lead, Site Director, the site PI or clinical approver where 5.4.1 applies, and the Network Quality Lead, who confirms the addendum does not lower a network requirement
  • site-only SOPs and site work instructions: as in 5.4.3, with notice to the Network Quality Lead
5.11.4
N-Integrated: where the member sites and the network entity are one legal entity, network approval makes a network SOP binding at every site from its effective date. N-Integrated defaults apply only where the member site and the network entity are the same legal entity. A separate subsidiary, or a professional corporation under a management services arrangement, follows the N-Affiliated rows for PHI, direction of staff, contract signature, records custody and payments unless counsel confirms otherwise (SOP-900, 5.2.1). N-Affiliated: each member site is a separate legal entity, and the Network Office cannot bind it except as the network or affiliation agreement allows. The member site adopts each network SOP as its own procedure by the Site Director's adoption signature in 5.11.3. Until the site signs, its existing procedure stays effective and the Site Quality Lead tells the Network Quality Lead.
5.11.5
The Network Quality Lead sets the network effective date. The Site Quality Lead confirms site training under 5.5 before that date. Where a site cannot finish training in time, the Network Quality Lead records a later site effective date on F-100-03. Until then that site keeps the previous version (SOP-900 5.7.3).
5.11.6
Planned deviations from a network SOP at a member site follow 5.9.1, with approval by the Site Quality Lead and, where Appendix B assigns it, the Network Quality Lead (Appendix B, SOP-100 rows). The Site Quality Lead reports unplanned deviations from network SOPs to the Network Quality Lead, who trends them across sites under SOP-903 Network Oversight of Member Sites (Metrics, Central QA, Escalation). A deviation that recurs at more than one site leads to a network SOP revision.
5.11.7
A member site may keep site-only SOPs for activities the network library does not cover. The Site Quality Lead controls them under this SOP, lists them on the site's F-100-03 and sends the list to the Network Quality Lead. When the network later issues an SOP on the same activity, the site-only SOP is retired under 5.8 or converted to a local addendum.
5.11.8
When a member site joins or leaves the network, the move from its own SOPs to network SOPs, or back, follows SOP-901 Member Site Onboarding, Integration and Exit. On exit, the site keeps the network SOP versions that were effective during its studies, with their training records, for the retention period in 5.8.2.
  • F-100-01 SOP Review and Approval Record
  • F-100-02 SOP Training Acknowledgment
  • F-100-03 SOP Master Index and Review Schedule
  • F-103-01 Staff Training Log
  • F-306-01 Note to File
  • F-703-01 CAPA Record
  • F-702-01 Inspection Request and Document Log
  • F-900-01 Local Addendum to a Network SOP (Model N only)
  • F-900-02 Network Operating Model and Appendix B Adoption Record (Model N only)
  • Appendix A State Law Worksheet
  • Appendix B Central and Site Responsibility Matrix (Model N only)
  • SOP-103 Staff Qualification, Training and Training Records
  • SOP-204 Essential Documents and the Investigator Site File
  • SOP-308 Protocol Deviations and Noncompliance
  • SOP-401 Computerized Systems and Electronic Records
  • SOP-402 Record Retention, Archiving and Destruction
  • SOP-703 Corrective and Preventive Action (CAPA)
  • SOP-900 Network Governance, SOP Hierarchy and Local Addenda (Model N only)
  • SOP-901 Member Site Onboarding, Integration and Exit (Model N only)
  • SOP-903 Network Oversight of Member Sites (Metrics, Central QA, Escalation) (Model N only)

7. References

ReferenceTitle
ICH E6(R3) Principle 6Quality should be built into the scientific and operational design and conduct of clinical trials
ICH E6(R3) Principle 10Roles and responsibilities in clinical trials should be clear and documented appropriately
ICH E6(R3) Appendix C, C.2.1 and C.2.12Management of Essential Records (version control; SOPs as non-trial-specific essential records)
ICH E6(R3) GlossaryStandard Operating Procedures (SOPs)
21 CFR 11Electronic Records; Electronic Signatures
21 CFR 312.60General responsibilities of investigators
21 CFR 812.100General responsibilities of investigators
FDA Compliance Program 7348.811Bioresearch Monitoring: Clinical Investigators and Sponsor-Investigators

Independent Site SOP Library. Licensed CC BY-NC 4.0 by the American Institute for Medical Research (AIMR), with added permission for any site's internal use (license terms). Not legal advice: each adopting site confirms state law, IRB and sponsor requirements with its own counsel and owns every step it approves.