HOW TO WRITE | A Cx Testing Method Statement / Script

A Testing and Commissioning Method Statement, also referred to as a Testing and Commissioning Procedure or Functional Testing Script, is a critical written document that provides clear and concise, step-by-step instructions for completing a specific test or inspection within a project construction and commissioning process. 
The document serves as a technical blueprint for performance verification, detailing how a specific system or piece of equipment will be tested to prove it meets its design and operational performance criteria and intent.

This is particularly critical in complex environments like data centres and commercial buildings where system performance directly impacts business operations and occupant comfort.

---

⬜ 3 Key Takeaways

• A Testing and Commissioning Method Statement (also known as a Procedure or Functional Testing Script) is a crucial document providing step-by-step instructions for testing systems within a project, especially in complex environments like data centers.
• These documents are essential for ensuring quality assurance, mitigating risks, adhering to standards, facilitating client acceptance, and serving as a comprehensive record and future reference for system performance and maintenance.
• The creation of a Method Statement involves a thorough evaluation of project information (specifications, drawings, codes) followed by structured writing that includes introductory details, reference data, equipment lists, pre-requisites, system testing information, tolerances, the sequential method of testing, and a testing certificate.

🟩 Why Are These Documents Written and Needed?

These documents are written to ensure that the testing and commissioning of systems / plant and equipment is completed and verified ensuring that they are set up, tested, commissioned, verified, and documented in line with the Owners Project Requirements (OPR), Basis of Design (BOD), and manufacturers’ needs.

Beyond verification, testing and commissioning method statements / test scripts are written for several other reasons:

✅ Quality Assurance and Risk Mitigation: By detailing specific steps, tolerances, and pre-requisites, the method statement / test script will ensure that the testing is performed consistently and correctly for one or multiple of the same units, acting as a valuable quality assurance tool, helping to mitigate risks associated with improper installation, faulty equipment, or incorrect system integration, which could lead to operational failures.

✅ Ensuring Adherence to Standards and Regulations: The documents will help focus adherence to specific Codes, Guides, Standards, and Regulations, ensuring specification, legal compliance, safety, and operational legitimacy.

✅ Facilitating Client Acceptance and Accountability: These documents should be fully reviewed, accepted, and signed off by the client team/representatives [usually the commissioning agent] before any testing takes place. This will ensure that the ‘project team’ are in agreement with the works and that the testing to be conducted is correct and accepted. 

✅ Supporting Comprehensive Documentation and Handover: Method statements / test scripts will help contribute significantly to the project’s overall documentation and handover quality, ensuring a complete record of how systems were tested, which is vital for ongoing maintenance, fault finding, and future modification.

✅ Managing Complex System Integrations: Particularly in data centres and modern commercial buildings, systems such as Mechanical (HVAC), Electrical, Plumbing/Drainage, Fire, Building Management Systems (BMS), Controls, and Extra Low Voltage are highly integrated. Part of the document requirements  will be to review control logics, wiring diagrams, and BMS points lists ensuring that the testing addresses this, helping prove that systems work together as designed.

✅ Future Reference: If there are any queries or reviews required later of the testing completed, the document allows for quick and easy understanding of how the testing was completed and what information was used.

✅ Training: Especially useful as there are new people joining the facility team after completion and are looking for some additional information on the systems and equipment installed.

⚠️ It should be noted that the method statements / test scripts would usually focus upon how the testing will be completed from a technical point of view and not usually incorporate any strategies that may be required to facilitate potential live environments.

Separate, additional documentation is required for these live environment strategies.

🟩 Responsibilities & Process:

The process of writing, issuing, and reviewing a method statement / test script usually involves various roles and responsibilities:

👷 General/Main Contractor: Typically prepares or manages the document, handling its writing, issuing, and overall management. 

🧑‍🔧 Vendors/Subcontractors: Provides input to the General/Main Contractor.

🧑‍💼 Commissioning Manager: Responsible for the overall review, commenting, and approval of the documents.

✍️ MEP&F Designer: Provides input to the Commissioning Manager.👨‍💼Client: Provides input to the Commissioning Manager.

🟩 How to Write a Method Statement / Test Script:

The process of creating a Testing and Commissioning Method Statement typically involves two main steps:

🟧 Step 1 – Evaluation of Information

Before writing a method statement / test script, a comprehensive analysis of the project information must be completed to fully understand all requirements. This will help ensure that the testing method is effective, accurate, and aligned with all project and manufacturer requirements. 

The evaluation should cover reviewing:

🟧 Step 2 – Writing the Method Statement

Once all necessary information has been gathered, the document can be written and using a standard and consistent format is recommended. This will ensure that a standardised approach is used resulting in efficiency and clarity for the engineers and operatives involved.

A typical format and content of a Method Statement / Test Script would include:

Section	Description
Front Cover	Includes Company Logo, Project Name/Number, Title of the Method Statement, Document Number, and Document Revision.
Document Revision Register	Lists all revisions with number, date, author, and description of changes. Highlighting revised areas can be helpful for reviewers.
Index / Contents Page	Index / Contents page for reviewers
Introduction	A high-level overview of the document's purpose, how it will be reviewed, and its expected status before testing. It explicitly states the document's focus on technical testing, separate from strategies for live environments, which are covered by additional documentation.
Competency of Engineers	Includes a statement that work will be undertaken by suitably trained personnel, encompassing safety training, manufacturer training, and compliance with local government requirements. Particular attention is paid to specialised works such as Electrical, Authorized Persons (for lock-off procedures), Pressure Vessels, Gases, Refrigerant, and Test, Adjust, Balance (TAB). Emphasising why this is critical (safety, operational integrity, complex equipment) is important.
Permit to Work System	A statement is included to confirm that safety requirements will be reviewed, and all staff will adhere to any permit-to-work systems in place at the time of testing.
Programme	A general statement referencing the project programme for testing dates, as actual testing rarely adheres to rigid, pre-defined schedules.
System Installation Sign Off	A statement requiring the relevant installation sign-off certificate to be shown to the commissioning party before testing commences.
	🚀Note: The above sections are considered standard introductory information. They are often removed from the final project Operating and Maintenance Manuals to streamline documentation and save paper, while the core technical sections are retained.
General [Tabulated Information]	A new section often includes tabulated information completed at the time of testing, such as Project Name, Location/Floor, Start Date/Time, and Finish Date/Time.
Reference Data	This crucial section details all information reviewed to write the document, providing the reviewer confidence that the method statement is based on specific project requirements. This includes document numbers, page/section/item numbers for General/Particular Designer Specifications, Commissioning Plans/Specifications, Codes/Guides/Standards/Regulations, Drawings/Schematics, and Material/Technical Submissions.
Equipment / Instrumentation	Provides information in a table format on all equipment, instruments, tools, and accessories to be used. This includes the Type and Model (completed at writing), and spaces for the Serial Number and Calibration Certificate Expiration (to be completed at testing).
General Pre-Requisites	This section includes critical requirements for the operatives and engineers conducting the works, such as Operating System Pressures, Flow Rates through valves/dampers/equipment, Control Expectations, Electrical Supplies (e.g., dual-fed equipment), Room Condition requirements, Lux Levels, etc.. This section, along with testing tolerances, defines the specific performance benchmarks and acceptance criteria the system must meet. For data centres, this could involve very tight environmental (e.g., temperature, humidity) or power quality tolerances.
Testing Tolerances	Most testing requires adherence to specific parameters or tolerances, usually detailed in project specifications, codes, guides, standards, and regulations. A table outlines the Type of Tolerance, the Reference Document (e.g., BSRIA, CIBSE, NFPA, ANSI) including page/section/item, and the specific tolerance/specification/time period for the testing.
Method of Testing	This section covers all sequential, logical steps for completing the testing and commissioning, the ‘cause and effect’. Instructions should be detailed, step by step, clear and concise for the engineers and operatives. Sufficient space is provided for data input, and a box at the bottom of each page allows for signatures from the persons doing the testing and witnessing for recording.
Testing Certificate	The certificate is used to capture all relevant testing information. It is designed with ample space for clear data input, and like the method of testing section, includes a box at the bottom of each page for signatures from those completing and witnessing the testing.
Marked Up Drawing	A set of fully marked-up drawings, ideally A3 for clarity, should be attached in an appendix, showing the systems and equipment the document refers to.

🟩 Issuing and Approving the Method Statement:

Once complete, the method statement is issued for comments and approval to the client team, typically including the Commissioning Manager and MEP Designer, a separate document cover sheet may be required.

The document should be logged within a document tracking register for reporting and progress tracking.

Once reviewed, approved, and or commented upon by the client team, it is then assigned a Status (e.g., A, B, C). 

Depending on the status, updates and reissuing may be required before testing can commence, projects often allow work to proceed with a Status B, a Status A is typically required for inclusion within the Operating and Maintenance Manuals.

🟩 Method Statement / Test Script vs Checklist

It is important to note that while a Testing and Commissioning Method Statement details the procedural steps for testing, it is not the same as a Testing and Commissioning Checklist. 

A Checklist details specific items to be inspected, usually prior to testing, though a checklist can be included within a method statement if needed.

---

Download the Above/Below Instructions

You can download the below document, for free, at our shop by clicking the button.

WS-004.000-How-to-Write-a-Method-Statement-1

---

⬜ Frequently Asked Questions

---

⬜ Related Articles

⬛ Latest Articles

---

⬛ Author

If you would like to know more about the author, here is my Personal Linkedin Account