Commissioning Plan for Public Works: Requirements, Testing, Documentation, and Acceptance Criteria

How to structure a commissioning plan for public works: requirements, systems, FAT, SAT, integrated testing, documentation, acceptance criteria, handover, and Law 14.133.

Check it out!

A commissioning plan for public works is the document that transforms design and contract requirements into a verifiable strategy for inspections, tests, responsibilities, records, acceptance criteria, and transition to operations. It should state what will be commissioned, in what sequence, by whom, with which prerequisites, which procedures will be used, what evidence will be generated, and what constitutes approval, rejection, retesting, and release of each system.

In public works, this structure is especially important because delivery needs to connect execution, inspection, acceptance, and the public interest. Law 14.133/2021 provides that works and services are accepted after verification of technical and contractual requirements and allows inspections, tests, and other evidence to assess proper execution. If these criteria are discussed only at the end of construction, the risk of divergence increases: the contractor may consider a system complete because it is installed and energized, while the Administration expects integrated performance, complete documentation, training, and functional demonstration that were never objectively specified.

The commissioning plan reduces this ambiguity. It creates a traceability line from requirement to system, test procedure, result, evidence, punch item, and acceptance. For a low-complexity public works project, it may be relatively concise. For hospitals, data centers, stations, substations, control centers, buildings with automation, and other critical facilities, it should be developed as part of the project’s technical governance.

ABNT NBR IEC 62337:2020 provides a relevant methodological reference by distinguishing erection completion, pre-commissioning, commissioning, start-up, performance testing, and plant acceptance. Although its scope addresses electrical, instrumentation, and control systems in process industries, its phase-and-milestone logic is useful for structuring plans in other projects, provided it is adapted to the type of facility, specific standards, and contractual requirements.

Why the Plan Must Be Developed Before the Final Stage of Construction

Commissioning is not an activity that begins when the construction team announces that it has “finished.” If the plan is prepared only at closeout, much of the required evidence may already have been lost or become expensive to obtain.

Cables may have been installed and concealed without test records; piping may have been hidden before inspection; parameters may have been changed without version control; equipment may have been received without document verification; interlocks may depend on interfaces between suppliers that never defined responsibilities.

For this reason, a robust plan begins during design and evolves through procurement, fabrication, installation, testing, and handover. The strategy should define in advance which tests will be performed at the factory, which depend on field installation, which require operating conditions, and which can only occur after systems have been integrated.

The Complete Guide to Commissioning presents an overall view of the process. In public procurement, however, the next step is to convert that view into obligations, deliverables, and verifiable criteria within the plan.

The Commissioning Plan Should Answer Nine Questions

A useful document should allow any involved party to understand the process without relying on informal agreements.

1. What is the scope? Systems, subsystems, equipment, interfaces, and battery limits.
2. Which requirements will be verified? Design, specifications, standards, legislation, and contractual criteria.
3. What are the milestones? Completion, pre-commissioning, energization, startup, functional tests, integrated tests, performance, and acceptance.
4. Who does what? Contractor, manufacturers, inspection team, commissioning team, designers, operations, and third parties.
5. What are the prerequisites? Approved documents, completed installation, available utilities, safety clearance, calibrations, and environmental conditions.
6. How will each test be performed? Procedure, instruments, sequence, data, tolerances, and evidence.
7. What constitutes approval? A measurable criterion, not subjective expressions such as “operating normally.”
8. How are failures and outstanding items handled? NCR, punch list, retest, conditional acceptance, and traceability.
9. How does transfer occur? Data Book, As-Built, training, warranties, spare parts, assisted operation, and acceptance.

These questions form the backbone of the document.

Recommended Structure for a Commissioning Plan

The plan can be organized into chapters that follow the logic of execution and control.

1. Objective, scope, and boundaries

The opening section should define the purpose of the plan, systems covered, exclusions, interfaces, and assumptions. On projects with multiple contracts, it is essential to state where one package’s responsibility ends and another begins.

The most common mistake is to limit the scope to a list of equipment. Commissioning must consider functions and interfaces. An emergency generation system, for example, involves the generator, fuel system, switchboards, ATS, priority loads, automation, alarms, and operating procedures.

2. Requirements baseline and reference documents

The plan should list current documents and establish document hierarchy. These may include:

• Detailed Engineering Design documents and design narratives;
• technical specifications;
• Terms of Reference and contract;
• data sheets and manufacturer documents;
• applicable technical standards;
• legal and regulatory requirements;
• requirements matrix;
• safety and performance studies;
• operation and maintenance criteria.

Requirements, Evidence, and Acceptance Criteria Management is the link that prevents a test from existing without a requirement or a requirement from remaining without verification.

3. Organization and responsibilities

The plan should identify roles, not just names. A RACI matrix can define who prepares the procedure, who reviews it, who executes it, who witnesses it, who approves it, and who receives the records.

The Administration’s inspection function should not be confused with the commissioning company. Article 117 of Law 14.133 allows third parties to be hired to assist and support the public inspector with information, but this engagement does not transfer the inspector’s legal authority. The consultant may plan tests, witness them, analyze evidence, and issue technical opinions; administrative acts remain with the competent public agents.

4. Breakdown of systems and subsystems

The project should be decomposed in a way that supports commissioning. The construction WBS is not always suitable for testing. A package may be divided by functional system, zone, area, subsystem, or operating unit.

A typical matrix may include:

Code	System	Subsystem	Area	Responsible party	Current milestone	Final test
EL-01	Normal power	Main LV switchboard	Block A	electrical contractor	pre-commissioning	functional test
EL-02	Emergency	generator set	central plant	supplier	SAT	integrated test
AUT-01	Automation	BMS	building	integrator	configuration	integrated scenarios
INC-01	Fire protection	detection	all floors	installer	inspection	cause-and-effect test

This decomposition is what makes it possible to control progress and responsibility by system.

Phases and Milestones: From Installation Completion to Acceptance

ABNT NBR IEC 62337:2020 distinguishes useful milestones. Adapted to public works, they can be structured as follows.

Installation completion

The physical milestone at which the installation has been assembled to the level required for subsequent checks and tests. Evidence should exist for installation inspections, identification, torque where applicable, connections, cleaning, alignment, and minimum documentation.

Pre-commissioning

The verification phase before full functional operation. It includes continuity, insulation, calibration, flushing, pressure tests, alignment, loop checks, configuration, static tests, and other activities according to the discipline.

The article on Pre-Commissioning in Engineering details this transition.

Functional commissioning

The phase in which equipment and systems are operated under controlled conditions to verify functions, sequences, alarms, and interlocks.

Integrated testing

The phase that combines systems to verify real scenarios. This is where interface failures that are not detected during individual tests become apparent.

Performance testing

These tests verify capacity, consumption, efficiency, availability, or parameters defined in the contract.

Handover and acceptance

The approved system is transferred with documentation, records, classified outstanding items, and defined responsibilities.

Inspection and Test Plan Does Not Replace the Commissioning Plan

The Inspection and Test Plan — ITP controls inspection points, hold points, witness points, and quality records throughout execution. It may contain many tests that are relevant to commissioning, but it has a different purpose.

The commissioning plan integrates the project at a broader level. It organizes systems, milestones, dependencies, functional procedures, integrated tests, interfaces, handover, and operational readiness.

A sound document architecture connects both: the ITP demonstrates execution quality; the commissioning plan demonstrates that the constructed asset performs as required.

How to Define Tests Without Falling Back on Generic Checklists

Each test should exist because there is a function or requirement to demonstrate. The procedure needs to answer:

• which requirement is being verified;
• which system is under test;
• what the prerequisites are;
• which instruments will be used;
• which initial conditions must exist;
• which sequence will be executed;
• which values will be recorded;
• which tolerance is acceptable;
• which evidence will be attached;
• who witnesses and approves;
• how retesting occurs in the event of failure.

“Turn on the equipment and verify operation” is not a sufficient criterion for critical systems.

FAT, SAT, and Integrated Tests Should Form a Coherent Sequence

FAT verifies equipment or packages before shipment, in a controlled environment. SAT confirms installation and function at the final site. Integrated tests verify interfaces between systems.

FAT and SAT should be planned to avoid purposeless repetition and gaps. A well-executed FAT can reduce field risk, but it does not eliminate the need to test installation, integration, power supply, communications, and real operating conditions.

Example: an automation panel may pass FAT using simulators and fail SAT because of cabling, addressing, network, or sensor problems. Even after an approved SAT, the system may fail the integrated test because another subsystem does not respond to the cause-and-effect logic.

Acceptance Criteria Must Be Measurable and Contractually Traceable

The acceptance criterion is one of the most important parts of the plan. Expressions such as “in perfect working order,” “properly installed,” or “as expected” are weak when there is no associated verification method.

Whenever possible, the criterion should indicate:

Element	Example criterion
Functional response	command executed and feedback received within the specified time
Redundancy	loss of the primary component without interruption exceeding the defined limit
Alarms	event generates the correct alarm, correct priority, and a record in the system
Performance	minimum capacity or efficiency specified in the design
Power quality	parameters within specified tolerances
Documentation	complete, signed, identified, and traceable report

When the design does not contain values, the plan should record the need for a technical definition before the test is executed.

Instrumentation and Metrological Traceability

Quantitative tests depend on reliable instruments. The plan should specify instruments, ranges, accuracy, identification, and calibration status according to criticality.

Attaching just any certificate is not sufficient. The range and uncertainty must be appropriate for the measured quantity. Inadequate instrumentation can produce a formally recorded result that is technically incapable of demonstrating compliance.

Hold Points and Witness Points for Inspection

Not every activity requires the presence of the inspection team or consultant. An efficient plan classifies control points.

• Hold point: the activity does not proceed without the required release.
• Witness point: the interested party is called to witness the activity, and rules may allow continuation in the event of absence.
• Review point: subsequent document review.
• Surveillance: sampling-based or criticality-based monitoring.

This strategy reduces unnecessary attendance and concentrates resources on higher-risk tests.

How to Handle Failures, NCRs, Punch Lists, and Retests

The plan should establish the workflow before the first failure occurs. A failed test may generate a nonconformity, outstanding item, correction, and retest.

The failure should not disappear simply because the form is replaced. It is important to maintain traceability among the original test, cause, corrective action, evidence of correction, and new result.

The Outstanding Items, RFIs, and Nonconformities Management solution supports an auditable workflow for this process.

Integrated Scenarios Should Represent Real Failures and Degraded Modes

Normal operation is only one of the possible states. High-quality integrated tests should verify foreseeable failures and contingencies.

In a critical building, scenarios may include:

• loss of normal power supply;
• generator startup and transfer;
• UPS failure;
• loss of communication;
• fire alarm;
• opening of emergency doors;
• failure of redundant equipment;
• restoration of normal power;
• controller loss;
• sensor failure or protection trip.

The scenario needs to indicate preconditions, actions, expected response, and acceptance criteria.

Documents the Plan Should Require Throughout the Process

Commissioning generates a set of documents that should feed the Data Book.

• systems matrix;
• requirements matrix;
• test procedures;
• completion checklists;
• FAT and SAT reports;
• calibration certificates;
• inspection records;
• results and trends;
• NCRs and punch lists;
• retest records;
• completion certificates;
• As-Built documentation;
• manuals;
• spare-parts lists;
• training records;
• handover certificate;
• final commissioning report.

The Construction Data Book should be planned from the beginning, not assembled hurriedly after testing.

How to Integrate the Plan into the Construction Schedule

Commissioning needs to appear in the project’s physical schedule. Each test depends on predecessors: installation, energization, utilities, programming, cleaning, access, documentation, and manufacturer availability.

If the schedule reserves “one week for commissioning” at the end without decomposing systems and dependencies, there is a high risk of artificial schedule compression.

A more robust strategy works by systems and progressive releases. Construction and pre-commissioning can overlap in a controlled manner, as recognized by the logic of ABNT NBR IEC 62337. The key is to maintain boundaries and responsibility by area or system.

The Role of Commissioning Under Law 14.133 and in Formal Acceptance

Article 140 of Law 14.133 establishes detailed acceptance provisions and provides that the object may be rejected, in whole or in part, when it does not comply with the contract. It also addresses inspections, tests, and other evidence used to assess proper execution.

Commissioning creates precisely the technical evidence that can support this verification. It does not replace the public inspector, the acceptance committee, or administrative acts. Its function is to structure and produce the technical basis.

The article on acceptance of construction works under Article 140 presents the legal and contractual layer; the commissioning plan defines the operational testing layer.

How to Specify Commissioning in the Terms of Reference

To procure a construction project that will be commissioned, the Terms of Reference should define from the preparatory phase:

1. systems and commissioning scope;
2. responsibility for preparing and approving the plan;
3. required FATs and SATs;
4. integrated and performance tests;
5. manufacturer attendance when necessary;
6. instruments and calibrations;
7. documentation and records;
8. acceptance criteria;
9. retests and responsibility for costs arising from failed tests;
10. training;
11. As-Built documentation and Data Book;
12. handover and assisted operation where applicable.

Without these definitions, the contractor may price only installation and minimum manufacturer tests, while the Administration expects an integrated validation that was never included in the price.

When to Hire an Independent Commissioning Agent

Independent commissioning is advisable when project complexity, criticality, or the number of interfaces makes it insufficient to rely only on the executing contractor’s own controls.

The commissioning agent can:

• review requirements and design from a testability perspective;
• prepare or review the commissioning plan;
• analyze supplier procedures;
• witness FAT/SAT;
• monitor pre-commissioning;
• conduct or witness integrated tests;
• manage technical outstanding items;
• verify documentation;
• issue readiness and commissioning reports.

Independence does not remove responsibility from the contractor. The executing contractor remains responsible for delivering the object in accordance with the contract. The agent represents the owner’s need for verification.

Commissioning a Restarted Project Requires a Specific Strategy

On a suspended project, part of the systems may have been installed long before remobilization. The plan should consider the as-found condition, exposure time, validity of previous tests, design changes, software updates, and warranty status.

The condition assessment and survey of completed services identifies what can be reused. The commissioning plan defines what must be verified again before those items can be considered suitable for acceptance.

A test performed two years before suspension may not be sufficient if the system remained exposed, underwent intervention, or lost traceability. The decision should be based on risk and evidence.

Operational Readiness Should Be the Plan’s Exit Gate

The ultimate objective of commissioning is not to accumulate reports, but to demonstrate that the asset can be transferred safely and with the required performance.

The operational readiness assessment consolidates systems, documentation, teams, maintenance, licenses, and outstanding items.

The plan should define which conditions must exist before a readiness declaration or recommendation for entry into operation can be issued. Critical outstanding items should block release.

What to Procure to Structure and Execute the Plan

When the Administration does not have a specialized team to coordinate the entire process, procurement can combine different scopes.

Preparation and review of the commissioning plan

Appropriate when the project is still in design or execution and requirements need to be transformed into a complete testing and delivery strategy.

Commissioning management and execution

Appropriate when suppliers, tests, interfaces, evidence, and outstanding items need to be managed through handover.

Independent technical acceptance

Useful when the main need is to support final verification of the object and produce a technical opinion on compliance.

Owner’s Engineering

Useful on complex projects when the owner needs to integrate engineering, procurement, construction, testing, documentation, and operations.

A3A structures Engineering Commissioning and Owner’s Engineering with a focus on requirements, evidence, interface management, and acceptance.

Final Considerations

The commissioning plan is the link between what the design promised and what the constructed project can demonstrate. In public works, it also brings engineering closer to the formal acceptance process because it transforms generic concepts such as “operation” and “compliance” into procedures, records, and verifiable criteria.

The quality of the plan depends on starting early, decomposing the project into systems, tracing requirements, defining responsibilities, establishing coherent tests, and planning handover. When these decisions are left until the end, commissioning becomes a race to produce paperwork; when they are part of planning, they become a mechanism for preventing failures, disputes, and assets delivered without real operating readiness.

For the public manager, the central question is simple: if the contractor says tomorrow that the work is complete, does the contract already define exactly how to prove that each system is ready? If the answer is no, the commissioning plan still needs to be structured.

Technical references

[1] BRAZIL. Law No. 14.133, of April 1, 2021. Public Procurement and Administrative Contracts Law. Available at: https://www.planalto.gov.br/ccivil_03/_ato2019-2022/2021/lei/l14133.htm.

[2] BRAZILIAN ASSOCIATION OF TECHNICAL STANDARDS. ABNT NBR IEC 62337:2020 — Commissioning of electrical, instrumentation, and industrial process control systems — Specific phases and milestones.

[3] BRAZILIAN FEDERAL COURT OF ACCOUNTS. Procurement and Contracts: TCU guidance and case law. Available at: https://licitacoesecontratos.tcu.gov.br/.

[4] A3A ENGENHARIA. Commissioning: complete guide to planning, testing, acceptance, and handover. Available at: https://a3aengenharia.com.br/conteudo/guias-tecnicos/guia-completo-sobre-comissionamento/.

Frequently asked questions

What should a commissioning plan for a public works project contain?

It should contain scope, requirements baseline, systems and subsystems, responsibilities, milestones, prerequisites, test procedures, instruments, acceptance criteria, failure handling, documentation, handover, and conditions for operational readiness.

When should the commissioning plan be prepared?

Preferably during design and before execution of critical systems. Preparing it only at the end of construction increases the risk of lost evidence, unmanaged interfaces, and tests that were not contractually specified.

Is an Inspection and Test Plan the same as a commissioning plan?

No. The ITP controls quality inspections and tests throughout execution. The commissioning plan integrates systems, milestones, functional and integrated tests, performance, handover, and operational readiness.

Does commissioning replace acceptance under Article 140 of Law 14.133?

No. Commissioning produces and organizes technical evidence. Provisional and final acceptance continue to be performed by the competent Administration agents and committees in accordance with the contract and legislation.

Who should execute commissioning tests?

It depends on the contract. Manufacturers and executing contractors normally perform tests under their responsibilities, while the inspection team, commissioning agent, and operations team may review, witness, or approve evidence according to the responsibility matrix.

What is an integrated test?

It is a test that verifies the combined response of two or more systems under a functional or failure scenario, demonstrating interfaces, sequences, redundancies, and behaviors that do not appear in isolated tests.

How should a failed test be handled?

The failure should be recorded, analyzed, corrected, and retested while maintaining traceability among the original procedure, cause, corrective action, and final result. Depending on the case, it should generate an NCR or punch-list item.

When should independent commissioning be hired?

When the project has high complexity, critical systems, many suppliers or interfaces, high availability requirements, or when the Administration needs independent technical verification to support acceptance and entry into operation.

Complementary technical materials

Related solutions

• Requirements, Evidence, and Acceptance Criteria Management
• Outstanding Items, RFIs, and Nonconformities Management
• Contracts, Scope, and Deliverables Management
• Document Governance and Document Management System

Related services

• Engineering Commissioning
• Technical Acceptance of Construction Works and Engineering Services
• Owner’s Engineering
• Assisted Operation

Main content on the topic

• Commissioning of Buildings and Building Systems
• Inspection and Test Plan (ITP)
• Pre-Commissioning in Engineering
• FAT and SAT: integrated testing and acceptance criteria

Related technical content

• Commissioning: Complete Guide
• Method for Commissioning, Verification, and Acceptance of Low-Voltage Electrical Installations
• Technical Handover Framework for Construction Works and Systems
• Construction Data Book
• Article 140 of Law 14.133
• Operational readiness in public works