Start with the measure and its scope
A total adds the included values. An arithmetic mean, often called an average, divides a total by a defined number of observations, such as days, visits or transactions. The word “average” alone does not tell you which calculation a report uses.
In your Lexoh statistics view, confirm the selected site, date range, time zone, unit and grouping interval. Check the installed version’s report definition and your permissions before relying on a specific control or export option.
For each result, record what is counted, what is excluded and what the denominator represents. This makes a daily, weekly or monthly comparison reproducible.
Read the chart’s units and aggregation
Read series names and axis labels before comparing line heights. Entry counts and transaction amounts have different units. Their positions on one chart do not establish a ratio, and separate axis scales can make unrelated movements look similar.
Determine whether each point is a period total, an average or another aggregation. A weekly total is different from the average daily count within that week. Use the underlying values to confirm the meaning.
Check gaps, partial periods and the last update. A missing point does not mean zero activity. Use visible labels and values rather than colour alone; use a detailed table or record view when the graph cannot answer the question.
Keep the measures distinct
Entries and exits
Confirm which recorded events are included. Credential reads, gate commands and vehicle passages are different events. Entries and exits within one period need not match when visits cross its boundaries. Their difference alone does not measure queues or congestion.
Transaction amount
Check the currency, selected transaction states, date basis, taxes and treatment of refunds or cancellations. An amount grouped by transaction date may relate to a visit that began in another period. Keep the same definition when reconciling two reports.
Amount per entry
Divide the included transaction amount by the included entry count only when the scope is suitable for that comparison. Label the result “amount per entry”; it is not automatically an average payment per customer or per completed visit.
Average per day
Divide the period total by the number of days defined for that measure. State whether the denominator includes all calendar days or only operating days. Missing data should remain identified rather than silently becoming zero.
Combine ratios using the underlying totals
Illustrative example: the two days below have different numbers of entries. All amounts use the same currency and inclusion rules. These values explain the calculation; they are not results from a Lexoh installation.
| Period | Entries | Amount (CAD) |
|---|---|---|
| Day 1 | 10 | 100 |
| Day 2 | 90 | 450 |
| Combined | 100 | 550 |
The ratio for each day
Day 1: CAD 100 ÷ 10 = CAD 10 per entry. Day 2: CAD 450 ÷ 90 = CAD 5 per entry.
The ratio for both days
Combine the totals: CAD 550 ÷ 100 = CAD 5.50 per entry. Averaging the two daily ratios gives CAD 7.50, which gives both days equal weight despite their different entry counts.
Choose the denominator for the question
An equal-weight average of daily ratios can answer a different question, but it must be labelled that way. To calculate the combined amount per entry, use combined amount divided by combined entries. If there are no included entries, this ratio is undefined; report the amount and zero count separately.
Compare equivalent periods
A retained history and a selected reporting interval are separate things. Use the dates actually available in your installation; a day, week or month view does not establish a guaranteed retention period.
- Record the site, start and end timestamps, time zone and report filters.
- Confirm how a day, week or month is defined. Check the week start and whether the first or last interval is incomplete.
- Use the same grouping and denominator on both sides of the comparison. A 31-day total is not directly equivalent to a 28-day total.
- Identify closures, holidays, changes in operating hours and gaps in data delivery. Explain how excluded days are treated.
- Recheck scope and totals after opening a detailed view or using an available export.
Calculate change, then investigate its cause
For a positive previous value, percentage change = (current value − previous value) ÷ previous value × 100. A count rising from 100 to 120 is an increase of 20, or 20%. If the previous value is zero, this percentage is undefined; describe the absolute change instead.
A rising ratio does not prove a pricing strategy worked. Changes in the mix of visits, permits, transactions or opening hours can change the result. Compare the relevant records and note other changes during the period.
If counts or amounts differ from expectations, first check the filters, period boundaries, transaction states and latest received data. Then inspect a few underlying records. Preserve the report settings and examples so another operator can reproduce the finding.
Use a documented comparison baseline
Choose a baseline that matches the site’s purpose: a comparable operating period, an agreed target or a documented external study. State its date, scope, unit and method. A hospital, commuter lot and event site can have different traffic patterns and operating objectives.
Entry count per space measures movement over a period, not simultaneous occupancy. Revenue per space does not establish profitability without the relevant costs and accounting definitions. Choose the measure that answers the actual operational question.
Agree on any investigation threshold with the responsible manager and record why it is useful for the site. There is no universal growth rate, entry/exit ratio or amount-per-entry target established by this guide.
Keep a calculation and review record
Use the available reporting and export functions documented for your installation. When sharing a report, include enough context to reproduce the calculation and only the record details needed for the question.
- Name the measure and record its numerator, denominator, unit, filters and period.
- Check one total and one calculated ratio against the underlying records.
- Separate missing data, genuine zero activity and an undefined calculation.
- Record relevant site changes, the finding and the person responsible for follow-up.
- After a software or report change, reconfirm the definitions before comparing with earlier results.