{"id":73995,"date":"2026-09-01T17:56:13","date_gmt":"2026-09-01T20:56:13","guid":{"rendered":"https:\/\/a3aengenharia.com\/?post_type=articles&p=73995"},"modified":"2026-09-01T17:56:13","modified_gmt":"2026-09-01T20:56:13","slug":"commissioning-plan-public-works-testing-acceptance","status":"publish","type":"articles","link":"https:\/\/a3aengenharia.com\/en-us\/content\/technical-articles\/commissioning-plan-public-works-testing-acceptance\/","title":{"rendered":"Commissioning Plan for Public Works: Requirements, Testing, Documentation, and Acceptance Criteria"},"content":{"rendered":"\n

A commissioning plan for public works<\/strong> 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.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

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\u2019s technical governance.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

Why the Plan Must Be Developed Before the Final Stage of Construction<\/h2>\n\n\n\n
\n

When tests and acceptance criteria have not been defined before execution, the end of construction becomes a negotiation about what \u201cworking\u201d means. An independent commissioning plan turns requirements into procedures, evidence, and verifiable milestones.<\/p>\n\n\n\n

Engineering Commissioning to plan tests and acceptance<\/a><\/p>\n<\/div>\n\n\n\n

Commissioning is not an activity that begins when the construction team announces that it has \u201cfinished.\u201d If the plan is prepared only at closeout, much of the required evidence may already have been lost or become expensive to obtain.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

The Complete Guide to Commissioning<\/a> 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.<\/p>\n\n\n\n

The Commissioning Plan Should Answer Nine Questions<\/h2>\n\n\n\n

A useful document should allow any involved party to understand the process without relying on informal agreements.<\/p>\n\n\n\n

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

    These questions form the backbone of the document.<\/p>\n\n\n\n

    Recommended Structure for a Commissioning Plan<\/h2>\n\n\n\n

    The plan can be organized into chapters that follow the logic of execution and control.<\/p>\n\n\n\n

    1. Objective, scope, and boundaries<\/h3>\n\n\n\n

    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\u2019s responsibility ends and another begins.<\/p>\n\n\n\n

    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.<\/p>\n\n\n\n

    2. Requirements baseline and reference documents<\/h3>\n\n\n\n

    The plan should list current documents and establish document hierarchy. These may include:<\/p>\n\n\n\n