Who writes The QHSE Standard

The QHSE Standard publishes software profiles and buying guides to help readers compare operational requirements, product scope and evidence. Dimitris Mitsios is responsible for what is published here. Pages are researched and drafted with AI tools from the linked sources; he checks selected pages and dates those checks. Not every page has been individually reviewed.

Sponsored placements

Tekmon pays for sponsored placement of its listings. Those placements are labelled and sit apart from the documented-match ordering of the lists. A placement does not establish product capability, a test result or suitability for your organisation.

Use the evidence and limitations attached to a comparison rather than reading prominence as a recommendation.

How a software profile is built and labelled

Each software profile starts from a research record rather than from free-form copy. The record names the product and the exact scope being assessed, because a vendor brand often covers several products and plans. It lists the sources used, the date the sources were last checked, the capabilities examined and a short note on where the profile does not apply. Pages are generated from that record, so a change to a fact is made once and reaches every page that uses it.

Each capability in a record carries one of four labels. “Documented by vendor” means a source link supports the statement for the scope described, which is a statement about published documentation and not a test. “Depends on scope” means the source supports it only for certain plans, configurations or conditions, which the row spells out. “Not verified” means the sources reviewed did not settle the question, so it is an open item to raise with the vendor, not a finding that the feature is missing. “Documented as unsupported” marks a statement that a source itself says is not offered. Anything that could not be settled is gathered under a heading on the profile called “What we could not verify”.

Profiles also carry demonstration scripts. These are suggested exercises for a buyer to run with the vendor, such as capturing a finding offline and reconnecting, and they are written as tasks to perform, not as results that were observed. A dated note on a profile records what changed in the record and when.

Recording a personal check

A check by the editor is recorded in a log with the page, the date and one sentence on what was checked, and a page shows a checked-on line only when such an entry exists. An entry is added after the check has been done, not in advance. The log has no entries at present, so no page shows a personal check.

Some kinds of page never receive a checked-on line. These include generated answers, reader reviews, the contact, listing, quiz, privacy and terms pages, the pages generated from a single template, paid landing pages, and pages that name the commercial partner, because the editor works at that partner and a check by him would not be independent. The absence of a line on a page therefore says nothing about whether its content is accurate; it says only that no check has been logged for it.

Corrections policy

Send the page URL, disputed statement and a supporting source when reporting an error. Product scope and pricing can change between checks. Vendors can submit updates, which should be assessed against the underlying evidence. The editorial log lists past corrections.