Keep aggregated occupancy lines separate from independent counting presets

Decide whether crossings belong in one aggregate or separate presets before distributing occupancy statistics.

Source facts

Verkada Occupancy Trends estimates people or vehicle movement across configured virtual lines. Its guidance favors clear one-directional paths, limited occlusion, and adequate visibility on both sides. Multiple lines within the same configuration contribute to aggregated data. Custom line presets maintain separate data from one another. Results can be reviewed by date and interval and exported as CSV. The supported-camera list is model-specific, so a camera’s ability to display video does not establish availability of this analytics feature.

Source: Verkada Help — Occupancy Trends.

Applicability

Applies to supported Verkada cameras using Occupancy Trends. These are analytics estimates for operational review; this article does not establish a certified life-safety headcount or an evacuation accounting system.

DSE recommendation

DSE recommends naming every line and preset according to the business question. Combine lines only when their counts are intended to contribute to one measure; use separate presets for comparisons that must remain independent. Map entrances that can bypass the selected cameras and record known counting limitations. Have the operations owner approve the meaning of in and out before distributing a dashboard. Keep manual observation samples with the calibration record.

Verification

Walk a planned sequence through each crossing direction, including overlapping people and a bypass path where safe. Compare the resulting aggregated and preset-specific counts with observations over the same time interval. Document the difference and accepted limitations; do not turn a successful single-person crossing into a universal accuracy claim.

Official reference

Verkada Help — Occupancy Trends. Reviewed October 15, 2026.