Language support in QHSE software: what 209 profiles document

What the records show

1. Most records say nothing about languages. 172 of 209 (82%) carry no statement about the languages of the product. The records have no structured language field, so a statement exists only where a vendor page or a reviewer's note mentioned one. Of those, 20 records contain a language word without stating that the product supports one: mostly they ask the buyer to confirm languages or say that the vendor does not list them, and a few use the word in another sense, such as a country name or the translation of codes. These are not counted as support.
2. Few records name a language. 7 of 209 (3%) name at least one: English (7), German (2), French (3), Spanish (4), Portuguese (2), Italian (1), Dutch (2). A further 20 of 209 (10%) describe multilingual content, translation or a multilingual interface without a number or a language, so the reader cannot tell which languages are meant.
3. No record names Nordic languages, Polish, Turkish, Arabic, Chinese, Japanese or Greek. 3 of 209 (1%) name German or French as a product language, and 0 of 209 (0%) name Greek. The same gap appears in the Greek-language guide, which found no profile documenting a Greek interface, Greek templates or Greek legislation. A zero describes our records, not demand for the language and not what any product offers.
4. Where a number is stated, it is often large, and the largest figures are about content. 16 of 209 (8%) document at least two languages, 11 of 209 (5%) at least five and 10 of 209 (5%) at least ten. Among the 17 profiles with a number or a list, the largest figure is 100 and the median is 12. 7 of the 10 that reach ten state it for content such as documents, labels, questionnaires, messages or audit questions.
5. Few records quantify the interface. 9 profiles make a statement about the interface or app, but only 5 of them give a number or list of at least two, 2 at least five. 24 profiles make a statement about content, 2 about voice input and 1 about a support service. Only 2 profiles state the interface and the content separately, and 4 give a figure for the product without saying which part it covers.
6. The share with a statement differs by category, but the categories are small. Among the 12 categories with at least 5 profiles, the share with a language statement is lowest in QHSE Management (0 of 16, 0%) and Asset Management (0 of 7, 0%) and highest in Chemical Management (4 of 5, 80%). With between 5 and 43 profiles in a category, one corrected record moves a percentage by several points, so read the spread as a pattern in this sample.

What counts as a language statement

A record counts when it says that the product, or an add-on, offers, outputs or translates into a language. A question to the buyer, a request to confirm languages and a note that languages are not described do not count, and neither does the language of the vendor's own website. Each statement is assigned to the part of the product the record describes, using the record's words rather than ours. Where a record gives a figure for the product without saying whether it covers the interface or the content, the statement stays in a separate group instead of being placed in one of them. A profile can appear in several rows.

The thresholds use the largest figure a record gives for one part of the product, whether it states a number or lists the languages. "Ten or more" therefore does not mean that the interface offers ten: the largest figures come from content such as label and sheet output, and 2 profiles reach ten for the interface or app alone. Some records give a floor ("12 or more") and we use the floor. Where two pages of a vendor give different figures for the same thing, we use the lower; where a record gives different figures for different content, we use the largest.

Which languages the records name

A language counts for a profile once, however many parts of the product the record attaches it to. The table gives the profiles that name the language for any part of the product, and those that name it for the interface or app. A record that says a feature works only in English is counted as naming English, because the record states the language.

English is named most often, but 7 profiles are too few to say which languages the market supports. The gap that matters to a buyer is between a language the buyer needs and a record that names it: for Nordic languages, Polish, Turkish, Arabic, Chinese, Japanese or Greek the records cannot answer the question at all. For those languages the only route is to ask the vendor for the list and to test a representative task, in the language, on the device the crew will use.

How many languages the records state

17 profiles state a number or list at least one language for the product. The chart groups the largest figure each gives. A high figure says that the vendor documents many languages somewhere in the product; it does not say that the language you need is among them, or that the interface, the help text and the reports all have it.

Of the 10 profiles that reach ten, 7 state the figure for content and 2 for the interface or app. The two answer different questions. An interface figure tells a crew whether it can read the screen. A content figure tells a document owner whether the text the product produces or sends is available in the recipient's language. They are separate requirements and should be written down separately.

By category

The charts below use the 12 categories with at least 5 profiles, which together hold 180 of the 209 profiles. The other 12 categories hold 29 profiles between them and are pooled in the table and the CSV, so that no row describes one or two products. A profile belongs to one category, the one shown in the directory.

The share of profiles that document at least ten languages is highest in Chemical Management (3 of 5, 60%), and no profile reaches ten in 6 of the 12 categories. That describes what the records contain; it is not a finding about how many products in a category are multilingual.

The gap between languages needed and languages documented

3 of 209 profiles (1%) name German or French as a product language, and 0 name Greek. No language is named by more than 7 profiles, so a buyer who needs one still has to ask the vendor which part of the product it covers. Where no record names it, the first request is the vendor's own written list for each part of the product, since a figure for one part says little about the others.

The guide to Greece reports the Greek case in detail, and the other regional guides link to this page for the same question about their own markets.

How to read these numbers

• Named by the vendor, not tested by us. Every language and number counted here is a statement on a vendor page or in a reviewer's note. We did not install an app, switch an interface or open a translated document, so none of it is verified.
• Silence is not absence. A record with no language statement may describe a product that offers many languages. The records cover price, trial, integrations, offline use and many other points, and language appears only where a page or a note raised it. Absence in a record is not absence in a product.
• Interface, content and support are different claims. A screen in a language is not a report in that language, a translated form is not a translated report, and a multilingual interface does not mean that a support line answers in that language. Where the records do not separate them, neither do we.
• Machine translation is not a language list. Several records describe automatic or AI translation of forms, messages or documents. These are counted as content statements without a language, and some records say that the translation excludes certain content or needs human review.
• Figures differ between pages. Some records say that a vendor's pages disagree; where two pages give different figures for the same thing, we use the lower. 7 records say in so many words that the languages are not described or not itemised; they are counted once as such and are not guessed.
• These are counts of profiles, not of the market. The 209 profiles are the products we researched, not every QHSE product, and the figures describe the records on the date they were checked, not what any product offers today.

What to ask when languages matter

1. Which languages does the interface offer on the web application and on the mobile app, and does each worker choose a language or does the administrator set one for the account?
2. Which content is available in each language: forms and checklists, notifications, reports, training and the help text? Which parts are translated by people, which by software, and who maintains a customer's own wording?
3. If a vendor translates automatically, what is excluded, who reviews the result, and is the original text kept beside the translation in the record?
4. For voice input, which languages are supported on each device, and does dictation work without a connection?
5. In which languages does the vendor's support, training and documentation operate, and what hours apply?
6. Can a worker in one language and a supervisor in another work on the same record, and which language is the record kept in for audit purposes?

Put the answers in writing in the RFP template, and turn them into a test with the demo checklist: one worker completes one real task in the required language, on the device and connection the crew will use.

How the figures were computed

The profile records have no structured language field, so the statements were read once from the record text and written to a table, each with the exact words of the record that support it. A script computes the counts from that table and from the structured category of each profile, and the page and the CSV are rebuilt from the same output. The script stops if any quoted words are no longer in the record, so a changed record has to be read again, and a test searches every record for language words and fails when one appears that is neither a statement nor a reviewed exclusion. 45 statements were recorded in all. A profile's category is its own category, or the catalogue category where the profile has none. Percentages are rounded to whole numbers. Records were checked through 3 October 2026.

No score, rating, price or payment is an input, and the page does not rank or name any product. The profile set is described in the methodology, and the same records feed the 2026 report on vendor transparency.

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, it is counted in every figure above like any other profile, and it is not named on this page.