Where duplicates come from
A swipe notification contains the first name and surname (required), an acronym, the company name (required), the number of the active card, phone, e-mail and language. A swipe by a person unknown to the system creates an account and a company from these data, which is why the access control vendor should pass the first name, surname and company name in a uniform form.
Typical sources of discrepancy are abbreviations of the agency name, legal-form suffixes sometimes with a full stop and sometimes without, letter case, a different order of first name and surname, and Polish letters replaced by plain letters. Each of these differences can become a separate company or a separate account.
Step 1: set up a dictionary of agency names
The access control administrator prepares a list of agencies with one binding name for each. A good source is the panel for external companies in InnerWeb, which manages companies, their workers, pending invitations and guests, with a default contact person. The name set in the panel is the pattern that the access control system should repeat in its notifications.
Practice: the agency name in the access control system is a selection field from a list, not a free-text field. This removes the typos at the point where they arise.
Number of companies after a season with three agencies, example
- Without a name dictionary
- With a name dictionary
Step 2: uniform spelling of the first name and surname
Fix the order: first name, then surname, without titles, with Polish letters. Write down the rule for double-barrelled surnames and for people with several first names. A uniform spelling reduces the number of false duplicates and makes search easier: the account search requires at least 3 characters of the surname and returns up to 13 results.
Step 3: review existing duplicates and merge them
If duplicates have already been created, do not delete accounts by hand. A training result recorded on a duplicated, deleted account is redirected to the account it was merged with, for up to 3 consecutive merges. This gives a safe way of tidying up, but the order matters: first decide which account is the correct one, then merge the others.
A guest can also be moved to an external company on the same account, so if a company was created by mistake, the person is moved to the correct one, and training results, the pass and the entry history stay.
Step 4: a check after the first week of the season
After the first week of the season, check the list of companies: whether new names have appeared that look like variants of existing ones. With three agencies in the season, every new company beyond three is suspicious. This is a simple, quick check.
It is worth repeating the check after each larger wave of recruitment, and recording the results in the note of the access control administrator.
- Compare the list of companies in InnerWeb with the agency dictionary.
- Identify new companies without an invitation and verify them with the agency coordinator.
- Merge or move people, and keep the remaining accounts for audit.
Video
Frequently asked questions
Does InnerWeb merge companies with similar names on its own?
A swipe creates an account and a company from the data it receives, so the uniform spelling must be ensured by the access control vendor.
Do duplicate accounts cause loss of training results?
No, if the accounts are merged: the result from the deleted account is redirected to the target account, for up to 3 merges.
How do you fix a company that was created by mistake?
The person is moved to the correct external company on the same account, without losing the history.
Who is responsible for the name dictionary?
The access control administrator together with HR, based on the list of companies in the InnerWeb panel.
Tidy up agency names in the access control system
Book a call with the access control administrator. We will go through the name dictionary, the spelling of surnames and merging existing duplicates.
Let's talk