InnerWeb
Skip to main content

How to check accounts with a wrong training language

An account with an accidental language, chosen carelessly at registration, causes training in a version the worker does not understand, or a requirement for Polish training they cannot follow. The data administrator can detect this, prepare a list and correct the accounts on the installation after making a backup. Below is the procedure in six steps.

6
steps of the procedure for correcting account languages
Source: sample calculation

Why a wrong account language persists

The account language is set only when the account is created, and registering an existing person again changes nothing in the account. A worker therefore cannot fix the error alone by scanning the poster again. The browser language does not change the account language either: the language of the training session equals the account language.

The error usually has three sources: registration on someone else's phone, an accidental tap on the default option on the tablet at the gate, and mass creation of accounts from a file in which the language column was filled with one value. Each of them leaves a trace in the list of accounts.

Steps 1 and 2: detection and list

Start with the list of accounts grouped by language. The task is to find discrepancies: companies where most people are not English speakers but the accounts have English or Polish, accounts with a language for which the plant has no training, and clusters of accounts created on the same day with the same language.

From the detected accounts, prepare a correction list: the account identifier, the company, the current language, the target language and the source of information about the correct language. The source can be the worker's answer, the agency's record or a registration document. Do not guess the language from a surname.

Time of the correction steps (example, minutes)

Time of the correction steps (example, minutes)Horizontal bar chart of step times: list 15 minutes, preparation 30, backup 10, correction 20, test and proof 15.0102030minList of accounts by languageList of accounts by language: 15 min15Preparing the correction listPreparing the correction list: 30 min30Backup and confirmationBackup and confirmation: 10 min10Correction in the panelCorrection in the panel: 20 min20Test and proofTest and proof: 15 min15
Source: Sample calculation based on an assumption of 40 accounts to correct

Steps 3 to 5: backup, correction, check

Before any change, make a backup of the data on the installation's server and confirm that the file exists and has a non-zero size. Only then correct the language in the administrator panel, and use SQL only when the panel does not have such a function. On a client installation we do this at the plant administrator's request sent by e-mail.

After the correction, open several corrected accounts and check that the tablet takes over the account language when the person enters with a credential: an invitation link, a badge or a card. When the language is chosen manually, the choice stays with the person, so the test must be run with a credential.

Watch the gap counts that are calculated retroactively

After the mechanism is switched on, existing non-Polish accounts in a plant with training only in Polish are treated as requiring it, and the reports count gaps retroactively. Changing an account language can therefore change the number of overdue trainings in a report. Warn the safety department before the change, so that a sudden drop or rise does not come as a surprise.

Step 6: proof and message

Record the proof: the date, the number of corrected accounts, the name of the backup file with its size, the list of changes and the person who made them. A short text file in the plant's documentation is enough. Report the result to the plant administrator with a brief note that the change has been made.

If after the correction it turns out that the plant has no training in the correct language, the system requires the training in Polish instead of skipping safety training. In that case the right decision is to prepare the language version, not to reverse the correction.

How to prevent a repeat

The simplest measure is a clear choice of language on the tablet at the gate, with a flag and the name of the language, and a QR poster that accepts Polish and English and treats a missing value as Polish. Registration from the poster rejects any other language with a validation error.

The second measure is a monthly review of the list of accounts by language, which takes a dozen minutes. It catches clusters of errors before they become a backlog in the report.

Checklist

Video

Frequently asked questions

Can the worker correct the account language alone?

No. The language is set only when the account is created, and registering again changes nothing. The correction is made by the data administrator.

Does the correction require a code change?

No. It is a data change on the installation, made in the panel after a backup.

Why did the number of gaps change after the correction?

Gap reports count retroactively, and non-Polish accounts in a plant with Polish-only training are treated as requiring that training.

Let us check the accounts at your plant

We will help you prepare a list of accounts by language and carry out the correction with a backup and proof. Book a meeting with InnerWeb.

Let's talk