Data centres

Data centre punch lists, closed on evidence before the hall goes live.

Install checks with hold points, the commissioning punch list and the defects after handover, on one record: filed by hall, row and room, issued to the trade that owns each item, and closed by someone who did not do the work. Works offline in the plant rooms where phones lose signal.

One list, however many contractors

Electrical, mechanical, controls, fire, containment and the equipment vendors each open their own items from an emailed link, with no seat to buy and no app to install. None of them sees another trade’s work, and none of them can close their own.

Filed the way the building is

Import the tree as paths, DC2/Level 1/Data Hall 3/Row C, up to five levels deep. Every item, checklist and drawing hangs off it, and a QR label on the UPS room door opens that room’s list for a signed-in user, offline too.

A handover the operator can read

The operator gets rooms with dated histories: what failed, who fixed it, who accepted it and when. Not a punch list export with the closing comments stripped out.

Installation QA

Install checks with hold points nobody waves through.

Build each inspection and test plan once as a reusable checklist, then run it against the hall, the row or the electrical room it covers. Answer Yes or No as you go. Every No raises a tracked item linked back to the question, and the question flips back to Yes on its own when that item closes, so the checklist and the punch list never disagree. The checks that have to be witnessed become hold points, and the checklist waits on them.

A subcontractor can answer its own part of a checklist from a link, without an account, and the link reaches only as far as the next hold point. The checklists page lists every one running across every project, with a marker on any hold point still open.

Data Hall 3 · this weekLIVE

MonContainment check · Row C · 3 of 18 failed

Mon3 items raised · issued to containment

TueBusway check · Hall 3 · hold point open

WedElectrical answered its stretch · link

ThuContainment closed 3 · photos attached

Your ITPs as reusable checklists
Build the containment install check, the busway check or the fire-stopping walk once, then run it per hall, per row or per room.
A No raises the item for you
Every failed check becomes a tracked item linked back to the question, and the question flips back to Yes when that item closes.
Hold points that stop the walk
Mark the checks that must not be waved through and the checklist waits on them, with a marker on every list until someone answers.
The trade answers its own stretch
Send a subcontractor a link to its part of a checklist, up to the next hold point and no further. It can be revoked, extended or re-sent, and every attempt is logged.
Every hall on one sheet
The Wall Sheet rolls open items, checklist progress and outstanding hold points up the tree, so Data Hall 3 reads as one row before you drill into Row C.
Works where the signal does not
Items, photos and checklist answers save on the phone in a shielded hall or a basement plant room and sync in order when it reconnects.

Commissioning punch list

Hundreds of items, one owner each, closed before the test window.

The commissioning agent walks the hall, then the client’s rep walks it, and between them there are three hundred items and a date that does not move. Each one goes on the register as a tracked item against the room it is in, typed as a defect, incomplete works or a safety issue, and issued to the contractor who owns it. The trade marks it fixed with a photo of the finished work; someone on your side closes it. Every transition is stamped with a name, a role and a time.

Workflow rules chase what goes overdue, and a saved report filtered to the hall can email itself as a PDF before the morning coordination meeting. Where the job needs a scope and a cost code, the batch becomes a work order with a backcharge flag.

Punch list · 10 days to ISTLIVE

06:30Outstanding items · Hall 3 · emailed

09:14CRAH 3.07 · access panel not fitted

11:02Controls dispute 2 items · design intent

14:4041 closed today · 118 open

17:00Overdue digest · project manager

Defect, incomplete works or safety
The Type field keeps an unfinished cable tray run out of your defect count, and a safety item out of both, without a second list.
Assigned in bulk by room or trade
Two hundred items from the client walk go to the right contractors in a few actions, not two hundred.
Your terms on every item you send
Standing clauses, a sign-off and a CC list go out with every item issued. On a project that needs it, the email waits until someone presses Send.
Disputes decided on the record
A trade that says it is design intent raises a dispute. The item waits for a supervisor to decide, and both sides stay in the history.
Chased without a spreadsheet
Workflow rules escalate anything past its due date and send a digest on the schedule you set, to roles, named people or outside addresses.
The report for the morning meeting
Save the outstanding-items report filtered to the hall and schedule it as a daily PDF. It generates and emails with nobody logged in.

Drawings, contractors, plant

The revision they built to, and the cover they worked under.

The drawing register keeps every revision byte for byte, and a distribution records which revision each contractor acknowledged, so “we built to rev C” is checkable. The contractor record holds each company’s insurance policies with their expiries and its SWMS, linked to the project when the company is assigned to it.

The scissor lifts and EWPs working in the halls go on the plant register, with a daily pre-start from a phone and a reminder before a service or a policy falls due. A failed pre-start reaches every manager straight away, naming the machine and the check.

Project register · this weekLIVE

MonSingle line diagram · rev D issued

MonDistributed to electrical · ack required

TueElectrical acknowledged rev D

WedFire services · PL policy expiring

ThuSL-04 scissor lift · pre-start failed

Revisions that never overwrite
Rev D of the single line diagram arrives and rev C is archived with its uploader, its date and the pins placed on it. Issued documents are withdrawn, never deleted.
Proof they got rev D
Distribute a revision with acknowledgement required. Each recipient confirms against that revision, including outside addresses with no account.
SWMS on file before they start
A contractor’s SWMS link to the project the moment the company is assigned to it, from the one library on the company record.
Cover with an expiry date
Public liability, workers compensation and the rest held as policies with amounts and expiries, and the soonest expiry flagged on the dashboard.
Scissor lifts pre-started
The EWPs and scissor lifts in the halls sit on the plant register with a daily pre-start from a phone. A No tells the managers straight away.
Already running Aconex?
Defects can sync both ways with an Aconex project, so the field record lands in the contractual one.

How an item flows

Found on the walk

A failed install check, the commissioning agent’s walk or the client’s. Logged against the hall, the row or the room, with a photo where the site allows one.

Owned by one trade

Issued to the contractor who owns it with a due date. They open the link, fix it and mark it complete. They cannot close it.

Closed before the hall goes live

Someone on your side closes it, stamped with a name, a role and a time. The operator inherits the room’s history, not a spreadsheet.

IST, liability, handover

The expensive arguments on a data centre are about dates.

When a hall slips, somebody pays for the slip, and the question is always the same: what was open, whose was it, and when did it close. A punch list that only shows today’s state cannot answer that. A record with a dated trail can. Four arguments it settles.

The item closed the night before IST

Who closed it, when, on whose word and with what evidence. When the test turns something up the next morning, the argument starts from the record, not from memory.

The vendor who says it was damaged after install

The install check answered Yes by a named person on a dated day, and every item raised on that row since, each with its own date and photo. That is a different conversation from “it was fine when we left”.

The defects liability claim

A fault in the second UPS room, first logged in month four of the liability period, issued to the builder, and still open in month eleven. Dated, attributed, and on the same record the handover came from.

The operator’s handover review

Every hall and room with its closed items, the checklists behind them and the drawing revisions they were built to. A register export and the item reports filtered room by room, rather than a folder of emails.

Asked by data centre teams

Questions data centre builders ask first

How does IssuesId fit a data centre build?

It carries the installation QA and the commissioning punch list. Each inspection and test plan becomes a reusable checklist run against the hall, row or room, with hold points on the checks that have to be witnessed, and every No raises a tracked item. Every item the commissioning agent or the client’s rep raises goes on the same register, is issued to the trade that owns it, and is closed on evidence by someone on your side, with a name, a role and a time on every step.

What if the data hall does not allow cameras?

A photo is optional when an item is logged, and each project decides whether a trade needs a photo of the finished work before marking it fixed: Required, which is the default, Optional or Off. Without photos the record rests on the location, the names, the roles and the times, which are kept either way. Two things your security team should know before a pilot: photos keep their original capture metadata, including position where the phone records it, shown to your own staff only; and the new-item form asks the browser for the device’s position, which the browser asks permission for first.

How do subcontractors and equipment vendors get access?

Add the company to your contractor list and issue items to it. Its contact gets an email with a link that opens that work, with no account and no app. They see their own items only, not another trade’s work and not costs, and they can mark an item fixed or dispute it but cannot close it. A checklist can also be sent as a link that reaches only as far as the next hold point, and it can be revoked at any time. Every outside role is bound to the projects it was added to.

Can the client or the operator follow progress without seeing every open item?

Yes. Invite their representative with the client role: read-only access to the items on their projects, with comments and a client summary PDF, and no documents, work orders or search. A per-project setting can narrow that further to items already fixed or closed, so they see progress rather than every raw finding.

Does it work with no signal in the halls and plant rooms?

Logging items, their photos and checklist answers works offline: they save on the phone and sync in order when it reconnects, and a QR label on a room door still opens that room’s list.

What happens after the operator takes the site over?

The record carries on. Defects in the liability period, the fit-out of the next hall and faults in the support spaces are logged against the same rooms the build used, issued to the builder or the contractor by link, and closed on evidence, so every room keeps one history from installation onwards.

Also built for

Builders →Practical completion, the handover pack, and the month-eleven DLP call answered from the record.Real estate agencies →Tenants raise a maintenance request with a photo; it routes to the trade and closes with proof.Property managers →Maintenance and defects across a residential portfolio, with an audit-logged record for every owner.Strata & owners corporations →The common-property defect register: by unit and level, dated photos, and the trail the inspector reads.Facilities management →Reactive faults and condition walks in commercial buildings, logged by room and closed on evidence.Manufacturing →Line inspections with hold points, non-conformances, and an ISO 9001-ready audit trail.Logistics & warehousing →Pre-trip, asset and facility inspections with photo proof of condition at the dock.

Before the next hall

Run one hall on it and compare the handover.

A pilot runs on a live project for two weeks, alongside whatever you use now. Trades, the client’s rep and your own team each see only what their role allows, and outside access is scoped on the server. The same record carries a builder’s handover and a commercial building’s faults after it. Pricing is per active site, with every user included.