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

How Should You Manage a Controls Commissioning Punch List?

TB
ThynkBlox Automation Team
Automation Engineering

Manage a controls commissioning punch list as a record of decisions and proof: give every open item an owner, a consequence and a verifiable closure condition. Separate defects that block start-up from work that may be deferred under agreed conditions. Close an item only after its required retest passes and the authorised reviewer accepts the evidence; carrying it into handover must leave it visibly open.

What should each punch-list item contain?

Write each item so someone who missed the commissioning test can understand the problem and repeat the check. “Sequence issue” is too vague. Describe the equipment, operating mode, trigger, expected response and observed response.

Use the agreed functional design specification as the reference for expected behaviour. If that document is unclear, record a decision request rather than quietly treating an assumption as a requirement.

FieldWhat to record
Item referenceA unique reference that stays with the item through retesting and handover
Observed defectWhat happened, where, and under which test conditions
Expected behaviourThe agreed requirement and its reference
ConsequenceThe effect on people, equipment, product, operation or records
ClassificationStart-up blocker, restricted-operation item or deferred work
Action ownerOne person accountable for arranging the correction
Closure conditionThe observable result required to pass
Retest scopeThe failed test and related behaviour to check again
Acceptance authorityThe person authorised to accept the result or approve deferral
Evidence and statusTest results, remaining conditions and the current decision

Add a target completion point, such as before the next start-up attempt or before an agreed production campaign. Avoid “as soon as possible”.

Which defects should block start-up?

Decide the release criteria before pressure builds to start production. Ask what could happen if the defect remains, which operating conditions expose it, and whether the proposed test covers those conditions.

Treat an unresolved safety-related function, an unexplained equipment movement or an unverified protective response as a hold point for the affected operation. Have safety-related design decisions and their verification reviewed with a qualified assessor.

Do not classify by how easy a defect looks to fix. A short logic change may affect a critical sequence; a lengthy drawing correction may have a different consequence.

For each proposed start-up blocker, record:

  • The operation that must remain unavailable.
  • The consequence supporting that restriction.
  • The correction and evidence needed to remove it.
  • Who can authorise release of the affected operation.

Where only part of a plant is ready, define the permitted boundary explicitly. “Commissioning may continue” should identify which equipment, modes and tests are allowed.

Signal faults found before start-up belong on the punch list. Our guide to what an instrument loop check should include explains how to trace each signal and record discrepancies.

When can you defer an open item?

Allow deferral only through a recorded decision about the remaining consequence and the conditions of operation. A promised fix is not a control measure.

A deferral should name the affected equipment, permitted use, temporary controls, responsible owner and completion point. State what ends the permission: a change of product, a different operating mode, loss of a temporary control or arrival at the agreed review point.

Keep the item's status as “deferred — open”. Do not move it into the closed count because someone has acknowledged it.

For safety-related matters, involve the qualified assessor in defining the decision and the authority required. A project sign-off should not substitute for the relevant technical assessment.

Plan access for the eventual correction and retest. The guide to planning a PLC retrofit around a shutdown window helps connect outstanding work with the next available plant access.

How do you make closure verifiable?

Write the closure condition before changing the system. Specify the initial state, operator action or simulated condition, expected response and evidence to retain.

“Alarm fixed” leaves too much open. A better condition might require the alarm to appear under the agreed fault condition, display the approved instruction, follow the agreed acknowledgement behaviour and clear only under the specified recovery condition.

For alarm defects, check the intended operator response as well as the display. The guide to why operators ignore alarms provides related questions about alarm usefulness.

Use distinct statuses:

  • Open: correction or investigation remains.
  • Ready for retest: the correction is available for verification.
  • Retest failed: the required result was not achieved.
  • Deferred — open: operation is permitted only under recorded conditions.
  • Closed: the evidence passed review and the authorised person accepted it.

Record who changed the status and the reason. Preserve the original observation alongside the correction.

What should a retest cover?

Repeat the failed test, then check the related behaviour affected by the correction. Ask which modes, sequences, interfaces and recovery paths share the changed logic or configuration.

Agree that scope before testing. For a sequence correction, consider the normal path, interruption, reset and restart. For an interface correction, consider unavailable data and recovery after communication returns.

Identify the controller program, operator-screen configuration and other relevant versions used for the retest. Evidence from an earlier configuration should not close a defect against a later one without a recorded technical review.

If the retest fails, keep the failure visible. Record the new observation and reconsider the diagnosis. If the failure reveals a separate defect, create a linked item rather than stretching the original description until it becomes unrecognisable.

What does a well-managed item look like?

Illustrative example: During a commissioning test, an operator stops a transfer sequence. On the next start request, the sequence resumes from an unexpected step.

Record the item as follows:

  • Consequence: the restart path may command equipment in an unintended order.
  • Classification: block release of the affected automatic sequence pending assessment and verification.
  • Owner: the named controls engineer responsible for coordinating the correction.
  • Closure condition: after interruption at each agreed test point, restart follows the approved sequence and shows the correct state to the operator.
  • Retest scope: interruption, reset and restart, including related permissives and indications.
  • Acceptance authority: the designated plant technical representative, with qualified assessment where safety-related behaviour is involved.
  • Evidence: completed test steps, observed results and the configuration tested.

The engineer marking the correction “ready” starts verification. It does not close the item.

Who should accept closure and handover?

Name the acceptance authority for each item or class of item before testing begins. Distinguish the person doing the correction, the person witnessing the test and the person accepting the result.

Use the relevant authority for the consequence involved. Production acceptance alone should not settle a maintenance access concern or a safety-related design question.

At handover, review the open list explicitly. Include every deferred item, its restrictions, owner, remaining test and completion point. Link supporting evidence to the same item reference.

Record operational acceptance and defect closure separately. Permission to use the system under stated conditions must not imply that every defect has been resolved.

What common mistakes should you avoid?

Closing on a promise. Keep the item open until the agreed evidence exists.

Using priority without consequence. Explain what the defect affects and why it matters.

Assigning an organisation as owner. Name one accountable person, even where several parties contribute.

Accepting an informal workaround. Record its conditions, limits and review trigger.

Losing defects in handover notes. Carry them forward in the active register with their original references.

Treating a changed requirement as a passed test. Record and approve the requirement change, assess its consequences, then verify against it.

What are the frequently asked questions?

Is a commissioning punch list the same as a snag list?

For this approach, either name can work. Require the same ownership, consequence, closure evidence and acceptance decision regardless of the document's title.

Can commissioning finish with open items?

Define completion against agreed acceptance criteria. If deferred items remain, state that explicitly and retain their operating conditions and closure obligations. Do not describe them as resolved.

Who owns an item involving several suppliers?

Appoint one action owner to coordinate the response. Record each supplier's contribution and keep technical acceptance with the designated authority.

What should happen when a defect returns?

Reopen the original item when the accepted behaviour fails again, preserving its history. Review the diagnosis, correction and earlier evidence before agreeing another retest.

Next step

Want to apply this to your plant?

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