Start a free trial
Menu

One requirement, many standards: how ComplyTrain stops duplicate compliance work

Learn how the autumn 2026 release lets you work each obligation once, reuse evidence across standards, and see upfront how much of a new standard you already cover.

Few organisations follow a single standard for long. A quality standard comes first, then a customer asks for an information security standard, then a regulation arrives, then a contract adds its own clauses. Each one says, in slightly different words, that you must control your documents, assess your suppliers and train your people.

If your system treats every standard as a separate list, you do that work several times. The autumn 2026 release changes the model underneath. This article is part of the series on what is new in ComplyTrain.

One working requirement per obligation

ComplyTrain now separates two things that used to be one:

  • The obligation. What you actually have to do. You work it once: one owner, one set of evidence, one verdict, one document mapping.
  • The standard's view of it. Each standard keeps its own clause number, its own wording, its own scope decision and its own milestone.

When you subscribe to a second standard that states an obligation you already work, ComplyTrain reuses the existing working requirement. The evidence you collected for the first standard counts for the second.

If two requirements later turn out to be the same obligation, they can be merged. The old reference keeps working and points to the survivor, so links in documents and audit records do not break.

See how much you already handle

Before you commit to a new standard, the catalogue shows how much of it your current work covers: the share that is already handled, and the share that is partially credited. This comes from crosswalks, which map requirements between two standards and record where the mapping came from.

The same figures appear during onboarding and are available to the AI Assistant, so you can ask what a new standard would add to your workload and get an answer based on your own status.

No second quality manual

A new standard often needs content that belongs in a document you already have. Earlier, that meant a second document on the same topic.

Now ComplyTrain keeps one document per topic. When a further standard needs content in it, you get an amendment proposal: the sections to add to the existing document. You accept it, decline it (which is remembered), or have the AI draft the addition for you. If you later leave the standard, only its contribution is removed.

The same applies to processes. A standard can bring complete process templates, and when a further standard touches a process you already run, you get a proposal to amend it.

Your own standards

Not every requirement comes from a published standard. You can now create your own standards for:

  • internal rules and policies,
  • a customer's contract requirements,
  • a standard that is not public, which you complete yourself from your licensed copy.

Requirements can be added by hand, imported from a spreadsheet, or extracted by AI from uploaded source documents, with a full review before anything is accepted. You can link them to requirements you already work on, freeze revisions and export to Excel or PDF.

How many custom standards you can have depends on your plan; see pricing.

Track before you implement

A standard can be held in tracked mode. You follow how close you are without taking on its tasks, documents and milestones. This is useful when a customer has announced a future requirement, or when you want to compare options before choosing.

Share a standard with your suppliers

A standard you own can be shared with suppliers who also use ComplyTrain. They adopt it, receive clause-level differences when you update it, and report their compliance status back. Sharing between organisations uses signed, encrypted messages; neither organisation gets access to the other's data.

For suppliers outside ComplyTrain you can generate a stakeholder questionnaire from the same standard.

National variants

EU acts are often implemented differently per country. ComplyTrain can now show where a country adds to, tightens, changes or does not apply a clause, applied per product market, with a National Laws page per act. Your company profile holds your countries of operation and your country of main establishment, which decides what applies to you.

Registers that live where the work is

Several standards ask for registers. These now sit in the module that owns the subject, and feed your requirement verdicts as evidence:

  • a requirements register with legal and regulatory sources and owners,
  • management-system objectives per discipline,
  • an incident register in Risk Management, with notification obligations and deadlines,
  • a configurable asset register,
  • Stakeholder Management as the single supplier register, with supplier contracts.

Requirement verdicts now count effective controls and module records as evidence, and a person can override a verdict with the history kept.

Why this matters

The cost of a new standard should be what is new in it. With one working requirement per obligation, a second standard starts from the work you have done, and the system can say how much that is.

ComplyTrain gives you the structure to build and evidence your management system against the standards you choose. The certificate remains yours to earn. More on the modules involved is on the QMS and Requirements pages.

To see how your current standards overlap with the next one on your list, book a demo.