Process family

Change control: twelve templates for approving a change before it goes live

Change control templates for a quality system, IT production, an SOP, a controlled document, a furniture design, a laboratory method, a plant modification, a project baseline and a ship repair scope: one gate, different change authorities.

Change control is the gate between 'we should change this' and 'this is now how it is done': a request, an impact and risk assessment, an authority that can say no, implementation against a plan, and verification that it did what it was meant to. The twelve templates are that gate in a quality system, an IT department, a laboratory, a plant, a project and a design office, grouped, not sequenced, because a change enters one of them, not all.

The generic form is the change control process: request, impact and risk assessment, a change authority or CAB, implementation against a rollback plan, verification, review and closure, with an emergency route that shortcuts the queue but not the record. The IT change management workflow and the ITIL change management process are the production-systems version, where the evidence SOC 2 CC8.1 asks for is the ticket, the test result and the approval. Document and SOP change control are the version where implementation means a new revision, a distribution list and, for a safety-critical SOP step, signed retraining.

The failures are the same in all of them. A change implemented before it was approved, because the approver was also the implementer. An impact assessment that covered the thing being changed and not what depended on it, which is why management of change screens for replacement in kind first and ends in a pre-startup safety review, and why the laboratory and analytical method change controls ask what evaluation or qualification work a method change needs before it reaches the records. And a change whose verification is that nothing has broken yet, which is what the post-implementation review in the generic and IT templates exists to replace.

Four members change what a customer agreed to, so a customer decision sits in the path: the furniture design change approval disposes of completed work and gets cost and schedule impact approved before BOM and drawings change; the ship repair change order SOP stops extra work being done or billed without a signed decision; the electrical design change SOP gates installation on customer approval of the design package. The project change request re-baselines within tolerance or via the steering group. Change control is also step five of the nonconformance-to-CAPA loop: a corrective action that alters a procedure comes here first.

Templates in this family

  • Change control process flowchart — A change control process flowchart covering request, impact assessment, CAB approval, implementation, verification and closure, plus an emergency route.
  • IT change management workflow (SOC 2 CC8.1) — A SOC 2-ready IT change management workflow: change request, impact assessment, approval, testing, deployment, post-implementation review, with approval signatures captured per gate.
  • Change management process flowchart (ITIL) — An ITIL change management process flowchart covering RFC intake, standard, normal and emergency triage, CAB approval, scheduling, rollout and rollback.
  • SOP change control process flowchart — A SOP change control process flowchart with Requester, Process owner, Safety or QA reviewer, Approver and Trained operators lanes: safety-critical routing, QA-gated approval and mandatory hands-on retraining before go-live.
  • Document change control workflow flowchart — A document change control workflow flowchart covering minor/major classification, reviewer impact assessment, approval, version stamping, distribution list updates and formal supersession of the previous version.
  • Design change approval process flowchart (furniture in production) — A design change approval process flowchart covering engineering and production impact assessment, a completed-work disposition, and customer cost approval.
  • Laboratory change control process flowchart — An editable laboratory change control workflow for defining a proposed change, assessing method and data impact, planning evaluation, implementing approved updates and recording the outcome.
  • Analytical method change control process flowchart — An analytical method change control process chart for clarifying changes, assessing method and data impact, completing needed work, resolving approval concerns and implementing a controlled update.
  • Management of change process flowchart (MOC, PSSR, expiry) — A management of change (MOC) process flowchart for process safety: replacement-in-kind screening, classification, hazard review, authorisation, PSSR before start-up, and the temporary-change expiry loop.
  • Project change request process flowchart (scope, cost, schedule) — A project change request process flowchart covering the change register, impact assessment, the tolerance decision, steering group approval and re-baselining.
  • Change order approval SOP for a ship repair yard — A change order approval SOP for ship repair: a mid-repair finding is assessed against original scope, estimated, submitted to the customer for approval, executed, QA/QC inspected, and filed on closeout.
  • Electrical Engineering & Design Change SOP — An electrical engineering and design change SOP for Scanel: technical assessment, system design, drawings and schematics, an engineering review, and a customer-approval gate on the design before installation and commissioning begin.

Used in these industries

Related guides

  • How to create a change control process — How to design a change control process: define your change categories, keep the pre-approved list short, require a rollback plan, and draw the emergency route rather than pretending it does not exist.
  • How to create a flowchart from an SOP — How to convert a written SOP into a flowchart: split the prose into one action per step, turn every conditional sentence into a decision, assign owners, and reconcile what the text left out.
  • How to version control an SOP — SOP version control means numbering every procedure revision, routing safety-critical changes through hands-on retraining and a signed checklist instead of read-and-acknowledge, and retiring the copy it replaces.
  • Version control vs change control: what's the difference — Version control tracks which revision of a document is current and what changed; change control decides whether a proposed change is allowed to happen at all, and who has to approve it first.
  • How to create a flowchart from a document — How to turn a document whose steps were never numbered into a flowchart: which passages are not steps at all, where scope, definitions and responsibilities belong instead, and why the chart comes out too long.

QueryChart features for Change control

Related process families

More in Process families