A barrier that opens on a plate is not a booking system

Gate vendors describe the barrier as the control point of a car park. In a car park that runs on reservations, it is the worst possible place to discover a problem.

By the time the car is at the arm, the customer is in front of you and the queue is behind them. The only tools left are a phone call and goodwill. Everything that decided how that minute would go happened two days earlier, when the booking was captured and when the space was allocated.

What an arm can actually decide

A barrier answers one question with one bit. Is this input on the list. The input is a plate, a code, a ticket or a fob, and the answer is up or down.

It cannot ask a follow-up question. It cannot notice that the plate it read is one character off a plate it holds. It has no way of knowing that the booking exists under a name the reseller spelled differently, or that the customer is standing in a hire car because their own gearbox went on the Tuesday. It also has no memory of intent. The list it works from was built by something else, at some point in the past, and it has no opinion about how old that list is.

None of that is a criticism of the hardware. A modern reader is good at reading plates. The mistake is organisational: putting the moment of truth at the one point in your operation that has the fewest tools and the least time.

Three failures that all look like the barrier

When the arm stays down for a customer who has paid, the fault is almost never in the arm. It is one of three things, and all three happened before the car arrived.

The booking never landed. A reseller sent it from an address that is not on your sender whitelist, or they changed their email format on a Thursday and the parse failed. In ParkAgenda that row sits in the review queue with the raw email attached and a reason. Nothing is dropped silently. But if nobody opened the queue yesterday evening, it is still sitting there at 05:55 while a car idles at the arm.

The booking landed, the plate did not. Some resellers do not collect a plate at all. Some collect it and the customer typed it with spaces, or with an O where there is a zero, or booked in their partner's car and drove their own. A blank or wrong plate field is not a barrier problem and no reader will fix it.

The booking landed with the right plate, and the car is outside the window. Booked for the 12th, arriving at 23:40 on the 11th, because the flight leaves at 06:15 and your own confirmation email suggested arriving the night before. The plate matches. The rule says no.

That third one is the most common and the most annoying, because everybody involved did what they were asked to do.

What it costs to find out at the arm

Queue arithmetic is unforgiving, and it is worth doing once on paper. These numbers are an example.

Take a car park with a single entry lane and 46 arrivals in its busiest hour. That is one car every 78 seconds. A clean barrier cycle, from the car stopping to the arm coming back down, runs around 20 seconds. Across the hour, the arm is busy for roughly 15 minutes and idle for 45. That 45 minutes is all the slack you have.

A manual resolution eats three to four minutes. The customer stops, the intercom rings, somebody at reception searches the name, finds it filed as Mac Donald rather than McDonald, checks the dates, and raises the arm by hand. Four of those in the hour consume a third of your slack. Arrivals do not pause while you work, so the queue does not recover inside the hour. It recovers when the wave ends.

There is a second cost and it is the one operators feel. The person resolving the exception is the person who was going to check in the car behind, or drive the shuttle at ten to six. One stuck car at the arm removes a member of staff from the rest of the operation for four minutes, at the only time of day when you have none to spare.

The gate's real job is to be boring

In a reserved car park, the arm should confirm a decision that was already made, and it should do it in under five seconds. Everything interesting has to happen before the car is on the motorway.

Four things have to be true upstream for that to work.

• Capture. Every booking is in one queue before the car is on the road, whatever channel it came from. A reseller email, an API pull, a CSV import and a phone call at the counter all have to end up as the same kind of record.
• Exceptions cleared on a schedule. The review queue is a task for 20:00 the evening before, not an emergency at 05:55. If your quarantined bookings are only ever looked at when somebody complains, you have moved the work to the worst possible moment.
• Identity. The plate is on the booking and it is normalised, so a search for ab123cd finds AB-123-CD. A plate that only exists in a reseller's own back office is not identity, it is a rumour.
• Allocation. The space is committed and the spot is on the record. Nobody should be deciding where a car goes while it idles at the arm with three cars behind it.

Add one more thing that is not upstream, it is a fallback. A named person with a phone who can see the booking and raise the arm, with a record of who did it and why. Every car park has this. Most have it as folklore rather than as a procedure, and it stops working the week that person is on holiday.

What to ask a gate vendor

Four questions, and the answers tell you more than the brochure.

1. What happens when the plate is not read. Who does the intercom ring at 05:00, and what does that person see on their screen when it rings?
2. Can the arm be raised remotely by a named operator, and is there a record of who raised it and when?
3. What does the reader do with a foreign plate, a plate behind a towbar mounted bike rack, or a hire car with a dealer surround?
4. How is the list of authorised plates built, how often is it refreshed, and what happens to a booking that was created forty minutes ago?

The fourth one catches people. A list rebuilt nightly is fine for a season ticket car park and useless for a car park that takes a booking at 04:10 for an arrival at 05:30.

Where ParkAgenda sits, exactly

ParkAgenda does not control barriers. It does not supply them, it does not open them, and there is no plug and play link to any gate brand. Anybody telling you otherwise is selling you a demo you will not be able to run.

Here is what is true. Every stay carries a vehicle plate, typed by an operator or supplied by the booking source, and it is normalised for search. A plate that your own reader captured can therefore be matched against a booking. Where a link between ParkAgenda and an on-site system exists, our team built it for that site with the equipment supplier, through our API, the same way the Parkos and Solution Park booking sources were built. Physical installation is handled by a partner near you.

That is the whole claim, and we would rather say it plainly than lose an hour of a demo. The interesting work is upstream anyway. Matching an ANPR read to a reservation a reseller sent two days ago is the part that is actually hard, and the cases where a plate and a booking genuinely do not match are worth reading before you sign anything.

Questions operators ask

Can ParkAgenda open my barrier?

No. ParkAgenda holds the booking, the plate and the state of the stay. Raising the arm is your gate system's job, and any link between the two is a connector our team builds with your supplier for your site.

Do I need ANPR before ParkAgenda is useful?

No. A large share of off airport car parks run on a reception, a shuttle and a set of keys, with no gate at all. The booking queue, the check-in and the shuttle board do not depend on any hardware.

We already have a gate system. What changes if we add a booking system?

The arm keeps doing exactly what it does. What changes is the list it works from and when the exceptions get handled. Every channel lands in one queue, failed ingests are visible with the raw evidence, and the awkward cases are dealt with the evening before. There is a related trap on the enforcement side, covered in why a car park management system and a parking enforcement system are not the same product.

Next step: stand at your own entrance for one morning wave and write down every car that stops for more than thirty seconds, with the reason. Four mornings of that will tell you whether your problem is at the arm or two days upstream of it. The features page shows what the upstream queue looks like.