A commercial rooftop array, a containerised battery and a bank of fleet chargers all end the same way: someone has to prove that each thing installed was tested, that it passed, and who did the testing. On most installation projects that proof still lives in a mix of manufacturer commissioning sheets, a spreadsheet of string readings and photos on an engineer's phone. It gets assembled at the end, usually by someone in the office who was not on site.
This guide is about doing it the other way round: building testing forms and commissioning checklists that belong to the products themselves, so the evidence is created at the moment of testing and is already in the right place when handover arrives.
Why commissioning evidence falls apart
The problem is rarely that engineers skip tests. It is that the record of the test is disconnected from the thing tested. A typical failure looks like this:
- An insulation resistance reading is written against "string 4", but nobody recorded which inverter input string 4 landed on.
- A charger is commissioned, but the serial number on the form belongs to the unit that was swapped out after a delivery fault.
- A battery system's firmware version is noted on the manufacturer's app and never copied anywhere the customer or the service team can see it.
- Two engineers use two versions of the same checklist, so half the project has a polarity check field and half does not.
Each of these is fixable after the fact, but only by sending someone back to site or by trusting memory. The fix is structural: the form has to know which product it is about.
Commissioning checklists versus product testing forms
It helps to separate two kinds of record, because they do different jobs.
A commissioning checklist covers a system or an area. It asks whether the installation as a whole is ready: isolation in place and labelled, protective devices correct, earthing verified, the system energised in the right sequence, the customer's controls or monitoring connected. One checklist per system, per phase or per distribution board is typical.
A product testing form covers a single item. It records what that item is, where it went and the results of the tests carried out on it. On a solar project that might be each inverter and each string. On an EV project it is each charge point. On a building services job it might be each air handling unit, each controller or each fire damper.
Most contractors need both. The checklist tells you the system was brought into service properly; the product forms tell you every component in it was individually verified. When a fault appears two years later, it is the product-level record that the service engineer actually needs.
What the standards already expect
For solar PV installers working under MCS, the structure of the record is not optional. The MCS Solar PV installation standard, MIS 3002 issue 6.0 (published 18 March 2026), says the system shall be commissioned according to a documented procedure, and that the document pack given to the client includes copies of all forms and checklists used to commission the system. Its Appendix E reproduces a model PV array test report, adapted from BS EN 62446-1, with fields per string for open-circuit voltage, short-circuit current, polarity, array insulation resistance and earth continuity, plus the inverter make, model and serial number.
That is a useful template even outside MCS work, because it shows the shape of a good product test record: identity, location, measured values, pass or fail, instrument used, and the person responsible. EV charge point and battery installers will have equivalent requirements from their own codes of practice and manufacturers; the principle carries across.
Designing a testing form that engineers will actually complete
A form built in an office often fails on a roof. A few rules make the difference.
Start with identity. The first fields should pin the record to one product: serial number, model and location. If the product already exists in the project with its serial, the form should inherit it rather than ask for it again.
Ask for readings as numbers, not prose. A text box labelled "IR test" invites "OK". A number field for positive-to-earth and negative-to-earth resistance, in megohms, produces something you can check against a threshold later.
Use conditional logic to keep forms short. A three-phase charger and a single-phase charger need different fields. A hybrid inverter needs battery fields that a string inverter does not. Show the relevant section only when it applies, rather than building five near-identical forms.
Make the essentials mandatory. Integrio's form builder lets you mark fields as required, and product testing forms can be set so that required fields must be completed before a project can be signed off. That turns "we should have recorded that" into "we cannot close the job until it is recorded".
Capture the evidence, not just the answer. A photo of the label, a photo of the meter display or a signature from the witnessing engineer is worth more than a tick. Field types for photos, uploads and signature capture belong on the form, not in a separate folder.
Record the instrument. If a test meter is later found to be out of calibration, you need to know which results it produced.
Attaching forms to products, not just projects
In Integrio, testing forms are assigned to products in the product library. When a product type is added to a project, its testing form comes with it. So every inverter on a project carries its own inverter test form, every charge point carries a charger commissioning form, and every battery carries whatever checks your procedure requires.
This has three practical effects.
First, nothing is forgotten, because the list of outstanding tests is simply the list of products without a completed form.
Second, the record stays attached to the product for its whole life. When the customer raises a fault later through the helpdesk, the engineer opens the same product and sees the original test results alongside the service history.
Third, reusable templates keep the method consistent. A form built once can be attached to projects, sites or spaces across the business, so a new starter in Bristol and an experienced engineer in Leeds are filling in the same fields.
A worked example: a car park canopy with chargers and a battery
Consider a project for a logistics customer: a solar canopy over a staff car park, a battery system, and twelve dual-outlet chargers.
The project is built from product types already in the library: modules, inverters, the battery enclosure, the chargers and the distribution equipment. Each type brings its data points and its testing form.
- Inverters carry a form modelled on the PV array test report: per-string readings, polarity, insulation resistance, isolator checks, then inverter make, model, serial and functional check.
- The battery carries a form for the manufacturer's commissioning steps, firmware version, configured operating mode and the result of the functional test.
- Each charger carries a form for supply details, protective device checks, earthing arrangement, network or SIM details, the configuration applied and a test charge result.
- A system-level commissioning checklist sits on the project for energisation sequence, labelling, emergency isolation and customer controls.
The site team works through the products on the mobile app. The office can see which chargers are commissioned and which are still open without phoning anyone. When the last required field is completed, the project can move to sign-off.
From checklist to handover pack
The reason to structure commissioning like this is what happens next. A handover pack is largely a compilation of records that already exist: the commissioning checklist, each product's test results, serials, manuals and warranty details. When those are held against the products, the pack is assembled rather than written. Integrio's project sign-off tools produce a completion package with the documentation you specify, and branded PDF reports can be exported for the customer.
A free commissioning checklist template is a good starting point if you are building your first form.
Getting started
Pick one product type that causes you the most rework, often chargers or inverters, and build its testing form first. Put identity fields at the top, readings as numbers, evidence as photos, and mark the essentials as required. Run it on one project, collect engineer feedback, then roll it out to the next product type. Within a few projects the commissioning record stops being an end-of-job scramble and becomes a by-product of doing the work.