Logo DarkLogo Light
  • Home
  • KB Articles
  • 0 Read me first

0 Read me first

Last modified: April 6, 2021
You are here:
Estimated reading time: 3 min


Thank you for vising the Strytex Knowledge Base, we hope you find it useful.

Just to let you know, we are not experts in every compliance topic in every country in the world. To be experts, we would have to employ hundreds of subject matter experts around the world and that is not who we are.

However, because we deal with thousands of certificates across various industries, we pick up a lot of useful information and because we are curious, we do a bit of research to get a basic understanding of the document and what it’s used for. We happily make this information available for free and provided in good faith on the basis that it may provide some guidance.

We must stress that Strytex gives no warranty nor bears any liability whatsoever with respect to the correctness, accuracy, currency, completeness, relevancy or otherwise of this information any template or sample document. You must obtain professional advice from a duly qualified person or subject matter expert. Please read the full disclaimer here.

All of the global glossary articles follow this template. It’s not 100% perfect so please bear with us as we update over 100 articles.

ORC Matrix

Strytex has developed the ORC matrix (Obligations, Risk and Compliance) as a tool so that organisations can structure their operational compliance records in a systematic framework. It is similar to the way the finance department structures your financial records into ledgers e.g Sales Ledger, Purchasing Ledger and General Ledger.

Obligation Hierarchy

We’ve prioritised obligations into 6 levels. For a detailed description please see the article Obligation Hierarchy.

  • Legal
  • Critical
  • Best
  • Ethics
  • Discretionary
  • Legacy

Risk Topic

Every organisation is subject to multiple risks and every organisation has it’s own way of describing each risk topic. Here we will try to highlight the main risk topics.

Compliance Class

After analysing over 10,000 compliance documents, we’ve categorised them as into six classes.

  • Asset
  • Company
  • Product
  • Contract
  • Property
  • Staff

Description and purpose

This will have a brief explanation of what the glossary item is all about.


Depending on the type of glossary document, it has key aspects to it. We will pick out the most important, from a compliance perspective.

Renewal frequency

Many documents have multiple renewal periods, for example, you may have a 5-year drivers licences or a 10-year drivers licence. Asset maintenance or food safety documents have multiple renewal and/or maintenance frequencies. For example in Australia fire extinguishers must be serviced

  • six-monthly
  • yearly
  • every 5 years.


Occasionally, but not always, we will group a set of documents because they are all variants on a single type of document theme, e.g

  • Public Liability Insurance,
  • Product Liability Insurance
  • etc.

2nd level attributes

This is different to variants. Some glossary items have critical complaince related 2nd level attributes,

  • how much is the liability insurance for?
  • what type of plumber licence is it and what types of work are they authorised to carry out?

You want to make sure your suppleir has the right level of insurance, you want to make sure your plumber is qualified to carry out the task.

Also known as

Some glossary items have multiple names. It may depend on what part of the world you are in, what profession you are in or even how knowledgeable you are. For example, a drivers licence may also be known as a vehicle licence.

Geographic relevance

Glossary items can apply globally, across a trading zone, or just for one country. For example, a BWOF (Building Warrant of Fitness) is only used in New Zealand.

How and when Used

Internal compliance

How and when to use the glossary item for internal compliance

External compliance

How and when to use the glossary item for external compliance, e.g suppliers, contractors, supply network etc.

Obligation force

We believe the root cause of all obligations are external. Some are obvious, namely government statutes and regulations; others have less obvious external root causes. Applying the classic PESTLE analysis provides a starting point. Adding root cause analysis expands the picture. For example, this diagram provides a simple starting point.

We will attempt to define the external force for each glossary document

Internal controls

Obligations are often tied to a risk control, a policy or procedure.

Useful links

Kind of self-explanatory however we will not always include the link down as links get broken or archived.

Was this article helpful?
Dislike 1 1 of 2 found this article helpful.
Views: 37

Leave A Reply

WordPress Video Lightbox Plugin