A change request in.Only the affected tests out.

Upload the change request. Merivane maps it to the affected requirements, scripts, and steps, proposes the regression scope, and re-runs it. The rest of the matrix stays as it is.

Where a change enters the chain
  1. Approved requirement
  2. Test scripts
  3. Autonomous execution
  4. You take over
  5. Defects logged
  6. Signed OQ / PQ report
Impact

See what the change touches before you test.

Upload a change request. Merivane traces it forward from the requirement to the scripts and steps it affects, and proposes a regression scope.

  • Forward traceFrom the requirement to every script and step it touches.
  • You approve the scopeThe regression scope is proposed, not fixed.
  • Rationale per scriptEach affected script carries a reason.
CR-118Add a second approver to batch record approval
3 requirements
5 scripts
31 steps affected
65 steps unaffected
Re-run

Re-run the delta. Keep the evidence for the rest.

Only the affected steps run again. The unaffected steps keep their evidence from the baseline run, on the same version and configuration.

  • Baseline retainedBaseline evidence stays and is referenced by the new run.
  • Fresh evidence for the deltaThe new run has its own hashed evidence.
  • Addendum or re-issueYou choose how the report reflects the change.
Run comparisonOQ-2214 vs OQ-2214-C1
RunDateRe-executedNew defects
OQ-22142026-03Baseline—
OQ-2214-C12026-0931 of 96 steps0

65 steps carried forward on the same version and configuration.

Closure

The change record closes with a signed addendum.

The change record links the change request to the runs it triggered and to the report. It closes under a 21 CFR Part 11 signature.

  • Change to reportThe record links the change request, the runs, and the report.
  • Signed under Part 11Closure is a signed event.
  • Version history retainedEarlier matrix and script revisions stay available.
Change recordCR-118
ChangeCR-118
StatusClosed
AddendumOQ-2214-C1
SignedPriya N.
Change types

Common changes that trigger a regression scope.

Configuration changeVendor patchNew workflowUser role changeInterface changeMaster data change

Questions about change management.

If your question is not here, ask us. We reply within one working day.

Can it link to our change control system?

Not confirmed yet.

What if the change alters the screen?

The agent stops and asks. You take over, or update the script and re-approve.

Do we re-approve every script?

Only the changed ones. The rest keep their approval.

Can we re-issue the whole report instead of an addendum?

Yes.

Now onboarding validation pilot partners

See a full run on one of your systems.

Bring one approved requirement. We show you the chain end to end, on a system you already use, in under an hour.

Book a demo
Reply timeOne working day
FormatLive run, 45 minutes