Back to all posts
Projects & Retrofits7 min read·October 25, 2026

How Should PLC Changes Be Approved After Commissioning?

TB
ThynkBlox Automation Team
Automation Engineering

A PLC change management procedure after commissioning should move each proposed edit through a documented request, impact review, operating approval, controlled implementation and acceptance. Agree the test evidence, recovery plan and record updates before work starts. Give emergency edits a shorter approval route with clear limits, and involve a qualified assessor whenever a change could affect safety.

What should trigger a change request?

Use a change request whenever someone proposes altering the agreed behaviour of a commissioned control system. Include PLC logic, operator screens, alarm settings, sequences, interfaces and access settings within its scope.

Define which routine operating adjustments are already authorised. An operator choosing a recipe within an approved range should not need the same process as someone changing that range or removing its limit.

Record the boundary explicitly: who may adjust what, within which limits, and where those adjustments are recorded. Send anything outside that boundary through the change procedure.

Start the request with the operating problem, rather than a proposed code edit. “The transfer stops before the receiving vessel is ready” gives the reviewer something to investigate. “Increase the timer” assumes the solution before the cause has been checked.

What belongs in the documented request?

Keep the request short enough to use during maintenance work, but complete enough for someone else to review.

ItemWhat to record
ReasonThe observed problem and why a change is needed
ScopeEquipment, modes, screens and interfaces involved
Proposed behaviourWhat should happen before and after the change
ImpactProduction, quality, maintenance, alarms, data and safety considerations
ResponsibilitiesRequester, reviewer, implementer and operating approver
VerificationChecks, expected results and acceptance criteria
RecoveryHow to restore the previous state and when to stop
ClosureEvidence, final approval and records to update

Attach relevant observations, such as the operating mode and sequence step where the problem occurred. Avoid presenting an untested explanation as a confirmed cause.

Where the proposal changes an agreed requirement, update that requirement alongside the request. The guide to what a functional design specification should contain provides a useful structure for describing intended behaviour.

Who should review and approve a PLC change?

Separate technical review, permission to work on the plant and final acceptance.

Ask the technical reviewer to check whether the proposed change addresses the problem, what else it touches and whether the verification plan is sufficient. Where practical, use a reviewer other than the person making the edit.

Give operating approval to the person responsible for releasing the equipment for work. Their decision should cover plant condition, production timing, isolation arrangements where needed, operator communication and permission to begin testing.

Assign final acceptance to a named owner. That person should review the results and any remaining restrictions before releasing the equipment for normal operation.

One person may hold more than one role at a small site. Record each decision separately so that approval to start work does not become assumed acceptance of the result.

For changes that could affect safety, involve a qualified assessor to determine the assessment and verification needed. Do not let a routine software approval substitute for that assessment.

How should the impact review work?

Review the proposed behaviour across the equipment's operating states. Do not stop at the screen or sequence where the request began.

Use these questions as a starting checklist:

  • What happens during start, normal running, stopping and restart?
  • What happens in manual mode, cleaning and maintenance?
  • What happens when a sensor, drive or communication link is unavailable?
  • Does the change alter a permissive, interlock, alarm or operator action?
  • Does it change data sent to another system?
  • Could it affect safety, product quality or equipment protection?
  • Which related functions need to be checked again?

Trace shared signals and reused logic to identify other equipment within scope. Record why apparently unrelated functions can be excluded from testing.

For alarm changes, review the required operator response as well as the setting. The guide to why operators ignore alarms offers a starting point for that discussion.

If the review cannot establish whether safety is affected, pause the routine approval route and obtain a qualified assessor's input.

What must be ready before implementation?

Establish an identifiable starting version. Save the current controller project and the related configurations needed for recovery, then check that they represent the equipment being changed.

Prepare the proposed revision, test instructions and recovery steps before the work window. Include dependencies such as operator screens, drive settings, recipes and connected applications where relevant.

Set clear stop conditions. For example, stop if the actual controller version differs from the reviewed version, an expected backup is missing, or a test produces behaviour outside the agreed result.

Treat an online edit as a planned intervention. Require an explicit decision on whether to edit while running, stop the equipment or wait for a shutdown. Base that decision on the reviewed scope and plant conditions.

For work tied to a shutdown, include access, testing and recovery time in the plan. See how to plan a PLC retrofit around a shutdown window for the wider scheduling process.

How should emergency edits be controlled?

Define the emergency route before an urgent fault occurs. Specify who may declare an emergency, who can authorise the intervention and which changes remain outside that authority.

Use a brief record containing the fault, proposed action, affected equipment, authoriser, implementer and recovery plan. Capture approval before the edit wherever practicable.

Urgency should not remove the safety assessment. If the proposed action could affect safety, involve a qualified assessor and use the site's arrangements for keeping the equipment in a safe state while the decision is made.

Mark temporary changes clearly. Give each one an owner, operating restrictions, a review point and a decision to remove it or assess it for permanent use.

After the immediate problem is controlled, complete the impact review, verification and records. Keep the request open until that work is accepted.

What verification is enough to accept the change?

Write expected results before testing. “Machine runs” is too broad; describe the behaviour that demonstrates the request has been met.

Check the changed function and the related functions identified during review. Include abnormal conditions where they fall within the approved test scope. Carry out tests under agreed plant conditions, with the necessary operating authorisation.

Record the revision tested, conditions, expected result, actual result and witness. Record failures and deviations plainly. Resolve them or obtain explicit acceptance of a defined restriction before normal release.

Illustrative example: a transfer sequence is revised to wait for a receiving vessel's ready signal. Acceptance checks could cover a ready signal present at the start, a signal arriving later, no signal arriving, and the signal disappearing during transfer. The approved design should define the expected response in each case before anyone tests it.

Do not assume that restoring the old program completes recovery. Include checks that the restored configuration and equipment state are suitable for the next operating step.

Which records should be updated before closure?

Close the change against a checklist:

  • Save the accepted controller project and affected configurations.
  • Record what changed and the verified revision.
  • Update the functional description, alarm information and operating instructions where affected.
  • Retain approvals, test results and unresolved restrictions.
  • Brief the operators and maintenance staff who need the new information.
  • Confirm the location and ownership of the recovery copies.
  • Obtain final acceptance from the named owner.

Keep temporary changes visible until removed or formally accepted. A successful production run should not automatically close outstanding documentation or assessment work.

What common mistakes should plants avoid?

Approving only the code. Include operating conditions, dependencies and recovery in the approval.

Writing tests after seeing the result. Agree expected behaviour first, then compare the observed result with it.

Leaving emergency changes open-ended. Assign an owner and review point when authorising the intervention.

Treating a backup as a recovery plan. Specify the restoration steps, responsibilities and checks before restarting.

Closing on verbal reassurance. Retain evidence that another responsible person can review.

What are the frequently asked questions?

Does every parameter adjustment need formal change approval?

Define approved operating adjustments and their limits in advance. Use the change procedure for adjustments outside those limits or changes to the limits themselves.

Can the integrator approve a change alone?

Give the integrator responsibility for the technical work agreed in the request. Keep permission to intervene and release the equipment with the plant's named operating authority.

Can an emergency edit become permanent?

Yes, through a deliberate acceptance decision. Complete the review, required assessment, verification and record updates before removing its temporary status.

When should a qualified assessor be involved?

Involve one whenever a proposed change could affect safety, including changes whose safety impact is uncertain. Use their assessment to define the necessary review and verification.


Need help defining changes to an existing control system? Explore our automation services or contact us to discuss the equipment, operating constraints and acceptance requirements.

Next step

Want to apply this to your plant?

Every project starts with a fixed-fee assessment, and you can stop after the report.