Understand departures and completed sessions

Define what the exit report measures

Lexoh exit statistics summarize recorded departure activity for an operator’s reporting scope. They help identify busy departure periods and examine sessions associated with exits. The results depend on the data received, the counting rules, filters and permissions.

Confirm what creates an exit in your installation: a detected passage, an event, a completed session or another configured record. Credential validation, a barrier command and a vehicle physically leaving are distinct steps. A command or timestamp alone does not establish every part of that sequence.

Keep exit volume, completed-session duration, occupancy and payment results separate. Each answers a different question and may use a different set of records.

Read totals, today and peaks separately

Total exits

Check the selected devices, directions and period, and whether unmatched exit records are counted. Do not assume the total contains only sessions with both an entry and an exit. Confirm how repeated events and manually corrected records are handled.

Today’s exits

Verify the day’s exact start, end and time zone. A today card may not follow the same period as the charts. Check its behavior after changing filters, and distinguish today since midnight from a rolling 24-hour period.

Peak departure hour

Determine whether the metric selects a single dated hour or an hour of day combined across several dates. Check ties and empty results. A default midnight value does not establish a measured midnight peak.

Update state

Check when the figures were refreshed and whether devices have supplied their records. A chart can lag behind an actual departure. If loading fails, retain the error and request time rather than treating the result as zero exits.

Compare the same hourly measure

Read the time axis, unit and grouping before comparing periods. A total for several days differs from a daily average for the same hour. A profile based on complete days also differs from one containing closures, partial days or missing records.

For an illustrative 17:00–18:00 interval, Day A has 12 recorded exits and Day B has 28. The combined total is 40; the average across those two observed days is 20; the largest observed hourly count is 28. These are different measures, not alternative labels for one number.

Confirm the denominator used for an average. An observed open interval with no exits can count as zero; an interval with missing data is unknown. Check clock changes and interval lengths before comparing local-hour groups. A connecting curve does not provide additional measurements between plotted points.

Use departure patterns to investigate bottlenecks

Compare similar operating days and events. Use the site’s observed departures rather than generic office, hospital or shopping-centre peak times. The hour with the highest throughput does not necessarily have the longest wait: a blocked lane can show few departures while a queue grows.

Record queue length, wait time, payment or credential problems and available lanes alongside the exit count. Use those observations to decide where assistance, clearer instructions or an equipment investigation is needed.

Coordinate planned maintenance with the site’s operating procedure and available exit arrangements. Barrier motion, detection and safety settings belong to the approved equipment configuration; do not change opening or closing speeds solely to improve a chart. Confirm any lane or payment-process change before directing visitors to use it.

Check matched sessions before averaging duration

Inspect the available recent-exit records and open the detailed session where supported. Compare the stable reference, entry and exit devices, associated credential, timestamps and time zone. A recent-row list may be only a sample of the report’s population.

The following example uses matched sessions on the same time basis, without a clock change. It shows why an exit-date report can include arrivals from an earlier day. These are illustrative records, not customer data.

Unmatched, missing or unusual times

A missing entry prevents a verified entry-to-exit duration. A missing exit does not prove that a vehicle remains inside. Check delayed records, matching, time zones and corrections before interpreting a blank, negative or unusually long duration. Do not replace unknown durations with zero.

What duration can explain

A completed-session average describes the sessions included, not visits still open or every visitor. Duration alone does not prove whether someone was working, shopping or staying overnight. It also differs from billable duration, which depends on applicable pricing and grace rules.

Make the reporting population reproducible

1. Define the question: departures during a period, duration of sessions that ended in it, or movement through a particular exit.
2. Select the available site, devices and date range. Record the exact bounds and time zone. A calendar month is not always 30 days, and selectable dates do not establish retained history.
3. Confirm the timestamp used by the filter. A session may enter before the range and exit within it. Selecting by arrival date would produce a different population.
4. Apply the filters, wait for completion and check each card, chart and recent-record list. Verify boundary records and the treatment of unmatched exits.
5. Compare equivalent operating hours and day types. Note closures, device outages, incomplete days and changes to recording or session-matching rules.
6. If exporting, verify the actual format, fields and scope: selected rows, recent rows or all matching records. Compare counts and known references, then preserve the original file with the settings and generation time.

Reconcile departures without overstating them

More exits than entries can be expected

With consistent complete records, an illustrative site starting with 40 vehicles, receiving 15 entries and recording 35 exits ends with 20 vehicles: 40 + 15 − 35 = 20. The excess of exits over entries is not, by itself, a recording fault. Starting occupancy and earlier arrivals matter.

Equal counts do not prove accuracy

Missing or duplicated records can offset one another. Reconcile known sessions and device coverage instead of treating equal entry and exit totals as a complete data-quality test. Counts alone also do not reveal the highest occupancy reached during the period.

Departures per available space is a defined ratio

If a report deliberately uses 120 recorded departures divided by 60 available spaces for one day, the result is 2 departures per space for that day. Label the numerator, capacity basis and period. This ratio does not establish 200% occupancy, lane performance, profitability or a general facility-efficiency score.

Departures are not payment collections

A visitor may pay before departure, use a permit or have another billing arrangement. Use the relevant transaction and revenue records to verify amounts and timing. A departure record alone does not establish that money was collected or settled.

Investigate gaps and preserve the evidence

1. When departures appear to stop, first distinguish a reporting delay or device-communication issue from an actual exit-lane problem. Follow the site’s response procedure for a physical obstruction or equipment fault.
2. Compare a few known departures with the underlying records. Confirm device direction, timestamp meaning and any missing or repeated events.
3. Use an approved test or existing known session to verify recording. Record the expected and observed results; do not alter operational records merely to make a chart balance.
4. Keep the report scope, data gaps and chosen measure with the operational decision. Plan a follow-up measurement using the same definition.
5. Share aggregate findings when personal details are unnecessary. For support, provide only the session references and contextual evidence needed through the approved channel, and follow the site’s retention process.