Every Lock. Every Camera.
Every cell.
Pod 3B, Cell 47 — what's the lock test result? What's the camera feed status? What's the intercom test? POD documents every security device from installation through integration testing.
Why Correctional Construction Reporting Fails
BOP and state DOC auditors check security device testing cell by cell. Here's where your daily report falls short.
Detention hardware testing requires per-device documentation
Every detention lock, every strike plate, every food pass, every sally port interlock requires individual test documentation. BOP and state DOC auditors check by cell number. Your daily report lists ‘hardware installation in Wing B’ with no cell-level detail.
Camera and intercom integration testing falls between trades
Security cameras, intercom stations, and duress alarms are installed by the electrical sub but tested by the security integrator. Neither trade’s daily report captures the integration test results that the BOP requires per device.
Fire life safety device testing not linked to housing unit
Smoke detectors, sprinkler heads, and exit devices in a correctional facility require testing documentation per cell and per pod. Your fire alarm contractor’s daily report says ‘47 devices tested today’ — but doesn’t say which cells or pods.
Security zone transition points never documented in daily reports
Sally ports, man-traps, and vehicle sallyports have multi-device interlocking sequences that must be tested in specific order. The integration sequence documentation lives in the security consultant’s punch list — not in any daily construction report.
How POD Documents Every Security Zone
From perimeter fence to individual cell — voice-first reporting built for correctional construction.
Voice-capture lock testing per cell per pod
Walk the housing unit and speak cell number, lock model, test result, and strike plate verification. POD builds the BOP-compliant device testing register from daily voice reports.
Camera and intercom integration tracked across trades
Both the electrical sub and security integrator report through POD. Integration test results are linked to the device, the cell, and the zone — regardless of which trade performed the test.
Fire life safety testing linked to housing units
Every smoke detector, sprinkler head, and exit device documented with its cell/pod/zone location. POD aggregates fire life safety testing by housing unit for BOP inspection readiness.
Sally port interlock sequence documentation
Multi-device interlock sequences at every security transition point documented step-by-step. POD tracks which interlocks have been tested, which sequences verified, and which control room integrations completed.
Concentric Security Zones — Every Device Tracked
POD documents security devices from perimeter fence to individual cell, zone by zone.
Detention Construction Metrics — From Lock to Lockdown
Inspection bottleneck costs and training-to-quality correlation for security-critical detention trades.
Inspection Bottleneck Cost
PODDelay cost by inspection
Impact
Training → Quality
PODTraining vs pass rate
Avg pass rate
Built for Correctional Construction
Security Device Registry
Per-cell testing documentation for detention locks, strike plates, food passes, and emergency overrides — BOP audit-ready
Fire Life Safety Dashboard
Smoke detector, sprinkler, and exit device testing tracked by cell, pod, and building with AHJ inspection readiness scoring
Control Room Integration Log
Sally port interlock sequences, camera feed verification, intercom tests, and duress alarm functionality documented per zone
The POD Difference
POD captures component-level test documentation as part of the daily reporting flow, so every lock, camera, and cell has its own record instead of a one-line summary.
Frequently Asked Questions
Document Every Lock, Camera, and Intercom — Per Cell
See how POD builds BOP-compliant security device registers from 5-minute voice reports — or join the waitlist for early access.
Last updated: April 2026