Table of contents
At a glance
What does SimplerQMS validation involve?
Assess SimplerQMS against your intended quality processes, configured roles and migrated data. Check which version and tests the supplier package covers and where evidence is missing. Add targeted tests for document states, training, quality events and interfaces. Establish the actual operating architecture, responsibility for updates and how records remain accessible over time.
- Combine the manufacturer package and customer-specific suitability through a traceable assignment.
- Review document file, metadata, release, and history during migration together.
- Current operational architecture of its own environment; do not mix conflicting public data.
- Maintain separate control of software version, QMS configuration, and document versions.
Which SimplerQMS environment is being validated?
SimplerQMS is currently offered as a cloud-based eQMS with Microsoft Office integration. The company's technology page specifies Amazon Web Services as the hosting platform, along with single sign-on via Microsoft Entra ID or Google Workspace. It also includes an API for integration with other applications. Office integration does not imply that all QMS data resides within your Microsoft 365 tenant.
A key limitation of public disclosures: The SimplerQMS product catalog continues to reference M-Files and Azure. No reliable transition or version history can be derived from publicly available product information. The current public product description is primarily governed by the manufacturer's own website. For your specific environment, please obtain written confirmation regarding the platform, hosting, data locations, and involved service providers.
The article examines quality processes for the GMP manufacturing of human medicinal products. Requirements from medical device regulation or clinical applications are not automatically transferable. FDA Part 11 must be evaluated in light of the relevant FDA recordkeeping obligations and electronic usage. A general vendor compliance list does not substitute for this distinction.
What does the manufacturer's package actually contain?
The manufacturer mentions validation procedures, validation plan, report, and IQ, OQ, and PQ documents. He also describes revalidation for new versions and standard updates. These services can support your verification. On his compliance page, SimplerQMS anticipates that customers will not have to spend their own time or money on system validation. Arrange this manufacturer commitment to the actual scope of evidence provided; your operational requirements and clearance decisions remain to be assessed separately.
Request the specific package for the intended site status. Assign each risk-relevant requirement to a verifiable piece of evidence. What matters most is not the number of delivered documents, but the coverage of your workflow. For example, a package may justify a standard approval without having verified each of your site-specific role-based decisions.
| Component supplied | Clarifying question | Complementary addition in the case of a gap |
|---|---|---|
| Validation Plan and Report | Which version, environment, and features were evaluated? | Compare customer scope of release and document any deviations. |
| IQ-/OQ-/PQ-Documentation | Which tests were performed under what conditions? | Test uncovered configuration and critical end-to-end workflows. |
| Pre-configured workflows | Do the roles and responsibilities align with your SOPs? | Technical rules and authorization matrix confirmed. |
| Migration support | What contents, metadata, and historical references are transferred? | Mapping, identification of data errors, and definition of acceptance criteria. |
| Update documentation | What changes pertain to your released usage? | Assess impact, required post-test activities, and operational decisions. |
Document file, template and quality record differ
The current document overview describes a controlled lifecycle, versioning, and document attributes such as type, process, owner, and validity date. Working drafts are distinguished from valid versions. These functions should be particularly reviewed in areas where personnel work in Word and subsequently approve within the QMS or search for an active instruction.
Consider three distinct objects: A SOP describes the procedure. An empty template structures future data entry. A completed form documents a specific event. A new version of the template must not silently alter the content of historical records. Therefore, evaluate how the used template, stored content, and release remain traceable and verifiable to one another.
Use a boundary case: An employee is working on a new SOP version, while a colleague requires the currently valid version. Both must be able to identify the correct version for their respective tasks. Extend this scenario to include a locally stored printout or a downloaded file. Central version control alone does not prevent the use of an uncontrolled copy outside the approved workflow.
Plan the migration around the records the new system must preserve
SimplerQMS describes during the onboarding process an analysis of existing documents, the definition of requirements, and acceptance through review and release workflows. A new approval in the target system may establish the initial state therein. However, it must not be issued as the original historical signature.
Prepare a mapping list prior to takeover. It includes, for example, source ID, subject matter version, file format, validity date, status, owner, and associated records. For open CAPA or changes, include responsible parties, deadlines, and pending decisions. For completed activities, the traceable history takes precedence.
Make a deliberate decision regarding which historical data is transferred and which is retained in a controlled archive, particularly for historical signatures. If certain properties cannot be technically equivalently imported, describe an appropriate preservation and access pathway. Do not simply transfer a PDF and subsequently claim that all relationships and metadata have been preserved.
Plan a pilot run and a clearly defined handover deadline. Any changes made after the first export must either be explicitly incorporated or excluded and documented. Identical file counts do not prove content completeness; verify unique assignment, content, status, and required relationships.
Example: A small QMS inventory triggers a review
This example was not executed in SimplerQMS. A company assumes 24 valid SOPs, six blank forms, and three open CAPA actions. Historical original records shall remain in a defined legacy archive. One of the SOPs has the technical version 7; the new system must not assert a first-time creation from this version.
The test environment maintains a documented software and configuration state. QA defines acceptance criteria prior to testing. The test data intentionally includes a missing owner, a duplicate source ID, and a CAPA responsible party who has left the organization. The desired response is specified; it is not asserted as an automatically available product function.
| Test case | Source data or action | Expected professional justification |
|---|---|---|
| M1 – Inventory reconciliation | 24 SOPs, six templates, and three open processes to be taken over. | 33 unique assignments; additionally, content and object type are controlled. |
| M2 – duplicate | Two data records share the same source ID. | Conflict identified and resolved prior to release; no silent overwriting. |
| M3 – Historical Version | Import the SOP-QA-008 with technical version 7. | Source version remains traceable; separate identification of new system release is possible. |
| M4 – Operator changeover | Open CAPA has been assigned to outgoing responsible parties. | New responsibility will be clearly defined and controlled; history will remain understandable. |
| M5 – Training | Update a relevant SOP; compare affected and unaffected groups. | Matching training assignments; open requirements remain visible. |
| M6 – Readability | Retrieve a transaction and its legacy archive reference through the user workflow. | Files, decisions, and relevant linkages are accessible and understandable. |
Configure roles, training and change control
The manufacturer's introduction page outlines configuration decisions to be documented in user requirements, as well as organizational roles and permissions. Use this phase to make concrete decisions: who drafts, reviews, and approves a SOP? Who acts on behalf of an absent individual? Who is authorized to modify responsibilities or deadlines?
SimplerQMS defines Training Rules that assign documents, groups, or personnel. The Change Control page specifies which document types require a formal change control process. Therefore, evaluate a formal SOP amendment separately from a correction to a non-critical supporting document. It should be clearly evident why a particular approach was selected.
A training signature serves as evidence of a verified action. Whether a person reliably performs a task also depends on the content and methodology of the training. Define an appropriate performance control for critical tasks. Additionally, test a role transition: access may already be adjusted, while the required technical training is still pending.
Trace capa contents and electronic decisions
SimplerQMS describes CAPA documents based on predefined or provided templates, with links to quality incidents and reminders for effectiveness checks. This represents a different audit objective than merely archiving a completed form. Define the information that must be available prior to accepting a corrective action.
Test a case with insufficient evidence of implementation. Can QA return it, and can a reviewer trace the resubmission? Assess content, metadata and signature linkage together. A filename containing the word “approved” does not document a traceable electronic decision.
Determine which changes and historical information are reviewed in a specific review. A technical audit trail can support traceability; however, it does not assess the technical quality of the root cause analysis itself. The effectiveness of corresponding CAPA shall be evaluated in accordance with the pharmaceutical quality process. A reminder serves as an organizational trigger and is not itself a validity or effectiveness demonstration.
Evaluate software updates and configuration changes separately
Run three versions in parallel: the SimplerQMS software version, your approved configuration, and the technical document version. An unchanged SOP may appear differently after a software update. Conversely, a modified training rule may impact operations, even if the software version remains unchanged.
The manufacturer describes revalidation for new versions and standard updates. This does not yet establish a reliable customer-specific timeline for notification, internal review, or fallback procedures. Specifically define these points. Ensure appropriate release information, manufacturer documentation, and your impact assessment are maintained for any change.
Choose follow-up tests according to the function affected. For a change to the approval workflow, test roles and signatures. For document display, use a representative form with tables and attachments. For training, test assignment to a new employee. Record why any other tests are unnecessary. Assess the impact of each change before deciding which previous tests to repeat.
Include the Office, SSO, and data release in the operational phase
The current technology page describes Office integration, SSO, and API options. Review only the actually utilized connections. The provision of an API does not demonstrate a fully implemented ERP interface nor proper handling of failed transmissions.
For an office process, a controlled termination scenario is appropriate: a workflow is interrupted prior to confirmation of changes in the QMS. Subsequently, verify the preserved state and user information. Regarding the identity service, a critical case involves an employee's departure: access must terminate in accordance with the defined procedure, while historical decisions remain understandable.
Please explain and validate the backup and recovery procedures for your operational environment, and plan the exit from service. Early clarification is required regarding which contents, versions, signatures, relationships, and histories can be exported and in what format they will remain usable. A backup interval defined in a product specification does not guarantee a specific recovery time or a fully readable archive export.
What QA, IT, and Management can contribute before launch
At a smaller company, the primary drivers of effort are often found in legacy systems and unresolved decisions: inconsistent document numbers, location-specific release criteria, unclear training groups, and outstanding quality processes. Address these topics prior to finalizing migration and operational start dates.
QA is responsible for the technical requirements and evaluation of validation evidence. IT and system owners define the environment, access, and operational procedures; process owners provide representative case scenarios. Management ensures decision-making authority and resource availability. The supplier may provide support, but cannot reliably anticipate unknown local procedures.
- Operating architecture, performance scope, and actual software version are documented.
- GMP scope and required quality records are defined.
- Manufacturer package and remaining validation gaps have been assessed.
- Document types, versions, and release procedures are professionally determined.
- Data mapping, archive retention, and acceptance of transfer are defined.
- Training assignments, coverage, and authorizations were reviewed.
- The update process, disturbance escalation, and proof submission are operational.
- Restoration and long-term data access have specific acceptance criteria.
Project experience and collaboration
Map the supplier’s validation package to your quality process
With Quality, we trace a document change through the configured roles and follow-up tasks. We map available SimplerQMS evidence to that process. If it covers the necessary standard functions, focused additions may suffice. Custom rules, historical data and interfaces receive separate consideration. Future users then work through a current and a historical transaction. The process should fit your team and have clear ownership in operation.
Frequently asked questions about SimplerQMS
Does the standalone validation provided by the SimplerQMS package become obsolete?
The package can provide key tests and documents. However, it does not replace the evaluation of whether your actual usage is adequately covered. Verify version, configuration, roles, and data transfer against the supporting evidence. Add only justified missing documentation. This approach avoids unnecessary duplicate reviews and ensures release decisions are not based solely on general manufacturer assurances.
Is SimplerQMS running on AWS, Azure, or M-Files?
The technology section of SimplerQMS identifies Amazon Web Services as the hosting platform. The also available M-Files catalog describes M-Files and Azure. A reliable temporal or version-based relationship cannot be inferred therefrom. For your system description, use the environment version confirmed by the vendor, including hosting and sub-contractors. A Microsoft Office integration alone does not constitute evidence of Azure hosting.
Which version number should be included in the validation documentation?
Capture the actual software version and the associated configuration. Additionally document which versions of key templates or work instructions were used during testing. These are distinct pieces of information. Publicly available marketing websites do not necessarily indicate the current status of your client's software. Verify release and package reference, rather than treating an older, publicly accessible version number as current.
Can existing SOPs be simply imported and immediately put into use?
Document availability alone is insufficient. Clarify document type, status, subject matter version, owner, and validity. The manufacturer describes a migration procedure involving review and approval to define the source baseline. Determine which verification is required and how original evidence remains accessible. Subsequently, verify that the correct target audience can locate the document and assess whether training may be necessary.
How do we retain historical signatures during migration?
First, define which original records and associated information must be retained. A new approval in SimplerQMS represents a new action; it does not supersede an existing signature. Demonstrate the actual supported transition method. If historical records remain in the legacy archive, a clear reference, controlled access, and an appropriate solution for the retention period must be established.
Must all users be granted the same rights to ensure workflows function?
No. Derive rights from tasks and responsibilities. SimplerQMS describes role-based access; your review should include both permitted and unauthorized actions. Additionally test substitution, location change, and exit scenarios. A perceived process solution relying on comprehensive administrator rights may undermine the intended separation between processing, evaluation, and configuration changes.
How do we verify training following an SOP amendment?
Compare affected and unaffected groups using the version of document in use. Review an open training case, a new employee, and a role change. Determine when the new workflow may be applied and the control that ensures this. Electronic confirmation must align with the training objective; practical competence is not established solely by completion of a task.
Is a CAPA with completed tasks demonstrably effective?
Not automated. Completed tasks first display documented execution. Effectiveness assessment requires appropriate criteria and meaningful observations. SimplerQMS records reminders for relevant inspections; professional evaluation is carried out by the responsible team. Define at planning stage which outcomes constitute evidence of a successful intervention and how inadequate results will be further addressed.
How resource-intensive is the implementation for a small team?
Key factors include process diversity, condition of legacy documents, role models, and utilized integrations. Prepare a complete inventory list and identify outstanding decisions, and designate available points of contact. The manufacturer provides workshops and support for configuration and migration. However, a general weekly estimate does not adequately indicate whether your team can timely clean the data and make the necessary technical and scientific decisions.
Sources: [4]
Do we need to perform full retesting after a standard software update?
First, assess what has changed and which approved procedures are affected. Use version-specific supplier documentation and supplement with appropriate testing for your configuration. Ensure the decision rationale is clearly documented. A change to the Office integration may necessitate a document test, while an unchanged CAPA configuration does not require a full new run solely due to version numbering.
Sources and review date
Supplier and regulatory sources were opened on 6 October 2026. The internal current technology page serves as the primary public product description; discrepancies in the M-Files catalog do not indicate a general version or hosting history. Example inventory, test matrix, and checklist are internal work aids, not completed product tests.
- SimplerQMS: Technology Platform
- M-Files Catalog: SimplerQMS
- SimplerQMS: Certification & Regulatory Compliance
- SimplerQMS: Implementation
- SimplerQMS: Document Control Software
- SimplerQMS: Training Management
- SimplerQMS: Change Control Management
- SimplerQMS: CAPA Management
- European Commission: EU GMP Annex 11 — Computerised Systems
- FDA: Part 11, Electronic Records; Electronic Signatures — Scope and Application
- European Commission: EU GMP Chapter 4 — Documentation
- European Commission: EU GMP Chapter 2 — Personnel
- European Commission: EU GMP Chapter 1 — Pharmaceutical Quality System
- European Commission: EudraLex Volume 4 — current document overview
Sources checked: .
Provide traceable approval for the intended SimplerQMS usage.
Daniel Herrmann Consulting supports you in the evaluation of the manufacturer's package, the definition of your quality processes, and the planning of targeted checks for configuration and data transfer.
- Cloud and SaaS validation →
Maintain the validated state of cloud and SaaS systems as suppliers issue new versions. We define the boundary between your responsibilities and the supplier’s and agree how each release will be assessed.

