Six features carry almost all the operational value. The rest is either specific to your risk profile — or demo decoration.
Every vendor demo shows the same twenty features. Most facilities end up using six of them. The gap between what gets demonstrated and what gets used is where budgets quietly disappear.
This guide separates the features that change daily operations in Saudi facilities from the ones that look impressive on a slide and are never switched on.
| Feature | Why it matters |
|---|---|
| Pre-registration | Moves data entry off the gate and out of the queue |
| Fast check-in | Determines whether the system survives peak hour |
| Host notification | Removes the phone call that delays every arrival |
| Badge issuance | Makes an unescorted person visibly identifiable |
| Check-out capture | Without it you never know who is still inside |
| Searchable records | Turns a log into something an auditor accepts |
The fifth row is the one most systems handle badly, and it is the one that matters most in an emergency: a facility that captures arrivals but not departures has a headcount that is always wrong.
Some requirements are not universal and are easy to miss when evaluating an international product:
The first item is the one to test rather than accept: ask to see the guard screen in Arabic during the demo. A product that treats Arabic as a translation layer shows it immediately in form alignment, date fields and search behaviour.
| Feature | Verdict |
|---|---|
| Watchlist and blocklist | Must-have for most facilities |
| Digital NDA signing | Must-have where visitors see sensitive areas |
| Emergency roll call | Must-have at any site with evacuation duties |
| Contractor document tracking | Must-have wherever contractors work |
| Facial recognition | Situational — high cost, narrow benefit |
| Visitor satisfaction surveys | Rarely used after month one |
| Custom branded kiosk themes | Cosmetic |
A useful test for any feature on the fence: name the person who would use it and how often. If neither answer is specific, it belongs in the nice-to-have column regardless of how well it demos.
Automatic plate recognition earns its cost in a narrow set of conditions: high vehicle volume, a barrier that would otherwise need a guard, and pre-registered vehicles you can match against. Ports, logistics yards and large industrial sites usually qualify. A head office with thirty visitor cars a day usually does not.
The question that settles it is not whether the technology works but what it replaces. If a guard still has to be present at that gate for other reasons, ANPR speeds up a queue rather than removing a cost.
Integration is where feature lists become project plans. The four that come up most:
What to check is not whether integration is possible but whether it is a product capability or a custom project. The first is documented and supported; the second is a line item you will pay for again at every upgrade.
Feature lists are organised into tiers, and the split is rarely where a buyer would put it. Three items commonly sit one tier above where facilities expect them:
Check these three against the tier you are quoted rather than against the product as a whole. See visitor management system cost in Saudi Arabia for how tiers translate into total spend.
Personal data protection requirements shape several features directly, and these are worth verifying in the product rather than in a brochure:
The first is the one that fails most often in practice: a system that stores data indefinitely because deletion was never configured is a compliance gap that grows every day — and it is invisible until someone asks.
Take this into your evaluation and score each candidate rather than asking whether the feature exists:
Question ten is the one most rarely asked and most quickly regretted. Ask for it to be demonstrated by disconnecting, not described.
Haseen is built for Saudi facilities rather than adapted for them: Arabic and English interfaces at equal depth, Iqama and national ID field handling, Saudi plate recognition, and a Sunday-to-Thursday operating rhythm throughout scheduling and reporting. Contractor management, permits and visitor registration sit in one platform rather than in separate products.
See Haseen visitor management and the wider market view in how to compare visitor management systems in Saudi Arabia.
Six carry most of the value: pre-registration, fast on-site check-in, host notification, badge issuance, reliable check-out capture, and searchable records. Everything beyond those depends on your risk profile — watchlists, NDA signing, roll call and contractor document tracking become essential in specific contexts rather than universally.
Full Arabic RTL interface rather than translated labels, Arabic name search and matching, Iqama and national ID field structures, Hijri date display where operations need it, a Sunday-to-Thursday work week in scheduling and reports, Saudi plate recognition covering both Arabic and Latin characters, and local data residency options where compliance requires them.
Only where three conditions hold: high vehicle volume, a barrier that would otherwise require a guard, and pre-registered vehicles to match against. Ports, logistics yards and large industrial sites usually qualify; a head office with thirty visitor cars a day usually does not. The deciding question is what it replaces, not whether it works.
It is claimed far more often than it is delivered properly. Many international products translate labels while keeping a left-to-right layout, which shows up in form alignment, date fields and search behaviour. Ask to see the guard screen in Arabic during the demo rather than accepting a checkbox on a feature list.
Configuration changes — new forms, new approval rules, new areas — should be adjustable at any time without a project. Genuine new capability depends on the vendor's roadmap and licensing model, so ask two things before signing: which items are configuration versus development, and whether enabling a module later carries a different price than including it now.
Fewer than are demonstrated, which is normal and not a problem in itself. The risk is paying for a tier defined by features nobody will switch on. Map each feature you are paying for to a named user and a frequency; anything that fails that test is a candidate to defer rather than buy.
Take the ten-question checklist to your next demo and require demonstrations rather than answers. The questions a vendor prefers to answer verbally are usually the ones worth watching.
Arabic and English at equal depth, Iqama and national ID handling, Saudi plate recognition, Sunday-to-Thursday throughout.