{
“@context”: “https://schema.org”,
“@type”: “Article”,
“mainEntityOfPage”: {
“@type”: “WebPage”,
“@id”: “https://www.Clinicalstudies.in/SOP-for-Database-Lock-and-Unblinding-Control”
},
“headline”: “SOP for Database Lock and Unblinding Control in Clinical Trials”,
“description”: “This SOP establishes procedures for database lock and unblinding control in clinical trials, ensuring data integrity, blinded trial conduct, and compliance with ICH GCP, FDA, EMA, CDSCO, and WHO regulations.”,
“author”: {
“@type”: “Organization”,
“name”: “ClinicalStudies.in”
},
“publisher”: {
“@type”: “Organization”,
“name”: “ClinicalStudies.in”,
“logo”: {
“@type”: “ImageObject”,
“url”: “https://www.clinicalstudies.in/logo.png”
}
},
“datePublished”: “2025-08-26”,
“dateModified”: “2025-08-26”
}
Published on 23/12/2025
Standard Operating Procedure for Database Lock and Unblinding Control
| Department | Clinical Research |
| SOP No. | CR/DATA/054/2025 |
| Supersedes | NA |
| Page No. | 1 of 22 |
| Issue Date | 26/08/2025 |
| Effective Date | 01/09/2025 |
| Review Date | 01/09/2026 |
Purpose
The purpose of this SOP is to define the process for locking clinical trial databases and managing unblinding in blinded trials. These procedures ensure the integrity
Scope
This SOP applies to sponsors, data managers, statisticians, CROs, and investigators involved in database management. It covers final data cleaning, query resolution, SAE reconciliation, database lock procedures, and controlled unblinding.
Responsibilities
- Data Manager: Ensures database is clean, all queries are resolved, and final dataset is ready for lock.
- Statistician: Confirms database readiness for analysis and manages controlled unblinding procedures.
- PI and Site Staff: Ensure source documents and CRFs are complete and verified before lock.
- Sponsor/CRO: Approves database lock and oversees unblinding procedures.
- QA Officer: Reviews database lock and unblinding records during audits and inspections.
Accountability
The sponsor is accountable for final database lock and controlled unblinding, while the data manager is responsible for operational execution and documentation.
Procedure
1. Pre-Lock Activities
Resolve all outstanding data queries.
Reconcile SAE data with safety database.
Perform consistency checks and final data cleaning.
Conduct a pre-lock review meeting (data management, biostatistics, QA, sponsor).
2. Database Lock
Once all discrepancies are resolved, lock the database in the validated clinical data management system (CDMS).
Generate final data listings and archive them in TMF.
Record lock details in Database Lock Log (Annexure-1).
3. Unblinding Control
Controlled unblinding may only occur after sponsor authorization.
Emergency unblinding (subject-specific) is permitted only for safety reasons and must be documented in Emergency Unblinding Log (Annexure-2).
For interim analyses, partial unblinding must follow pre-defined statistical analysis plan (SAP).
4. Documentation
File database lock certificates, meeting minutes, and logs in TMF.
Ensure ISF has subject-level unblinding documentation if applicable.
5. Archiving
Archive final locked database and unblinding records for at least 15 years or as per local regulations.
Abbreviations
- SOP: Standard Operating Procedure
- CRF: Case Report Form
- PI: Principal Investigator
- CRO: Clinical Research Organization
- QA: Quality Assurance
- TMF: Trial Master File
- ISF: Investigator Site File
- SAE: Serious Adverse Event
- CDMS: Clinical Data Management System
- SAP: Statistical Analysis Plan
Documents
- Database Lock Log (Annexure-1)
- Emergency Unblinding Log (Annexure-2)
- Database Lock Certificate (Annexure-3)
References
- ICH E6(R2) – Good Clinical Practice
- ICH E9 – Statistical Principles for Clinical Trials
- US FDA – Clinical Data Management and Unblinding Guidance
- EMA – Data Management and Unblinding Guidelines
- CDSCO – Clinical Trial Data Lock and Unblinding Requirements
Version: 1.0
Approval Section
| Prepared By | Rajesh Kumar, Data Manager |
| Checked By | Sunita Reddy, QA Officer |
| Approved By | Dr. Anil Sharma, Principal Investigator |
Annexures
Annexure-1: Database Lock Log
| Date | Database Locked By | System | Remarks |
|---|---|---|---|
| 12/09/2025 | Rajesh Kumar | Medidata Rave | Final lock approved by sponsor |
Annexure-2: Emergency Unblinding Log
| Date | Subject ID | Reason for Unblinding | Authorized By | Outcome |
|---|---|---|---|---|
| 15/09/2025 | CT2025-SITE01-181 | Severe adverse reaction requiring treatment adjustment | PI | Unblinded for safety |
Annexure-3: Database Lock Certificate
| Date | Database | Version | Locked By | Approved By |
|---|---|---|---|---|
| 12/09/2025 | Phase III Oncology Trial Database | v3.2 | Data Manager | Sponsor |
Revision History
| Revision Date | Revision No. | Revision Details | Reason for Revision | Approved By |
|---|---|---|---|---|
| 26/08/2025 | 00 | Initial version | New SOP creation | Head, Clinical Research |
For more SOPs visit: Pharma SOP