InnerWeb
Skip to main content

Person and company data in access control: best practices

Duplicate accounts in an OHS system usually do not come from an integration error. They come from different spellings of the same company or person in the access control register. The access control administrator and HR can prevent this with a few data entry habits. Below are the practices with their rationale and a checklist for rollout.

2,000+
swipes per day, multiplying any spelling error

Why spelling matters

A swipe by a person InnerWeb does not know creates an account and a company from the request data. The vendor should therefore pass the personal data and company name in a consistent spelling, and responsibility for that consistency lies with those who enter the data into the access control register.

An external company is assigned based on the company name in the request. If the access control system lists one agency under its full name, its abbreviation and its name with the legal form, the OHS system ends up with three companies, and training requirements and reports split across them.

Practice 1: one company dictionary in access control

The company name in the access control system should be chosen from a dictionary, not typed by hand. The access control administrator maintains the dictionary and adds a new entry only after checking whether the company is already in it. If the access control system has no dictionary, a list agreed with HR and security and kept in one place is enough.

Companies in the system, example of one agency

Companies in the system, example of one agencyBefore introducing a dictionary, one agency creates three companies in the system; after introducing it, one company.0123number of companies in the systemWithout a dictionary: One agency: 3 number of companies in the system3Without a dictionaryWith a dictionary: One agency: 1 number of companies in the system1With a dictionary
Source: Example calculation: illustrative assumption of three spellings of one agency's name (full, abbreviated, with legal form).

Practice 2: a fixed format for first and last name

First and last name is a required field in the request. Set one format: first name, then last name, not in all capitals, without titles and without additions such as the agency name. Write names with their national diacritics the same way in access control and in all other systems, because a version without diacritics looks to the system like a different person.

For double-barrelled surnames, decide whether they are written with a hyphen. The choice must be the same for everyone.

Practice 3: the card number assigned to a person, not to a company

The active card number is the identifier by which InnerWeb links a swipe to a person's account. A card issued to a company and used by different people in turn disrupts that link. Recommendation: the card is assigned to one person, and a change of card holder is treated as issuing a new card.

Practice 4: periodic check of the company and person lists

Once a month, the access control administrator compares the company list in access control with the company list in InnerWeb. Every company that appears on only one side is a candidate for a duplicate or a mistake. HR indicates which companies are new and which are a change of spelling.

With high agency turnover, the check can be more frequent. Card traffic in such plants can exceed 2,000 swipes on a working day, so a spelling error multiplies quickly.

Practice 5: never merge accounts by surname alone

When one person has two active accounts, the system transfers the training result to the account holding the entry card, but it never merges accounts based on surname alone. Manual clean-up needs the same caution: confirm identity with a second field, for example the card number or phone, before treating two entries as one person.

Division of roles: who maintains what

The access control administrator is responsible for the register in the access control system: the company dictionary, the format of personal data and the assignment of cards. HR is responsible for the accuracy of information about a person, that is, who is employed, by which agency and since when. The OHS department uses the result: accounts, training and alerts in InnerWeb, and reports irregularities to both sides.

The division only works if it is written down. One page naming the person responsible for the company dictionary and the date of the monthly review saves disputes when an auditor asks who watches data quality. The access control vendor is not responsible for the content here, only for how the data is delivered.

Common mistakes and how to spot them

The first mistake is a legal form that appears in a company name sometimes and is missing other times. You recognise it when two companies in InnerWeb have almost identical names and both have people assigned. The second mistake is renaming an agency after an acquisition: access control receives a new name, but old cards stay assigned to the old one. The third mistake is one agency entering surnames in capitals while another uses normal capitalisation.

Each of these errors is easy to detect with one report: the list of company names sorted alphabetically, with the number of people next to each. Similar names sit next to each other and stand out immediately.

  • legal form sometimes present in the name, sometimes missing
  • agency renamed without updating the cards
  • inconsistent capitalisation in surnames
  • missing diacritics in one of the registers

How to measure the effect of duplicates in your plant

At a traffic level above 2,000 swipes on a working day, every spelling error repeats many times. Count how many companies in InnerWeb have similar names in your plant, and multiply the number of duplicates by the number of people assigned to each. The result shows how many people have training requirements and reports calculated separately.

It is also worth checking whether, for a duplicated company, the training requirement in ALL_EXCEPT mode has an exception assigned to only one version of the name. In that case, some people are covered by the requirement and some are not, and the difference comes from spelling, not from any decision.

Checklist

Video

Frequently asked questions

Who is responsible for consistent company spelling?

The access control administrator when entering data, and HR when verifying it. The webhook only passes on what is in access control.

What happens when a person swipes a card and is not in InnerWeb?

The system creates an account and a company from the request data, so the data in the request must be consistent.

Does the system merge duplicate accounts by surname?

No. The training result is transferred to the account holding the entry card, but accounts are never merged by surname alone.

Do you have duplicate companies in the system?

Book a call. We will show you how to check company name spelling in access control and clean up accounts in InnerWeb.

Let's talk