Waters Empower Export Method — first-run working review
WORKING NOTES — review decisions belong in your controlled records.
Guide: https://seal.run/integrations/waters-empower

Use this with the Waters Empower Export Method first-run procedure. Retain the actual configuration and evidence, then record what happened in each receiving exercise. Expected behavior is printed as a prompt; your observed result starts blank.

1. Installed configuration and source route
Record the installed Empower version, Export Method and Method Set where used. Identify Fields, Report and Raw Data selections, grouping settings, destination and retained export specimen. Separate database-field results from raw-signal evidence.
Your evidence and observations:
[Not recorded]

2. Identity and expected population
List the result set, injection and result/evaluation identities. For each exported row, retain the component identity and grouping basis. Reconcile expected injections and component rows with the exported population.
Your evidence and observations:
[Not recorded]

3. Quantity and receiving evidence
Compare the chosen source field, reported unit, working precision and result basis with the destination. For the two-injection exercise, account for all four component rows; do not let a summary or filename overwrite an individual result relationship.
Your evidence and observations:
[Not recorded]

4. Exercise 1: Import all four component measurements
Input: Map the complete worksheet above through the proposed receiving design.
Expected: RES-91 retains Main 125000 and Impurity A 420; RES-92 retains Main 124500 and Impurity A 435. Both injections point to S-482-01 and retain their source unit.
Record the actual input/evidence references, observed result, whether it matches the expectation and any unresolved issue.
Your evidence and observations:
[Not recorded]

5. Exercise 2: Deliver exactly the same file again
Input: Resend the unchanged specimen under the same source/evaluation contract.
Expected: There are still two results and four measurements. The repeated delivery is traceable without replacing one component with another or creating extra scientific results.
Record the actual input/evidence references, observed result, whether it matches the expectation and any unresolved issue.
Your evidence and observations:
[Not recorded]

6. Exercise 3: Add a newly evaluated result
Input: Provide RES-93 as a later evaluation of INJ-06, with Main 125100 and Impurity A 418, preserving RES-91.
Expected: The new evaluation has its own two measurements and relationship to the earlier result. The receiving review identifies the changed values; arrival order does not silently erase RES-91.
Record the actual input/evidence references, observed result, whether it matches the expectation and any unresolved issue.
Your evidence and observations:
[Not recorded]

7. Exercise 4: Change table shape without changing the science
Input: Export equivalent selected data using a summary table with component names as columns rather than component rows.
Expected: A mapping approved for the original layout either rejects the unfamiliar shape for review or uses a separately verified layout mapping. It never reports a successful two-row import while dropping two component measurements.
Record the actual input/evidence references, observed result, whether it matches the expectation and any unresolved issue.
Your evidence and observations:
[Not recorded]

8. Implementation review and next work
Identify the configuration/mapping revision tested, reviewer, open issues and owner for each next action. Cite the retained source and destination evidence. A filled note is not itself an accepted test; record the review decision through your actual process.
Your evidence and observations:
[Not recorded]

EVIDENCE NEEDED TO FINISH
The source selection and grouping produce the expected injection/component population, original and later evaluations remain distinguishable, and repeated export does not create extra scientific results. The packet includes actual export settings and observed outcomes, not only a successful file transfer.