Where duplicate accounts come from
A duplicate arises when the same person enters the system twice. The most common cases are registration by two different coordinators, or an employee who changed companies and received a new account. It also happens that the first and last name were recorded differently, for example with and without Polish diacritics, so the automated matching did not recognize the person.
The existence of a duplicate is not a problem in itself, as long as the training results and the card sit on the same account. The trouble starts when the training was completed on account A, and the card is assigned to account B. A card scan then produces a verdict for account B, which has no training. The employee is blameless, and from the data's point of view the gate is right.
The situation resembles a fault in which the result was lost even though the training was completed. That is why the first diagnostic step is to establish which account the result was recorded on, not to repeat the training.
How the system moves the result
A training result recorded on a duplicate, deleted account is redirected to the active account with the card, but only after an explicit merge mark, never on the basis of the surname alone. At most 3 steps of the chain are followed. The solution is conservative: the system does not guess that two people with similar surnames are the same person.
The requirement of an explicit merge mark has a safety rationale. If results moved by surname, John Smith from company A would receive the training of John Smith from company B and would enter the plant without a valid training. Such an error is not visible in any report, and its consequences can be serious.
The limit of three steps in the chain protects against loops and against cases where accounts were merged many times. If the chain is longer than three steps, the administrator should tidy it up manually, pointing to one target account.
False training gaps before and after the merges
- Before the merge
- After the merge
Diagnosis: steps for the administrator
When security reports a missing training and the employee claims to have completed it, the administrator should follow a fixed path. He starts with the account holding the card and checks which trainings are recorded on it. Then he searches for accounts with the same surname in the same company. Searching for an account by RFID card requires at least 3 characters of the surname, returns up to 13 results and does not reveal the card number, so there is no need to reach for raw data.
If he finds an account with the result, he checks whether it is the same person: by document number, date of birth, company, or possibly by confirmation from the coordinator. Only then does he set the merge mark.
- Check the account with the card and its trainings.
- Search for similar accounts (at least 3 characters, up to 13 results).
- Confirm identity with an independent source, not the surname alone.
- Set the merge mark explicitly and record who performed it.
- Verify the verdict with another card scan.
Merging pitfalls
The first pitfall is merging two different people. Two people with the same first and last name in one company happen more often than one might think. Always confirm identity with a second source. The second pitfall is merging in the wrong direction: the target account should hold the card and an active status, not the other way round.
The third pitfall is overlooking the consequences for permissions. A merge moves the training result, but it should not automatically move roles or permissions to permits. After a merge, check that the person has exactly the permissions they should have.
The fourth pitfall concerns dates. If a training is valid for one year from the completion date, a result moved to a new account keeps the completion date, not the date of the merge. An employee whose result from 11 months ago was moved has only one month of validity left.
Prevention: how to limit duplicates
The most effective method is to search for an existing account before creating a new one. The registering coordinator should check whether the person is already in the system, especially when they have changed companies. A document number criterion helps here, if the plant collects it in line with data protection rules.
The second method is the report. The training report shows people without a valid training, and what counts is the status at any moment of presence on the site. If people on the list claim they completed the training, it is often a duplicate. A periodic review of such people finds the errors before the gate does.
The third method is invalidating lost and replaced cards, so that several versions of one person's card do not circulate. The fourth is a transparent procedure for the administrator: who merges, when, and after what verification.
Numerical example
Suppose that after the first month of the gate's operation, the report shows 14 people flagged as having no training, although they completed it. After a review it turns out that 11 of them are duplicates and 3 are real gaps. After the merges the number of false gaps drops to zero, and the 3 real ones return to the coordinators. The figures are illustrative, but they show the proportion usually seen in the first weeks.
The practical conclusion: the first weeks after launching control at the gate are worth treating as a period of data cleaning. Do not treat them as an examination of the employees.
Checklist
Video
Frequently asked questions
Why does the system not merge accounts by surname?
Because two different people can share a surname, and moving someone else's result would give a person entry without a valid training.
How many steps can a merge chain have?
At most 3. The administrator should tidy up longer chains manually, pointing to one target account.
Does the account search reveal the card number?
No. It requires at least 3 characters of the surname, returns up to 13 results and does not show the card number.
Does a merge change the training completion date?
It should not. The result keeps the completion date, so validity is counted from it, not from the day of the merge.
Let's talk about conditional admission
We will show, using your plant as an example, how trainings and qualifications become a condition for entering the site. Book a short conversation or a demo.
Let's talk