Starting point: a workforce that does not read Polish
The plant belongs to a global group, and renovation and assembly work is done by external companies with a foreign workforce. The OHS manager issues permits for hazardous work, but the contractor's worker must receive a document they will actually read: the job description, the hazards, the preventive measures and the end conditions.
This is an implementation scenario, not a description of a finished project. We show how such a plant can organise its work with the system during the pilot, based on functions the system already has. The interface and the generated documents work in six languages: Polish, English, German, Finnish, Russian and Swedish.
The problem is not translating the screen alone. The permit printout is the document the worker takes to the workstation, so it has to be understandable at the point where the decision to start work is made.
Why the printout is a separate layer from the screen
The printout layer has its own translation key space, independent of the interface. This lets the wording of the document, which has a legal character, differ from the labels visible on screen, and that is intended: a button label does not need the same weight as a formulation in a document signed by several people.
For the OHS manager this means two things to check before the start. First, whether the printout in a given language contains all sections of the permit. Second, whether the names of hazards and preventive measures have equivalents in that language. The second point is described separately on the page about multilingual dictionaries.
Document language versus account language
Documents are generated in the worker's language. When a worker registers from a QR poster or on a tablet at the gate, the selected language becomes the account language and also decides the language of the induction training. If induction training in that language is missing, the gate requires training in Polish instead of skipping this step.
Languages supported by the system and the pilot scope
How this could look at a group plant
The concept assumes three stages. First, the contractor registers its workers, and each one chooses their language. Next, they complete the induction training in that language. Only then does the OHS manager, or the person issuing the permit, prepare the document, which reaches the worker in their language version.
The plant does not change its own access control or time-and-attendance systems. InnerWeb is an independent system that complements the client's existing systems rather than replacing them, so the pilot can be limited to one hall and one group of contractors.
- Registration of a contractor worker with a choice of language
- Induction training in the account language, with a requirement for the Polish version as a fallback
- Permit issued from a template and printed in the worker's language
- Review of the printout by the OHS manager before the first shift
What to check in the pilot before the whole plant starts
At the start, choose one permit and generate it in all six languages. Compare the printouts with the Polish version for completeness of fields, not for style. An empty field on a foreign-language printout is a sign that a dictionary entry or a label has no version in that language.
The second test is a screen showing a Polish label in a foreign-language interface. This usually means a label override in the plant settings, not a missing translation. It is worth verifying labels and dictionaries on a live permit wizard, not only in the settings.
The third question is which languages will actually appear on site. The system supports six, but the pilot may cover two or three, which shortens the translation review.
Conclusions for the OHS manager
A multilingual printout does not replace the responsibility of the person issuing the permit, nor the instruction at the workstation. It does shorten the path from the decision to the worker's understanding, and it leaves a record of the language in which the document was issued.
Before the pilot, agree with the IT department and the group's head office who is responsible for the translation content in each language, and who approves changes to the dictionaries. Without this, the first change to a template will leave a mismatch between the versions.
Video
Frequently asked questions
Will a contractor worker receive the permit in their own language?
Yes, documents are generated in the worker's language, provided it is one of the six supported languages and the dictionaries have its equivalents.
What if induction training in the account language is missing?
The gate then requires induction training in Polish instead of skipping this step.
Is the language of the printout the same as the screen language?
No. The printout layer has separate translation keys, so the wording of the document can differ from the interface labels.
Check the printout in your language
Book a call about a pilot in one hall. We will show a permit printout in the selected languages and agree the translation scope.
Let's talk