By building type — Data centres
Clone one CRAC/CRAH checklist across every unit in the room. Each one gets its own record, its own equipment tag, and its own place on the tracker.
First project free · contractors always free · no card
Screenshot — the tracker, showing dozens of individually-tagged cooling units
A template is cloned per unit with its own equipment tag, so each of two hundred identical cooling units gets its own real, distinct record — not one shared checklist standing in for all of them.
Screenshot — cloning a template across multiple equipment tags
Pulling a unit to confirm the standby cooling picks up the load runs through the same functional-test-step recording every other system uses — the result is a timestamped record, not a verbal confirmation.
Screenshot — a redundancy/failover functional test in progress
Equipment goes in, and the trade that installed it fills the checklist section for it — measured values, not a tick.
Systems get run through the sequence. Step results are recorded live, not transcribed afterward from a clipboard.
Anything that fails gets logged where it happened, assigned to a trade, and tracked in a comment thread until it's marked closed.
The handover package assembles itself from what's already been submitted and approved — nothing re-typed.
| Evidence required | Produced by | Form it arrives in |
|---|---|---|
| Every individual unit was verified, not sampled | Per-unit checklist, cloned from one template | Per-unit checklist PDF |
| N+1 (or 2N) failover actually works | Functional test step result | Functional test PDF |
| A complete equipment inventory at handover | Equipment tags across the project | Closeout package |
"—"
DX-Cooling Split Unit
VRF Condensing Unit
Air Handling Unit
Browse the full template library — 17 real templates, all editable.
No — clone one template as many times as you have units. Each clone is a real, independent record with its own equipment tag.
Yes — filter by system, trade, or equipment tag to see exactly the scope you're asking about.
As a functional test sequence, the same mechanism used for any other system test — step results are timestamped as they're run, not written up afterward.
Yes — tags are per-unit identifiers scoped to the project, built for exactly this kind of large, repetitive equipment count.
First project free · contractors always free · no card