Car park reports: what parking history and revenue should show

Car park managers rarely stand at the lane. What they know about the car park comes from the parking history and statistics, so any field missing from the report is a part of the operation they cannot control.

This post lists what parking history, traffic statistics and revenue statistics need to contain, based on the functions of the Sol26 Parking central application.

Parking history is the source data

Every statistic is built from the record of each visit. When records are complete, a manager can trace a figure on a chart back to the exact vehicle visit.

• Vehicle plate
• Front image of the vehicle and image of the driver on entry
• Driver name
• Entry time and exit time
• Visit status: in or out
• Approver, for visits handled manually

Search and export

The central application lets managers search by name or plate and download the list. Downloaded lists are used for periodic reconciliation or sent to other departments when a specific vehicle needs checking.

Each visit has a detail view with images, plate, time and driver. When there is a complaint about a visit, the manager opens that exact visit instead of asking the guard on duty.

Tracking manually handled visits

Manually handled visits need the closest review, because a person rather than the system made the decision. Sol26 Parking alerts when a vehicle leaves through manual handling and records the approver for each visit.

• Visits with mismatched entry and exit plates that a guard allowed out
• Visits where exit was rejected
• Visits where the vehicle was not recorded inside at check-out
• Visits with a duplicate plate on entry

Traffic statistics by period

Traffic statistics are viewed by period and displayed as charts. Managers choose the period to see vehicle flow, and combine it with the overcapacity alert to assess the car park's capacity.

The gate software manages vehicle counts and shows the entry and exit status. The number of vehicles currently inside is therefore always available without adding and subtracting from reports.

Revenue statistics

For car parks that charge fees, revenue is reported by period. The fee for each visit is shown on exit, so every payment is tied to a visit with a plate, time and images.

Visitor cars pay the guard directly. Revenue statistics by period are the basis for reconciling the cash a guard hands in after each shift against the recorded visits.

Reports across several stations

The central application supports managing several stations at once. History, traffic and revenue for all stations are viewed in one application instead of being compiled by hand from each guard house.

In the same application, administrators add, edit, activate or deactivate guard accounts. Because each guard has an individual account, the approver field in the history always points to the person who handled the visit at each station.

Frequently asked questions

Does a free car park need revenue statistics?

It is not required. Revenue statistics apply to car parks that charge fees, while parking history and traffic statistics are useful for any car park.

Can parking history be downloaded?

Yes. The central application lets you search by name or plate and download the list.

How can I tell which visits a guard decided?

The parking history records the approver for each visit, and the system alerts on vehicles that left through manual handling.