# Certification Mark Usage Rules: [Organization name]

> Internal rules for how [Organization name] refers to its ISO/IEC
> 27001:2022 + Amd 1:2024 certification and uses the certification
> body's (CB) mark, the certificate and any accreditation-related mark.
> Certification bodies must have rules on reference to certification and
> use of marks under ISO/IEC 17021-1:2015, and the certification agreement
> binds you to them; this document turns those rules into internal
> wording, channels, prohibited uses and an approval workflow. It also
> supports clause 7.4 (communication) of ISO/IEC 27001. Replace every
> `[bracketed]` value and every row marked *Example*. This is a
> documentation format, not legal advice.

<!--
Guidance: How to use this template
- Use it as soon as the certification decision is made, before anyone
  publishes the news, and keep it for the life of the certificate.
- Fill first: section 2 (the exact rules documents your CB and
  accreditation body issue, with versions), section 3 (the marks you are
  licensed to use) and the certified scope wording in Document control.
  Your CB's rules prevail over anything in this template.
- Main pitfall: product-level claims. An ISMS certificate covers a
  management system, not a product, so "ISO 27001 certified software"
  or a mark on packaging misleads buyers and breaches most CB rules.
- Never use the ISO logo. ISO does not certify organizations and does
  not allow certified organizations to use its logo.
- Related templates: `isms/certification-cycle-plan` (status changes
  that stop all claims), `isms/security-whitepaper-trust-center`
  (public security page), `isms/security-questionnaire-answer-library`
  (approved answers about certification), `isms/customer-security-addendum`,
  `isms/isms-communication-plan`, `isms/surveillance-readiness-health-check`
  (checks public claims before each audit), `compliance/ms-scope`.
-->

## Document control

<!-- Guidance: Copy the certified scope exactly as printed on the certificate. Any change in scope, certificate status or CB rules is a new version of this document. -->

| Field | Value |
|---|---|
| Document ID | DOC-ISMS-097 |
| Version | [1.0] |
| Status | [Draft / Approved / Superseded] |
| Owner | [@isms-manager] |
| Approvers/reviewers | [@marketing-lead], [@legal-counsel], [@ceo] |
| Last updated | YYYY-MM-DD |
| Classification | [Internal] |
| Standard and edition | ISO/IEC 27001:2022 + Amd 1:2024 (clause 7.4); CB rules per ISO/IEC 17021-1:2015 (clause 8.3) |
| Certification body | [CB name] |
| CB rules document | [title, version, date] |
| Accreditation body and its mark rules | [accreditation body name], [rules document, version] |
| Certificate number and expiry | [n], YYYY-MM-DD |
| Certified legal entity | [legal entity name exactly as on the certificate] |
| Certified scope (as printed) | [scope wording exactly as on the certificate] |
| Certified sites | [list exactly as on the certificate] |
| Next scheduled review | [Annually, and at any change of certificate status or CB rules] |

### Approvals

| Role | Name | Decision | Date |
|---|---|---|---|
| ISMS manager | [@isms-manager] | [Prepared] | YYYY-MM-DD |
| Marketing lead | [@marketing-lead] | [Agreed] | YYYY-MM-DD |
| Legal counsel | [@legal-counsel] | [Reviewed] | YYYY-MM-DD |
| Top management | [@ceo] | [Approved] | YYYY-MM-DD |

### Revision history

| Version | Date | Author | Change |
|---|---|---|---|
| 1.0 *(Example)* | 2027-06-16 | [@isms-manager] | First version after the certification decision on 2027-06-15 |
| 1.1 *(Example)* | 2028-03-07 | [@isms-manager] | Website footer wording corrected after the surveillance readiness health check |
| [x.y] | YYYY-MM-DD | [@author] | [Change] |

## Contents

<!-- Guidance: Sections 1 to 3 set the authority, 4 to 7 say what may and may not be said, 8 to 10 run the controls, 11 to 13 cover tiers, records and references. -->

1. Purpose and scope
2. Whose rules apply
3. Marks and materials you may use
4. What you may claim
5. Prohibited uses
6. Channels and placement
7. Correct and incorrect wording
8. Approval workflow
9. Changes in certificate status
10. Monitoring and handling misuse
11. Size tiers
12. Records and evidence
13. References

## 1. Purpose and scope

<!-- Guidance: Say who must follow these rules. Questions to answer: who publishes content that mentions certification (marketing, sales, bid teams, partners, resellers), and how do they learn the rules? Auditor check: CBs review the use of marks and references at surveillance. -->

These rules make sure every reference to the ISO/IEC 27001 certification
of [Organization name] is accurate, limited to the certified scope, and
allowed by the CB's rules. They apply to:

- all employees and contractors who write external content: marketing,
  sales, bid and proposal teams, customer success, recruitment, investor
  relations;
- agencies that produce material on the organization's behalf;
- partners, resellers and group companies that mention the certification;
- internal material that may be shared outside (sales decks, templates,
  e-mail signatures).

Misuse has consequences. A CB can require corrective action, suspend or
withdraw a certificate when its marks or the certification are used in a
misleading way, and misleading claims can also raise consumer protection
or contract issues in many jurisdictions. Clear rules prevent all three.

## 2. Whose rules apply

<!-- Guidance: List the rule sources in order of authority, with versions. Get the CB's current rules document in writing. Pitfall: copying another organization's wording, which may follow a different CB's rules. -->

| Order | Source | What it governs | Version and location |
|---|---|---|---|
| 1 | Certification agreement with [CB name] | Your contractual obligations, including the use of marks and references | [agreement ref, date] |
| 2 | CB rules for use of certificates and marks | Mark artwork, size, colour, placement, permitted statements | [title, version, date] |
| 3 | Accreditation body rules, where the CB allows its mark to be combined with the accreditation body's mark | Conditions for any combined mark | [title, version, date] |
| 4 | International accreditation system rules on the recognition mark (Global ACI MRA, formerly IAF MLA) | Who may use the international recognition mark (generally not certified organizations) | See the note below |
| 5 | ISO's position on its name and logo | ISO logo not to be used by certified organizations; ISO does not certify | ISO public guidance on publicizing certification (check the current version on iso.org) |
| 6 | This document | Internal wording, channels, approval workflow | DOC-ISMS-097 |

Notes:

- ISO/IEC 17021-1:2015 requires CBs to control the ownership and use of
  their certification marks and references to certification, and to act
  on misuse. The detail is in each CB's own rules.
- The International Accreditation Forum (IAF) and ILAC ceased operations
  on 1 January 2026; their work passed to Global Accreditation
  Cooperation Incorporated (Global ACI), and the IAF MLA was replaced by
  the Global ACI Multilateral Recognition Arrangement (MRA), so an
  accredited CB is now one accredited by a signatory of the Global ACI
  MRA (formerly the IAF MLA). The legacy IAF MLA mark is being replaced
  by a Global ACI MRA mark; some accreditation bodies have indicated that
  legacy mark use may continue until around 2029 (check your
  accreditation body's notices and the current Global ACI rules). These
  international recognition marks are licensed to accreditation bodies
  and accredited CBs, not to certified organizations: under the IAF MLA
  mark licences that accreditation bodies issued, CBs had to stop their
  certified clients using the mark. Do not use it unless your CB confirms
  in writing that the current rules allow it.
- Accreditation body symbols: most accreditation bodies do not let
  certified organizations use their symbol on its own; some allow it only
  as part of a combined mark supplied by the CB (MRK-002). Follow the CB
  and accreditation body rules exactly.
- When in doubt, ask the CB in writing and keep the answer.

## 3. Marks and materials you may use

<!-- Guidance: List each mark or material the CB has licensed to you, with artwork version and conditions. Store the approved artwork in one controlled place so nobody downloads a logo from the web. -->

| ID | Mark or material | Source | Conditions *(Example, confirm in CB rules)* | Artwork location |
|---|---|---|---|---|
| MRK-001 *(Example)* | CB certification mark for ISO/IEC 27001 | Issued by [CB name] with the certificate | Use only the supplied artwork, unaltered; keep minimum size and clear space; show with certificate number or standard reference where the CB requires | [brand asset library path] |
| MRK-002 *(Example)* | CB mark combined with accreditation body mark | Issued by [CB name] | Only if the CB allows; never the accreditation mark alone | [path] |
| MRK-003 *(Example)* | Copy of the certificate (PDF) | [CB name] | Whole document, unaltered, current version, with expiry date visible | [path] |
| MRK-004 *(Example)* | Approved text statements (section 7) | This document | Use word for word or with approved substitutions only | Section 7 |
| [MRK-NNN] | [mark] | [source] | [conditions] | [location] |

Not licensed to [Organization name] and never to be used: the ISO logo,
the IEC logo, the international recognition mark (legacy IAF MLA mark or
Global ACI MRA mark, unless the CB confirms otherwise in writing), any CB mark for a standard or scope you are
not certified for, and marks of other organizations in the group unless
their certificate covers you.

## 4. What you may claim

<!-- Guidance: Every claim must name the right entity, standard and edition, and stay within the certified scope. Questions to answer: what exactly is certified, where, and by whom? Pitfall: claiming the whole company is certified when the scope covers one service. -->

A correct claim has five elements:

1. **Who**: the legal entity on the certificate (not the brand, the group
   or a parent company, unless they are on the certificate).
2. **What**: the information security management system, not a product,
   service output, person or test result.
3. **Which standard**: ISO/IEC 27001:2022 (the edition on the
   certificate). Do not claim certification to ISO/IEC 27002, which is
   guidance and not certifiable, or to any standard you hold no
   certificate for.
4. **Scope**: the scope as printed, or a faithful short form approved in
   section 7. If the scope covers only some services or sites, say so.
5. **By whom**: the CB name, and the certificate number where useful so
   readers can verify it.

Claims about related work must be clearly separate: "aligned with",
"based on" or "following the guidance of" ISO/IEC 27002 or ISO/IEC
27017 is acceptable only when true and when it is not placed so as to
suggest certification. Statements about SOC 2 reports, other frameworks
or customer audits must not be merged into the ISO/IEC 27001 claim.

Readers may want to verify a certificate. Point them to the CB's
certificate directory and, where available, the accreditation system's
certificate search database (IAF CertSearch, the database of accredited
certifications set up under IAF; check whether it now operates under
Global ACI and whether your CB uploads to it).

## 5. Prohibited uses

<!-- Guidance: State prohibitions plainly. These reflect common CB rules and ISO's public position; your CB's rules may add more. Auditor check: none of these appear on the website, in proposals or on products. -->

| ID | Prohibited use | Why |
|---|---|---|
| PRH-001 | Any certification mark on a product, product packaging or product documentation, and any claim there that suggests the product is certified | ISO/IEC 27001 certifies a management system, not a product; CBs are required not to allow their marks to be used in a way that can be read as product conformity |
| PRH-002 | A mark or claim on laboratory test reports, calibration certificates or inspection reports | These imply product or result conformity, which management system certification does not give |
| PRH-003 | The ISO logo, in any form, or the words "ISO approved" or "certified by ISO" | ISO does not certify organizations and does not license its logo for this |
| PRH-004 | Claims that extend beyond the certified scope, sites or legal entity | Misleading; a frequent cause of CB findings |
| PRH-005 | Altered, recoloured, redrawn, cropped or animated marks | CB artwork must be used as supplied |
| PRH-006 | The accreditation body symbol on its own, or the international recognition mark (IAF MLA or Global ACI MRA) in any form | Accreditation body symbols are at most allowed inside a combined mark supplied by the CB; the international recognition mark is licensed to accreditation bodies and accredited CBs, not to certified organizations |
| PRH-007 | Any claim while the certificate is suspended, withdrawn or expired | The certification is not valid during those states |
| PRH-008 | Statements that the organization is "secure", "breach-proof" or "guaranteed compliant" because it is certified | Certification shows a conforming management system, not the absence of risk |
| PRH-009 | Use by a partner, reseller or group company not on the certificate as if it were their own certification | Misleading about who is certified |
| PRH-010 | Claims of certification before the CB's certification decision (for example after Stage 2 but before the decision) | The certificate does not exist until the decision |

## 6. Channels and placement

<!-- Guidance: Decide channel by channel what is allowed. Questions to answer: where does certification appear today, who controls each channel, and which channel needs approval every time? -->

| Channel | Allowed content | Status | Approval needed |
|---|---|---|---|
| Corporate website, security or trust page | Approved statement, CB mark (MRK-001), certificate copy, certificate number | Allowed | Once per page version |
| Proposals, bids, security questionnaires | Approved statement, certificate copy | Allowed | Standard wording pre-approved; changes need approval |
| Letterhead, business cards, e-mail signatures | CB mark with standard reference, if the CB allows on stationery | Conditional (check CB rules) | Once per template |
| Sales and investor presentations | Approved statement and mark on a company-level slide | Allowed | Once per master deck |
| Press releases and social media posts | Approved statement; mark only if CB rules allow in that medium | Conditional | Every time |
| Trade show stands and banners | Approved statement and mark at company level, not next to product displays | Conditional | Every time |
| Vehicles and buildings | CB mark only where CB rules explicitly allow | Conditional (often restricted) | Every time |
| Product user interface, product pages naming a single product | Statement that the ISMS covering the service is certified, linked to the trust page; no mark on the product itself | Conditional | Every time |
| Product packaging, labels, product documentation | No mark, ever. A plain statement naming the certified organization, the management system standard and the CB is something some CB rules allow in accompanying product information, never wording that implies a certified product; this policy's default is not to use it | Mark prohibited (PRH-001); statement only if CB rules allow and top management decides to use it | Every time, with the CB rule cited |
| Test reports, calibration or inspection documents | Not allowed | Prohibited (PRH-002) | Not applicable |
| Job adverts | Approved short statement | Allowed | Standard wording pre-approved |

## 7. Correct and incorrect wording

<!-- Guidance: Give writers ready-made sentences. Use the certified scope of the Example organization only as a model; replace with your own scope wording. -->

*Example* certificate: Quillmere Analytics Ltd, certified to ISO/IEC
27001:2022 by [CB name], certificate [number], scope "The information
security management system supporting the development, operation and
support of the Quillmere analytics SaaS platform".

Approved statements (*Example*):

- **Long form**: "Quillmere Analytics Ltd operates an information
  security management system certified to ISO/IEC 27001:2022 by [CB
  name] (certificate [number]) for the development, operation and
  support of the Quillmere analytics SaaS platform."
- **Short form**: "Our information security management system for the
  Quillmere analytics platform is certified to ISO/IEC 27001:2022."
- **Questionnaire answer**: "Yes. Quillmere Analytics Ltd holds ISO/IEC
  27001:2022 certification issued by [CB name], certificate [number],
  valid until [date]. The scope covers the development, operation and
  support of the Quillmere analytics SaaS platform. A copy of the
  certificate is attached."

| Incorrect wording | Problem | Correct alternative |
|---|---|---|
| "ISO certified company" | Does not name the standard; implies ISO certifies; implies whole company | "Our ISMS for [scope] is certified to ISO/IEC 27001:2022" |
| "Our software is ISO 27001 certified" | Implies product certification | "The information security management system that runs our platform is certified to ISO/IEC 27001:2022" |
| "Certified by ISO" | ISO does not certify | "Certified by [CB name]" |
| "ISO 27001 and ISO 27002 certified" | ISO/IEC 27002 is not certifiable | "Certified to ISO/IEC 27001:2022; controls implemented with guidance from ISO/IEC 27002:2022" |
| "Quillmere is certified across all its businesses" (Quillmere Analytics Ltd text) | Extends beyond legal entity and scope | Name the certified entity and scope |
| "Fully compliant with ISO 27001, so your data is 100 percent safe" | Overstates what certification means | "Our ISMS is certified to ISO/IEC 27001:2022 and audited by [CB name] each year" |
| "ISO 27001 certified (in progress)" or "certified, pending decision" | No certificate exists yet | "We are preparing for ISO/IEC 27001:2022 certification, with the certification audit planned for [month year]" |
| "ISO 27701 certified" (when only ISO/IEC 27001 is held) | Claims a certification not held | State only certificates held; describe privacy controls separately |
| The ISO logo next to the company logo | Prohibited (PRH-003) | Use the CB mark (MRK-001) under the CB rules |

## 8. Approval workflow

<!-- Guidance: Any new use of the mark or a new form of words goes through this workflow. Questions to answer: who checks against the CB rules, who signs off, and how long does it take? Auditor check: an approval record exists for the material the auditor finds. -->

```mermaid
flowchart TD
  A["Requester drafts content with certification reference"] --> B{"Uses only pre-approved statements and channels?"}
  B -- "Yes" --> C["Publish and log in approval log"]
  B -- "No" --> D["Submit to ISMS manager with draft and channel"]
  D --> E["Check against CB rules, scope and section 5 prohibitions"]
  E --> F{"Compliant?"}
  F -- "No" --> G["Return with corrections"]
  G --> A
  F -- "Yes" --> H{"New channel or mark use not covered by CB rules?"}
  H -- "Yes" --> I["Ask CB in writing, keep reply"]
  I --> J["Marketing lead and ISMS manager approve"]
  H -- "No" --> J
  J --> C
```

*Example* service level: decision within 5 working days, or 10 working
days when the CB must be asked.

Approval log:

| Approval ID | Date | Requester | Material and channel | Statement or mark used | Decision | Approver | Withdrawal date if status changes |
|---|---|---|---|---|---|---|---|
| MUA-2027-001 *(Example)* | 2027-06-16 | [@marketing-lead] | Press release, certification news | Long form, MRK-001 | Approved | [@isms-manager] | Not applicable |
| MUA-2027-002 *(Example)* | 2027-06-18 | [@marketing-lead] | Website trust page | Long form, MRK-001, MRK-003 | Approved | [@isms-manager] | Not applicable |
| MUA-2027-003 *(Example)* | 2027-07-02 | [@sales-lead] | Product data sheet with mark in header | MRK-001 | Rejected: product documentation (PRH-001); short form statement allowed in company section | [@isms-manager] | Not applicable |
| MUA-2028-001 *(Example)* | 2028-03-07 | [@marketing-lead] | Website footer correction | Short form | Approved | [@isms-manager] | Not applicable |
| [MUA-YYYY-NNN] | YYYY-MM-DD | [@requester] | [material] | [statement] | [decision] | [@approver] | [date] |

## 9. Changes in certificate status

<!-- Guidance: Plan the response before it is needed. A suspension requires all claims to stop quickly; keep a list of where claims appear so you can find them. Pitfall: an old certificate copy still downloadable after expiry or a scope reduction. -->

| Event | Required action | Deadline *(Example, confirm in CB rules)* | Owner |
|---|---|---|---|
| Certificate suspended | Stop all claims and mark use; remove certificate copies; tell sales and partners; answer questionnaires truthfully | Immediately, per CB rules | ISMS manager and marketing |
| Certificate withdrawn | Remove all claims and marks permanently; update contracts where required | Immediately, per CB rules | ISMS manager, legal |
| Scope reduced | Update all statements to the new scope; replace certificate copies | Per CB rules (*Example*: before the next publication or within 30 days) | ISMS manager |
| Certificate renewed after recertification | Replace certificate copies with the new one; update expiry dates | Within *Example* 10 working days of receipt | ISMS manager |
| Certificate expired | Remove claims until a new certificate is issued | Immediately | ISMS manager |
| Change of CB | Replace old CB mark and certificate with the new CB's; update statements | When the new certificate is issued | ISMS manager |
| Scope extended | Update statements only after the CB issues the updated certificate | On receipt of the updated certificate | ISMS manager |

Keep a **claims inventory**: every page, template, deck and partner
listing that shows the certification, with owner. The approval log in
section 8 is the starting point.

## 10. Monitoring and handling misuse

<!-- Guidance: Check use regularly, including by others. Questions to answer: who searches for misuse, how often, and what happens when it is found? -->

- Review the claims inventory every quarter and before each CB audit
  (`isms/surveillance-readiness-health-check`, area G).
- Search the public web and partner sites for the organization's name
  together with "ISO 27001" at least twice a year.
- Brief new marketing, sales and bid staff on these rules during
  onboarding; include them in the communication plan (DOC-ISMS-027).
- Ask partners and resellers to follow these rules in their agreements.

When misuse is found:

1. Record it as a nonconformity under clause 10.2 when it comes from
   inside the organization or from someone acting for it.
2. Correct or remove the material and record the date.
3. Find the root cause (missing approval step, unclear wording, outdated
   template) and fix it.
4. If a third party misuses the certification, ask them in writing to
   correct it, and tell the CB if they refuse or if the misuse is
   significant.
5. Tell the CB about significant misuse by the organization before the
   next audit rather than waiting for the auditor to find it.

## 11. Size tiers

<!-- Guidance: The rules are the same for all; the number of channels, writers and partners changes. These tiers are the library's working tiers, not official definitions. -->

| Aspect | Small: Quillmere Analytics Ltd (46 staff) | Medium: Quillmere Health Systems (320 staff) | Large or multi-site: Quillmere Group (2,400 staff, 6 sites) |
|---|---|---|---|
| Who approves | Part-time ISMS manager, with the CEO for press releases | ISMS manager and marketing lead; legal for contracts | Group CISO office with group communications; site managers for local material |
| Channels | Website, trust page, proposals, questionnaires | Plus hospital tenders, conference stands, partner portals | Plus multiple country websites, product brochures for plants, OT customer documents |
| Main risk | Website wording written once and never checked | Tender teams copying old wording with an outdated scope | Sites not yet in the phased scope using the group claim; plant product documents carrying the mark (PRH-001) |
| Specific control | Pre-approved short and long forms only | Claims inventory with an owner per channel | Site-level claims list showing which sites are in the certified scope; separate wording for ISO 9001 and ISO 22301 certificates so claims are not mixed |
| Multi-certificate wording | One certificate | ISO/IEC 27001 now; add ISO/IEC 27701:2025 wording only after that certificate is issued | Separate statements per certificate and per scope; combined marks only if the CB rules allow |

## 12. Records and evidence

<!-- Guidance: List the records that prove the rules operate. The CB may ask for them at surveillance. Map them in the control evidence matrix. -->

| Record | Owner | Location | Retention *(Example)* |
|---|---|---|---|
| CB rules and certification agreement, each version | ISMS manager | Certification folder | Life of certificate plus one cycle |
| Licensed artwork and certificate copies | Marketing | Brand asset library, controlled folder | Current only, previous versions archived |
| Approval log | ISMS manager | Section 8 of this document | Life of certificate plus one cycle |
| Claims inventory and quarterly reviews | Marketing | Claims inventory sheet | Current and previous cycle |
| CB replies to questions about mark use | ISMS manager | Certification folder | Life of certificate plus one cycle |
| Misuse records and corrective actions | ISMS manager | `compliance/capa-nonconformity`, DOC-ISMS-086 | Per DOC-ISMS-028 |
| Training or briefing records for writers | HR or marketing | Competence records (DOC-ISMS-026) | Per DOC-ISMS-028 |

Map these records in `isms/control-evidence-matrix` (DOC-ISMS-033)
under clause 7.4 (communication) and clause 10.2.

## 13. References

<!-- Guidance: Cite editions exactly and check for newer ones before use. CB and accreditation rules change more often than standards; check them at each review. -->

| Reference | Edition | Use |
|---|---|---|
| ISO/IEC 27001:2022 + Amd 1:2024 | https://www.iso.org/standard/82875.html ; Amd 1: https://www.iso.org/standard/88435.html | The certified standard; clause 7.4 communication |
| ISO/IEC 17021-1:2015 | https://www.iso.org/standard/61651.html | CB control of marks and references to certification (clause 8.3) |
| ISO/IEC 27006-1:2024 | https://www.iso.org/standard/82908.html | ISMS-specific CB requirements |
| ISO public guidance on publicizing certification | Current version on iso.org | ISO's position on its logo and on wording |
| Global ACI MRA documents on the use of the recognition mark | Current version on the Global ACI website | Rules for the international recognition mark and the transition from legacy IAF and ILAC marks |
| Your CB's rules for use of certificates and marks | Current version | Binding artwork and wording rules |

Related templates: `isms/certification-cycle-plan` (DOC-ISMS-094),
`isms/surveillance-readiness-health-check` (DOC-ISMS-096),
`isms/security-whitepaper-trust-center` (DOC-ISMS-116),
`isms/security-questionnaire-answer-library` (DOC-ISMS-115),
`isms/customer-security-addendum` (DOC-ISMS-117),
`isms/isms-communication-plan` (DOC-ISMS-027),
`compliance/ms-scope` (DOC-ISMS-002).

## Standard and licence note

Structure aligned with ISO/IEC 27001:2022 + Amd 1:2024 clause 7.4 and
with the certification body obligations on marks and references to
certification in ISO/IEC 17021-1:2015. The rules, wording examples and
guidance are original and summarize common certification body practice;
no ISO or IEC text is reproduced. Your certification body's rules and
agreement are binding and prevail over this template: obtain them,
together with the official standards (purchase or licensed access from
ISO, IEC or your national standards body). Check the current edition of
each standard and the current accreditation system rules before use.
This is a documentation format, not legal advice. Template licence: MIT.