The 30-day retention default exists because it was the capacity planning answer for recording systems in the late 2000s. Hard drives were expensive; 30 days filled them. Modern NVR storage is orders of magnitude cheaper, and network-attached storage or cloud archival can extend retention indefinitely. Yet most commercial buildings are still running 30-day retention policies set during the original system design, never revisited.

The problem surfaces when an incident is reported after day 31. An employee files a workers’ compensation claim from an event that occurred 45 days ago. A vehicle break-in in the parking deck was noticed last week but happened six weeks prior. The police ask for footage from an event that preceded the current retention window. In each case, the answer is: the footage doesn’t exist. The policy that was “good enough” has now cost the building.

What the codes say — and don’t say

Most building codes and life-safety standards don’t specify video retention requirements directly. The IBC, NFPA, and local fire codes regulate the camera system’s functional requirements but leave retention duration to the owner and AHJ. The exceptions:

  • Federally regulated facilities. Banks (FDIC-regulated institutions), licensed cannabis facilities, and federally licensed firearms dealers each face retention mandates from their regulatory bodies — typically 30–90 days minimum depending on the regulation.
  • Healthcare facilities. CMS Conditions of Participation don’t specify retention directly, but Joint Commission standards for security environment management imply that footage relevant to incidents must be preserved. The practical standard in healthcare is 30 days minimum, 90 days for high-risk areas.
  • Local ordinances. Some municipalities that require camera registration for large commercial properties specify minimum retention durations (typically 30 days) in the ordinance. Check local requirements for your market.

The absence of a universal retention mandate means the retention decision is primarily driven by three factors: incident response needs, insurance requirements, and storage budget. The building owner owns the risk of that decision.

What your insurance carrier actually wants

Insurance carriers don’t universally publish camera retention requirements in policy language. The retention expectation surfaces in claims. When a claim is filed and the footage that would support or refute it doesn’t exist, the carrier’s assessment shifts — and not in the building owner’s favor.

In practice, commercial property and general liability carriers expect:

  • Slip-and-fall and premises liability claims: Most claims are reported within 30 days, but a meaningful fraction — especially those involving delayed-onset injuries or late-reported incidents — are filed 30–90 days after the event. Coverage of exterior entrances, parking areas, and common-use spaces at 90 days captures the bulk of this population.
  • Workers’ compensation claims: Workers’ comp claims are sometimes filed months after the injury. A 90-day retention policy is the common recommendation from commercial insurance brokers because it covers the majority of late-reported incidents.
  • Crime and theft claims: Insurance carriers investigating theft claims want footage of the access point and the area of loss. For high-value storage areas or distribution centers, 30 days may not cover the investigation window.
  • Large commercial and industrial clients: Some carriers for large commercial real estate and manufacturing explicitly require 30-day minimum retention as a policy condition. Review your policy language; if retention is specified, it’s a binding requirement.
Ask before you renew: Many commercial property policies have camera and recording requirements buried in the security schedule or loss-control recommendations. Pull those documents before next renewal and confirm your current retention policy meets or exceeds what the policy expects. A mismatch between your actual configuration and the policy language can affect claims outcomes.

The storage math at 30, 60, 90, and 365 days

Camera storage requirements depend on three variables: number of cameras, resolution and frame rate, and encoding efficiency. A rough framework for H.265 (HEVC) encoded IP cameras at common settings:

Configuration Per-camera / day 32-camera / 30 days 32-camera / 90 days 32-camera / 365 days
2MP (1080p), continuous, 15 fps, H.265 ~25 GB ~24 TB ~72 TB ~292 TB
4MP, continuous, 15 fps, H.265 ~40 GB ~38 TB ~115 TB ~467 TB
2MP, motion-triggered (est. 6 hrs/day active) ~6 GB ~6 TB ~18 TB ~70 TB

These are estimates — actual consumption varies with scene complexity and encoder settings. The important pattern: moving from 30 to 90 days triples storage. At 2MP continuous for a 32-camera system, the jump from 24 TB to 72 TB is the difference between a single NVR and a multi-bay storage expansion or a cloud tier. The budget question is whether that delta is more or less than the cost of an unrecorded incident — and that volume of camera traffic should live on its own VLAN regardless of where the disk physically sits.

Analytics-led video — extending retention without buying disk

The most effective approach to extending retention without linearly scaling storage is using on-camera analytics or NVR video analytics to reduce recording to event-triggered clips rather than continuous streams. Most modern IP camera platforms — Axis, Hanwha, Verkada, Milestone-partnered cameras — support on-camera detection analytics (motion, line-crossing, loitering, object classification) that trigger recording only when activity is detected.

The reduction is substantial. A parking lot camera on continuous recording at 2MP captures ~25 GB/day. The same camera with motion-and-object-triggered recording calibrated to exclude vegetation and small animals captures 3–8 GB/day. At that rate, 365-day retention for 32 cameras requires roughly 35–90 TB — the same storage budget that supported 30-day continuous recording.

The caveat: analytic-triggered recording is only as good as the analytics. A camera configured to record only when a person is detected will miss a vehicle break-in that occurs before a person exits the vehicle. Coverage requirements analysis — mapping which cameras need what detection type — is the design step that makes analytics-driven retention practical.

Retention by building type — a working framework

As a practical starting point for Atlanta and Southeast commercial buildings:

  • Class A and B office, multi-tenant: 60-day minimum across common areas, entry points, and parking. 90 days for elevator lobbies and loading dock areas.
  • Retail and mixed-use: 30 days for interior sales floor; 60–90 days for parking areas and exterior access points. Confirm franchise or chain lease requirements — some tenant agreements specify retention.
  • Healthcare (outpatient / MOB): 90 days for all interior common areas, medication storage, and patient-access corridors. 30 days for exterior and parking is generally sufficient.
  • Industrial / distribution / warehouse: 90 days for dock and freight access. 30 days for interior production floor where incident frequency is lower. Verify that cameras in federally funded or regulated facilities meet NDAA Section 889 requirements — retention policy discussions are a good time to audit camera brand compliance simultaneously.
  • Multifamily residential (commercial owner): 30–60 days for common areas and entry/exit. Some states have tenant notification requirements for common-area recording that affect placement more than retention duration.

Bottom line

Video retention policy is a risk management decision, not a default setting. The combination of your insurance policy language, the incident reporting timeline for your building type, and the regulatory requirements for your use case should drive the retention floor. Storage cost is not the primary constraint it was in 2010; the relevant math is the cost of a retention gap on a liability claim versus the cost of 2–3x more disk or a cloud archive tier. Most commercial buildings should be operating at 60–90 days, not 30 — and most aren’t.

Reassessing your camera system and retention policy?

We design CCTV systems with the retention window as a starting requirement, not an afterthought — including analytics configuration that extends effective retention without linearly scaling storage. Serving Atlanta and the Southeast.