Version 1.0 · reviewed 26 July 2026

Free PLC Commissioning ToolkitFAT, SAT & I/O Templates

Eight editable resources that connect requirements, hardware, software and field evidence. Preview everything, download without signup and adapt the columns to your project's controlled procedures.

Download the complete pack (.zip)Open the I/O list builder

Requirements flow through engineering registers, FAT, site loop checks and SAT into an as-built evidence pack — Stable IDs let a requirement point to a signal, cause, test result and exception without relying on someone's memory.

Download pack

Start with the document you own

CSV opens in Excel, LibreOffice and Google Sheets. Preserve revision, owner and status columns when adapting the files.

01FAT checklistFactory tests for documents, hardware, software, HMI, failures, evidence and handover.CSV 02SAT checklistSite readiness, field I/O, functional tests, operations and final acceptance.CSV 03PLC I/O list builderBuild, validate and export an I/O register locally in the browser.Interactive 04Instrument indexField dictionary, workflow, example and CSV for tags, ranges, connections and datasheets.Guide + CSV 05Cable scheduleField dictionary, example and CSV for origins, terminals, construction, routes and glands.Guide + CSV 06Cause-and-effect matrixTraceability workflow, example and CSV for causes, effects, resets, bypasses and tests.Guide + CSV 07Control narrativeWriting method, worked requirement trace and CSV prompts for modes, sequences and recovery.Guide + CSV 08Loop-check sheetEnd-to-end procedure, signal-path diagram and CSV for stimulus, indication and restoration.Guide + CSV

How the files fit together

1.Write testable requirementsUse the control narrative and cause-and-effect matrix before building logic. Give each requirement an ID.
2.Create the registersAlign instruments, I/O, cables, terminals, ranges and drawing references. Resolve conflicts before FAT.
3.Prove offline and at FATTest normal operation, failures, restarts and communication loss. Store evidence beside each test ID.
4.Reconcile the installationAt site, compare the actual panel and field wiring with the controlled registers before functional tests.
5.Close with SAT evidenceRecord as-left values, clear forces and bypasses, archive the running software and control every exception.

Quality rules worth keeping

One owner: each row needs someone responsible for closing it.
One status vocabulary: define Draft, Ready, Pass, Fail, Blocked and Accepted Exception.
No silent deletion: retire a row with a reason instead of erasing the evidence.
As-found and as-left: preserve both when calibration or correction changes a value.
Separate safety validation: reference the approved record; do not reduce it to a generic FAT checkbox.
Controlled handover: the archive must match the program and hardware actually running.

Need the workflow behind the sheets?

Read the functional design specification, cause-and-effect matrix and site acceptance test references.

A minimal evidence pack

At handover, an independent engineer should be able to identify the approved requirement, installed hardware, running software, field signal, test result and unresolved exception without reconstructing the project from email. At minimum, retain approved specifications, as-built drawings, I/O and instrument registers, network schedules, backups, FAT/SAT records, calibration/loop evidence, punch lists, training records and the final change log.

Review the pack after the first real project and send corrections through the corrections process. Versioned improvements make this asset more useful than a static checklist copied between jobs.

Reference or share this toolkit

If a training note, project standard or article points readers to these files, link to this versioned landing page so they also receive the use boundary, updates and corrections—not an orphaned spreadsheet.

https://plcprogramming.io/tools/commissioning-toolkit