Independent and not affiliated with the FDA, MHRA, ISPE, PDA, or any agency. Get the appgoutham@madhadi.com
madhadi.comData Integrity & GxP Quality
Browse all topics → Articles Templates & Procedures Learning paths GlossaryScenariosToolsRegulatory ReferencesLearning PathsTopics About Start here
SOP Plug-and-play starting point Equipment Qualification

SOP: Equipment and Instrument Decommissioning and Retirement

A plug-and-play SOP for retiring qualified GxP equipment and instruments without stranding data: change control, GxP data assessment and verified migration, final as-found checks, cleaning and removal, systems-of-record updates, and a decommissioning report, with a filled specimen.

Document type: SOP

Read and copy the template below into your own quality system. It is a generic starting point for your own internal use, provided as is, with no warranty; see the Terms and License. Adopting it does not by itself create compliance.

This is a ready-to-use SOP for the end of the equipment lifecycle. Replace every <<FILL: ...>> placeholder with your own specifics, set your document numbers and dates, and route it through your normal document control. A worked filled specimen follows the template. The central principle is simple: you can dispose of the hardware, but the records it produced still have to be produced on request for their full retention period, so the data is the real subject of a decommissioning. Verify each cited regulation against the current source before you rely on it.

Document control header

FieldEntry
Document titleEquipment and Instrument Decommissioning and Retirement
Document number<<FILL: SOP-ID, e.g. SOP-VAL-031>>
Version<<FILL: version, e.g. 1.0>>
Effective date<<FILL: effective date>>
Supersedes<<FILL: prior version or "New">>
Document owner<<FILL: role, e.g. Head of Validation / Engineering>>
Applies to<<FILL: sites / departments in scope>>

1. Purpose

This procedure defines how <<FILL: COMPANY NAME>> retires GxP equipment and instruments from service in a controlled way that preserves the integrity, retrievability, and readability of the GxP data the asset generated or held, removes the asset cleanly from the quality systems that track it, and documents the retirement so it can be reconstructed later. The objective is that no historical record becomes unproducible or uninterpretable because the equipment that made it was removed.

2. Scope

This procedure applies to all equipment, instruments, and computerized systems used in GxP activities at the sites in the header that are being permanently removed from GxP service, whether because of end of life, replacement, obsolescence, a failed requalification not worth restoring, or discontinuation of the process they served. It covers physical removal, disposal, sale, transfer to another site, and repurposing to non-GxP use. It does not cover temporary removal from service for repair (handled under maintenance and change control) or the retirement of computerized systems where a separate system-decommissioning procedure governs the data (in that case, follow both and do not duplicate the data steps).

3. Responsibilities

RoleResponsibility
Equipment / system ownerInitiates the decommissioning, identifies the GxP data at risk, and confirms the process the asset served is no longer dependent on it.
Validation / EngineeringPlans and executes the decommissioning steps, arranges verified data migration or archival, and authors the decommissioning report.
IT / system administratorFor computerized assets, performs or supports data export, verified migration, and secure decommissioning of the software and its storage.
Quality AssuranceApproves the change control and the decommissioning report, confirms retention obligations are met, and confirms the asset is removed from all quality systems.
Records management / archivistConfirms the retention period for the migrated or archived data and takes custody of records where applicable.

4. Definitions

  • Decommissioning: the controlled process of permanently removing an asset from GxP service.
  • Retention period: the minimum time a GxP record must be kept and be retrievable, defined by the records retention schedule and the applicable regulation for the record type.
  • True copy: a copy of original data that preserves the full content and meaning of the original, including its metadata and audit trail, verified against the original. See 21 CFR Part 11 and the MHRA and PIC/S data-integrity guidance for the controlling expectation.
  • As-found verification: a measurement of the asset’s condition taken before any final adjustment, used to bracket the reliability of the last results it produced.

5. Procedure

5.1 Initiate through change control

  1. The equipment owner raises a change request per <<FILL: SOP-ID for change control>> to retire the asset, stating the reason, the target date, and the process or product impact.
  2. Confirm no active GxP process still depends on the asset, or that a qualified replacement is in place. Do not retire an asset a running process needs.
  3. QA reviews and approves the change before any physical or data action begins.

5.2 Assess the GxP data

  1. Identify every record the asset generated or holds that is still within its retention period: results and reports, raw data, audit trails, methods and configuration, calibration and maintenance history, and any batch or study data.
  2. Determine, for each data set, the retention period and the location it must live in after retirement.
  3. Do not delete, overwrite, or dispose of any data until section 5.3 is complete and verified.

5.3 Migrate or archive the data as verified true copies

  1. Export or migrate the identified data to a controlled location or archive, preserving content and meaning, including the audit trail and the metadata needed to interpret a result.
  2. Verify the migration: confirm completeness (record counts reconcile), confirm readability (a sample can be opened and interpreted in the target environment), and confirm the audit trail and metadata survived. Document the verification. See the data migration validation approach for the method.
  3. Where the original format cannot be preserved, document what was converted, how meaning was retained, and who approved the approach.

5.4 Final as-found verification where results are open

  1. Where the asset produced measurement data whose reliability could later be questioned, perform a final as-found calibration or performance check before any adjustment or teardown.
  2. Record the as-found result. If it is out of tolerance, raise a deviation per <<FILL: SOP-ID for deviations>> and assess the impact on results produced since the last passing check.

5.5 Clean, reconcile, and physically remove

  1. Decontaminate or clean the asset per the applicable cleaning procedure. This is mandatory for any asset that contacted product, biological material, or hazardous substances, and the cleaning is documented.
  2. Reconcile and dispose of associated consumables, reference materials, and spare parts.
  3. Remove, transfer, sell, or dispose of the asset. For transfer or sale, confirm no GxP data or licensed software leaves with it uncontrolled.

5.6 Update the systems of record

  1. Remove the asset from the calibration schedule, the preventive maintenance schedule, the qualification and periodic-review program, and the asset inventory.
  2. Update the validation master plan or equipment list so the retired asset no longer appears as active.
  3. Confirm no stale scheduled tasks remain that would flag the asset as overdue after it is gone.

5.7 Write and approve the decommissioning report

  1. Complete the decommissioning report (section 8) stating what was retired, where its data went and that migration was verified, the final as-found result, how it was cleaned and disposed, and the effective date.
  2. QA reviews and approves the report. The approved report is what closes the change.

5.8 Retain the qualification history

  1. Retain the qualification, calibration, maintenance, and decommissioning records for the full retention period even after the asset is gone.
  2. Confirm the migrated GxP data remains retrievable and readable for the balance of its retention period, including in any future migration of the archive itself.

6. Acceptance criteria

A decommissioning is acceptable when all of the following are true:

  • The retirement was approved through change control before any data or physical action.
  • Every GxP record still within its retention period was migrated or archived as a verified true copy, with the audit trail and metadata preserved, and the verification is documented.
  • A final as-found check was taken where results were open, and any out-of-tolerance result was assessed for impact.
  • Cleaning and disposal were performed and documented, with no GxP data or licensed software leaving on transferred or sold assets.
  • The asset was removed from the calibration, PM, qualification, periodic-review, and inventory systems.
  • A QA-approved decommissioning report exists, and the qualification history and migrated data are retained and retrievable for the full retention period.

7. References

21 CFR 211.180 and 211.194 (records and retention). 21 CFR Part 11 (electronic records; true copies). EU GMP Annex 11 (computerised systems) and Chapter 4 (documentation). MHRA GxP Data Integrity Guidance and Definitions; PIC/S PI 041 (true copy and data retention). ICH Q9 (Quality Risk Management) for scaling the effort to the data risk.

Confirm the current version and clause numbers of each reference and your own retention schedule before issue.

8. Record generated: equipment decommissioning report

FieldEntry
Asset name and ID<<FILL: NAME / ASSET ID>>
Change control reference<<FILL: number>>
Reason for retirement<<FILL: end of life / replacement / obsolescence / failed requalification / process discontinued>>
GxP data identified<<FILL: data sets and retention periods>>
Data destination and migration verified<<FILL: location; verification reference; Yes/No>>
Final as-found result<<FILL: value / in or out of tolerance / N/A>>
Deviation raised (if any)<<FILL: number or N/A>>
Cleaning and disposal<<FILL: method; disposal route; transfer details>>
Systems of record updatedCalibration / PM / qualification / periodic review / inventory (all Yes)
Effective retirement date<<FILL: date>>
Prepared by (name, signature, date)<<FILL>>
QA approval (name, signature, date)<<FILL>>

9. Revision history

VersionDateAuthorSummary of change
<<FILL: 1.0>><<FILL: date>><<FILL: author>>Initial issue.

10. Approvals

RoleNameSignatureDate
Author<<FILL>>
Reviewer (Validation/Engineering)<<FILL>>
Approver (Quality)<<FILL>>

Filled specimen

The following shows the report completed for an example benchtop pH meter with a small local data store, being replaced. The company, asset, and numbers are illustrative; replace them with your own.

FieldEntry
Asset name and IDBenchtop pH meter, PH-QC-04
Change control referenceCC-2026-0288
Reason for retirementEnd of life; replaced by PH-QC-09 (qualified, in service)
GxP data identifiedLocal measurement logs and audit trail, 2021 to 2026, 7-year retention; calibration history, same retention
Data destination and migration verifiedExported to the validated QC network archive; migration verified against source record count (1,204 = 1,204), sample records opened and readable, audit trail intact. Verification MIG-2026-017. Yes
Final as-found resultBuffer 7.00 read 7.01, buffer 4.00 read 4.00; within tolerance
Deviation raised (if any)N/A
Cleaning and disposalElectrode removed and discarded per lab waste procedure; unit wiped down; sent to asset disposal (no data left on device)
Systems of record updatedCalibration / PM / qualification / periodic review / inventory all updated, PH-QC-04 removed
Effective retirement date18 July 2026
Prepared byJ. Nguyen (Metrology), signed, 18 July 2026
QA approvalR. Gomez (QA), signed, 21 July 2026

In this example the team migrated and verified the data before touching the hardware, took a final as-found reading that confirmed the last results were sound, and removed the asset from every schedule so it would not later show as an overdue calibration. That order, data first and hardware last, is what an inspector expects to see.

Common inspection findings this SOP prevents

  • Equipment retired and its GxP data lost, made unreadable, or made inaccessible before the retention period expired, so a historical record cannot be produced.
  • A data migration during retirement that kept the result but lost the audit trail or the metadata, so the copy is not a true copy.
  • Retired equipment still appearing on calibration or PM schedules as overdue, with no record it was decommissioned.
  • No final as-found check on an instrument whose last results later came into question.
  • Equipment sold or transferred with GxP data or licensed software still on it.
  • Decommissioning done as an informal work order with no change control and no QA-approved record.

How to adapt this SOP

  1. Set your document number, owner, and effective date in the header.
  2. Point the cross-references in sections 5.1 and 5.4 to your real change control and deviation procedures, and section 5.3 to your data migration validation method.
  3. Align section 5.8 with your records retention schedule and archive strategy, including how the archive itself is kept readable over time.
  4. If you have a separate computerized-system decommissioning procedure, state in section 2 how the two interact so the data steps are done once, not twice.
  5. Confirm every regulation in section 7 and your retention periods against the current published sources before issue.
Use madhadi.com as an app Full screen, works offline, one tap from your home screen.