On this page (6)
A note in a lever-arch file, a message in a group chat and the shift supervisor’s memory don’t meet that condition. Gate staff change, the note gets lost, and the driver drives in yet again.
Why a site ban does not close the barrier
A site ban entry doesn’t block the gate automatically: TraxSystem shows the operator a clear warning, and a person makes the decision. The system was deliberately designed this way, for several reasons:
- data can be wrong, and a typo in a surname or a case of mistaken identity would stop the wrong person, with no quick way to appeal at the gate;
- the ban may be out of date, because the matter has been cleared up and nobody removed the entry;
- exceptional situations happen: an emergency services vehicle, a breakdown, a critical delivery;
- turning someone away is an act directed at a person, and a person should be answerable for it, because an automated system can’t explain the reason.
An automatic block that stops the wrong person at the first data error will get switched off by security, and then nothing works at all.
How the ban list works at the gate
- A ban entry contains the person, the reason, the period it applies and who entered it.
- When registering an entry, the gate operator sees the warning the moment the driver is identified.
- The operator decides: let them in, turn them away, or contact a supervisor.
- An attempt to enter by a banned person is recorded in the log whatever the decision.
The record in the log is often underrated, yet it is the basis for the conversation with the carrier. The sentence “your banned driver turned up three times this month” can be backed up with an entry from the log.
In TraxSystem bans and warnings have their own module, Bans and warnings, which is added to the system’s base package; the pricing configurator will show the amount for the base together with this module.
How the system recognises a banned driver
A banned driver doesn’t give their name the same way every time: once as “Jan Kowalski”, once as “Kowalski Jan”, once with a hyphen or a full stop in the surname. A letter-for-letter comparison would catch only the first variant, so TraxSystem compares a normalised form of the data, ignoring differences in letter case, spaces, hyphens and full stops. Polish characters are kept, so the system treats “Łukasz” and “Lukasz” as two different first names.
Normalisation applies only to the comparison. The data in the database stays exactly as it was entered, and the system doesn’t “correct” anyone’s name.
Identification relies on personal details and an identity document. The system doesn’t use biometrics: facial recognition is neither a feature nor planned.
Warning or site ban
The system distinguishes two levels of entry about a driver:
| Warning | Ban | |
|---|---|---|
| What it is for | information for the operator | refusing entry |
| Example | “a disciplinary incident on the previous visit” | “banned from site until further notice” |
| Effect | entry usually goes ahead | entry needs a supervisor’s decision |
The split protects the credibility of the whole mechanism, because when everything is a ban, security stops distinguishing how serious each signal is.
What the ban list does not do
TraxSystem won’t lock the barrier against a banned driver: it shows the operator a warning, and the decision stays with a person. Nor does it share ban lists between sites, so a ban applies at your site. There is no shared database of “unwanted drivers” across companies, and there won’t be, because that would be processing personal data without a legal basis and without the knowledge of the person concerned.
The system doesn’t recognise faces and doesn’t judge whether a ban is justified. The entry is your decision and your responsibility. A site ban involves personal data, so agree it with the person responsible for data protection: who may enter bans, how long an entry stays in force and how the person concerned is informed.
Questions and answers
Can a ban be set for a fixed period?
Yes, with a start and end date. The entry then expires by itself and nobody has to remember to remove it.
Does the driver find out they are banned?
Not from the system, because TraxSystem doesn’t notify them. Whether and how the driver is informed is your decision, and since it concerns the processing of their data, it has to be a considered one.
What if the same driver turns up working for a different company?
You don’t need to do anything. The warning is attached to the person, so it appears regardless of whom the driver represents. Getting round a ban by changing company is covered in a separate article on a site ban bypassed by changing employer.
See also: Site bans bypassed by changing employer · Driver data at the gatehouse: how long to keep it and what to delete · Who is responsible for entry control in a logistics park