← Back to journal

tech-saas / JAY CLOUD JOURNAL

Data Center Presence Gap: Why Badge Logs Fail Life Safety and SOC 2 Audits

In facilities running at AI-infrastructure scale, knowing who badged in is not the same as knowing who is on-site — and that gap carries real compliance and safety exposure.

Poksundo Team ·

Data Center Presence Gap: Why Badge Logs Fail Life Safety and SOC 2 Audits

In facilities running at AI-infrastructure scale, knowing who badged in is not the same as knowing who is on-site — and that gap carries real compliance and safety exposure.

Key Takeaways

  • Access control logs record entry events. They do not confirm who is still present, still authorized, or still accounted for — three questions that matter when an emergency or a SOC 2 audit arrives.
  • OSHA 29 CFR 1910.38(c)(4) requires employers to account for all personnel after evacuation. In a multi-contractor data center, a badge log alone cannot produce that answer in real time.
  • A Workforce Presence Validation Layer connects physical access events to live workforce records — making on-site presence provable, auditable, and actionable.

AI Infrastructure Scale Changed What "On-Site" Actually Means

North American data center capacity hit 8,155 MW in the first half of 2025 — a 43% year-over-year increase, according to CBRE. That number reflects more than growth.

Modern AI infrastructure campuses routinely exceed one to three million square feet. They operate with a workforce composition no single HR or access control system was designed to manage: general contractors, specialty trades, design-build teams, and vendor personnel — all on-site simultaneously, across multiple secure zones.

According to data from the Associated General Contractors, more than 80% of construction firms are struggling to fill the skilled-trades positions these campuses demand. That pressure means more contractors, more rotations, and more temporary credentialing.

It also means more operational surface area where the record of who badged in quietly diverges from who is actually present.

The Three Questions a Badge Log Cannot Answer

Access control does exactly what it was built to do: verify a credential at an entry point and log the event. The problem is what facility managers often assume it does — confirm that someone is still on-site, still authorized, still accounted for.

Those are three different questions. A badge log answers none of them reliably.

Someone can badge in and then exit through a fire door. A contractor can hold valid credentials for one zone and be working in another. A vendor technician can be on-site during a shift that closed two hours ago in the HCM. In each case, the access log shows an entry event — and nothing about what happened after.

"If time isn't validated at the point of entry, it isn't reliable."

This is the presence gap. It lives between the moment of badge swipe and the operational reality on the floor, and it grows wider as facility complexity increases.

When the Presence Gap Becomes a Life Safety Event

In September 2025, a lithium-ion battery fire at a South Korean government-run data center forced its closure and disrupted 647 public systems — including emergency vehicle tracking across two cities, as reported by The Independent and cited by UL Solutions.

That is what fire and emergency events look like inside critical infrastructure at scale.

OSHA 29 CFR 1910.38 requires employers with 10 or more employees to maintain a written Emergency Action Plan that includes documented procedures to account for all employees after evacuation [29 CFR 1910.38(c)(4)]. That is not an aspirational standard. It is the compliance floor.

"You can't ensure safety without knowing who is actually on-site."

In a multi-employer data center environment, executing a reliable post-evacuation headcount requires knowing which contractors are on campus that day, which zones they were credentialed for, and whether the count from the access log matches the count standing at the muster point.

Badge systems and HCMs, operating independently, cannot produce that answer in real time.

SOC 2 Demands Proof, Not Just Logs

SOC 2 Common Criterion CC6.4 requires restricting physical access to facilities and sensitive locations to authorized personnel only, with audit trail evidence sufficient for Type II examination.

An access log demonstrates that a credential was used at a specific door at a specific time. It does not demonstrate that the person holding that credential was authorized for that zone on that shift, or that their presence was validated against a current workforce record.

For a SOC 2 Type II examination, that distinction surfaces quickly in high-turnover, multi-contractor environments — where the documentation gap between "credential was valid" and "presence was verified" is hardest to close.

What a Workforce Presence Validation Layer Does at the Point of Entry

jay cloud is not an access control replacement. It operates as a real-time validation layer between physical access events and workforce systems — connecting what the badge log recorded to what the HCM, scheduling system, and credentialing record say should be true.

Three things happen at the moment of entry that do not happen today:

Time is validated against scheduled shift and role authorization. If a contractor badges in outside their credentialed window, that discrepancy surfaces immediately — not during a payroll audit three weeks later.

Zone access is validated against current workforce records. A valid badge for Building A does not confirm authorization for the high-security compute floor in Building C. jay cloud connects those two data sets in real time.

On-site presence becomes provable and auditable. When an emergency occurs, the muster point works from a validated, current record of who is on-site — the record that OSHA 1910.38(c)(4) requires and that SOC 2 CC6.4 demands be audit-ready.

jay cloud integrates with the workforce systems operators are already running — SAP SuccessFactors, Workday, HiBob — and works alongside existing physical access infrastructure, not in place of it.

"Payroll accuracy is important — life safety is critical."

The Question Every Data Center Operations Leader Should Be Asking

AI infrastructure demand is not slowing. Campus scale is not shrinking. The workforce complexity that comes with both will continue to outpace what any single access control or IT monitoring system was designed to manage.

The question is not whether the presence gap exists. In a facility of this scale, it does. The question is whether it is visible, manageable, and defensible under audit — or whether it is waiting to surface during an emergency or a SOC 2 examination.

See How It Works

More from the journal