Transcript
The change label does not set the test
A minor, major, standard, or emergency label helps route change control. It does not tell you how much regression testing is needed. A one-line configuration update can change a critical approval rule, while a large visual redesign may not affect a G X P function.
Trace affected functions and dependencies
Map the changed component to approved intended use, configured workflows, interfaces, data, records, signatures, identity services, and open transactions. Identify the credible failure, potential impact, existing controls, supplier evidence, and remaining uncertainty. Include unchanged functions only when a shared dependency can affect them.
Document why each test is in or out
Choose no impact, focused confirmation, or broader regression from the analysis. Record accepted supplier evidence, local tests, deviations, monitoring, and reassessment criteria. The strongest change record explains why the selected evidence can detect the relevant failure, not merely why the change was called minor.