The problem: two languages on one screen
At a packaging producer of corrugated board, with its head office in Germany, guests arrive from different countries. At the entrance a video safety induction applies, and under the BRCGS standard a health declaration is also required. Both steps should be understandable to the person who accepts them.
A typical error looks like this: a guest chooses English, the video starts in English, but the declaration text and the confirm button stay in Polish, because the screen uses a different language setting from the player. A consent given under a text the person does not understand is hard to defend at an audit.
The solution: one source of language, the guest account
At this plant guests watch the safety induction video in the language versions and group variants prepared for them, and they sign the health declaration in the language of their account. The language is one piece of data assigned to the person, so the video, the interface and the declaration cannot drift apart.
Registration at the desk takes the list of available languages from the plant setting, by default Polish and English. The training reader knows four languages, while the interface and generated documents work in six: Polish, English, German, Finnish, Russian and Swedish.
How it works at the desk
The guest, or the secretary, selects the language while the account is created. From that moment the tablet takes the language of the account when the person signs in with a credential, for example from an invitation link. The video plays in the same version, and the health declaration is displayed in the same language.
Groups and the assembly point
The induction is additionally differentiated for guest groups, for example visitors to the production hall and to the office, with an assembly point appropriate to each group.
Languages available in successive layers of guest registration
Result and the measures worth tracking
We do not publish figures from a specific plant. We do recommend measuring three things: the share of guests who completed the video in their own language, the number of guests directed to the fallback version, and the number of reports the secretariat receives about a screen that is not understood.
Once these indicators are available, it is easy to decide which language versions to add next. The decision rests on the actual structure of visitors, not on assumptions.
- account language set at registration,
- video in the same language version,
- health declaration in the account language,
- record of completion linked to the person and the date of the visit.
A day in practice: three guests, three languages
In the morning three guests arrive at the plant: a client's auditor, a machine service engineer and a representative of a raw material supplier. The secretariat invites each of them from the registration screen, naming the inviter, that is the employee responsible for the visit. The guest receives a link on his phone, registers and chooses a language.
At the gate there is no longer any question of whether someone understands the video. The account carries the language, so the tablet shows the material in the version the plant holds. If a version matching the account does not exist, the secretariat sees this before the visit and not at the gate, because the language list at the desk comes from the plant setting and should match the video library.
After the video ends, the guest confirms the health declaration in the same language. The visit record contains the person, the date and the result, which is evidence that can be shown to a food safety auditor without searching for paper forms.
Settings to check before the start
The plant administrator should check three elements: the language list at the desk, the set of video versions, and the text of the declaration in every language on the list. When one of them does not match, the guest sees an inconsistent screen. The simplest approach is a table with three columns, compared once a quarter with the actual structure of visitors.
Remember that adding a video to the library is a change of data on the instance, not a change of code, so it does not require deploying the application. The administrator adds the version, and the language list can be extended only once the material is ready.
What this case does not promise
We do not promise materials in every language. Availability depends on the versions the plant holds, and InnerWeb provides the mechanism for choosing the language, the requirement and the proof of completion. If the language list at the desk is longer than the list of videos, the guest will see a mismatch, which is why the list must be synchronised with the library.
The details of the list configuration on the IT side are described in the recommendations for the tablet administrator.
Video
Frequently asked questions
Why must the declaration language be the same as the video language?
Because the consent is given by a person who must understand the text. A single source of language, the account, reduces the risk of the declaration being challenged at an audit.
Can the guest change the language during the process?
A manual choice of language remains a human choice. The account language, however, is set only when the account is created.
Is the language list at the desk fixed?
No, it comes from the plant setting. By default it is Polish and English, and the administrator can match it to the materials the plant actually has.
Guest registration in one language
We invite you to a short demonstration of the registration desk with your versions of the video and the declaration.
Let's talk