Skip to the disclosure focus

GRI Training Partner GRI 2 · General Disclosures · Disclosure GRI 2-26

Mechanisms for seeking advice and raising concerns

GRI 2-26 · mandatory · narrative disclosure

Disclosure 2-26 requires an organization to describe the mechanisms through which individuals can seek advice on implementing its policies and practices for responsible business conduct and raise concerns about its business conduct.

Disclosure focus

The disclosure covers responsible business conduct in the organization’s operations and business relationships. It should not be limited automatically to internal employee channels. The organization should identify the intended users of each mechanism, which can include employees, other workers, contractors, suppliers, business partners or other individuals.

Advice mechanisms help individuals understand and apply the organization’s responsible-business-conduct policies and practices before or while making a decision. Examples can include line-management escalation processes, Ethics or Compliance advisers, Legal helpdesks, dedicated advice lines or confidential interviews. A policy document or intranet page does not by itself constitute an advice mechanism unless individuals can use the arrangement to obtain guidance.

Concern-reporting mechanisms enable individuals to report suspected wrongdoing, breaches of law or other concerns about the organization’s business conduct in its operations or business relationships, regardless of whether the individuals themselves have been harmed. Examples can include confidential interviews during site visits, management escalation processes, hotlines, non-compliance reporting mechanisms and whistleblowing mechanisms.

These mechanisms should be distinguished from grievance mechanisms reported under Disclosure 2-25. Grievance mechanisms enable affected or potentially affected stakeholders to raise concerns about negative impacts on them and seek remedy or remediation. Where one channel performs both grievance and whistleblowing functions, the organization can provide a single operational description but should explain the different functions, users and processes covered.

For each mechanism, the organization can explain its intended users, how it operates, the level or function responsible for it, whether it is operated independently by a third party, how concerns are investigated, whether requests and concerns are treated confidentially, and whether anonymous use is possible.

The organization can also report how intended users are informed and trained, the hours and days the mechanism is available, the languages offered, how users’ human rights are respected, how users are protected against retaliation, and how user satisfaction is assessed.

Quantitative information is optional. The organization can report the number and types of advice requests and the percentage answered, and the number and types of concerns and the percentages addressed, resolved or found to be unsubstantiated. Where such data are reported, advice requests and concerns should be counted separately and all statuses and denominators should be defined.

The existence of several channels or a high closure rate does not by itself demonstrate an accessible, trusted or effective mechanism. Mechanism design, intended users, confidentiality, anonymity, investigation, non-retaliation, accessibility and user experience provide necessary context.

If the organization uses one channel for both advice and raising concerns, the disclosure should state both functions explicitly. Where a channel also handles grievances, the disclosure should distinguish the GRI 2-25 remediation function from the GRI 2-26 business-conduct function.

If an advice or concern-reporting mechanism does not exist, the organization should report this fact directly. Reasons for omission are permitted for Disclosure 2-26 where required information exists but cannot be reported. In that case, the affected requirement, applicable reason and required explanation must be provided in the 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.

  • Mechanisms for seeking advice

    Legal / Compliance

    Describe mechanisms through which individuals can seek advice on implementing responsible-business-conduct policies and practices.

    Evidence Dated source records, governance papers and approval evidence supporting mechanisms for seeking advice.

    Watch for The published response for mechanisms for seeking advice is incomplete or does not match the supporting records.

  • Mechanisms for raising concerns

    Legal / Compliance

    Describe mechanisms through which individuals can raise concerns about business conduct in operations and business relationships.

    Evidence Dated source records, governance papers and approval evidence supporting mechanisms for raising concerns.

    Watch for The published response for mechanisms for raising concerns is incomplete or does not match the supporting records.

Before you start

  • Identify intended users across operations and business relationships; do not limit the disclosure automatically to internal employee channels.
  • Where one channel serves advice, concern-reporting and grievance functions, explain each function, user group and process separately.
  • Have the supporting records and the final response been reconciled?
+ Show GRI 2-26 sub-elements (LRA working checklist)

How to prepare it

Identify intended users across operations and business relationships; do not limit the disclosure automatically to internal employee channels.
Collect and reconcile the records for: Mechanisms for seeking advice; Mechanisms for raising concerns.
Where one channel serves advice, concern-reporting and grievance functions, explain each function, user group and process separately.
Draft the response using the defined terms shown in the disclosure focus; do not substitute broader internal labels.
Review the final wording against every requirement and the supporting governance or data records before sign-off.

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 mechanism inventory, intended-user mapping, operating procedures, responsible functions, investigation process, confidentiality, anonymity, non-retaliation and accessibility evidence.

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

Better request

Provide the mechanism inventory, intended-user mapping, operating procedures, responsible functions, investigation process, confidentiality, anonymity, non-retaliation and accessibility evidence.

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 advice requests separately from concerns where optional metrics are used and define all statuses and denominators.

Context note

State directly where an advice or concern-reporting mechanism does not exist.

Download Centre

Preparation tools & forms

Download preparation tools for GRI 2-26 with free verified email access for 24 hours. Source-report links remain public.

Free · Email access

Check

For each claim, check the evidence

  • Mechanisms for seeking advice is reported accurately and completely.

    Risk The response omits, misclassifies or overstates mechanisms for seeking advice.

    Evidence to check Dated source records, governance papers and approval evidence supporting mechanisms for seeking advice.

  • Mechanisms for raising concerns is reported accurately and completely.

    Risk The response omits, misclassifies or overstates mechanisms for raising concerns.

    Evidence to check Dated source records, governance papers and approval evidence supporting mechanisms for raising concerns.

Evidence pack to prepare

Common reporting gaps

  • Treating a policy document or intranet page as an advice mechanism.
  • Limiting the scope to employees.
  • Combining advice requests and reported concerns in one metric.
  • Failing to distinguish GRI 2-25 grievance and remediation functions.
  • Using channel counts or closure rates as proof of accessibility or effectiveness.
✓ Knowledge Hub AI Assistant · Human-in-the-loop
Dr Ross Kurinko

Ask the Knowledge Hub AI Assistant about this disclosure

Get practical answers for your reporting context.

Try How do I prepare GRI 2-26? What data do I need to collect? What mistakes should I avoid?

Framework references

Relevant GRI requirements and related disclosures

GRI

GRI 2-26

within GRI 2: General Disclosures

Open official source →

Guides that settle this question

Related & explore

More in GRI 2 →Browse full catalogue →Search all disclosures →

How this library is built 1,211 published reports indexed 315,012 pages with page-level citations 272 published cards in the active catalogue
/en/knowledge-hub/disclosure-cards/gri-2-26/