Russian 
English 
Turkish 
Spanish 
French 
German 
Japanese 
Standard operating procedure for managing the list of Quality Assurance SOPs in the Pharmaceutical Industry.
1.0 ЦЕЛЬ:
To lay down the procedure for preparing, maintaining, and controlling the Master List of Quality Assurance Standard Operating Procedures across the pharmaceutical plant. The goal is simple: every active QA SOP gets accounted for, and every obsolete version gets pulled out of use.
2.0 ОБЛАСТЬ ПРИМЕНЕНИЯ:
This Procedure covers the Master List of SOPs that the Quality Assurance department owns. All QA SOPs currently in force across manufacturing, quality control, warehouse, engineering, and administration departments fall under the scope.
3.0 ОТВЕТСТВЕННОСТЬ:
Document Controller & QA Officer
4.0 ОТВЕТСТВЕННОСТЬ:
QA Head.
5.0 ПРОЦЕДУРА:
5.1 The Master List of SOPs sits as a controlled document and captures every active QA SOP at the site. Day to day, the Document Controller takes care of the list. The QA Head supervises that work directly.
5.2 A controlled electronic file holds the list, and that file carries its own unique document number. Paper copies only get printed on demand, such as during audits or when someone has to review the list offline.
5.3 Each time a new SOP, a revision, or a withdrawal goes through, the Master List has to be updated within one working day. Each update is dated and signed by the Document Controller.
5.4 Any department that needs to pick up a current SOP has to check the Master List first to find the right version. Do not use any SOP unless it shows up on the Master List as active.
5.5 Structure of the Master List:
5.5.1 A fixed set of columns makes up the Master List. Each row belongs to one SOP, and each column holds one data field for that SOP.
5.5.2 The required columns on the Master List are spelled out below:
5.5.2.1 SOP Number: a unique identifier given at the time of first release. Across revisions, this number stays the same.
5.5.2.2 SOP Title: the full title as shown on the document header.
5.5.2.3 Current Version: the version number of whichever SOP is active right now. With every formal revision, the version number bumps up by one.
5.5.2.4 Effective Date: the date on which the current version came into use.
5.5.2.5 Next Review Date: when the next periodic review is scheduled. As a rule of thumb, this falls two years after the effective date.
5.5.2.6 Document Owner: the department or the role that owns the content of the SOP.
5.5.2.7 Status: one of four values as defined below.
5.5.2.7.1 Active: staff are using this SOP right now and must follow it.
5.5.2.7.2 Under Revision: a new version is being drafted. The old version stays Active for the duration of this phase.
5.5.2.7.3 Withdrawn: whatever activity the SOP used to cover is no longer done at the site. No active version is left.
5.5.2.7.4 Archived: an older version that a newer Active version has replaced. These stay on file to preserve the audit trail.
5.5.3 Extra columns can be added to cover site specific needs. Cross reference numbers, related forms, and training requirements are common additions.
5.5.4 The Master List is sorted by SOP Number. For anyone searching by name instead, a second sorted view by SOP Title is kept in a separate index tab.
5.6 SOP Categories:
5.6.1 Every QA SOP on the Master List carries a category tag based on what it covers. Categories save staff from scrolling through the full list whenever they need a single procedure.
5.6.2 The standard QA SOP categories are as follows:
5.6.2.1 Document Control SOPs: all the usual document work, from writing and reviewing, through approval and issuance, and on through retention.
5.6.2.2 Change Control SOPs: the review and sign-off of any proposed change to a product, a process, or a system.
5.6.2.3 Deviation and CAPA SOPs: deviations from procedure and the follow-up corrective and preventive actions that close them out.
5.6.2.4 Batch Release SOPs: the steps that take a batch from manufacturing through to final release to the market.
5.6.2.5 Complaint Handling SOPs: receiving a product complaint, investigating it, and closing it.
5.6.2.6 Audit SOPs: internal audits, supplier audits, and regulatory inspections.
5.6.2.7 Training SOPs: training staff on new or revised procedures.
5.6.2.8 Validation and Qualification SOPs: the full lifecycle of equipment, utility, and process validation.
5.6.2.9 Environmental Control SOPs: temperature, humidity, particle, and microbial monitoring.
5.6.2.10 Recall and Market Action SOPs: product recalls and any related market actions.
5.6.3 Every new SOP has to be assigned to one primary category. Where the content spans more than one area, cross references to secondary categories can be listed as well.
5.7 Adding a New SOP to the List:
5.7.1 Raising a new SOP starts with the Document Request Form. On the form, the requester fills in the proposed title, the category, the document owner, and the business reason for the SOP.
5.7.2 The Document Controller then looks through the request to confirm that no similar SOP already exists. If one does, the request goes back to the requester with a pointer to the current SOP.
5.7.3 Once the request is approved, the Document Controller hands out a unique SOP Number and holds a place for it on the Master List. The status sits at Under Revision until the first version has been issued.
5.7.4 Drafting the SOP falls to the document owner, using the current Document Template. That draft then goes around to all affected departments for review.
5.7.5 After the final draft has been approved and signed, the Document Controller enters the effective date on the Master List and flips the status across to Active.
5.7.6 The approved SOP then reaches all affected users through the Document Distribution Record. Training on the new SOP is set up within 15 days of issue.
5.8 Revising an Existing SOP:
5.8.1 Several triggers can call for a revision:
5.8.1.1 A scheduled periodic review turns up updates that need to go in.
5.8.1.2 A change control action calls for a procedure change.
5.8.1.3 A deviation investigation flags a gap in the current procedure.
5.8.1.4 A regulatory update brings in new requirements.
5.8.1.5 Equipment or process changes leave the current SOP out of step with reality.
5.8.2 Raise a revision request through the Change Control system. Lay out what the change is and why it is being made.
5.8.3 Once approval comes through, the Document Controller starts a new draft version while the current version stays live. On the Master List, the current version shows as Active and the new version appears as Under Revision.
5.8.4 When the revised SOP is approved and effective, the Document Controller swaps the statuses on the Master List. The new version steps up to Active. The old version drops to Archived.
5.8.5 Track down any paper copies of the old version across user departments. Stamp them or destroy them so nobody accidentally picks one up.
5.9 Withdrawing an SOP:
5.9.1 Withdrawal applies when the activity covered by an SOP is no longer carried out at the site. A discontinued product, a piece of equipment being decommissioned, or two procedures being merged are typical triggers.
5.9.2 A withdrawal request goes through the Change Control system. The request lays out the reason and confirms that nothing ongoing still relies on the SOP.
5.9.3 On approval, the Document Controller flips the SOP status on the Master List from Active to Withdrawn. The effective date of withdrawal gets noted as well.
5.9.4 All copies of the withdrawn SOP have to be pulled from user departments. The master copy goes to the archive room with a Withdrawn stamp across the cover.
5.9.5 Every affected staff member is notified of the withdrawal through the Document Distribution Record. That way nobody ends up still following a procedure that has been pulled.
5.10 Periodic Review of the Master List:
5.10.1 Twice a year, the QA Head runs through the full Master List. The purpose of the review is to confirm every entry is accurate and no active SOP has been missed.
5.10.2 Points the review checks for:
5.10.2.1 Every Active SOP shows a valid effective date and a future review date.
5.10.2.2 No SOP has run past its Next Review Date by more than 30 days.
5.10.2.3 Every Withdrawn entry carries a recorded withdrawal date and a recorded reason.
5.10.2.4 The count on the list matches the count of signed masters stored in the QA file room.
5.10.3 Any gap that shows up during the review has to be closed within 15 working days. If a gap keeps coming back, the QA Head takes it on for a root cause investigation.
5.10.4 When the review is complete, the QA Head signs off. The completed review then goes into the Master List Review Log.
5.11 Access and Distribution:
5.11.1 Plant staff reach the Master List through the internal document management system. Read access is open to all. Write access belongs only to the Document Controller.
5.11.2 For offline reference during power outages or system downtime, a printed copy of the Master List is kept in the QA office.
5.11.3 External parties such as regulatory inspectors and corporate auditors can access the Master List on request. Every external access is logged by the Document Controller in the Access Register.
5.11.4 The Master List is never handed out to third parties without written approval from the QA Head. Any shared copy has to carry a confidentiality watermark.
5.12 Document Retention:
5.12.1 All versions of every SOP are retained as part of the site GMP records. Active, Archived, and Withdrawn SOPs all stay on file, regardless of how old they are.
5.12.2 For a Withdrawn SOP, the retention period runs five years from the date of withdrawal. Where the SOP covered batch manufacturing, retention instead runs to the shelf life of the last batch produced under it plus one year, whichever of the two comes out longer.
5.12.3 Archived versions of an Active SOP stay on file for as long as the current version is in use. Once the current version is itself withdrawn, the full version history falls under the withdrawal rule above.
5.12.4 A linked version history lives on the Master List itself. Click any SOP Number and the version history opens with dates, authors, and revision reasons.
5.12.5 Paper masters sit in fireproof cabinets inside the QA file room. Electronic masters are backed up daily to an offsite server.
5.13 Audit Readiness:
5.13.1 During regulatory inspections, the Master List is one of the primary documents auditors ask for. Whenever an audit calls for it, the Document Controller has to pull the current list within 10 minutes.
5.13.2 Common audit questions around the Master List include the following:
5.13.2.1 How many Active SOPs are on the list today?
5.13.2.2 When was each SOP last reviewed?
5.13.2.3 What changed between the current version and the prior version of a given SOP?
5.13.2.4 How does the site confirm that every user has the right version of the SOP?
5.13.3 Keep a standard Audit Pack ready to answer the questions above. The Audit Pack gets refreshed on the first working day of each month.
5.13.4 Any gap that turns up during an audit is treated as a deviation. File a deviation report under the site deviation SOP and close the gap inside 30 days.
5.14 RECORDS:
5.14.1 Master List of SOPs.
5.14.2 Document Request Form.
5.14.3 Document Template.
5.14.4 Document Distribution Record.
5.14.5 Master List Review Log.
5.14.6 Access Register.
5.14.7 Audit Pack.
6.0 СОКРАЩЕНИЯ:
6.1 SOP: Стандартная процедура выполнения работ.
6.2 QA: Гарантия качества.
6.3 CAPA: Corrective Action and Preventive Action.
6.4 GMP: Надлежащая производственная практика.
