Why the auditor asks about change control
Every update of a safety system is a code change, and a code change is a potential source of error in a function on which the plant's permits and alarms depend. That is why a vendor audit covers the question of who checks a change and how, before it reaches the version released to the client.
A good answer is not: we have an experienced team. A good answer points to a mechanism that works regardless of who writes the code and that leaves a trail. The five practices below are such a mechanism, in a form that can be checked.
Practice 1: an automatic gate on every change
Every change in the repository goes through static analysis, style checks and unit tests, and the merge is blocked until the result is green. This is the foundation: a change that has not passed the automated checks does not reach the main branch.
The auditor can ask to see the blocking configuration and the history of several recent changes with their results. It is important that the block applies to everyone, including urgent changes, because an exception for an urgent change is often the cause of the most serious errors.
Change control parameters
Practices 2 and 3: independent review and measurement after the merge
A second, independent control agent reads every change on the open merge request and assesses whether the code matches the description of the change and the domain rules. Independence is key: the author does not review their own work. In InnerWeb documentation this mechanism is described as designed and built, but in the state of August 2026 not yet deployed to production, so the auditor should ask about the current state, not about the plan.
The control measures the result after the merge with the main branch, not only the working branch. A working branch may be green while, after merging with the main branch, it produces an error. The conflict is reported as a separate, blocking error. This is a practice that is rarely asked about, yet it prevents surprises after the merge.
Practice 4: three classes of findings and a pass threshold
The control findings have three classes. Blocking: one is enough to fail. Weighted warnings: the pass threshold is 89 points. Suggestions: they never block. This division protects against two extremes: letting a serious error through and halting a release because of a trifle.
The auditor should ask about the definitions of the classes and who sets them. Checking whether a blocking class has actually stopped any change gives more than a declaration. A result in which nothing was ever blocked is a warning sign.
Practice 5: fixed responses to findings and a round limit
The author of a change may respond to a finding in only one of three set ways: fixed, contested, or deliberately left. A deliberately left risk is reported to the product owner. As a result, no finding disappears without a trace: each has a response and a record.
The control has a limit of two rounds. After the second failed round the author switches to a decision mode and reports the open questions instead of iterating endlessly. This practice is for the team rather than for the client, but its existence shows that the process has a safeguard against both delaying and forcing a release.
- an automatic gate that blocks the merge
- independent review of the change against its description and the domain rules
- measurement after the merge with the main branch
- three classes of findings: blocking, weighted, suggestions
- a response to every finding in one of three permitted forms
- a limit of two control rounds
How to confirm the practices with the vendor
Prepare a short list of samples: the three most recent changes, including one urgent one, with the gate results, the text of the findings and the author's responses. Ask to see one change that was stopped, and one in which the author deliberately left a risk, with confirmation that it went to the product owner.
Record in the protocol not only the result but also the date and the version of the process. An audit of change control is valuable when it can be compared with the next one a year later. Then it is visible whether the process has held up or degraded.
Checklist
Video
Frequently asked questions
Does change control delay releases?
The automatic gate works within minutes. The two-round limit prevents endless fixes, and suggestion-class findings never block.
What does the 89-point threshold mean?
It is the pass threshold for weighted warnings. A blocking finding causes a fail regardless of the points.
Is the independent review already deployed to production?
The documentation describes it as designed and built, but in the state of August 2026 it was not yet deployed to production. It is worth confirming the current state with the vendor.
Go through the change control process with us
We will show the gate, the finding classes and samples of changes you can examine during a vendor audit. Book a talk.
Let's talk