What is change control?
Change control is a formal path for proposing, assessing, approving, implementing and verifying a change before it is closed. See a worked QueryChart process and practical steps for applying it.
Change control is a formal path for proposing, assessing, approving, implementing and verifying a change before it is closed.
The short version
- Describe the proposal: Log reason, current baseline, requested outcome and affected objects.
- Assess and authorize: Review safety, quality, operational, legal and training effects at a depth proportional to risk.
- Implement and verify: Release the approved revision, update dependent records, check the result and close with evidence.
What is change control in practice
Its central question is whether a proposed change should happen and under which conditions. Version control records the changed state afterward. Without impact review, an apparently small edit can break a related form, system or training instruction.
Define what changes enter the process, classify risk, record affected items and rollback needs, obtain approval before implementation, and verify the outcome. Close only when related controlled documents and users reflect the new state.
See the document change control workflow workflow
Step through the decisions behind what is change control.
Describe the proposal
A change request is logged against the current document so its baseline remains identifiable.
Assess and authorize
Classification determines the depth of impact review before an explicit approval decision.
Implement and verify
The new version is published and distributed, the former one withdrawn, and closure evidence retained.
How it works
Describe the proposal
Log reason, current baseline, requested outcome and affected objects.
Assess and authorize
Review safety, quality, operational, legal and training effects at a depth proportional to risk.
Implement and verify
Release the approved revision, update dependent records, check the result and close with evidence.
Mistakes to avoid
Missing the decision record
Keep the actor, decision and effective state alongside the output. Its central question is whether a proposed change should happen and under which conditions. Version control records the changed state afterward. Without impact review, an apparently small edit can break a related form, system or training instruction.
Related QueryChart feature
Open the worked process
Use the linked document change control workflow template to adapt the workflow to your team.
Frequently asked questions
Is every edit a controlled change?
Set a documented threshold; minor draft edits can be treated differently from changes to approved work.
Who approves a change?
The accountable owner and any specialist reviewers required by its assessed impact.
When does version control begin?
Revision history can record drafts, but the new issued version follows approval and release.