Template: SOP Software Validation

Template Download

This is a free template, provided by OpenRegulatory.

If you are a user of Formwork, our eQMS software, choose “QMS” on the top menu and “OpenRegulatory Templates” on the left menu, and then open the relevant folder to find this template ready to load into Formwork.

If, for some mysterious reason, you’re using a different QMS Software, you can also simply download this template – specifically, as Word (.docx), PDF, Google Docs or Markdown file. Scroll down for a preview!

The template license applies (don’t remove the copyright at the bottom).

Tired of copy-pasting? If you want to save time and edit these templates directly, you can use Formwork, our eQMS software. And if you’re looking for step-by-step instructions for filling them out, check out our Wizard 🙂

Don't Miss Updates to This Template
Subscribe to our newsletter and we'll keep you posted on which templates we've changed.

Questions? Still Lost in Regulation?

Good news! Our goal is to provide lots of stuff for free, but we also offer consulting if you need a more hands-on approach. We get stuff done really fast. Have a look!

Template preview


This SOP ensures that the organization only works with validated computer/software systems to avoid erroneous systems affecting the safety and performance of its medical devices. The process outlines requirements for validation before use.

Process Owner<enter role of process owner>
Key Performance Indicators<enter KPIs to be tracked for the Management Review>
Regulatory ReferencesISO 13485:2016 Sec. 4.1.6 and 6.3 and 7.6
IEC 62304:2016 Sec. 9.8

Process Steps

1.1 Collecting Information and Preliminary Assessment

  • Employee notifies QMO of the new system and provides the minimum information required for preliminary assessment, such as intended use description and preliminary risk estimation.
  • QMO documents the intended use and determines whether the system is relevant for the QMS or the organization’s medical devices as part of the Software Validation Form.
  • If quality-relevant: continue to fill out the Software Validation Form (assessing criticality and risks).
  • If not quality-relevant: document the system in the Software List and release the software system for use.
ResponsibleEmployee intending to work with the new system
InputInformation about the system
Software Validation Form
List of Software
OutputPreliminary Software Assessment

1.2 Plan Validation

  • QMO continues to fill out the Software Validation Form by planning the validation and documenting the requirements for expected validation results.
InputSoftware Validation Form
OutputUpdated Software Validation Form

1.3 Perform Validation

  • Perform the validation based on the validation plan and fill out the validation report as part of the software validation form.
  • Where appropriate, save additional proof of validation (e.g. screenshots) and add them to the validation report.
ResponsibleEmployee working with the system
InputSoftware Validation Form
OutputUpdated Software Validation Form

1.4 Release

If validation was not successful:

  • Document the validation results in the List of Software and classify the system as “blocked” / “not released for use”.

If validation was successful:

  • Document the validation results and sign the validation report as part of the Software Validation Form.
  • Release the software by adding it to the List of Software.
  • Inform relevant staff about the approval of the system.
InputSoftware Validation Form
List of Software
OutputCompleted Software Validation Form
Updated List of Software
Notification Sent

1.5 Monitoring of Softwares

  • User feedback and error reports by developers are monitored for relevant occurrences that may affect the organization or its medical devices.
  • New version updates are implemented and the List of Software is updated accordingly. If necessary, a revalidation is carried out.
ResponsibleQMO in collaboration with employee working with the system
InputError reports by users / developers
OutputUpdated Software Validation Form
If required: new record of Softwares Validation Form created

1.6 Decommissioning of Software

  • In case it is decided to decommission a software, evaluate possible effects and document the actions in the List of Software.
InputSoftware Validation Form
List of Software
OutputUpdated List of Software

Template Copyright openregulatory.com. See template license.

Please don’t remove this notice even if you’ve modified contents of this template.

Template preview


Leave the first comment