Disclosure focus
Critical concerns include concerns about the organization’s potential and actual negative impacts on stakeholders that are raised through grievance mechanisms or other processes. They also include concerns identified through other mechanisms about the organization’s business conduct in its operations and business relationships.
Critical concerns can therefore arise through grievance mechanisms, whistleblowing and ethics channels, compliance or legal investigations, internal audit, risk-management processes, human rights due diligence, regulatory interactions and other processes. Not every complaint, hotline report, risk or routine management update is a critical concern. The organization should apply documented criticality criteria that are consistent with the scope described in the GRI Guidance.
The highest governance body is the governance body with the highest authority in the organization. The term “Board” should be used only where the Board is the organization’s highest governance body. Where concerns are first communicated to a committee, the organization should identify whether it is a committee of the highest governance body, describe its authority and explain how the concerns are communicated to the full highest governance body or otherwise treated as formally communicated to it.
The communication-process description should explain the main sources of critical concerns, who assesses whether a concern is critical, the routine and urgent escalation routes, the recipient governance body and the communication format. Routine reporting should not be included in the total unless it communicates a critical concern.
The reported total should normally represent distinct critical concerns communicated during the reporting period, rather than the number of emails, updates, meetings or Board papers. The organization should document how it treats continuing concerns, recurring concerns and multiple communications concerning the same matter.
The nature of the concerns can be reported through high-level, aggregated categories, such as occupational health and safety, human rights, business conduct, corruption, data protection or supply-chain conduct. Disclosure of identifying case details is not required.
If no critical concerns were communicated during the reporting period, the organization should report a total of zero and state this clearly.
Reasons for omission are permitted for Disclosure 2-16. Before omitting information because of confidentiality, the organization should consider whether it can report the total and provide aggregated or anonymised information on the nature of the concerns. Where a requirement cannot be reported, the organization must identify the affected requirement and provide an applicable reason for omission and the required specific explanation in its GRI content index.
This LRA educational guidance supports disclosure preparation. For the exact requirements, always refer to the official GRI source.
Prepare
What to collect before drafting
Tick each field as the evidence lands. Owners are the teams that usually hold the source files.
-
Communication of critical concerns
Company Secretariat / LegalDescribe whether and how critical concerns are communicated to the highest governance body.
Evidence Dated source records, governance papers and approval evidence supporting communication of critical concerns.
Watch for The published response for communication of critical concerns is incomplete or does not match the supporting records.
-
Total number and nature
Company Secretariat / LegalReport distinct critical concerns communicated during the period and describe their nature in suitable aggregated categories.
Evidence Dated source records, governance papers and approval evidence supporting total number and nature.
Watch for The published response for total number and nature is incomplete or does not match the supporting records.
Before you start
- Apply documented criticality criteria consistent with GRI Guidance; not every complaint, risk, hotline report or routine update is a critical concern.
- If concerns first reach a committee, identify its status and explain how they are formally communicated to the highest governance body.
- Have the supporting records and the final response been reconciled?
How to prepare it
Request the data
Request the disclosure evidence
Translate the disclosure into an internal business question — then adapt it to your organisation's own language.
Provide the critical-concern definition and escalation route, the distinct concerns communicated during the period, their aggregated nature and evidence of communication to the highest governance body.
Use the organisation's own role and document names, but preserve the defined GRI terms and the scope described above.
Better request
Provide the critical-concern definition and escalation route, the distinct concerns communicated during the period, their aggregated nature and evidence of communication to the highest governance body.
Draft your disclosure
Notes that turn data into a disclosure
LRA training templates — adapt them to your organisation, and check the official source before sign-off.
Method note
Count distinct critical concerns, not emails, updates, meetings or papers, and document treatment of recurring or continuing matters.
Context note
Report zero clearly where no critical concerns were communicated; use aggregated or anonymised categories before considering confidentiality omission.
Download Centre
Preparation tools & forms
Download preparation tools for GRI 2-16 with free verified email access for 24 hours. Source-report links remain public.
Check
For each claim, check the evidence
Communication of critical concerns is reported accurately and completely.
Risk The response omits, misclassifies or overstates communication of critical concerns.
Evidence to check Dated source records, governance papers and approval evidence supporting communication of critical concerns.
Total number and nature is reported accurately and completely.
Risk The response omits, misclassifies or overstates total number and nature.
Evidence to check Dated source records, governance papers and approval evidence supporting total number and nature.
Evidence pack to prepare
Common reporting gaps
- Replacing critical concerns with serious issues.
- Counting communications rather than distinct concerns.
- Equating receipt by a management committee with communication to the highest governance body.
- Describing confidential case details instead of aggregated nature.
- Estimating or rounding the required total.
Ask the Knowledge Hub AI Assistant about this disclosure
Get practical answers for your reporting context.
Check your text
Paste one or two paragraphs. The fragment is used for this check only and is not stored in your conversation.
Peer comparison uses examples on this card, not prevalence in the report corpus.
Advice, not assurance
Framework references
Relevant GRI requirements and related disclosures
GRI
GRI 2-16
within GRI 2: General Disclosures
Guides that settle this question
Related & explore
More in GRI 2 →Browse full catalogue →Search all disclosures →