Skip to main content
    QHSEtech

    List Your Software

    Send a candidate product or an update for editorial consideration. Submission does not publish a listing or guarantee inclusion, placement or a response.

    Before you write to us: Dimitris Mitsios, who is responsible for what this site publishes, works in marketing at Tekmon. Tekmon sells QHSE software and pays for sponsored placement here, so for most vendors listed it is a competitor. Weigh everything on this page with that in mind (the disclosure, ownership and funding).

    Software Details

    Submissions are reviewed by Dimitris Mitsios (editor; he works at Tekmon, a commercial partner of this site — see the disclosure); there is no guaranteed response time. If there are next steps, you will hear by email.

    What makes a submission usable

    Provide the current product name, the vendor's official website and a factual description of the software offered. Do not include confidential customer information in this form.

    • A submission is a lead for checking; vendor-supplied text is not automatically published as editorial evidence.
    • Product scope, pricing and limitations may be checked against accessible first-party sources before they appear on a profile.
    • Directory inclusion does not create a ranking, certification or endorsement.

    How software pages are researched · Browse the current directory · Report a correction instead

    How a profile is built

    A profile reviews documentation; it is not a product test. It is drafted with AI tools from your public pages and other dated sources, and nobody here runs the software hands-on. The methodology sets out the method and the statement on AI use says what the editor checks and what he does not, so this section only summarises what a profile holds.

    Each researched profile records:

    • Identity and scope: the product name, your website and, where the research records them, the products or modules the profile covers and the category and tags it assigned.
    • Capabilities, each with one of four labels: “Documented by vendor”, “Depends on scope”, “Not verified” or “Documented as unsupported”. Every row except a “Not verified” one links the page it was read from.
    • Prices only where your own pages print them, with the unit, the term and the date they were read (how prices are recorded).
    • Whether a free trial is documented, and what the sources say about offline and mobile use.
    • What we could not verify, listed apart from what is documented.
    • A short note on who the product suits and what to watch for, and a demo script of workflows and questions a buyer can ask you to show.
    • Screenshots or videos from your own published pages where there are any, each linked to its source and shown as vendor visuals, not test results.
    • The sources, the date they were checked and, where the record has changed, a dated change log.

    A profile's date is the day its sources were checked, not the month in which someone reads it. The methodology promises no fixed re-check interval, and the editor does not re-check every source whenever a page changes, so a date moves only when that record is checked again. The 212 researched profiles carry check dates from to ; each data study states its own check window (how the counts are made).

    Request a correction with a primary source

    If a profile states something about your product that is wrong or out of date, write through the contact form. Requests from vendors and from readers go through the same corrections policy.

    What to send

    • The qhsetech.com address of the page and the sentence or table row you dispute, quoted as it appears.
    • What is wrong, what is correct now and, where it matters, the country, plan, edition or date it applies to.
    • A link to a primary source that shows the correct statement.

    Evidence that can be used

    • Your own public pages: product documentation, help-centre articles, pricing pages, release notes, and trust or security pages.
    • For a certification: the certificate, or a public page naming the certifying body, the scope and the validity dates.
    • A statement given only by email, on a call or in a demo cannot be opened by a reader, so it is not cited as a source on its own. Where a profile records one, it is labelled as the vendor's statement and marked “Not verified”.
    • Leave out confidential customer data, passwords and personal records: a public link is easier to check than an attachment.

    What a correction changes

    An accepted correction changes the record it concerns. Where a record has changed, the profile dates the change in a log beside its sources, and the editorial log lists past corrections. A request from a vendor does not by itself change an editorial conclusion, and no response time is promised.

    Lists follow published ordering rules that read the record, for example whether a price is published or a trial is documented. After a correction the same rule is applied to the corrected record, exactly as for every other product; nothing else about the order changes.