Operator console
Run the whole operation
from one workspace.
The console is where operators and cities map their streets, set the rules, manage their teams and follow every session, fine and appeal, with the numbers that show how it all performs.
Operator console
The bigger picture, and what needs you now.
The console opens on the last 30 days and a short list of what is waiting for you — appeals, unanswered drivers, failed payments. Every number links to the records behind it.
- Trends first, filtered by country and operator
- Open items ranked by urgency
- A dedicated page for every driver, zone and fine
Wednesday 23 September · Manchester · United Kingdom
Sessions started per day
Open items: 3, most urgent first
Simplified previews of the IPark console and mobile app. Vehicles, zones and activity are demo data.
Inside the operator console
Your whole operation.
In one console.
From the first zone to the last appeal, one workspace connects the decisions made in the office with the apps used on the street.
Draw the streets you manage, attach a tariff and set the maximum stay. Drivers see the rules for the exact place they parked.
See the connected platformGive every administrator and inspector a role and a geographic scope, so each person works only where they are responsible.
See the connected platformFollow an inspection through to a fine and an appeal. Review the evidence and record the decision in the same workspace.
See the connected platformConfigure a parking zone
Every change lands where it matters.
- Operator
- Manchester City Council
- Zone
- Portland Crescent
- Tariff
- GBP 2.00 / hour
- Maximum stay
- 4 hours
Try this workflow with illustrative data.
Interactive preview · changes stay in your browser
In the console
Every decision,
connected to the street.
Zones, streets and tariffs
Draw zones and streets on the map, attach tariffs one by one or from a file, and set maximum stays.
Country rules, set once
Currency, VAT, grace periods and payment providers are set per country and apply wherever they should.
Teams and access
Give every administrator and inspector a role and a geographic scope, so each person works where they are responsible.
Fines and appeals
Follow an inspection to a fine and an appeal, review the evidence and record the decision.
Verified owners
Review registration certificates in a queue next to the plate, and approve them or say what is missing.
Open items first
Appeals, unanswered drivers and failed payments are ranked by urgency on the overview.
Reports and trends
Sessions, revenue and inspections over time, filtered by country and operator, with every number linked to its records.
An audit trail
Approvals, rejections and revocations are kept in the audit log, with who made them and when.
Questions & answers
Common questions
about this part of IPark.
Getting to know IPark? Start here.
All questionsCan we set our own zones, tariffs and rules?
Yes. Operators draw zones and streets, attach tariffs one by one or by uploading a tariff file, and set maximum stays. Country rules such as grace periods, VAT and the default currency are configured once and apply wherever they should.
Does IPark work across several cities or countries?
Yes. One platform can serve several countries, operators and zones, each with its own currency, tax and parking rules. Roles and geographic scopes keep every team member focused on the areas they manage.
How does a driver prove they own a car?
From the car in their garage, they send a photo of the registration certificate with its number and the keeper’s name. Operator staff check it in the console and approve it or explain what is missing. Each plate can have only one verified owner.
Can drivers dispute a fine?
Yes. Drivers can dispute a fine from the app. The appeal reaches the operator console with the inspection evidence and the session record attached, so staff can review it and record a decision in one place.
Make your parking network work together.
See the platform with your zones, teams and operating requirements in mind.