IT systems · Practical guide

Validating SoftMax Pro GxP: from the plate signal to the reviewed result

Which sample occupied each well, which protocol applied and why was a replicate excluded? SoftMax Pro GxP connects plate-reader measurements, calculations and documented processing. Define the edition, components, analysis and review in scope, then compare results with independently determined values.

Table of contents

At a glance

What does SoftMax Pro GxP validation involve?

Demonstrate that the configured SoftMax Pro GxP software supports its intended laboratory process. Assess protocol version, plate layout, raw signals, calculations, access and result review. Evaluate the relevance of supplier evidence and test uncovered requirements. Treat software validation, reader qualification and suitability of the analytical procedure as separate assessments. A GxP licence does not replace any of them.

  • Standard, GLP mode, and GxP have different functions and must not be equated.
  • The protocol, data record, and professionally evaluated results serve distinct functions.
  • Calculations are verified using independently defined inputs and set values.
  • An export or auto-save does not constitute evidence of complete recoverability.

State the edition and version unambiguously

Molecular Devices describes SoftMax Pro as data acquisition and analysis software for microplate readers. The product family includes standard, GLP mode, and GxP modes.

The documented reference point for this article is version 7.6: the IT Configuration Guide 5325894A dated July 2026 and the datasheet 2771D dated August 2026. The datasheet includes its own GxP functionality matrix. No statement is made regarding the patch level currently installed. Please jointly review license, components, and device connectivity.

The manufacturer's documentation designates the product as Research Use Only and not for diagnostic applications. This distinction is not waived by the inclusion of GxP. Clarify the specific intended use prior to project initiation. Similarly, the product name does not imply general approval or pre-validated suitability for any in-house assay.

Sources: [1] [2] [3]

Three pieces of evidence distinguish: Reader, Software, and analytical method.

In the context of human medicinal products under GMP, Annex 11 addresses computerised systems. Device qualification and analytical method validation have distinct objectives. Chapter 6 of the EU GMP Guideline covers testing methods, records, and the critical review of calculations.

The following internal guidance document defines the boundaries of these levels. A common plan can integrate the supporting evidence from each level; separate document systems are not required. However, a successful test of one level shall not be considered representative or acceptable for all other levels. When referencing FDA requirements, the actual applicable record-keeping rules shall be determined separately.

Own definition of validation objectives in the laboratory process
LevelQuestion to be answeredRelevant evidenceStill not answered
Reader and Connectivity Is the specific device suitable under the intended use conditions? Appropriate qualification and functionality documentation including used integration. Correct sample loading and professional calculation rules.
Software and Configuration Does the defined system version correctly process inputs and roles? Traceable requirements, configuration, and targeted as-built verifications. Appropriateness of the analytical method for the specific investigation question.
Analytical Method Does the assay provide suitable results for its intended purpose? Method validation or required suitability demonstration in the specific laboratory. Full user rights, system audit trail, and recovery.

Sources: [5] [6] [10] [11] [9]

From the protocol to the specific sample in the well

Start with the outcome question: What conclusion should the subsequent report enable? Describe the measurement mode, plate occupancy, sample identifiers, controls, calculation method, rounding procedure, and decision logic. A pre-prepared protocol may assist in setup; its availability does not confirm that it accurately reflects your question.

The 7.6 Guideline distinguishes between protocols with settings and data documents that additionally contain measurement data and calculated results. For your traceability evidence, it should be clearly evident which released starting batch was used in a measurement and which subsequent changes were made. The file name alone is not always sufficient as a basis for comparison.

Investigate a deliberately swapped sample assignment and a missing well labeling. Predefine which cases are to be excluded from analysis and which are to be monitored and supplemented. The software cannot independently identify the physically pipetted content based solely on an entered identifier. This transition requires appropriate documentation aligned with the laboratory process.

Sources: [1] [3] [11]

The associated components and settings are captured.

The manufacturer segregates SoftMax-Pro-GxP Client, Admin Portal, and GxP Admin. The IT guideline describes single- and multi-computer configurations and requires consistent component versions following installation or update. Therefore, the inventory review must extend beyond the version dialog of the measurement site.

Document the selected architecture, data storage, reader, and firmware, as well as the utilized connections. Assess manufacturer requirements for operating system and environment in relation to the selected architecture. Evidence from a standalone system cannot adequately address access and security considerations of a distributed installation.

The guide for version 7.6 specifies a decimal point for processing calculations. Check the actual regional settings and the data-entry route. The number format used to illustrate this article does not set the technical configuration. Include a test that catches format errors before the system accepts the results.

Sources: [3] [6]

Rights, document status, and business decision-making are binding

The manufacturer's guidance for section 7.6 explicitly limits the document workflow to the GxP license; GLP functionalities are not visible. Therefore, verify the actual workflow in place before defining requirements for status changes. Furthermore, a predefined role name does not guarantee appropriate authorization segregation.

The technical question is: Who is authorized to develop a template, make it available for use, perform measurements, and evaluate results? Review permitted actions and intentionally missing rights using different test accounts. Consider document access and editing permissions. A user may be allowed to view a dataset without being authorized to modify its analysis.

Define the significance of approval or signature within your own process. A technical status change and a substantive review are not interchangeable. The evidence must demonstrate which individual assessed which content at which stage. A green status alone neither confirms the scope of the review nor the underlying decision.

Sources: [3] [6] [7]

Sample calculation: Blank correction and replicates calculated independently

The following example is not a real assay and does not represent a product release test. The in-house target defines two associated replicates, a blank, and a factor of 5. The dimensionless test parameter K is calculated as: the average of the two signal values minus the blank, followed by multiplication by 5. Both replicates are required for final release. There are no concentration or product release limits.

Under Protocol V1, the signals 0.82 and 0.86, as well as Blank 0.10, are applicable. Independently calculated: mean value 0.84; corrected value 0.74; K = 3.70. V2 modifies only the Blank to 0.12. The testing utilizes predefined test data within an appropriate test environment. A manually entered numerical check does not constitute actual optical measurement.

Every failure scenario begins from a restored defined initial state. Expected responses are predefined prior to execution; the table does not assert any automatic product holds. During testing, supplement the actual observed outcome and supporting evidence. In particular, an excluded value must not be omitted solely because a later result appears more favorable.

Expected results for a dimensionless test value
Test caseInputs and RulesIndependently established expected resultReview and correlation to results
1 · Normal case V1 0.82 and 0.86; Blank 0.10; Factor 5 ((0.82 + 0.86) / 2 − 0.10) × 5 = 3.70 Both Wells, Probe, and V1 are assigned.
2 · New Site V2 Identical signals; Blank 0.12; Factor 5 ((0.82 + 0.86) / 2 − 0.12) × 5 = 3.60 New result remains distinguishable from the previous V1 result.
3 · Replica missing Only 0.86 available; V1 requires two replicates No final issuance upon own requirement Missing value and processing remain identifiable; 3.80 would not be a valid substitute.
4 · Blank missing Both signals present; Blank empty No implicit replacement by zero 4.20 would be the incorrect result under invalid null hypothesis assumption.
5 · Incorrect sample identification Values formally correct, but unknown identifier X No regular assignment of results to intended use Misidentification is clarified; no covert renaming.
6 · History after V2 Show the original V1 dataset again V1-Result 3.70 with original context reconstructible Change, new evaluation and old basis are not mixed.

Sources: [6] [11] [7] [8]

Trace changes and exclusions up to the result

Molecular Devices' public GxP self-certification distinguishes raw data from modifications to reduction and analysis. For the review, the key question remains: Which analysis stage was actually used, and why? The unaltered retention of a raw signal does not validate any derived analysis as professionally accurate.

Purposefully evaluate a change in the calculation rule, a justified exclusion, and a subsequent re-evaluation. The reviewer must establish the relationship between the original basis, the modification, the rationale for the change, and the final result obtained. A simple search for the final value would fail to capture this essential linkage.

Determine relevant events based on the system's own workflow and assess their capture and readability. System history and data document history may address different questions. The review scope should align with identified risks and be professionally justified. The presence of a history function does not imply that all desired events are automatically and completely covered.

Sources: [4] [6] [11]

Further reading:

Separate export, auto-save, and full recovery functionality

A supplemental report does not necessarily serve the same purpose as the complete electronic dataset. The 7.6 IT Guideline for the single-computer configuration indicates that exported files may not retain the full system audit trail. Therefore, prior to transfer, determine which additional contextual information must remain available at the source location or in another appropriate format.

Verify restoration using a dataset containing changes and a technical review status. If only the latest result display opens, the required context has not been established. Compare the restored baseline with a previously secured, independent master list.

The manufacturer describes different backup procedures per set-up and warns against inconsistencies while simultaneously using them during certain backup operations. Therefore, agree the process with the specific operating instructions. An AutoSave or Recovery function of the application does not replace a suitable backup concept. Intervals and storage are derived from the own process, not from a flat-rate product promise.

Sources: [3] [4] [6] [7]

Further reading:

Evaluate supplier packages and changes in alignment with own scope and requirements

A validation package can provide appropriate evidence. However, each required justification must be aligned to its specific status and purpose: which edition, function, configuration, and prerequisites were assessed? A general package description alone does not fully address these questions. Gaps in coverage should be specifically addressed, rather than relying on vendor names as a substitute for a proper evaluation.

For changes, consider both software and laboratory logic. A software update may impact data retention or user permissions; a protocol modification may alter results, even if the software version remains unchanged. Justify which existing records remain valid and which additional testing is required. A universal obligation to fully reperform all steps does not follow.

Document any open findings and decisions prior to intended use. A mathematically correct test result does not resolve any unresolved issue regarding sample assignment loss. Similarly, a technical version update shall not substitute the professional evaluation of affected protocols. The handover includes the verified status, responsibilities, and procedures for handling subsequent anomalies.

Sources: [2] [6] [8]

What QA, Laboratory, and IT Should Prepare Before Launch

First, specify the intended assay and the intended use of its results. The laboratory manager provides technical guidelines and representative data. QA defines the detection and decision requirements. IT outlines the components and operational procedures. The supplier provides version-compatible documentation. A common requirements summary is generally more helpful than multiple disconnected document lists.

The effort depends among other factors on various analysis logic, legacy protocols, interfaces, roles, and existing evidence. The availability of professionally justified target values also plays a significant role. Therefore, the mere number of installed workstations is not a reliable basis for estimation. Use the following preparation checklist:

  • Usage, scope of application, and manufacturer limitations documented.
  • Edition, license, and associated component versions recorded.
  • Reader, firmware, integration and environment described.
  • Device qualification, software validation, and method suitability assigned.
  • Sample identification, well occupancy, and controls defined.
  • Calculations, rounding, and exclusion rules substantiated technically.
  • Independent normal and failure cases prepared.
  • Roles, review, and determine, if applicable, the requirement for signature.
  • Export context and recovery of appropriate data sets are provided.
  • Supplier invoices, changes, and operational responsibility assigned.

Sources: [6] [8] [11]

Project experience and collaboration

Test a plate analysis from template to report

For SoftMax Pro GxP, we examine a specific plate analysis with the laboratory, from raw signal and template through calculation to the result version used. We identify which data and relationships must remain available and what the exported report actually contains. An existing analysis may permit focused investigation. For a new measurement workflow, we first agree requirements, responsibilities and suitable cases with the people involved.

Frequently asked questions about SoftMax Pro GxP

Has SoftMax Pro GxP been validated by the manufacturer for our assay?

Manufacturer documentation and test packages can demonstrate product functionality. However, for your assay, the intended use, configuration, sample assignment, and calculation methodology remain to be evaluated. Review the actual scope of coverage provided by the package and supplement any missing requirements. The GxP license is neither a general assay validation nor a guarantee that any customer-specific template is correct or appropriate for the intended application.

Sources: [2] [6] [11]

Can we treat Standard, GLP mode, and GxP equally?

No. The product options differ in functionality. The 7.6 Guideline specifically identifies Document Workflow as a GxP function that is not visible under GLP. Determine your actual license and derive available controls accordingly. Required controls are assessed based on the process; one alternative edition name neither supersedes this assessment nor constitutes a missing justification.

Sources: [1] [3]

Does a qualified reader replace software validation?

Device qualification addresses questions of suitability and performance of the reader. It does not automatically validate correct sample identification, well-to-well mapping, calculation rules, or authorizations within your configuration. Link the evidence together without conflating their scope. A manually entered numeric case can verify the calculation, but cannot provide proof of a real optical measurement process.

Sources: [10] [6] [11]

Which version of the protocol should the evidence identify?

Obtain the relevant settings and rules for the specific evaluation, including identity and version. This may include plate layout, controls, formulas, and rounding. Link this version to the data document and subsequent changes. A current screenshot of a similarly named template is insufficient if it remains unclear whether the template has been modified since the original measurement.

Sources: [3] [7]

Can we exclude an atypical replicate from the analysis?

An exclusion must be based on a technically sound justification and a rule appropriate to the procedure. It must not be permitted solely to achieve a desired outcome. Verify that the original value, exclusion, justification, and subsequent evaluation remain clearly identifiable. The implications for the result's usability determine your procedure. In the example presented in this article, both replicates are explicitly required.

Sources: [11] [4]

Which component versions must we document during the upgrade?

Consider the integrated state of client, administration, and other deployed components. The 7.6 IT Guideline requires synchronized versions across the specified components following installation or update. Additionally, document the relevant prerequisites for your setup. A single version dialog at the reader workbench does not address all questions associated with a distributed installation.

Sources: [3] [6]

Is an exported results report sufficient for retention?

An exported results view may exclude raw data, context, or relevant history. For the described individual workstation setup, the manufacturer highlights limitations of exported files. Therefore, define which data package must be retained for subsequent audit purposes and verify readability and assignment. A results report may be associated; a blanket PDF requirement does not follow.

Sources: [3] [7] [6]

Is AutoSave equivalent to adequate data backup?

No. Automatic saving and temporary recovery do not necessarily meet the objectives of operational backup. Critical factors are secured data, data consistency, and demonstrable recovery in the intended environment. Also assess the relationship with administration and audit trails. Do not derive a universal backup interval from the AutoSave function.

Sources: [4] [3] [6]

Does the GxP edition retain the "Research Use Only" designation?

No. The supplier labels the software for research purposes only and not for diagnostic applications. The designation GxP does not lift this usage boundary. Clarify with the supplier prior to procurement the intended use and the available evidence of suitability for such use. The product name alone does not imply approval for diagnostic applications nor a general assertion of suitability for any GMP laboratory process.

Sources: [2] [3]

What information does a small and medium-sized enterprise need for project planning?

Useful are edition and system setup, reader lists, existing protocols, representative data documents, and available manufacturer documentation. Supplement with professional evaluation rules, roles, and known manual transfers. This enables visibility into different testing pathways. Without these foundational elements, the effort cannot be meaningfully derived from workforce numbers. Additionally, agree on who can independently define and verify expected results.

Sources and review date

Date: 6 October 2026. Supplier reference: SoftMax Pro 7.6, IT Handbook 5325894A dated July 2026 and Data Sheet 2771D dated August 2026. Standard, GLP mode, and GxP modes must be considered separately; no latest patch version is claimed. Manufacturer restriction: Research Use Only; not intended for diagnostic applications. Regulatory framework: Human Medicinal Product GMP; FDA applicability limited to scope that is specifically relevant. Examples represent intended use cases, not product testing or validated assays.

  1. SoftMax Pro Data Acquisition and Analysis Software
  2. SoftMax Pro Data Acquisition and Analysis Software — For SpectraMax microplate readers
  3. SoftMax Pro Data Acquisition and Analysis Software — IT Configuration Guide, Software Version 7.6
  4. SoftMax Pro GxP Software — GxP Assessment Questionnaire
  5. European Commission: EudraLex Volume 4
  6. EU GMP Annex 11: Computerised Systems
  7. EU GMP Chapter 4: Documentation
  8. EMA: ICH Q9(R1), Step 5, Corr.2
  9. FDA: Part 11 — Scope and Application
  10. EU GMP Annex 15: Qualification and Validation
  11. European Commission: EU GMP Chapter 6 – Quality Control

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Close the gap between measurement and result

We support you in aligning device suitability, software scope, and technical evaluation, and in defining the open assessments for your specific configuration.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →