Equipment Commissioning Checklist: Verify Readiness, Tests and Handover
Use this equipment commissioning checklist to control readiness, verification, testing, exceptions, acceptance and operational handover.
On this page +
- Establish the commissioning boundary
- Confirm documentation readiness
- Verify physical and installation readiness
- Hold a pre-commissioning readiness review
- Execute tests in approved stages
- Control defects, deviations and retests
- Verify operating and maintenance readiness
- Complete the handover record
- Use this master commissioning checklist
- Review the commissioning package for consistency
- Adapt the checklist to the equipment
An equipment commissioning checklist provides a controlled path from installed equipment to accepted operational responsibility. It should answer five questions: Is this the correct equipment? Is the installation ready? Were approved tests completed? Are exceptions visible? Has responsibility been transferred to people who have the information and competence to operate and maintain it?
Commissioning is not a celebratory final tick. It is a staged evidence process. The equipment inspection checklist can support condition checks, while the field service visit checklist helps organize a technician visit. Neither alone proves commissioning acceptance.
Establish the commissioning boundary
Define exactly what system, subsystem or asset is being accepted. Complex equipment may be mechanically complete while controls, utilities or safety interfaces remain unavailable.
Project / commissioning package:
Equipment name, ID, model and configuration:
Location and system boundary:
Included interfaces:
Explicit exclusions:
Approved design and instruction references:
Commissioning owner:
Target handover stage:
Use configuration references that can be traced later. Do not rely on a nickname or location alone. If the physical asset and approved documentation disagree, record the discrepancy and escalate it before testing.
Confirm documentation readiness
Commissioning should use current, approved information. The exact document set varies, but the readiness review commonly checks drawings, specifications, manufacturer instructions, certificates, inspection records, software or configuration baselines, permits and operating documentation.
| Document control | Question |
|---|---|
| Identity | Does it apply to this asset and configuration? |
| Revision | Is the current approved revision available? |
| Status | Is it approved for the intended use? |
| Deviations | Are approved changes incorporated? |
| Accessibility | Can performers and reviewers access it? |
List references and versions rather than pasting partial technical requirements into the checklist. That prevents an editable form from becoming an unofficial engineering specification.
Verify physical and installation readiness
Use discipline-specific, approved inspection sheets. The master checklist should show whether required inspections are complete and where the evidence lives.
[ ] Asset identity and labels confirmed
[ ] Installation checks completed under approved procedure
[ ] Connections and interfaces verified
[ ] Required guards, access and housekeeping reviewed
[ ] Utilities and supporting systems available
[ ] Instruments and test equipment status confirmed
[ ] Open construction or installation items reviewed
[ ] Area released for the planned test stage
Do not infer safety from visual completion. Follow applicable isolation, permit, energization and risk-control processes. Only qualified and authorized people should perform consequential checks.
Hold a pre-commissioning readiness review
Before introducing energy, material, load or automated operation, confirm the test plan, roles, communication method, stop criteria and recovery route. Record attendees and decisions, but do not treat attendance as approval.
Test leader:
Authorized operators and witnesses:
Communication channel:
Prerequisites:
Defined stop conditions:
Expected operating envelope:
Contingency / recovery reference:
Decision authority:
For a structured cross-team decision record, use a decision log template. The log should point to the controlled technical evidence rather than paraphrasing safety-sensitive instructions.
Execute tests in approved stages
Commissioning often moves from static verification to controlled functional checks and integrated operation. The sequence must come from the approved plan for the equipment, not from a generic web checklist.
| Test ID | Approved method | Preconditions | Result | Evidence | Witness |
|---|---|---|---|---|---|
| T-01 | Procedure reference | Confirmed / blocked | Pass / fail | Record ID | Role |
| T-02 | Procedure reference | Confirmed / blocked | Pass / fail | Record ID | Role |
| T-03 | Procedure reference | Confirmed / blocked | Pass / fail | Record ID | Role |
Record actual values with units, operating conditions and test points. Never replace raw evidence with “works fine.” If a test is interrupted or performed under a changed condition, mark it incomplete until an authorized person determines the required disposition.
Control defects, deviations and retests
Every exception needs more than a comment. Make its relationship to acceptance explicit.
Exception ID and description:
Observed evidence:
Requirement or test affected:
Immediate approved condition:
Owner and due date:
Retest required: yes / no / decision pending
Acceptance impact:
Decision authority and date:
A conditional acceptance should define the condition, owner, deadline and operating boundary. It is not permission to hide incomplete work. Use the action ownership approach in who completes the action item form so every open item transfers to a named person.
Need a reviewable draft from an agreed commissioning discussion? Kuno supports visible, consented in-person capture. Qualified people must verify every test reference, value, exception and acceptance decision. Explore Kuno
Verify operating and maintenance readiness
Technical test completion is only one part of handover. Confirm that responsible teams have the approved information, access and competence needed for the accepted operating state.
[ ] Asset register and configuration records updated
[ ] Operating information transferred
[ ] Maintenance plan and initial schedule established
[ ] Required spares and consumables addressed
[ ] Training or competency evidence completed
[ ] Alarms, escalation routes and contacts communicated
[ ] Open exceptions accepted by authorized roles
[ ] Warranty or supplier records transferred where applicable
The first maintenance schedule should be based on approved technical sources and operating context. A preventive maintenance checklist can then convert that plan into repeatable tasks without rewriting the commissioning record.
Complete the handover record
Handover transfers defined responsibility; it does not erase project accountability. Record the exact stage, asset condition, accepted boundaries and remaining items.
Handover stage and effective time:
Accepted equipment / boundary:
Current authorized operating state:
Open exceptions and restrictions:
Transferred documents and records:
Outgoing owner:
Incoming owner:
Technical acceptance:
Required next review:
The incoming owner should be able to distinguish accepted capability from planned future capability. Preserve signatures or approvals according to the organization’s controlled process.
Use this master commissioning checklist
DEFINE
[ ] Asset, configuration, system boundary and stage identified
PREPARE
[ ] Approved documentation available
[ ] Installation evidence complete
[ ] People, equipment, controls and test plan ready
TEST
[ ] Preconditions verified for each stage
[ ] Results and raw evidence captured
[ ] Failures stopped and escalated under approved process
DISPOSITION
[ ] Defects have owners, dates and acceptance impact
[ ] Retests and deviations are authorized and traceable
HAND OVER
[ ] Operations and maintenance readiness confirmed
[ ] Asset status and open restrictions communicated
[ ] Named roles accept the defined transfer
Keep separate discipline sheets where detailed checks require specialist content. The master record should index evidence and show status without becoming an uncontrolled technical manual.
Review the commissioning package for consistency
Before archive, check that asset identifiers match across records, passed tests have evidence, failed tests have dispositions, approved changes appear in the final configuration and every open item has transferred ownership. Conflicting records should remain visible until resolved; do not edit one merely to create a clean package.
A structured maintenance shift handover checklist can support continuity during a multi-shift commissioning window. It does not replace the formal acceptance package.
Preserve context without outsourcing acceptance. Kuno can turn an authorized room conversation into draft notes for human review; it cannot test equipment, determine readiness or authorize operation. See Kuno
Adapt the checklist to the equipment
This equipment commissioning checklist is a framework, not a test procedure. Adapt it with engineering, operations, maintenance, safety, quality, privacy and legal owners. Use current manufacturer and controlled project sources. A defensible commissioning record makes the accepted boundary, supporting evidence, unresolved risk and transfer of responsibility easy to understand.