NominalQC Feature

Change Control

What changes, why, what it touches, who has to approve — in order — and the evidence the change worked.

Try this in the live demo — no signup →

Change request with the approval chain — approvers in order with their decisions — above the request, impact review and decisionChange Control register listing requests by type, part, requested date and status

What you can do

  • A request states the current state, the proposed change and the reason, with the part and the affected documents and drawings named
  • Impact review and a risk assessment — the risks and how they are controlled — before any decision
  • A sequential approval chain: approvers in order, each emailed when it is their turn, each decision stamped with who and when
  • Temporary changes are deviations with an end date, so a concession cannot quietly become permanent
  • Customer-approval-required flag with the customer’s reference recorded
  • Effective-from and implemented-on dates, then a named verifier and the evidence the change worked
  • Attach the redlined print, the customer email or the test report to the request

See it with your own parts.

Free for one user. No credit card required.

Create your free account