gLodRa · Cx Cx Tracker

LEED v4 · v4.1 · v5 commissioning · CxA-led

Commissioning, delivered as one job.

CxA, field team and our own Cx tracking software, from one hand. Every device, every functional test and every decision on one chain. Cx that proves LEED v5, LL97 and decarbonization targets in the field, with evidence. Verified performance protects the owner's investment.

We don't sell software and we don't sell site services. We deliver the complete Cx job. The software is its biggest advantage.

Meet us at Greenbuild 2026 · Javits Center, New York

Six commitments

A tailor-made model: one core, cut to your project.

Full control

Every device, every item, every decision in one record. Nothing stays in someone's inbox.

Full flexibility

Any request from the site or the owner is added as a module within days.

Tailor-made

The pattern is ready, the fit is yours. The system takes on your project's language, disciplines and layout.

100%devices

Every device and piece of equipment on the list sits on the key plan and on the chain. Not a sample, all of it.

100%evidence

No decision without a photo, a measurement and a witness. Statements don't count.

100%data

Records survive a lost connection. A published report is frozen and stays exactly as issued.

Why

What happens when site information is lost?

Industry research says the same thing: when site information is lost, time, money and work are lost with it.

35%

A third of the time is wasted

Construction workers spend more than 14 hours a week looking for information, resolving disputes and fixing mistakes.

14 hours of a 40-hour week
48%

Half of all rework comes from bad information

Wrong or missing information and poor communication cause 48% of rework. In the US alone it cost $31.3 billion in 2018.

  • Wrong information, poor communication
  • Other causes
48 of every 100 reworks
11%

Only 11% always have the information

Only 11% of field teams always have the information they need on what to build and where. Coordination problems raise budgets by 9% on average.

11 of every 100 field workers

Source: FMI and PlanGrid, 2018 (approx. 600 respondents) · Dodge Construction Network, 2024 (US and Canadian contractors)

Method

Eight rings, one chain

Every site record sits on a ring of this chain. The rings never change; what goes inside them changes with the job.

  1. 1

    Island

    A place on the key plan

  2. 2

    Building

    Comes from the drawings

  3. 3

    Stop

    Permanent number, permanent place

  4. 4

    Device

    Tag, nameplate, model

  5. 5

    Checklist item

    Pass, fail, not visible

  6. 6

    Evidence

    Photo, measurement, witness

  7. 7

    Cx issue

    Numbered in the issues log: open, resolved, closed

  8. 8

    Decision

    Made by the CxA, Cx report freezes

On site

Tablet, stop by stop on the key plan. No connection? The record waits, it is never lost.

In the office

Visible the same minute. Approve, reject and conditions from one place; everyone touches only what their role allows.

In the Cx report

Cx reports are not written, they are printed. A published report is frozen and never changes after the fact.

Functional testing and acceptance

One device, eight rings

Acceptance is not a statement, it is a witnessed functional test. Every device passes this chain; one that fails shows as "Failed" on its ring in the overview.

  1. 1

    Visit

    Opened as a functional test visit, required witnesses set

  2. 2

    Device

    Tapped on the key plan; tag and system

  3. 3

    Test steps

    FPT steps load automatically by system

  4. 4

    Measurement

    Value, unit, field note

  5. 5

    Result

    Pass or fail; photo, video

  6. 6

    Witness

    CxA, contractor, operations and owner sign

  7. 7

    Decision

    Passed, conditionally accepted or failed; by the CxA

  8. 8

    Status

    Device takes its place, Cx report goes on file

Speed

An installed device is functionally tested the same day. A failed item is in the issues log at once; nobody waits for a report.

Trust

No device is accepted until every party has signed. Every witness at the test is on record.

Trace

If a fix is needed the test is repeated. The first result is kept too; nothing changes silently.

One principle

Every decision tied to evidence,
every piece of evidence tied to a place.

Statements don't count. Photos, measurements and witness sign-off do. Every piece of evidence has its island, building, stop and device; the person who decided and the time are on record.

Tailor-made

Flexible in both directions

Tailor-made means exactly this: we move freely on both axes. The project grows and the system stays the same; the procedure gets deeper and the system models it.

Two-axis diagram: scale on the horizontal axis, procedural depth on the vertical axis Tailor-made: anywhere in this space 2-floor fit-out, LEED Fundamental Cx Single building, deep testinghealthcare, data center 400+ buildings, site observation 100 islands, Enhanced Cx + code HORIZONTAL · SCALE VERTICAL · PROCEDURAL DEPTH 1 building100 islands

Horizontal

Project size

1 building or 100 islands, 2 floors or 100. Same setup, same screen, the same single tap on site.

See the scale band ↓

Vertical

Procedural depth and variety

However many standards, tests, checklists, witnesses and documents there are, they are modeled: ASHRAE 202, IECC C408, Title 24 acceptance testing, LEED v5, the owner's own requirements.

Scopes and standards ↓

Horizontal · scale

1 island or 100. 2 floors or 100.

Same setup, same screen, the same single tap on site.

1Islands
2Floors (tallest)
40Devices
  • Setup: same
  • Screen: same
  • On site: one tap
Aurora Bay· demo project

New screen

Portfolio map

Every island and building on one screen. Each column is a building, each slice a floor, color is the acceptance rate. Aurora Bay: 3 islands, about 3,069 devices.

Marina Tower A

New screen

Tower section

A 30-story tower, floor by floor: device count, acceptance bar, open Cx issues. Tap a floor to open its stops.

Flexibility

One backbone, plug-in modules

Site observation, construction checklists, functional testing and every new discipline share one backbone. Each module brings only what is unique to it. A new module needs a definition, not a rebuild.

  • Site observation visit

    • Stop
    • Observation
    • Photo
  • Construction checklist

    • Device
    • Installation verification
    • Hold point
  • Functional testing (FPT)

    • Device
    • Test step
    • Witnessed result
  • Functional testing schedule

    • Week
    • Device group
    • Witness calendar
  • Issues log

    • Contractor
    • Cx issue number
    • Close-out proof
  • New

    Portfolio map

    • Island
    • Building column
    • Floor slice
  • New

    Tower section

    • Floor
    • Device count
    • Open Cx issues
  • Your request

BackboneIsland › Building › Stop · Evidence · Cx issue number · Decision · Cx report · Key plan · Offline
01

Request

The site or the owner asks for something new: a list, a check, a view.

02

Module

It is added as a module within days. It sits on the same backbone and follows the same evidence rule.

03

Catalogue

A module written for one project is ready on the next. The catalogue grows with every job.

Modules are switched on by your CxA, and only by your CxA.

Vertical · procedural depth

Any building. Any standard. One commissioning record.

We model the procedure your project is held to, then prove it in the field, item by item.

Cx types we deliver

    Standards we model

      LEED v5 ready
      • The CxA starts at schematic design; the record opens on day one
      • Envelope Cx is part of fundamental Cx
      • Three years of monitoring-based Cx (MBCx) continue on the same record
      Building performance standards

      Every year of a BPS needs evidence: the same record that commissions the building proves its performance.

      LL97 · BERDO · DC BEPS · Seattle

      After turnover

      The project ends, the record lives on

      At turnover the owner receives not scattered files, but the complete, recorded history of every device.

      During the project
      1. Construction

        Every check and test recorded on the spot, with its photo

      2. Turnover

        Every device passes a witnessed functional test; nothing is turned over until accepted

      After turnover
      1. Opening

        Device list, test results and decisions handed to operations in full

      2. Maintenance

        When something fails, its history and test results are known

      3. Warranty

        Service records and device history are ready; warranty claims run in full

      The usual turnover
      • Cx reports sit in folders as PDFs
      • Decisions live in people's memory
      • Which device passed which test is unclear
      • Operations learns the site from scratch
      Turnover with this method
      • Every device's place, functional test and result in one record
      • Who decided, and when, is written down
      • Cx issues are tracked by number in the issues log: open, resolved, closed
      • Operations starts day one with a current device list

      Live reference

      Already running at resort scale

      A 4-island resort in the Indian Ocean, live since 2026. The same backbone and the same screen, with modules cut to the project.

      Live · since 2026
      4Islands
      400+Buildings
      8,595Devices
      88Functional test activities

      The pattern is ready, the fit is yours

      Your project, cut to measure.

      Sign in with the account your CxA gave you; your project's screen opens directly.

      Projects are private. Each project runs on its own database.