What Should a Data Center Inspection Report Contain?

1. What was inspected, precisely

Not "the electrical room." The specific checkpoints in the electrical room, each with an identifier that means the same thing on every pass, so this month's report can be compared to last month's.

If a checkpoint is on the route and doesn't appear in the report, that should be visible rather than silent.

2. When, and on which pass

The exact date and time each capture was taken, tied to a numbered run through the building. Not the date somebody typed it up.

This matters because the first question anyone asks about a record is when it was created, and "sometime in March" is not an answer.

3. The evidence itself, not a summary of it

The thermal image. The visible photo taken from the same position at the same moment. The environmental readings at that point.

A report that says "temperature within range" and shows nothing is asking the reader to trust the person who wrote it. A report that shows the image lets them see for themselves.

4. The position each capture was taken from

How far, what angle. This is the least glamorous item on the list and one of the most important, because it's what makes two readings comparable.

Without it you have a year of accurate numbers that can't be put side by side.

5. Findings, grouped so somebody can act

One route through the building produces findings across electrical, cooling, fire and life safety, and mechanical. Group them by area or by system, not by the order the robot happened to reach them.

Each finding should say what it is, where, and what would need to be checked. Severity if you can support it. Nothing that implies a repair decision the evidence doesn't support.

6. What could not be captured

The item almost every report leaves out.

If a checkpoint couldn't be reached, if the view was blocked, if a surface wouldn't give a clean read, that belongs in the report with the reason.

A report with no gaps in it is either a perfect building or an incomplete report, and auditors know which is more likely.

7. Who reviewed it

A person, named, who checked the findings before the report went out. Automated capture doesn't mean unreviewed output, and an auditor will ask who stands behind the document.

8. Something that proves it wasn't edited

Every record carries a check value. Change a temperature and the record stops matching itself and names the field that changed. Swap an image and the checkpoint flags the mismatch. Delete a record to clean up a bad month and the chain breaks across the gap.

The tool that runs the check works on your laptop, offline, without contacting us. Hand it to your auditor and they can verify the whole year themselves.

What it should not contain

• A compliance claim. No inspection report makes you compliant with a standard, and any vendor saying otherwise is overselling. A report contains condition evidence against a standard. That's a different sentence and the difference matters when someone is reading it carefully.
• Numbers without provenance. Every figure should trace to a capture, a checkpoint and a time.
• A gap that looks like a pass. If it wasn't captured, the report says so.

The test

Hand the report to somebody who wasn't there and ask them what happened in the mechanical room on the fourteenth.

If they can answer without calling you, the report works. If they can also check that the answer wasn't edited, it's evidence.