LabVantage result-entry recovery — first-run working review
WORKING NOTES — review decisions belong in your controlled records.
Guide: https://seal.run/integrations/labvantage

Use this with the LabVantage result-entry recovery 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 version, enabled business operation and service wrapper, action/version reference and explicit released-data or missing-data options. Identify the supported lookup used to verify outcomes; record actual settings rather than relying on undocumented defaults.
Your evidence and observations:
[Not recorded]

2. Identity and expected population
For each target, retain SDC and record keys, parameter list/version/variant, dataset, parameter/type and replicate. Show how the source and destination identify the same existing item. List any auto-add/default-selection behavior that could change the target.
Your evidence and observations:
[Not recorded]

3. Quantity and receiving evidence
Compare intended entered text, configured unit and actual read-back value for every target. Classify matched, conflicting, absent and unresolved outcomes separately. Keep entered, transformed/display and reviewed values distinguishable when those differ.
Your evidence and observations:
[Not recorded]

4. Exercise 1: Recover a lost response without sending the value again
Input: Start with the worksheet above, then provide read-back evidence of 1190 mg/L for dataset 1, replicate 2 under the same test definition.
Expected: Both intended results become matched. There are still two scientific replicates and no third replicate created by recovery.
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: Find a conflicting value on the correct target
Input: Return 1180 mg/L for the intended second replicate instead of 1190.
Expected: The recovery item records expected 1190 and observed 1180 with the same complete target identity. It remains a conflict for review and does not silently replace the observed result.
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: Return the expected number on a different dataset
Input: Return 1190 mg/L for dataset 2 while the pending target is dataset 1, replicate 2.
Expected: That observation does not resolve the pending row. The later dataset remains separate source evidence; the original target still needs a valid lookup.
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: Replay against released or missing targets
Input: Test the effective wrapper policy against a released data item and, separately, a target that has not been assigned.
Expected: Under this evaluation’s explicit policy, released content is unchanged and absent targets do not trigger additional sample/dataset/replicate creation. Each failure retains its target identity and actionable reason.
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
Each intended data item has a supported lookup outcome. Recovery targets the exact unresolved item; it neither creates another replicate to hide a failure nor overwrites released data contrary to the chosen policy. All submitted rows have an explicit reconciliation state.