Commissioning software
A commissioning agent or QA firm on a data center, plant or hospital has one deliverable: proof that every piece of equipment was installed, started, tested and integrated the way the design said. Commissioning software exists to hold that proof in a shape an owner can accept. Most of it is a filing cabinet with checklists. The question is whether it can refuse.
What commissioning software actually has to do
Keep one record per asset that follows it from delivery through installation, pre-functional checks, functional performance tests, integrated systems testing and turnover — the CSI 01 91 00 levels, L0 to L5, or whatever your specification calls them.
Attach the evidence to the step that required it: the photograph of the nameplate, the reading and its acceptable range, the signature of the person who witnessed the start-up, the vendor's test report. A checklist tick with nothing behind it is a promise, not a record.
Name who actually performed every test. The commissioning agent witnesses and documents; the contractor and the vendor perform. When a warranty dispute lands, that line matters legally.
Produce the turnover package as a consequence of the work, so the owner's acceptance is a review of what already exists rather than a scramble to build it.
What to look for in any commissioning tool
- 1Can a step close without its evidence?Ask the vendor to try. If a required photograph or reading can be skipped and the checklist still turns green, the record is only as good as the most tired technician on the job.
- 2Does the rule hold for everyone?In some tools a rule is a suggestion: an administrator, an import or an API call goes around it. Ask whether the rule holds the same way no matter who is asking or how.
- 3Does the record survive handover?Many tools are priced and built for the construction phase and go quiet at turnover. The owner then inherits a PDF. Ask what the owner can do with the record in year three.
- 4Is the history editable?If an administrator can correct a closed test record in place, an auditor cannot tell the correction from a cover-up. Look for a history that can only be added to, with every correction attributed and dated.
- 5Can the owner watch it happen?An owner who sees the register fill in as the work happens needs fewer meetings and fewer surprises. Portals should be included, not an add-on seat.
- 6Can you take everything out?Every record as CSV and every file, in bulk, on demand — not a ticket to support. If the data cannot leave, it is not yours.
How Veristep does it
A step that asks for a photograph, a reading in range, a signature or a document stays open until that exact thing is recorded. Nothing — not an import, not the API, not an administrator — closes it around the rule. That is proven by an automated test, not promised in a policy.
Each asset carries its commissioning level, L0 to L5, each one earned by its proof; passing a level earns the coloured tag that goes on the machine, and the tag colour is the register's colour.
Every test record names who performed it and who witnessed it. The QA firm's role — observe, document, report — is built in.
Every closed step is already in the turnover package. The owner reads it in their portal and accepts it there.
At handover the site moves to the owner's own workspace, with its maintenance routines and warranty windows, and the firm keeps its sealed history. Years later the same record answers the question.
Every record as CSV and every file as one archive, on demand, for customers — and for ninety days after a plan ends.
What you bring: your functional test scripts, written once as templates per discipline and reused on every job — the checklist is yours, and Veristep makes sure it's followed. BMS trend logs come in as uploaded evidence on the step that asks for them, and design review covers requirement feasibility and deviations while your Cx design-review workflow stays where it runs today.
Questions people ask
It runs alongside either. Firms usually keep the general contractor's platform for RFIs and drawings and run the commissioning record in Veristep, because this is where the rules actually hold. Everything exports as CSV so nothing is locked in.
Yes. Each asset carries its level, each level has to be earned with the proof the template names, and passing a level earns a physical colour tag.
Your firm, the subcontractors you admit for their scope, the vendors for theirs, and the owner through a portal — all on one record, each seeing what their role allows. Team members are unlimited.
The package is already assembled. The owner accepts it in their portal, and the firm can hand the site over so the owner runs maintenance and warranty on the same record.