Guide

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 with a tick and no artefact is a promise, not a record.

Attribute every test to the party who performed it. 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

  1. 1
    Can 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.
  2. 2
    Where is the rule enforced?
    In the interface, a rule is a suggestion: a direct API call or a database token goes around it. In the database, it is a fact. Ask which.
  3. 3
    Does 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.
  4. 4
    Is 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 append-only history with attributed corrections.
  5. 5
    Can 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.
  6. 6
    Can 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

The database refuses

A step that asks for a photograph, a reading in range, a signature or a document stays open until that exact thing is recorded. The refusal is a trigger in PostgreSQL, so nothing — not the app, not a raw token, not an administrator — closes it around the rule. This is proven by an automated test suite that runs the real migrations.

Levels with physical tags

Each asset carries its commissioning level, L0 to L5, gated by evidence; passing a level earns the coloured tag that goes on the machine, and the tag colour is the register's colour.

Attributed tests

Every test record names the party who performed it and the person who witnessed it. The QA firm's boundary — observe, document, report — is built into the model.

The closeout builds itself

Every closed step is already in the turnover package. The owner reads it in their portal and accepts it there.

The record outlives the job

At handover the site moves to the owner's own tenant, with its maintenance routines and warranty windows, and the firm keeps its sealed history. Years later the same record answers the question.

It leaves with you

Every record as CSV and every file as one archive, on demand, for customers — and for ninety days after a plan ends.

Where we are thinner

Where we are thinner than a specialist commissioning product today: there is no built-in library of manufacturer-specific functional test scripts — you bring your own templates or write them once; there is no native trend-log ingestion from a building management system; and the design-review module covers requirement feasibility and deviations, not full Cx design review workflows. We say so here so you do not find out in week two.

Questions people ask

Is Veristep a replacement for CxAlloy or a Procore add-on?

It runs alongside either. Firms usually keep the general contractor's platform for RFIs and drawings and run the commissioning record in Veristep because the enforcement lives here. Everything exports as CSV so nothing is locked in.

Does it handle the L0–L5 commissioning levels?

Yes. Each asset carries its level, each level is gated by the evidence the template names, and passing a level earns a physical colour tag.

Who can see the record during construction?

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.

What happens at turnover?

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.

Related: Turnover package software · Punch list software · How it works

See it refuse to close a step.