Part of the Operations series on the Mobtag platform.
In short: A lot of sites do not need a full parking stack. They need the barrier, reception, and security to be looking at the same current pass, bay, or rule—today.
Printed lists at 08:00 are a fiction by lunch. A tag on a pass or a bay record, tied to a live object, is a cheap way to align three roles that usually operate from three inboxes.
When this is enough (and when it is not)
- Enough when you have moderate volume and simple, written rules (per day, per contract, or per zone) and the cost of a new parking vendor is not justified.
- Not a substitute for ANPR, dynamic pricing, or a city centre operator—if your problem is optimisation at 50k events a day, you are in a different product class.
| Failure if you have no system of record | How it shows up |
|---|---|
| The “master” lives in one head | A dispute at the gate, no timestamp |
| Exceptions in chat | “Which message was the last word?” |
| Fuzzy match of name to reg | Wrong vehicle, right badge |
What good looks like
- Current flag on a permission or a bay, with time-boxing you can see from the record.
- A scan path at the gate: pass or check, then move on.
- After the fact: who was in which zone, when, without a manual merge.
Summary: Tag-backed parking records are allocation you can stand behind: lightweight, honest about scale, and a single current truth for everyone who has to get the barrier up.