Parking is the part everyone forgets until the guest is already at the barrier. The Car Pass turns your bays into real, bookable inventory and attaches to whichever pass the visitor already holds — Meeting, Visitor, Residential or Event. Approve the visit, approve the car with it.
The Car Pass is the only pass designed to travel with another one. Whoever you are issuing a pass to, the vehicle is approved in the same step, by the same approver, against the same record.
Car PassPlate, zone, bay and window — carried inside the pass they already hold
What breaks today
Across the Gulf, parking is the bottleneck nobody owns.
Most towers have bays. Very few have a system that can say which of them is free right now. That gap is where the guest experience goes wrong — and where capacity you already paid for goes unused.
The problem
There is parking. There is no parking system.
The tower has bays. What it does not have is a way to allocate them. Allocation is a phone call to the facilities office, a name on a clipboard and a traffic cone. Nobody can say what is free right now, so nobody can promise anything to a visitor.
With MeetPass
Bays, zones and rules live in the admin panel as real inventory. A slot is either free, held or occupied — and the answer is the same for the host, the guard and the guest.
The problem
The bays sit empty all day.
Residents and staff drive out in the morning. Their bays stay empty until the evening while visitors circle the block looking for somewhere to leave the car. The capacity exists; nothing releases it.
With MeetPass
Configure a daytime pool: bays that are free during set hours are released to visitors automatically, and returned to their owner before they come back.
The problem
Parking is booked separately from the visit — or not at all.
The meeting is approved, the visitor pass is issued, and nobody thought about the car. The guest reaches the barrier with a valid pass for the building and nothing for the vehicle.
With MeetPass
The Car Pass attaches to the pass the person already holds — Meeting, Visitor, Residential or Event. Approve the visit, approve the car with it.
The problem
The VIP arrives and there is nowhere to put the car.
A delegation you have prepared for over weeks arrives at the barrier and is waved towards the street. It is the first thing they experience of your organisation, and there is no recovering it.
With MeetPass
Reserve a named bay in advance and hold it. The bay cannot be taken by anyone else, and the barrier already knows the plate before the car turns in.
The problem
The guard is the parking system.
A plate written on a sheet, a bay remembered from a conversation, no record of who came in or when they left. When someone parks in the wrong bay for six hours, nothing catches it.
With MeetPass
The plate and the pass are validated at the barrier, the bay is assigned on arrival, overstays are flagged and every movement lands in the same audit trail as the visit.
How it functions
From empty bay to released bay.
Follow a Car Pass end to end. Pick any stage — it runs on its own if you leave it alone.
Stage 01 · Configure
Your parking, described once.
An admin maps the real car park into MeetPass — zones, bays, capacity and the rules that govern them. Which pass types may park, how many bays a department may hold, which bays open to visitors during the day.
Zones and individual bays defined in the admin module
Rules per pass type — Meeting, Visitor, Residential, Event
Quotas per host, department or tenant
Daytime vacancy pool — bays released while their owner is out
Stage 02 · Attach
It rides along with any pass.
The Car Pass is not a separate journey. It attaches to whichever pass the person is already being issued, so the vehicle is approved by the same person, in the same step, against the same record.
Attaches to a Meeting, Visitor, Residential or Event Pass
Issued standalone where a vehicle is all that is needed
More than one vehicle per guest where required
Driver captured separately from the guest when they differ
Stage 03 · Reserve
A slot is held, not hoped for.
The host or an admin books a slot from the backend. Inventory updates the moment it is taken, so the next person to look sees the truth — and a bay promised to a visitor cannot be quietly given away.
Slots booked from the backend against live availability
Inventory updates immediately for every other user
Named bays reserved and held for VIP arrivals
Waitlist and alternative zones offered when a zone is full
Stage 04 · Issue
Plate and pass, together.
The vehicle registration is captured with the request and travels inside the same QR the guest already carries. Nothing extra to print, nothing extra for the visitor to remember.
Plate number captured at request and bound to the pass
Car details carried inside the guest's existing QR
Zone, bay and access window shown on the pass
Directions to the right gate sent with it
Stage 05 · Arrive
The barrier already knows the car.
At the gate the plate is read or the QR is scanned, the vehicle is matched against a live reservation and the bay is confirmed. No clipboard, no call upstairs, no queue behind the barrier.
Plate or QR validated at the barrier in one action
Bay assigned and confirmed on arrival
Invalid, expired and unreserved vehicles rejected with a reason
Host notified when their guest's vehicle enters
Stage 06 · Occupy
Live, bay by bay.
Security and facilities see the car park as it actually is — which bays are taken, by whom, under which pass, and which vehicles are approaching or past the end of their window.
Live occupancy across every zone and bay
Which pass and which host each vehicle belongs to
Overstay flagged automatically against the visit
Capacity and utilisation visible before you promise a bay
Stage 07 · Release
The bay goes back to the pool.
The vehicle exits, the bay returns to inventory and becomes available to the next request. Daytime pool bays are handed back to their owner before they return, and every movement is retained for audit.
Exit releases the bay back to available inventory
Pool bays returned to their owner ahead of their return window
Utilisation, peak-hour and overstay reporting
Full audit of every vehicle movement, on your own infrastructure
The capacity you already have
Empty at 10am. Full of visitors by 10:05.
In most buildings the bays are allocated permanently, so they are only used part of the day. Residents and staff drive out in the morning and their spaces sit empty until evening — while your visitors circle the block. Nothing is short of capacity; the capacity is simply locked up.
Release by window — bays open to visitors during the hours their owner is out
Returned automatically before the owner is due back, with a buffer you set
Owner keeps priority — a released bay is never double-promised
Per zone or per bay, so you can start with one level and grow
Level B2 · 12 bays10:05
A1A2A3A4A5A6B1B2B3B4B5B6
Owner in
Released
Visitor parked
Held for VIP
Where it matters most
A VIP should never be looking for parking.
You prepare a ministerial visit for weeks. The agenda is right, the room is right, the briefing pack is right — and the first thing the delegation experiences is being waved past a full barrier towards the street. Hold the bay when you book the meeting, and the arrival matches the preparation.
A named bay, reserved and locked to that arrival alone
The barrier knows the plate before the car turns in
Escort and host notified the moment the vehicle enters
Whole convoys handled as one arrival, not five separate cars
ReservedBay A1 · Level B2
Attached to
Meeting Pass · MP‑2026‑0417
Vehicle
Land Cruiser · 4 4 9 2 1 7
Held from
08:45, released 12:30
Convoy
3 vehicles · bays A1–A3
Gate 2 recognises the plate on approach
Everything on the pass
What a Car Pass actually carries.
Grouped by where the work happens — the admin panel, the issued pass, and the barrier itself.
Configured in the admin panel
Zones & bays
Describe the car park as it really is — levels, zones, individual bays, capacity and the restrictions on each.
Rules per pass type
Decide which pass types may park, for how long and where. A visitor and a resident do not get the same rights.
Quotas by host or tenant
Cap how many bays a department, host or tenant can hold at once, so no single team absorbs the whole car park.
Daytime vacancy pool
Release bays whose owners are out during set hours, and return them automatically before those owners come back.
Windows & blackout periods
Set the hours parking is available per zone, and close zones for events, maintenance or deliveries.
Issued with the visit
Attaches to any pass
Meeting, Visitor, Residential or Event — the Car Pass is part of that approval rather than a second process.
Plate bound to the pass
The registration is captured at request time and carried inside the same QR the guest already holds.
VIP reserved bays
Hold a named bay for a specific arrival. It cannot be allocated to anyone else, and the barrier expects the plate.
Multiple vehicles
A delegation arriving in three cars is three vehicles on one visit, not three separate problems.
Backend slot booking
Hosts and admins book from live inventory, and every other view updates the moment they do.
At the barrier and after
Validation at the gate
Plate read or QR scanned, matched to a live reservation, barrier opens — or it does not, with the reason on screen.
Live occupancy
Every zone and bay as it stands right now, with the pass and host behind each vehicle.
Overstay flagging
Vehicles past the end of their window are surfaced automatically and tied back to the visit record.
Utilisation reporting
Occupancy over time, peak hours, turnover and how much of the daytime pool is actually being used.
Car Pass FAQ
Questions about vehicle access.
No. ANPR is supported where you already have it, but the plate can equally be checked by an officer against the credential on screen. The record is the same either way.
Yes — that is the point of it. Parking travels with whichever pass the person already holds, so a visitor, a meeting attendee or an event guest can be given a bay without a second system or a second credential.
The plate can be updated on the existing pass up to the moment of arrival, by the host or by the visitor from their own pass. The change is recorded rather than replacing the original silently.
Yes. Bays can be held for named roles, departments or protocol visits, and released automatically when the visit ends so the space is not lost for the rest of the day.
In most cases yes. MeetPass drives barriers and access controllers you already run rather than replacing them — the credential is validated by MeetPass and the open signal goes to your existing hardware.
Turn your bays into bookable inventory.
Book a briefing and we will model your car park — zones, quotas and a daytime pool — against a real arrival.