Define what the report counts
Occupancy is the number of vehicles or occupied spaces within a defined site or zone at a particular time. A count derived from lane movements depends on the starting count and which entry and exit events are included. A space-sensor installation may use a different source; identify the method configured at your Lexoh site.
Use your authorized account to open the relevant occupancy or statistics view. Check the selected system, zone, time and last update. Available reports, labels and filters depend on the installed version and your permissions. This guide explains how to interpret the data and check a discrepancy.
An access permission, a gate-opening command and a vehicle passage are different events. Confirm which event changes your count. A successful credential read alone does not prove that one vehicle entered or occupied a space.
Reconcile the count and capacity
For a movement-based count, start with a verified baseline: expected count = starting count + counted entries − counted exits + documented adjustments. Each term must cover the same physical area and time interval.
Worked example: a defined area starts with 20 vehicles. It records 15 counted entries and 8 counted exits, with no adjustments. The expected result is 27 vehicles. These numbers illustrate the method; they are not a Lexoh installation result.
Scroll the table horizontally. With a keyboard, focus the table and use the left and right arrow keys.
| Item | Value | What to verify |
|---|---|---|
| Starting count | 20 | The baseline applies to this area at the interval start. |
| Counted entries | +15 | Each included record represents one entry into the area. |
| Counted exits | −8 | Each included record represents one exit from the area. |
| Adjustments | 0 | No manual or automatic correction is included. |
| Expected count | 27 | 20 + 15 − 8 + 0. Compare with the recorded result. |
Occupancy percentage
With 27 occupied spaces and a defined capacity of 60 spaces, occupancy is 27 ÷ 60 × 100 = 45%. Confirm that the count and capacity describe the same area. If capacity is zero or unknown, this percentage cannot be calculated meaningfully.
Available capacity
Confirm how reserved, closed or unavailable spaces are handled before interpreting capacity minus occupancy as spaces available to an arriving driver. A configured capacity is not a live inspection of every space.
A count that differs from the site
Check missing or duplicate movements, open lanes, incorrect direction, event delays and baseline changes. Preserve the records and involve the responsible operator before correcting the count. A reset can hide the cause of the discrepancy.
Read occupancy over time
Read the axis labels, units and aggregation before interpreting a chart. A point can represent an instantaneous count, an interval average or a maximum. An hourly average can hide a short period at capacity. The top of a chart’s scale is not necessarily the configured site capacity.
Compare similar operating periods: the same zone, opening hours, weekdays and counting method. Record closures, events, outages or changes in available spaces. Missing data is a gap to investigate, not evidence that the site was empty.
Use the site’s agreed operating thresholds and overflow procedure. A percentage alone does not establish that expansion is needed or authorize turning away drivers. Review observed queues, unavailable spaces and local access requirements with the site manager.
Interpret visit duration
A completed visit duration is the elapsed time between its matched entry and exit. For a mean duration, divide the sum of the included visit durations by the number of those visits. Check the report’s inclusion rules for open visits, unmatched events and visits crossing the selected date range.
For example, completed visits of 30, 60 and 180 minutes have a mean of 90 minutes. That mean does not describe each visitor’s stay. Use the distribution or individual records, when available, to understand the mix.
Read duration-band boundaries carefully. A visit lasting exactly two hours must belong to the band defined by the report; do not assume whether a displayed “1–2 h” label includes its upper boundary. Use labels and totals rather than colour alone.
Visit duration does not determine the amount paid. Rates, permits, free periods, caps and transaction status can change the charge. Reconcile revenue using the relevant transaction records.
Keep visitors, visits and accounts distinct
A visit count measures sessions. A distinct-identifier count measures the different identifiers included in a period. Neither automatically equals the number of individual people: one person may use several credentials, and an account may represent a company.
If a customer breakdown is available, confirm the grouping key, selected period and included records. An empty customer panel can result from filters, permissions or records that are not linked to an account. Check the underlying visits before interpreting it as no activity.
Frequent visits do not, by themselves, prove loyalty or high revenue. Use only the customer detail needed for the operational question and keep shared reports within your organization’s access and retention rules.
Compare like-for-like periods
A report for a longer period is only as complete as its retained data. Check the dates actually available; this guide does not promise a fixed number of years of history.
- Record the selected site or zone and the start and end timestamps, including the time zone.
- Check whether a preset means a rolling period or a calendar period. “Last 24 hours” and “yesterday” can cover different visits.
- Identify how visits crossing the interval boundary and ongoing visits enter the report. Keep that rule consistent between comparisons.
- Check the last update and any known event-delivery gap. Recheck filters when opening a detailed view.
- Record changes in capacity, lane configuration or counting rules alongside the result.
Use evidence before changing operations
Investigate repeated busy periods with the manager responsible for the site. Compare counts with observations of queues, actual space availability, arrival and departure patterns, and service requirements. This provides context for staffing, maintenance windows or an overflow plan.
Evaluate any pricing change with the applicable tariff and transaction data. Occupancy and average duration alone cannot calculate revenue or show that a change caused an improvement. Record other changes, such as an event or a closure, when comparing periods.
For unresolved count differences, provide the system, zone, interval, expected count, displayed count and a few relevant event references. Include the last known correct baseline and any recent lane or capacity change.
Keep a repeatable review record
After a change to lanes, detection equipment or counting rules, repeat the acceptance checks with the installer or administrator. Keep the procedure aligned with the equipment and software actually in use.
- Confirm the site, counting source, capacity definition and responsible operator.
- Check freshness and compare a sample of entry and exit records with the reported movement.
- Investigate an unexplained difference before changing the baseline or configuration.
- Document any authorized correction, its reason, time and effect.
- Record the result and unresolved follow-up for the next operator.