Product · QMS
Change Control, exactly as your SOP describes it — signed, sequenced and audit-ready.
OneXPro QMS turns your paper change control form into a guided digital record. Each section opens at its stage, waits on the right people, and is closed by the signature your form names — with nothing for an inspector to reconstruct.
The lifecycle
Twelve sections. One continuous, signed record.
Transcribed from a real pharmaceutical change control form: the same section numbers, titles and impact items, so a reviewer holding the paper form finds every box on screen.
- § 1
Initiation
A person with the Initiated By designation chooses the client, adds a note for QA and signs. The number is issued at that moment: client / CC / department / year / serial.
- § 1
QA issuance
Anyone with the Issued By designation reads the initiation and issues it. Only then does the initiating department see it and write the description, current state, proposed change, references and justification.
- § 2
Impact assessment
The QA-QMS Coordinator assesses the change against 32 impact items — documents, equipment, validation, regulatory, training and more — each Applicable or Not applicable, with the action required.
- § 3
Department review
Quality Assurance signs first and must; every other impacted department records what it noted and signs its own row. An optional Additional Information Sheet carries its own signature.
- § 4
Classification
The coordinator classifies the change as Major or Minor and allocates the target completion date.
- § 5
Head QA approval
Head QA records recommendations and approves or rejects. The decision on screen must match the decision in the signature.
- § 6
Principal party
For contract manufacturing, the change is sent to your client by a secure e-mailed link. They review sections 1–5 as a PDF and e-sign with a one-time code — no account needed.
- § 7–8
Extensions & discontinuation
Up to two justified extensions of the target date, each decided by Head QA — or a signed proposal to discontinue. Both can be signed Not applicable.
- § 9–12
Implementation & closure
Closing documents attached and reviewed, QA post-implementation review, the initiating department's review, and Head QA's final verification closes the record.
Capabilities
Everything QA needs to run the register.
Numbers you never type
Your flow, enforced
Department-scoped visibility
Waiting on you
Target dates that hold
Closing evidence
Paper-layout PDF
Dashboard & reports
AI drafting — optional
Compliance
Every signature means something — and says so.
Each electronic signature records who signed, their designation and department at that moment, what the signature means, and the date and time in your site's time zone.
- Password re-entered for every signature; wrong attempts count toward lockout
- Signed sections are frozen — later edits cannot touch them
- Before-and-after values for every change in the audit trail
- Audit trail exportable as CSV or JSON, and appended to every PDF
- Signatures made soon after an administrator password reset are flagged for review
Validation package included
Ten controlled Word documents, versioned with the software, to start your computerised system validation:
- Validation Plan
- User Requirements Specification (URS)
- Functional Requirements Specification (FRS)
- Design Specification (DS)
- Installation, Operational and Performance Qualification protocols (IQ / OQ / PQ)
- Deviation Report
- Traceability Matrix
- Validation Summary Report
Built for
Everyone on the form has a place.
Initiators & departments
Raise a change for your own department, then write and sign your parts.
QA & QMS coordinators
Issue, assess impact, classify, review closure — from one register.
Clients (principal parties)
Review and e-sign through a secure link, without an account.
Head QA & management
Approve, verify and see where every change stands.
Bring us your change control form.
We'll show it running in OneXPro — your sections, your flow, your numbering.
