ICH Q10
Change management
Changes are evaluated by scope, approved by the quality unit, and followed by an evaluation of whether the change achieved its aim.
A change request in Corpex-eQMS goes through authorization, a scope-by-scope impact assessment, an approved implementation plan with an action plan, an evaluation against criteria for success, and a closure review. Each decision is e-signed and every CAPA raised from the change is tracked to its end.
The standard change workflow. Rejection is possible at authorization and at assessment; every approval is e-signed.
A change request needs a title, the justification, the current situation, the proposed change and a named authorizer before it can be submitted. The initiator can propose the class and level, but the quality assessor decides them during assessment.
The impact tab lists one row per active scope. A row with no rating, or a rating that needs an explanation and has none, blocks the assessor from finishing. Which scopes you assess is your choice, so documents, validation status, regulatory filings and training can each have their own row.

The change owner writes the implementation plan, the documentation update summary and the resources needed, and builds the action plan from tasks and CAPAs. From plan approval on, the action plan is locked: nothing is added or rewritten, only carried out.

Most change control tools stop at implementation. Corpex asks whether the change did what it was for.
When every action is done, the change owner starts the evaluation of the implemented change and signs it. The criteria for success sit on the change from the planning stage.
Linked CAPAs carry their own planned effectiveness checks. The change cannot be closed while one is still pending, and the closure shows the result.
The closure request names a reviewer who did not work on the change. Approval of the closure is e-signed and ends the change. See CAPA for the checks.
Each of these is a check made before a change moves, with a message that says what is missing.
The assessor cannot finish while a scope has no rating, details are missing or a required department has not signed off.
The plan needs an implementation plan, a change owner, the documentation summary and a reviewer already on record.
Open action-plan tasks, open CAPAs and pending effectiveness checks each hold the change back.
The initiator and everyone who acted on an earlier step cannot sign the next one.
Submit, approve, reject, evaluate, close and reopen each ask for the password and record what the signature means.
Every GMP write enters an audit trail chained to the one before it.
Each card names the control in the software that answers it.
Change management
Changes are evaluated by scope, approved by the quality unit, and followed by an evaluation of whether the change achieved its aim.
Validated state
The impact scopes include validation status, so the effect on qualification and validation is rated and explained before the plan is approved.
Written procedures
Changes to procedures and processes are reviewed and approved by the quality unit, and the record shows who signed and when.
Records and signatures
Password re-entry at each signature, role-based rights and an audit trail on every GMP write.
This page describes software controls. Your quality unit decides how they meet each rule.
Short answers, based on what the software does today.
Every new change gets one blank impact row for each active scope in your master data, for example product quality, regulatory filing, validation status, documentation or training. The assessor rates each one (high, moderate, low or no impact by default) and writes details where the rating asks for them. The assessment cannot be approved while a scope has no rating. Departments affected can be named, and each can be asked to sign off its own row.
Your administrator can make an approved risk assessment a condition for finishing the impact assessment. The change record starts risk assessment requests from its Risk tab, and when the rule is active the assessor cannot move on until one has been approved.
They are held while the change is not yet approved. Final approval of the plan releases them into their own CAPA workflow, and the change cannot be closed until every action and CAPA linked to it is finished and every planned effectiveness check has a result.
After the plan is carried out, the change owner starts an evaluation, signed as their own attestation, against the criteria for success written in the plan. Closure cannot be requested until the actual end date, a conclusion and the evaluation are written. A different person then reviews the closure.
The initiator proposes a class, level and level categories. The quality assessor decides them, and the assessment cannot be finished without the class. Each change has exactly one class; the class list, levels and categories are yours to define.
Yes. Reopening needs an e-signature and a reason, and the change keeps a count of how often it was reopened. A change can be rejected only at authorization and at assessment; later steps return it for information instead.
Book a demo and we will walk one change through impact assessment, plan, CAPA release, evaluation and closure with you.
Request a Demo