Productivity & Best Practices 4 min readORG-F04

PLC Code Review Checklist Before Factory Acceptance Testing

Share

A pre-FAT code review finds ambiguous ownership, unsafe state transitions, hidden bypasses, weak diagnostics, and untestable interfaces before the factory floor becomes the test environment. The review should connect each finding to a requirement, revision, risk, owner, and FAT case.

The short answer

Freeze the review candidate and its build environment, then inspect structure, data ownership, modes, sequences, interlocks, alarms, communications, restart behavior, diagnostics, security-relevant settings, and test hooks against approved requirements. Record findings by severity and disposition. FAT should begin only after blocking findings are corrected in a new controlled revision and the test team can trace every critical requirement to an executable case.

  • Review a reproducible source revision and exact target configuration, not an engineer’s live workstation.
  • Trace safety and process requirements to code modules, interfaces, alarms, and planned tests.
  • Distinguish correctness, maintainability, diagnosability, cybersecurity, and performance findings.
  • Close every accepted, corrected, deferred, or rejected finding with an owner and rationale.
Review the behavior that operators and maintainers will depend on, not only syntax and style.
Text-free PLC code review map covering architecture, states, interlocks, alarms, diagnostics and release

Review the behavior that operators and maintainers will depend on, not only syntax and style.

Decision guide

Review areaQuestions to askRelease evidence
Architecture and dataAre responsibilities, interfaces, writers, types, units, limits and retained values explicit?Module map, interface list, naming checks and dependency review
Modes and sequencesAre transitions, permissives, interlocks, timeouts, aborts, restart and recovery deterministic?State model, cause-and-effect trace and abnormal-path tests
Operations and diagnosticsCan operators identify cause, affected scope and safe next action?Alarm mapping, diagnostic paths, simulation and fault-injection results
Configuration and releaseAre hardware, libraries, communications, access, clock and build versions controlled?Export, dependency versions, checksums, review approval and FAT baseline

A practical workflow

  1. 01

    Define review scope, reviewers, severity rules, required evidence and the exact source, library, hardware and firmware baseline.

  2. 02

    Map requirements and cause-and-effect entries to modules, data interfaces, modes, states, alarms and test cases.

  3. 03

    Walk normal start, stop and production paths, then power loss, communication loss, sensor faults, actuator faults, restart and manual recovery.

  4. 04

    Run static checks, simulation and selected bench tests; capture each finding with location, consequence, recommendation, owner and disposition.

  5. 05

    Correct blocking findings in a new revision, repeat affected checks, approve the FAT baseline and prohibit uncontrolled online changes.

A review finding is complete only when its disposition and affected retest are recorded.
Text-free workflow from frozen code baseline through findings, correction, retest and FAT approval

A review finding is complete only when its disposition and affected retest are recorded.

Evidence and acceptance

Retain the review plan, source and compiled checksums, hardware and software versions, architecture, requirement trace, code-review findings, severity and disposition, screenshots or exports, simulation results, corrected revisions, approvals, open risks, FAT cases, and the baseline released to the test team.

Common mistakes

  • Reviewing style while skipping restart, fault, manual and recovery behavior.
  • Inspecting code without the hardware configuration, libraries, symbols and requirements used to build it.
  • Allowing findings to disappear in chat or email without ownership and retest evidence.
  • Treating a successful download or clean compile as functional acceptance.
  • Changing code during FAT without a new revision, impact review and repeated tests.

Engineering and security boundary

Primary sources

Technical claims and product boundaries were checked against these primary sources. Fact-checked

  1. IEC 61131-3:2025 Programmable controllers — Programming languagesInternational Electrotechnical Commission
  2. PLCopen Software Construction GuidelinesPLCopen

Frequently asked questions

When should the PLC code review happen?

Review the design early, then perform a formal review on the frozen pre-FAT candidate with its exact dependencies and configuration.

Is a compiler warning check enough?

No. The review must cover requirements, architecture, modes, abnormal behavior, diagnostics, interfaces, access and testability.

Can findings remain open at FAT?

Only explicitly accepted non-blocking findings with owners, risk rationale and closure dates should remain.

Does AutoNexit review PLC logic automatically?

No. Qualified reviewers perform the engineering review; AutoNexit keeps its inputs, findings, revisions and evidence connected.

Related articles

ORG-F03

Maintainable PLC Program Architecture: Modules, States, Interfaces, and Naming

A maintainable PLC program makes machine states, module responsibilities, interfaces, commands, permissives, alarms, modes, diagnostics, and recovery behavior understandable without tracing every rung. Architecture should reduce coupling while preserving deterministic behavior, safe authority, online diagnosability, and controlled change.