Reading Language Claims in QHSE Software: 209 Profiles

A second site in another country, a crew whose first language differs from the language of the procedures, or suppliers in several markets: each turns "multilingual" from a feature line into a requirement. The word alone settles nothing. It can describe the screens, the documents the product produces, voice input, a help desk, or the vendor's own website. We counted what the records of our researched profiles say about it, and which part of the product each statement covers.

The short answer is that 37 of 209 profiles (18%) make any statement about which languages the product handles, and 7 of 209 profiles (3%) name a language. This article gives the counts from our language support study, explains why interface, content, voice and support are separate claims, and sets out how to test the one you need.

The figures at a glance

Each figure in the box comes from the study's data file, and the sections that follow say what each one means.

What the records show

We read the records of 209 profiles for statements about languages. A total of 37 of 209 profiles (18%) contain one, and the other 172 of 209 (82%) do not. Because the records hold no dedicated language field, a statement appears only if a vendor page or a reviewer's note happened to cover languages. For the 172 the right reading is a gap in what we recorded, and not a finding about the product.

Of the 37 profiles with a statement, 17 of the 37 give a number or a list of languages, and 20 of the 37 speak of translated content, translation tools, a multilingual interface or a language service in general terms, with no figure and no language. A reader of those 20 records cannot tell which languages are meant. Across all 209, 7 profiles (3%) name at least one language.

The statements also differ in the part of the product they describe. Content such as documents, forms, labels and messages comes first, at 24 of 209 profiles (11%), followed by the interface or mobile app at 9 of 209 (4%). Voice input is described by 2 profiles and a support service by 1. Separately, 4 profiles state a figure for the product as a whole and leave the part unspecified.

Four claims behind one word

The part of the product matters more than the number. The counts show how far the claims can diverge:

• Interface. The screens and the app a worker, a supervisor or an administrator uses. Of the 9 profiles that make an interface statement, 5 of the 9 state two or more languages, as a number or a list, and 2 state five or more.
• Content. The forms, checklists, sheets, labels, questionnaires, courses, alerts and reports the product holds or produces. This is where the large figures sit: 7 of the 10 profiles that document ten or more languages state that figure for content, and 2 state it for the interface.
• Voice input. Spoken input that a record ties to a stated language. Only 2 profiles describe it.
• Support. A help desk or assistance service offered in more than one language, which is a statement about the vendor's team and not about the software. One profile describes it.

Just 2 profiles treat the interface and the content as separate statements. A figure for "the product" is therefore hard to use, because a crew needs the language of the screen it reads and a document owner needs the language of the report a recipient receives. These are separate requirements, and a statement about one part says nothing about the other.

The language of the vendor's own website is not counted at all. Five records mention it, and one of them says nothing else about languages.

How many languages the records state

A total of 17 profiles give a number or a list of languages for some part of the product. The largest figure any record gives is 100 and the median is 12. Counting the largest figure each record gives for any part of the product, 16 of 209 profiles (8%) document at least two languages, 11 of 209 (5%) at least five and 10 of 209 (5%) at least ten.

A large figure says that somewhere in the product the vendor documents many languages. It does not say that yours is among them, or that the part you need, whether screens, reports or help text, carries it. Where a record gives a floor, such as "12 or more", we use the floor, and where a vendor's pages disagree, we use the lower figure.

Which languages the records name

Seven profiles name a language. English is named by 7 of 209 profiles (3%), Spanish by 4, French by 3, German, Portuguese and Dutch by 2 each and Italian by 1. No language statement names a Nordic language, Polish, Turkish, Arabic, Chinese, Japanese, Greek or any language beyond those seven.

These counts are too small to say which languages the market supports. They do show that a buyer who needs a language other than the few named often will not find the answer in a record, which is a limit of the records and not a finding about products. The guide to Greece looks at the Greek case, and the regional guides for the EU, the US, APAC and the Middle East link to the study for the same question in their own regions.

By category, the share with a language statement is highest in Chemical Management (4 of 5, 80%) and lowest in QHSE Management (0 of 16) and Asset Management (0 of 7). Categories here hold from 5 to 43 profiles and one changed record alters a percentage by several points, so the spread describes this sample only.

How to test a language claim

Put the language in the requirement part by part, then test it in that part. A workable sequence:

1. Write four lines. For each of screens, documents and messages, voice and support, state the languages you need and who needs them.
2. Ask for the list in writing, per part. A written list with a date can be checked later. "Fully multilingual" cannot.
3. Have the right person run the task. A worker whose first language is the one in question completes a real task, such as an inspection or an incident report, on the phone or tablet, and under the network conditions, that the crew works with. Export or print the result and check the language of what comes out.
4. Check your own wording. Ask who translates the checklists and templates you write, whether it is people or software, and whether the original text is kept beside the translation in the record.
5. Try a mixed team. One person works in one language and a supervisor reads the same record in another. Note which language the record is stored in for audit.
6. Check the script and the format. If your language uses another alphabet or reads right to left, check names, dates, numbers and exports.

Steps 3 to 6 need access to the product, and our article on free trials shows how often a trial is documented. The demo checklist shows where to fit this into a scripted evaluation, and the RFP template can hold the written list as a requirement. For training and sign-off in a second language, the guide to toolbox talks software looks at whether a signature shows understanding.

Method and limits

The profile records have no language field. The record text was read once, and each language statement was written to a table alongside the words of the record that back it up. A script then derives the counts and stops if any quoted words have disappeared from a record. In all, 45 statements were recorded. A prompt to the buyer to confirm languages, a note that languages are not described and the language of the vendor's own website do not count. Seven records say in so many words that languages are not described, and 20 reviewed records contain a language word without stating support. Neither group is counted as support. A profile's category is its own, or the catalogue category where it has none. Our records were checked through 3 October 2026; see the methodology for how the profile set was chosen.

Three limits apply. Every statement is the vendor's own and nobody here installed an app, switched an interface or opened a translated document, so documented is not the same as available. Silence is not absence: a product can offer many languages even where its record is quiet, since the subject is recorded only when a page or a note covered it. Nor do the 209 profiles stand for the whole market. No score, price or payment feeds into the counts, and this article ranks and recommends nothing.

Disclosure. One of the 209 profiles belongs to a vendor that pays for sponsored placement on this site, and the editor works at that vendor. Its record was read by the same rules as every other and is counted in every figure above like any other profile. It is not named in this article.

FAQ

Does a record with no language named mean the product is English only?

No. 172 of 209 profiles (82%) have no language statement in their records, and 20 of the 37 that have one describe multilingual features without a number or a language. Neither says what the product offers. Ask the vendor for a written list that covers each part of the product.

Is a multilingual interface the same as multilingual reports?

No. The interface is what a person reads on the screen. Reports, forms and messages are content, and a support service is a third matter. In our records just 2 profiles make separate interface and content statements, so ask for each in writing and test each one.

Sources

• The QHSE Standard: Language support 2026, which holds the counts and a CSV file
• The QHSE Standard: Capability map 2026, the study of capability families built on the same records