What ParkWayz gives you
-
Every decision is evidenced
Each detection stores the plate, camera, direction, vehicle type, snapshot, access result and a confidence score.
-
Occupancy counted, not estimated
Slots are drawn on a floor layout and carry their own status, so occupancy is per slot rather than a running total.
-
Overstays are actionable
Vehicles past their allowed duration are flagged, can be blocked from exit, and released by an operator when resolved.
-
Reports your auditors accept
Event log, overstayer, vehicle registry and zone utilisation reports export to PDF, Excel and Word.
How it works
Detect, decide, log, act
Four steps run on every vehicle that reaches a gate. Nothing depends on a human watching a screen.
-
Detect
An LPR camera at the entry or exit lane reads the plate and captures a snapshot. The reading carries a confidence score, and a threshold you set decides what counts as a read.
-
Decide
The plate is matched against the vehicle registry. Whitelisted vehicles are allowed, blacklisted vehicles are denied, and anything not on file is recorded as unknown.
-
Log
The event is written with timestamp, camera, direction, vehicle type, snapshot, access result and confidence — filterable and paginated, and kept for as long as your retention setting says.
-
Act
Occupancy updates against the slot the vehicle is assigned to. Duration is tracked, overstays are flagged, and an operator can release a blocked vehicle for exit.
Plain about "live": the ParkWayz interface refreshes on a polling interval you configure — dashboards and event lists stay current without anyone reloading the page.
The platform
Six pages, one system
Start wherever your job starts — the gate, the car park, the registry or the audit trail.
Next step
See it read your plates
A short session on your own site: your gates, your vehicle list, your zones. We will show the detection flow end to end and answer the deployment questions your IT team will ask.