Перейти к сути раскрытия

Библиотека раскрытийПрактическое руководство по каждому раскрытию в отчётности

GRI 416: Customer Health and Safety·Disclosure GRI 416-2

Incidents of non-compliance concerning the health and safety impacts of products and services

Практическое руководство по подготовке этого раскрытия. Используйте карточку, чтобы определить, какую информацию подготовить, проверить утверждения и организовать подтверждающие доказательства. За точными требованиями всегда обращайтесь к официальному источнику Global Reporting Initiative.

Правовой статус

GRI 416: Customer Health and Safety 2016 remains the applicable published GRI Topic Standard and is effective for reports or other materials published on or after 1 July 2018.

Опубликованный паспорт

Последняя проверка 2026-08-03
RK Проверил Dr Ross KurinkoLinkedIn Strategic ESG Advisor · IFRS S1 & S2 / GRI / ESRS expert GRI Certified Global Trainer · PhD, University of Cambridge · ESG-AI expert 15+ years on FTSE 100 & Fortune Global 500 disclosures Canary Wharf, London Учебные материалы LRA · Не выпущено и не одобрено Global Reporting Initiative

Стандарт

GRI 416: Customer Health and Safety

Disclosure GRI 416-2 · 2016

Вступает в силу

2018-07-01

Официальный источник: Открыть ↗

Последняя проверка

2026-08-03

Учебные материалы LRA · Не выпущено и не одобрено Global Reporting Initiative

Суть раскрытия

This disclosure requires the organization to report incidents of non-compliance with regulations and voluntary codes concerning the health and safety impacts of products and services.

Report the incidents separately as:

regulatory non-compliance resulting in a fine or penalty;

regulatory non-compliance resulting in a warning; and

non-compliance with voluntary codes.

The disclosure concerns non-compliance rather than every complaint, defect, recall, adverse event or safety concern. Actual customer harm is not required, but an incident of non-compliance must be established.

Exclude incidents where the organization was determined not to be at fault and incidents related to product and service information or labelling.

Where an incident reported in the current period relates to an event from an earlier period, identify that fact.

If no incidents were identified, a brief statement confirming this is sufficient.

The disclosure does not require incident rates, fine values, corrective-action outcomes or a description of every individual case.

Это учебное руководство LRA помогает в подготовке раскрытия. За точными требованиями всегда обращайтесь к официальному источнику Global Reporting Initiative.

Прежде чем начать

Прежде чем начать

Короткий чек-лист перед подготовкой этого раскрытия — отмечайте пункты по мере их закрытия.

Подготовка

Ключевая информация для подготовки

Поле подготовки Что зафиксировать Подсказка по доказательствам Ответственный
Incident population Potential product or service health and safety non-compliance matters identified across applicable systems. Legal, regulatory, quality, recall, complaint and voluntary-code records. Product Safety / Regulatory / Legal
Applicable requirement Regulation or voluntary code associated with each matter. Legal register, code documentation and assessment record. Legal / Compliance
Non-compliance conclusion Evidence that non-compliance occurred and that the organization was not determined to be without fault. Regulator decision, investigation or code-review outcome. Legal / Regulatory
Fine or penalty incidents Regulatory incidents resulting in a fine or penalty. Penalty notices, regulator decisions and payment records. Legal / Finance
Warning incidents Regulatory incidents resulting in a warning. Warning letters, official notices and decisions. Regulatory / Legal
Voluntary-code incidents Incidents of non-compliance with voluntary health and safety codes. Code assessment and internal or external determination. Product Safety / Compliance
Labelling exclusion Matters transferred to GRI 417-2. Incident classification and labelling records. Regulatory / Sustainability
Not-at-fault exclusion Incidents excluded because the organization was determined not to be at fault. Investigation and determination records. Legal
Prior-period event link Current-period incidents relating to events in earlier reporting periods. Event, resolution and reporting-period dates. Legal / Sustainability
Final category counts Exact counts for the three required categories. Controlled incident register and reconciliation. Sustainability Reporting
Zero statement — if applicable Confirmation that no relevant non-compliance was identified. Cross-functional search and sign-off. Legal / Product Safety
+ Показать подпункты GRI 416-2 (рабочий чек-лист LRA)

Как это подготовить

Identify applicable product and service health and safety regulations.
Identify applicable voluntary health and safety codes.
Consolidate potential matters from legal, regulatory, quality, complaint, recall and product-safety systems.
Create one incident-level register and remove duplicates.
Determine whether each matter represents established non-compliance.
Exclude matters where the organization was determined not to be at fault.
Exclude information and labelling matters for GRI 417-2.
Classify regulatory incidents as resulting in a fine or penalty or resulting in a warning.
Classify incidents involving voluntary-code non-compliance.
Record the underlying event date, outcome date and resolution date.
Identify incidents relating to prior-period events.
Calculate the three exact category counts.
Reconcile the counts to the incident register.
Where all category counts are zero, prepare the brief no-incidents statement.
Apply an applicable reason for omission where required information cannot be reported.
Verify the final disclosure against GRI 416-2(a)–(b) and 2.1.1–2.1.3.

Запросить данные

Request the disclosure evidence

Переведите раскрытие на язык внутреннего бизнес-вопроса, а затем адаптируйте его под терминологию вашей организации.

Please provide the product and service health and safety compliance register for [reporting period]. For each potentially relevant matter, include: controlled incident ID; product or service category; country and legal entity; applicable regulation or voluntary code; description of the alleged non-compliance; date of the underlying event; date non-compliance was determined; formal resolution date; whether the matter resulted in a fine or penalty; whether it resulted in a regulatory warning; whether it involved a voluntary-code breach; whether the organization was determined not to be at fault; whether the matter concerns information or labelling; recall, complaint or adverse-event references; evidence source; and reporting classification. Please also provide the reconciled counts for the three GRI 416-2 categories.

Use the organisation's own role and document names, but preserve the defined GRI terms and the scope described above.

Более удачный запрос

Please provide the product and service health and safety compliance register for [reporting period]. For each potentially relevant matter, include: controlled incident ID; product or service category; country and legal entity; applicable regulation or voluntary code; description of the alleged non-compliance; date of the underlying event; date non-compliance was determined; formal resolution date; whether the matter resulted in a fine or penalty; whether it resulted in a regulatory warning; whether it involved a voluntary-code breach; whether the organization was determined not to be at fault; whether the matter concerns information or labelling; recall, complaint or adverse-event references; evidence source; and reporting classification. Please also provide the reconciled counts for the three GRI 416-2 categories.

Составьте раскрытие

Заметки, которые превращают данные в раскрытие

Учебные шаблоны LRA — адаптируйте их под вашу организацию и сверьтесь с официальным источником перед утверждением.

Примечание о методике

Incidents were classified using the applicable product and service health and safety regulations and voluntary codes. Matters where the organization was determined not to be at fault and information or labelling incidents were excluded.

Примечание о контексте

Keep mandatory GRI Requirements, GRI recommendations and additional LRA preparation controls clearly distinguished. Apply a GRI 1 reason for omission where required information cannot be reported.

Центр загрузок

Инструменты и формы для подготовки

Профессиональные инструменты подготовки для GRI 416-2 — бесплатно с членством в LRA Community. Зарегистрируйтесь один раз (это бесплатно), и откроются все загрузки, а вместе с ними Библиотека раскрытий, шаблоны и AI-ассистент LRA.

Бесплатно · Участникам сообщества

Готовность к заверению

Для каждого утверждения проверьте доказательства

Утверждение Риски Доказательства для проверки
We identified the applicable product and service health and safety regulations.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
We identified the applicable voluntary health and safety codes.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
We consolidated potentially relevant matters from all applicable source systems.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
We counted incidents rather than complaints, products, recalls, affected customers or regulator documents.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Customer complaints were not treated automatically as incidents of non-compliance.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Recalls and safety notices were not treated automatically as incidents of non-compliance.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Adverse-event and vigilance reports were not treated automatically as incidents of non-compliance.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Every included matter has evidence that non-compliance occurred.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Actual customer harm was not used as a condition for inclusion.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Hazards and near misses without established non-compliance were not included.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Incidents where the organization was determined not to be at fault were excluded.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Information and labelling incidents were excluded for GRI 417-2.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Regulatory incidents resulting in a fine or penalty were reported separately.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Regulatory incidents resulting in a warning were reported separately.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Voluntary-code incidents were reported separately.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Preliminary observations and information requests were not classified automatically as warnings.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Duplicate records across legal, quality, complaint and regulatory systems were removed.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Incidents relating to prior-period events were identified where applicable.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
A prior-period event formally resolved in the current period was not excluded automatically.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Older open matters were not counted solely because they remained active.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Incident counts are exact whole numbers and were not estimated or rounded.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
The overall total, where shown, reconciles to the three categories.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
The zero statement, where used, is supported across the reporting boundary.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.
Any unavailable required information is addressed through the applicable GRI reason-for-omission requirements.The published response does not support this human-reviewed assurance check.Trace the statement to current approved records and the official IFRS source.

Пакет доказательств для подготовки

Типичные пробелы в отчётности

Only one aggregate incident count is disclosed.
The three required categories are not reported separately.
Only fines and penalties are reported.
Warnings are omitted.
Voluntary-code incidents are omitted.
The report states that no fines occurred but does not address warnings or voluntary codes.
The report states that no material incidents occurred rather than confirming whether any incidents occurred.
Actual customer harm is used as a condition for inclusion.
Every complaint is counted as non-compliance.
Every recall is counted as non-compliance.
Every adverse-event or vigilance report is counted.
A product defect is counted without identifying a breached regulation or voluntary code.
Preliminary regulator observations are counted as warnings.
Information and labelling incidents are included instead of being reported under GRI 417-2.
Cases where the organization was determined not to be at fault are included.
Prior-period events formally resolved in the current period are excluded automatically.
Old open matters are included solely because they remained active.
Several notices concerning one matter are counted as several incidents without a methodology.
Products, batches, customers or recalls are counted instead of incidents.
Incident counts are estimated or rounded.
An incidence rate is presented instead of the required counts.
A zero result is implied but not stated.
The published counts cannot be reconciled to incident records.

Примеры

Иллюстративные примеры

Синтетические, написаны LRA — это не выдержки из отчёта компании и не текст какого-либо стандарта.

Illustrative example 1

Illustrative synthetic example — Consumer goods manufacturing
During the reporting period:
one incident of regulatory non-compliance resulted in a fine;
one incident of regulatory non-compliance resulted in a warning; and
no incidents of non-compliance with voluntary codes were identified.
The warning related to a product event from the previous reporting period and was formally resolved in the current period.
Two additional product recalls were reviewed but were not included because they did not result from non-compliance with a relevant regulation or voluntary code.

Synthetic LRA illustration. Replace every figure and fact with the reporting organisation's evidence.

Illustrative example 2

Illustrative synthetic example — Online retail and logistics
During the reporting period:
no regulatory incidents resulted in a fine or penalty;
one regulatory incident resulted in a warning; and
one incident involved non-compliance with a voluntary product-safety code.
One additional customer complaint was excluded because the review did not identify non-compliance. One product-information matter was transferred to GRI 417-2.

Synthetic LRA illustration. Replace every figure and fact with the reporting organisation's evidence.

Illustrative example 3

Illustrative synthetic example — Zero incidents
No incidents of non-compliance with regulations or voluntary codes concerning the health and safety impacts of products and services were identified during 2026.

Synthetic LRA illustration. Replace every figure and fact with the reporting organisation's evidence.

Illustrative example 4

Illustrative treatment — organization not at fault
A regulator reviewed a customer-safety allegation and determined that the organization was not at fault. The matter was excluded from the GRI 416-2 counts.

Synthetic LRA illustration. Replace every figure and fact with the reporting organisation's evidence.

Illustrative example 5

Illustrative treatment — labelling
One incident concerned missing safety information on a product label. It was excluded from GRI 416-2 and reported under GRI 417-2.

Synthetic LRA illustration. Replace every figure and fact with the reporting organisation's evidence.

Отчёты компаний

Как компании раскрывают GRI 416-2 на практике

Примеры полного и частичного раскрытия на практике. Это разборы на основе доказательств, а не готовые шаблоны для копирования.

Реальные опубликованные отчёты
Zydus Lifesciences Limited
Pharmaceuticals / Biotech / Life Sciences · India · 2025
Открыть отчёт →

Zydus Lifesciences’ current card relies on the wrong disclosure.

Report page 134 states that there were no incidents concerning product and service information and labelling and marketing communications. This information relates to GRI 417-2 and GRI 417-3, not GRI 416-2.

The substantive product-quality information is on report page 50. The report discloses:

zero Class I recalls;

54 Class II recalls;

12 Form 483 observations or equivalent; and

one FDA warning letter or equivalent.

The GRI index maps Product Recalls to GRI 416-1 and GRI 416-2.

The card should:

replace page 135 with report page 50 as the principal substantive source;

remove the product-information and labelling zero result from GRI 416-2;

recognize the one FDA warning letter as potentially relevant to the regulatory-warning category;

avoid treating every recall or Form 483 observation automatically as a GRI 416-2 incident;

determine whether any incidents resulted in a fine or penalty;

determine whether any incidents involved non-compliance with voluntary codes;

confirm how the 54 recalls were classified against the GRI requirement; and

classify the disclosure as partial or requiring category-level reassessment.

Materiality and general risk-management information on page 148 is not required to complete Disclosure 416-2.

The official report contains separate product-recall, regulatory-observation and warning-letter information, while the cited labelling statement belongs to a different GRI disclosure.

Owens Corning
Building Products · United States · 2024
Открыть отчёт →

Owens Corning’s 2024 Sustainability Report states on report page 184 that the company had no material incidents of non-compliance concerning the health and safety of its products.

Its GRI index maps GRI 416-2(a) to None and GRI 416-2(b) to page 184.

The wording does not provide a fully aligned zero response because GRI 416-2 requires all incidents of non-compliance, not only incidents classified as material.

The card should:

remove the parental-leave return-to-work figure;

remove the SCS Global Services independence and competence statement;

use report page 184 as the substantive reference;

quote or paraphrase the company’s no material incidents wording accurately;

explain that no material incidents does not necessarily mean zero incidents;

assess whether the company can confirm zero incidents across the three GRI categories; and

classify the response as partial or imprecise rather than a complete zero disclosure.

No additional governance or assurance narrative is required solely for GRI 416-2.

Owens Corning’s report uses a materiality qualifier, while its GRI index indicates that the detailed incident-count requirement is not separately reported.

Thai Beverage Public Company Limited
Food and Beverage Processing · Thailand · 2024
Открыть отчёт →

Thai Beverage provides an adequate zero-incidents response on report page 92.

The report states that:

there were zero incidents of non-compliance with regulations or voluntary codes concerning the health and safety impacts of products and services; and

no regulatory incidents resulted in a fine, penalty or warning.

The broad zero statement is sufficient under GRI 416-2(b). Separate category details are not required when no incidents occurred.

The card should:

use report page 92 as the substantive reference;

retain the zero-incidents conclusion;

remove all child-labor references;

remove all forced-labor references;

remove supply-chain-management gaps;

state that no prior-period incident identification is applicable unless an incident exists; and

classify the disclosure as an adequate zero response.

ThaiBev explicitly reports zero incidents of non-compliance concerning the health and safety impacts of products and services.

Сравнить бок о бок →

✓ AI-ассистент LRA · С участием человека
Dr Ross Kurinko

Спросите AI-ассистента Study Studio об этом раскрытии

Получайте практические ответы для вашего контекста отчётности. Первые два ответа бесплатны — вступите в LRA Community бесплатно, чтобы продолжить без ограничений.

Попробуйте Как подготовить GRI 416-2? Какие данные нужно собрать? Где посмотреть пример из реального отчёта? Каких ошибок избегать?
2 бесплатных ответа

Ссылки на стандарты

Соответствующие требования GRI и смежные раскрытия

Доступные ссылки на стандарты и близкие раскрытия, полезные при подготовке этого требования.

GRI

GRI 416-2

в составе GRI 416: Customer Health and Safety

Открыть официальный источник →

Связанное и другое

Больше в GRI 416 → Открыть полный каталог → Главная Библиотеки раскрытий → Искать по всем раскрытиям →

Углубиться · GRI 416-2

Научитесь готовить это раскрытие от начала до конца

This guide covers the three incident categories, the conditional zero statement and the compilation rules required by GRI 416-2.

Available as Guided Flex, Live Cohort, 1:1 Expert Mentorship or Corporate Programme.

Explore GRI training (ESRS bundle) →
Как построена эта библиотека 312 опубликованных отчётов проиндексировано 63 171 страниц с постраничными ссылками 272 карточек раскрытий, созданных практиками
/ru/knowledge-hub/disclosure-cards/gri-416-2/