Method Statement: Low-Current (ELV/ICT) Systems Handover and As‑Built Documentation inspection and test plan example.

Inspection and Test Plan for Method Statement: Low-Current (ELV/ICT) Systems Handover and As‑Built Documentation

AI-assisted inspection and test plan connected to a method statement, with PDF and Excel export.

Published 15 Sep 2026 Rev. 00 2 views

Disclaimer: This ITP is provided as a public reference document. Verify all inspection activities, acceptance criteria, and records against your project specifications, applicable standards, and contractual requirements before use. Quollnet accepts no liability for its application on any project.

About this ITP: The ITP defines hold/witness points and acceptance criteria for ELV handover, including drawings, labeling, testing, O&M, asset verification, training, and final dossier.

More than a static template

Unlike a downloadable Word or PDF template, this ITP is an AI-assisted editable starting point directly connected to its method statement. Every inspection activity, hold point, and acceptance criterion is structured and ready to adapt to your project.

AI-assisted customization — Tailor inspection activities and acceptance criteria to your specific project scope.
Linked method statement — This ITP is connected to the corresponding method statement describing the work sequence.
Multiple export formats — Download as a formatted PDF or editable Excel spreadsheet.
Editable starting point, not a final document — Review and verify all content against your project specifications and standards before use.

Download ITP PDF Formatted ITP document Download ITP Excel Editable ITP spreadsheet Open Method Statement Method statement linked to this ITP

What you can customize

When you save this ITP to your account, every inspection row becomes editable. You can add, remove, or modify:

Inspection activity — Description of what is being inspected.
Inspection type — Hold point (H), Witness point (W), Review (R), or Monitor (M).
Responsibility — Contractor, subcontractor, engineer, or client.
Frequency — How often the inspection occurs.
Acceptance criteria — Referenced standard or specification requirement.
Records — Forms, test reports, or checklists required as evidence.

Why this ITP is used

To ensure systematic inspection, testing, and verification of ELV systems and documentation prior to Client acceptance.

Who uses this inspection and test plan

Contractor QA/QC, Commissioning teams, OEM vendors, Consultant, and Client/FM representatives.

When this ITP is prepared and submitted

From redline capture through final dossier submission and acceptance, with hold/witness points at key milestones.

Who receives or approves this ITP

Consultant and Client for review, witnessing, and acceptance.

Inspection scope

Covers documentation quality, labeling, structured cabling certification, FAS, security, BMS, PA/GA testing, asset and O&M verification, training, and final submission.

Typical hold, witness, and review points

As‑Built review (H), FAS functional (H), O&M review (H), labeling verification (W), cabling tests (W), security/BMS/PA-GA tests (W).

Typical inspection records

ITRs, calibrated test reports, redlines/as‑builts, labeling checklists, permits, training records, snag closure, transmittals, acceptance certificates.

Important approval note

This ITP is an AI-assisted editable starting point, not a pre-approved document. Before use on any project, all inspection activities, hold points, and acceptance criteria must be reviewed and approved by the relevant parties (superintendent, principal contractor, or client representative) in accordance with your contract and project quality plan.

Always verify acceptance criteria against your applicable drawings, specifications, and regulatory requirements. Hold points must be confirmed with the relevant authority before work proceeds past that point.