THE FIELD GUIDE
Data-center construction: a complete photo record is not an accepted system.
Build a traceable handover from field evidence to the project’s review process. Keep construction documentation distinct from commissioning and live operations.
Where this guide begins and ends
This guide covers the organization of construction evidence: what was observed, where it belongs, who reviews it, and which questions remain open. It does not provide an electrical test procedure, a commissioning checklist, a design specification, or permission to operate infrastructure. We have not established that any listed product is approved for a particular data-center owner.
Data-center construction deserves its own path because the destination of a record matters. An installer may capture a label or an installation condition, but that observation is not automatically an accepted turnover item. Live operations, change control, and integrated-system testing are separate specialist subjects that this launch edition does not cover.
The evidence has to enter an approval process
The WBDG Commissioning Committee’s documentation guidance distinguishes field observations, test data, issue logs, project requirements, and systems manuals. It describes issue records with responsibility and completion status. That is useful process guidance, not a universal current code checklist: actual review and acceptance roles come from the project requirements and commissioning plan.
The editorial implication is simple. A capture tool should preserve the identity and state of evidence until an authorized reviewer can act on it. A generated description must not silently turn ‘observed’ into ‘verified’, ‘installed’ into ‘tested’, or ‘submitted’ into ‘accepted’. Those transitions carry different meanings.
A minimal record to agree with the receiving team
Before selecting software, ask the project’s document owner for its accepted identifiers and formats. A proposed capture record might contain the project and package identifier, location, asset or assembly identifier, observation date, original evidence, current issue status, responsible reviewer, and the next action. Include drawing or document revisions only through the project’s approved process.
This is a starting template, not a substitute for the project’s quality plan. If the receiving system already defines these fields, use its definitions. Creating a second naming scheme that nobody reconciles can make an otherwise detailed record difficult to use.
What the current solution index can help evaluate
CompanyCam describes photo and report workflows; Fulcrum describes structured field-data capture and offline synchronization. These descriptions support a narrow question: can the chosen capture workflow deliver the required evidence to the next person? They do not establish technical acceptance authority or full commissioning-management capability.
Tool custody is another separate task. The stock-and-tools comparison can help frame questions about where a piece of equipment is assigned. It should not be cited as evidence that installed plant is complete, energized, or approved.
A documentation-only trial
- Use an authorized, non-sensitive pack from a completed project or a fictional example. Define the receiver’s required fields first.
- Include one mislabelled image, one corrected identifier, and one unresolved documentation issue.
- Capture the pack, correct the mistakes, and produce the intended export or shared record.
- Ask someone who did not attend capture to identify the item, original observation, correction, unresolved action, and responsible reviewer.
- Record missing fields, ambiguous states, duplicate records, and clarification time. Leave technical acceptance outside the exercise.
What a useful result would say
A useful conclusion is bounded: the receiving team could retrieve the original evidence and understand the open issue in this sample, or it could not. It should identify the configuration, devices, export, and review path actually used. It should not infer system performance, commissioning completion, or suitability for every data-center project.
Follow-on coverage needs practitioner review and project-specific sources before it addresses technical commissioning. The immediate opportunity is more modest and practical: reduce ambiguity in the record without weakening the authority of the people who must review it.
Sources & evidence
Official sources reviewed November 3, 2026. Vendor materials establish descriptions, not independently measured performance. Original evaluation criteria are our analysis.