Table of contents
At a glance
What does it mean to validate Empower for GMP use?
Empower validation demonstrates that the configured environment reliably supports the defined laboratory processes. Assess acquisition, methods, calculations, reprocessing, permissions, review and retention. Use intended use and risk to define the scope. Supplier documentation and qualification results can contribute evidence. Their relevance depends on the actual configuration, instruments, interfaces and laboratory workflows.
- Raw data, processing results, and reports must remain distinguishable and traceable.
- A manual labeling alone does not constitute proof of manual integration.
- The Result Audit Viewer, System Audit Trail, and Message Center address different questions.
- Project restoration and system audit trail archiving require separate validation evidence.
1. Define the GxP scope and specify the exact system version
Describe initially the intended use of the Empower laboratory system: for example, for quantification of content, purity testing, or stability analysis. Document which results support a quality-related decision, who uses them, and what data transfers follow. A purely method development activity may involve a different data and release process than the routine testing of a batch.
This article mainly looks at GMP-regulated drug laboratories. Annex 11 refers to computer-based systems in GMP activities; the applicability of other GxP requirements is to be classified separately. At the source reconciliation on 6 October 2026, the EU directory Annex 11 led with revision January 2011.
Document Empower release including service release, operating form, database, capture computer, device drivers and connected instruments. The Waters documents used here concern Empower or Empower 3; individual functions have explicitly named version limits. Therefore, check any settings taken against your installed help and release documentation. A general product name is not sufficient as a system description.
2. Separate raw data, methods, and results
For a robust requirements list, a specific data set is warranted: select a sample and trace its journey through Sample Set, Injection, detected channel, processing, and Result Report. Which sample information originates from manual entry and which from an interface? Which version of the Instrument Method was used for data capture, and which Processing Method for result evaluation?
Waters describes the linkage between method standards, data, and results, as well as individual histories for methods and sample information. These relationships should be visible in the validation documentation. A subsequent correction of a single weighing and a modified integration represent distinct interventions, even though both may influence the reported content.
For dynamic chromatography data, however, it does not replace the original electronic records. The FDA explicitly delimits both in its data integrity guidance. Determine which data including metadata are to be stored and how an examiner finds raw signal, parameters used and result context.
3. Verify authorizations based on actual actions performed
A user role list is only meaningful when it is clear what tasks users can perform in day-to-day operations. Create a test account for each relevant role: Analyst, Method Responsibility Holder, Inspector, and Administrator. Review permitted actions and explicitly prohibited activities. Where applicable, use an account with multiple assigned roles, if such a combination occurs in actual operations.
In Empower, system policies and user-type privileges operate in conjunction. The "Save Processing Methods" permission may override subordinate change rights under Waters. Therefore, it is insufficient to simply remove a single checkbox for integration parameters and infer a valid restriction from that action.
A suitable negative test is: The routine analyzer should use a shared method, but not save any new evaluation logic. Test the available paths in the specific interface. Capture not only the error message, but also whether another user type or allowed saving under other names is subject to the desired control target.
4. Properly assess reprocessing and manual integration
Reprocessing refers to the reprocessing of already captured data. Manual intervention in peak evaluation, on the other hand, involves direct modification of the peak analysis. Both actions require a clearly defined scientific justification and a transparent decision on which result shall be used. A lower numerical value is not an adequate justification.
A product-specific trap described by Waters in the policy prompts the user to save manual changes made during review: Results saved via this pathway are labeled "Manual" even when no manual integration has occurred. Therefore, reviewers should examine the specific changes and the origin pathway.
As a standalone evaluation, you may assess the same raw dataset once in its original form and once with a justified integration modification. Document the initial results, modified parameters, new results, and the decision rationale. Include a follow-up review attempt that was rejected. The FDA clarifies that rejected data must not be eliminated solely because a subsequent successful evaluation of the complete dataset yields valid results.
5. Select the appropriate sources for audit trail review
The Result Audit Viewer, as described by Waters, aggregates multiple result-related histories and enables comparison of previous results and method versions. However, its display remains a view of data. Please verify the time period and filters: for example, Manufacturer Tip 373 specifies a time-limited initial view. An empty result list therefore does not confirm an unchanged workflow.
The following assignment serves as a reference guide for the internal review procedure. It should specify which anomaly triggers additional investigation and who resolves outstanding items. A general note such as "Audit trail reviewed" often leaves this decision chain unresolved.
| Source | Assessment question | Additional Relationship |
|---|---|---|
| Result Audit Viewer | How do the original and selected results differ? | Review time period, method meeting records, and rationale. |
| Project Audit Trail and Object Histories | What relevant change occurred in the project? | Assign sample collection and relevant technical impact. |
| System Audit Trail | For example, was a relevant system or permissions setting changed? | Consult the responsible person and the approved change record. |
| Message Center | Is there an issue with data capture or processing? | Evaluate technical notification; not a replacement for the audit trail. |
6. Test example: re-evaluate a suspicious sample
The following example uses a pre-prepared test dataset with an overlapped peak. Prior to testing, the method responsible party defines which methodological adjustments are technically justified and which comparison parameters are to be considered. The specific acceptance criteria derive from your procedure; this document neither prescribes a universal integration limit nor establishes a general result tolerance.
Conduct the testing in an appropriate test environment. Document object references, users, and versioned methods so that a second reviewer can reconstruct the procedure without verbal explanation.
| Test action | Pre-established expectation | Evidence |
|---|---|---|
| Save original evaluation | The initial state remains accessible for comparison. | Raw data access, method and results |
| Perform allowable integration modifications | Changes and professional rationale are clearly justifiable. | Before/After Comparison and History |
| Unauthorized method changes attempted | The restricted action fails on the tested pathways. | Role, action and actual response |
| Reject processing | The rejection remains associated with the affected result. | Decision and subsequent handling procedure |
| Open the older period in the review | The previous processing is deliberately identified. | Filter setting and complete comparison |
7. Test the sign-off and locking procedure as a separate workflow
Describe what an electronic approval means in your process: performed, reviewed, or released. Define who is authorized to carry it out and which pre-evaluations must have been completed. An existing signature does not substitute for substantive assessment. Under the applicable requirements, the relationship to the approved data set must be maintained.
Empower provides policy-based sign-off controls and channel locks. Waters indicates that locked channels can prevent further result generation and that a separate unlock privilege exists. This leads to a specific test question: What happens after your release if someone wishes to reprocess or lift a lock?
Additionally, assess the legitimate correction scenario. A solely locked process without a predefined resumption procedure does not support the laboratory when a technical error is later identified. Document responsibility, rationale, and a subsequent re-evaluation for this scenario.
8. Project archive, system audit trail, and recovery are separated
A successful backup protocol does not confirm whether an older analytical process can be fully reviewed at a later date. Plan a restoration test using a modified dataset: multiple method versions, a justified intervention, a review decision, and, if applicable, a signature. Assess not only readability but also the technical and scientific coherence.
For Empower 3, Waters distinguishes the binary .maa format from a text export in the System Audit Trail: Only the binary variant can be played back into the offline system audit trails. This procedure can be distinguished from a project backup and the restoration of the operating environment.
Another boundary applies to restored projects in Empower 3 Enterprise. According to Waters, audit trail settings existing in the original version remain unchanged and reflect those of the secured project. Therefore, current system policies do not automatically correct prior deficiencies in data capture. Review older projects with due diligence and document any identified gaps in traceability evidence.
9. Device qualification, software testing and upgrade demarcation
The qualification of a chromatographic system, the validation of software installation, and the suitability of your laboratory workflow address distinct issues. A demonstrated pump flow does not establish authorization for subsequent modification of results. A successfully tested review workflow does not confirm detector suitability. Assign existing supplier documentation to specific requirements and address the remaining gaps.
Prior to an upgrade, the team requires a reviewed change list: which functions, drivers, calculations, reports, and data sets are impacted? Select representative regression tests from this list. For individual calculations or interfaces, known inputs and expected outputs must be available.
The effort arises primarily from variations and missing source documentation: inconsistent project templates, numerous methods, special rights, individual fields, data migration, and unclear review guidelines. A small, well-documented system can be planned differently than a historically evolved laboratory network. Therefore, deriving a general duration solely from the number of personnel would be poorly resilient.
Sources: [7]
10. Checklist for Joint Preparation
Management, system owner, QA, and IT should have a consistent understanding of scope and responsibilities prior to test planning. Ensure missing decisions are made visible as tasks, rather than being silently supplemented in the test report. The following list serves as a preparatory guide, not a universal mandatory package.
- Create a version and device overview including operating mode, drivers, and relevant interfaces.
- Provide a representative analysis together with original data, method records, and results report.
- Record which roles can process the data and which processing routes they can actually use. Assign responsibility for administrative tasks.
- Align valid integration, reprocessing, and review rules with the laboratory.
- Capture project templates, full audit trail settings, and used view filters.
- Name the release, correction, and escalation procedure including standing-in provisions.
- Define the archive scope, restoration environment, and responsibility for legacy projects.
- Evaluate existing documentation, open deviations, and relevant release notes collectively.
Sources: [7]
Project experience and collaboration
Bring together the evidence for a laboratory analysis
To scope Empower validation, we select a known analysis with your laboratory. We follow the sample, sequence, processing and decision on the result, then check whether the data and changes remain retrievable. A method change may need a limited investigation. Gaps across several steps require a broader review of roles and procedures. We agree the resulting tests with laboratory owners, QA and IT.
Frequently asked questions about Waters Empower
Has Empower been fully validated by Waters for our GMP laboratory?
No. Waters documentation can support development, functionalities, and certain testing activities. However, methods, rights, project templates, and interfaces are not automatically covered. Assign existing evidence to your specific requirements. Outstanding questions regarding your laboratory workflow determine the scope of additional testing and release.
Sources: [7]
Does "Manual" in an Empower result always indicate manual integration?
No. Waters describes a storage path within the review window wherein labeling may arise without manual integration. Therefore, consider result generation, actual parameter changes, and history collectively. A review rule that infers an unauthorized intervention solely from this field may misclassify the process.
Sources: [1]
Can a chromatographic result be reprocessed?
A reprocessing event must be justified by a clear, professional rationale and managed through a structured approach to all relevant results. Define who initiates it, which changes are permitted, and who reviews the selection of the reported result. Inappropriate results must not be eliminated simply through further processing.
Sources: [9]
Is the Result Audit Viewer sufficient for each review task?
It supports result-driven review. Whether additional sources are required depends on the question: a instrument malfunction or a change to system-wide permissions may require additional information. Additionally, test filters and time periods against known anomalies. A tool is only useful when the review procedure accounts for its scope and limitations.
Is the Empower Message Center considered an audit trail?
Waters explicitly excludes itself from this. The Message Center contains technical information, warnings, and errors. Such messages can support investigations, for example, following a failed data entry. The traceability of user modifications is verified through the designated audit trails and associated histories.
Sources: [4]
Can the audit trail be reviewed simply on an annual basis?
A one-year retention period is insufficient when relevant data modifications must be reviewed prior to a decision. The FDA Data Integrity Guidance from December 2018, for pharmaceutical cGMP, specifies that audit trails for data changes must be evaluated together with the associated records and in accordance with the prescribed frequency. Where no frequency is specified, process knowledge and risk assessment shall be applied. Separate the evaluation of data changes from additional system-specific controls and define responsibility for investigating anomalies.
Is a PDF report sufficient for long-term retention?
For dynamic empower chromatography data: no. A PDF preserves only a static snapshot; it does not retain the re-evaluatability of the electronic original. The FDA explains in its Data Integrity Guidance that static records do not substitute for dynamic original data. Define which electronic data, including metadata, must be retained, and verify future access, along with methods, processing, and audit trail functionality.
Sources: [9]
Who should prepare the initial validation, and what drives the effort?
The laboratory provides use cases and methods; QA clarifies analytical requirements and decision points, IT describes operational procedures and recovery; a named system owner coordinates. Effort arises particularly due to differing workflows, individual calculations, interfaces, and missing source documentation. Begin with a current-state assessment and prioritized validation gaps before defining timelines or test packages.
Sources: [7]
Must every Empower upgrade be revalidated?
The test scope should be derived from changes and their impact on the underlying functions. Consider new requirements, resolved defects, drivers, and historical data. Justify which previous evidence remains valid, and specifically evaluate affected critical processes. The designation "Service Release" alone does not determine this.
Sources: [7]
What should an restore test for Empower additionally demonstrate besides opening the project?
Review data mapping, relevant method statuses, result comparisons, and histories at a known process. Incorporate the adopted audit trail configuration. If system-wide events are part of the evidence, additionally maintain their archive and ensure appropriate access to it. Separate documentation for technical recovery and subject-matter usability is required.
Sources and review date
Source date: 6 October 2026. Waters documentation describes different Empower statuses; the installed version and its configuration remain decisive. Test procedures and checklists are standalone recommendations.
- Waters: System Policies and Privileges for Processing Data in Empower Software, 720006090
- Waters: Empower Software Audit Trails and Logs, 720005904
- Waters: Audit Trails – Result Audit Viewer, Tip 373 / WKB284003
- Waters: Does the Empower Message Center Function as an Audit Trail?, WKB119136
- Waters: Audit trail settings for restored projects, WKB112291
- Waters: Archive and Archive and Remove in Empower 3 System Audit Trail, WKB111434
- European Commission: EU GMP Annex 11, January 2011 revision
- European Commission: EudraLex Volume 4
- FDA: Data Integrity and Compliance With Drug CGMP – Questions and Answers, Final Guidance, December 2018
- eCFR: 21 CFR Part 11, Electronic Records; Electronic Signatures
Sources checked: .
Categorize targeted empowerment documentation purposefully
Daniel Herrmann Consulting helps you integrate existing documentation, system configurations, and laboratory procedures. This results in a justified task list tailored to your specific environment.
- 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.

