Disclosure LibraryPractitioner guidance for every reporting disclosure
Home Disclosure Library GRI GRI 2 GRI 2-26
GRI 2: General Disclosures
Disclosure GRI 2-26

Mechanisms for seeking advice and raising concerns

Practical guidance for preparing this disclosure. Use this card to identify datapoints, verify claims and organise supporting evidence. For exact requirements, always refer to the official GRI source.

Dr Ross Kurinko, GRI Certified Trainer
Reviewed by Dr Ross Kurinko · GRI Certified Trainer LRA educational guidance · Not issued or endorsed by GRI
To prepare this disclosure
Disclosure focus

This disclosure asks an organisation to explain how people can get advice, raise questions, or report concerns about the organisation’s conduct. In practice, it is about the channels that are available, how people are expected to use them, and whether those channels are open to the groups that need them, such as workers, contractors, or other relevant stakeholders.

The practical focus is on coverage and accessibility, not just the existence of a single hotline or policy. An organisation should think about whether the mechanisms work across its operations, locations, and relevant relationships, and whether people can use them in a way that is understandable, trusted, and appropriate to the context.

This LRA educational guidance supports disclosure preparation. For the exact requirements, always refer to the official GRI source.

Before you start

A quick mental checklist before you prepare this disclosure — tick each as you settle it.

Preparation

Key datapoints to prepare

Datapoint What to capture Evidence hint Owner
Advice channels Capture the ways people can ask for guidance on how to apply the organisation’s responsible business policies and working practices, including who can use them and how they are accessed. Policy documents, intranet pages, hotline or helpdesk procedures, ethics or compliance guidance, and any published contact routes for advice requests. Compliance / Ethics / Legal
Concern reporting routes Capture the routes individuals can use to report worries about the organisation’s business conduct, including the channels available and how a concern is submitted. Speak-up or whistleblowing policy, reporting portal screenshots, hotline procedures, case-management process notes, and employee communications on reporting concerns. Compliance / Ethics / Legal
+ Show GRI 2-26 sub-elements (LRA working checklist)

How to prepare it

1Set the scope first: decide which channels, teams, sites, or other parts of the business you will cover in the disclosure, so the write-up matches the organisation’s actual arrangements.
2Separate the two required topics clearly: one part should explain how people can get guidance on putting the organisation’s responsible conduct rules into practice, and the other should explain how they can report worries about business conduct.
3Gather the source material for each channel: policies, procedure notes, intranet pages, hotline details, contact routes, escalation paths, and any other internal records that show how the arrangements work in practice.
4Draft the disclosure in plain language, using a short narrative or bullet list that makes the routes easy to understand and keeps the two mechanisms distinct.
5Record any exclusions, changes, or limits in coverage, and explain them clearly so readers can see what is included and what is not.
6Check the final wording against the official source to confirm you have covered both required points, used the right scope, and not added or left out anything material.
Request the data

Request the speak-up and advice channels summary

Translate the disclosure into an internal business question — then adapt it to your organisation's own language.

What channels do people use to get guidance on responsible business conduct and to raise concerns about business conduct, and how are those channels described internally?

Use your organisation’s own names first for the relevant channels, routes and case-handling teams, then map them to the disclosure wording. Keep the request in the language people actually use internally, and check the source material before sign-off.

Weak request

Please provide the mechanisms for seeking advice and raising concerns for GRI 2:GRI 2-26.

Why it fails: It uses framework language only, so the owner may not know which internal routes, documents or teams to pull together. It also does not specify the period, boundary, source location or the organisation’s own channel names, so the response is likely to be incomplete or hard to verify.

Better request

Please send the current details for our internal advice and speak-up routes for [reporting period]: the channel names we use, what each route is for, who can use it, how people access it, who owns or manages it, and the source document or system link. If there are separate routes for policy guidance and for raising concerns, please include both. Use our own terms first, then I’ll map them for the disclosure draft.

Formal email template
Subject: Request for speak-up and advice channel details for [reporting period]

Hi [name/team],

I’m preparing the internal evidence pack for [reporting period] and need a short summary of the routes people can use to get guidance on our policies and to raise concerns about business conduct.

Please send, for each relevant channel:
- the internal name we use
- what it is used for
- who can use it
- how people access it
- who owns or manages it
- where the supporting source is held
- the date it was last reviewed or updated

If you have a policy page, hotline summary, case log extract, or intranet screenshot that already covers this, that would be ideal.

Please use your own internal terms first, then I’ll map them for the disclosure draft. This is a possible LRA training template only; please adapt it to your organisation and check the source material before sign-off.

Thanks,
[preparer name]
Short Teams / Slack version
Hi [name/team] — could you share the current details for our advice and speak-up routes for [period]? I need the internal channel names, what each is for, who can use them, how they’re accessed, who owns them, and the source link/file. Please use our own terms first; I’ll map them later. Thanks.
Industry examples
Manufacturing

Context. A group with factories, warehouse sites and a central compliance team uses a hotline, a policy helpdesk and line-manager escalation.

Adapted request. Please share the current details for the factory and office speak-up routes for [period]: hotline, compliance inbox, policy helpdesk and manager escalation. For each one, include the internal name, what it is used for, who can use it, how it is accessed, who owns it, and the source document or intranet page.

Example response. Hotline — used for reporting conduct concerns; open to employees, contractors and suppliers; accessed by phone/web; owned by Compliance; source: hotline provider summary and intranet page; reviewed 12 Feb 2025. Policy helpdesk — used for questions on policy application; open to employees and managers; accessed by email/intranet form; owned by Legal; source: policy page; reviewed 03 Mar 2025.

Financial services

Context. A regulated firm has a whistleblowing line, a conduct mailbox and a compliance advisory team.

Adapted request. Please provide the current details for our conduct advice and concern-reporting routes for [period], including the whistleblowing line, conduct mailbox and compliance advisory route. For each, include the internal name, purpose, user group, access method, owner and source reference.

Example response. Whistleblowing line — for raising conduct concerns; available to staff and third parties; phone and web; owned by Company Secretariat; source: whistleblowing policy and provider dashboard; last updated 21 Jan 2025. Conduct mailbox — for questions on policy interpretation; staff only; email; owned by Compliance; source: intranet guidance page; last updated 08 Apr 2025.

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

Explain how the organisation defines each route, what counts as a separate channel, and which people are included in the count or description.

Context note

Set out what the figures or descriptions show about how people can get help with applying the organisation’s conduct rules and how they can report worries about behaviour.

Fluctuation statement

If the number or availability of routes has changed, note whether this reflects new channels, removed channels, wider access, or a change in how the organisation records them.

Content index entry
GRI 2-26 Mechanisms for seeking advice and raising concerns — [location / page] / [notes]
Download Centre

Preparation tools & forms

Professional preparation tools for GRI 2-26 — free with an LRA Community membership. Register once (it's free) and every download unlocks, together with the Disclosure Library, templates and the LRA AI-assistant.

Free · Community members
Assurance readiness

For each claim, check the evidence

ClaimRiskEvidence to check
The information reported for this disclosure reconciles to the underlying source records.What is reported cannot be traced back to the systems or documents it was drawn from, or does not tie out to them.calculation_workbook reconciling the reported value to source_system_export
The information reported for this disclosure is current as at the reporting date.The disclosure reflects a different period, a cut-off before the reporting date, or stale data carried over from a prior period.approval_record showing the data cut-off date and the period covered
The scope behind the information reported for this disclosure is applied consistently.Parts of the organisation are silently in or out of scope, or the scope differs from the prior period without that change being explained.methodology defining the scope and a site_register of what it covers
Everything in scope is included in the information reported for this disclosure — nothing material is left out.Parts of the population that should be reported are omitted, understating or overstating the disclosure.site_register of the full population vs the calculation_workbook of what was actually included

Evidence pack to prepare

Common reporting gaps

The information is presented without a date or as-at point.The scope or boundary of the statement is left undefined.Key terms are used inconsistently across the report.Material changes since the previous period are not disclosed.Assertions are made without supporting detail or a source record.Boilerplate is used that does not actually answer what is asked.
Common gaps

Mistakes to avoid when collecting the data

Wrong owner
The team asks the wrong business owner for the source material, so the answer comes from a policy lead or hotline operator who cannot explain how people get advice or raise concerns in practice.
Framework language only
The request is written in reporting jargon instead of the organisation’s own terms, so the source team cannot map it to the actual advice route or concern-reporting channel they run.
No scope set
The data pull does not define which parts of the organisation, which channels, or which user groups are in scope, so the final evidence mixes unlike arrangements that should have been kept separate.
Wrong time basis
The collector uses the wrong reporting period or a different cut-off date from the rest of the pack, so the evidence reflects a different point in time from the disclosure being prepared.
Mixed counting basis
One source counts contacts, another counts people, and a third counts cases, but the team combines them without checking the basis, which makes the figures impossible to compare cleanly.
Source labels lost
The original names from the system, inbox, or tracker are stripped out during export, so later reviewers cannot trace each item back to the exact record or channel it came from.
Populations merged
Advice-seeking queries and concern-raising reports are rolled into one bucket even though they need separate handling, so the evidence no longer shows which activity each item belongs to.
Missing audit trail
The pack is saved without the underlying file names, dates, or reviewer sign-off, so no one can show where the data came from or who checked it before submission.

Where judgement is often needed

Acquisition or disposal during the reporting period
If a business is bought or sold part-way through the year, decide whether to include the new or exited teams in the description and explain the cut-off date you used.
Different local names for the same reporting route
Where countries use different labels for the same advice or concern route, group them under one plain description and note the local names only if that helps readers find the right channel.
Workers, contractors, and other close-in users
Be clear about whether the channels you describe are open to employees only or also to contractors, agency staff, and others who work closely with the organisation, and explain any limits.
Public-facing versus internal channels
If some routes are open to external parties and others are for internal use, separate them in the narrative so readers can see who can use each route and for what purpose.
Group-wide route or local route
When a central route sits alongside country or site-level routes, choose a consistent way to present them and explain whether the description covers the whole group or only parts of it.
Anonymous or named reporting options
If people can speak up without naming themselves in some places but not others, state the difference clearly and avoid implying a wider option than actually exists.
Privacy limits on detail
If privacy rules mean you cannot give site-level or country-level detail, say that the information has been combined and explain the level at which you have aggregated it.
Changes in the year
If the way people can seek advice or raise concerns changed during the period, describe the position at the end of the period and briefly note the main change and when it took effect.
Examples

Illustrative examples

Synthetic, written by LRA — not from a company report, not text from any standard.

Illustrative (synthetic) example — consumer goods manufacturing

*Synthetic example only.* We give employees, contractors and other affected people two routes: one for getting practical guidance on how to apply our responsible business rules, and another for flagging worries about how we are behaving. - Advice is available through line managers, the ethics team and a confidential helpline; in the year, 184 people used these channels, and 184/184 (100%) received a response within five working days. - Concerns can be raised through the same helpline, an online form or direct contact with the speak-up team; 27 concerns were logged, including 11 about labour practices, 8 about gifts and hospitality, 5 about supplier conduct and 3 about record-keeping.

This example shows two distinct access routes: one for help applying our rules in day-to-day work, and one for reporting worries about conduct. The figures are synthetic and internally consistent.

Illustrative (synthetic) example — healthcare services

*Synthetic example only.* Our group explains where people can go if they need help putting our conduct rules into practice, and where they can go if they want to report a concern about our behaviour. - Practical guidance is offered by the compliance team, local managers and a staffed advice mailbox; 96 requests for guidance were handled, with 72 from employees, 18 from agency staff and 6 from suppliers, and all 96 were answered. - Concerns may be raised through a hotline, a web portal or in person to a manager; 14 matters were reported, made up of 7 patient-safety issues, 4 procurement issues and 3 conflicts-of-interest issues.

This example separates advice-seeking from concern-raising and uses different channels for each. The counts are illustrative and add up consistently.

Company reports

How companies report GRI 2-26

Real reports where this topic is disclosed. These are report practice, not exact disclosure templates to copy.

Berli Jucker Public Company Limited
Food and Consumer Staples Retailing · Thailand · 2024
Open report →
Berli Jucker Public Company Limited’s Sustainability Report 2024 partially covers the disclosure related to responsible business conduct, mentioning robust due diligence processes and a policy framework aligned with the UN Guiding Principles on page 155. The report also references alignment of practices with sustainability goals and long-term business strategy on page 111. However, there is no clear headline value or detailed narrative for item (a-ii), and no quotable evidence was found for that part of the disclosure.
Meridian Energy Limited
Electric Utilities / IPP / Energy Traders · New Zealand · 2025
Open report →
Meridian Energy Limited’s 2025 Integrated Report includes a covered datapoint on the proportion of spending on local suppliers under GRI 204-1, found on page 167. This indicates some disclosure related to procurement practices and local community engagement. However, there is no quotable evidence for other narrative items related to this disclosure, as no additional relevant information was found elsewhere in the report.
Temenos AG
Software and Services · Switzerland · 2025
Open report →
Temenos AG’s Sustainability Report 2025 provides specific data on mechanisms for seeking advice and raising concerns related to business conduct and human rights, as noted on page 94. The report also details the number of concerns raised in 2025, including two cases from employees and six from external or anonymous sources, found on page 71. However, the report does not clearly elaborate on the effectiveness or follow-up of these mechanisms beyond these figures.
✓ LRA AI Assistant · Human-in-the-loop
Dr Ross Kurinko
Ask Study Studio AI assistant about this disclosure
Get a practical answer for your reporting context. Your first answer is free — create a free account to continue the conversation.
TryHow do I prepare GRI 2-26?What data do I need to collect?Where can I see a real-report example?What mistakes should I avoid?
1 free answer
Check your understanding

Scenarios to work through

A group policy says staff can ask for help before they act, but the draft report only mentions the whistleblowing line. The preparer has to decide whether the advice route also needs to be described.

QShould the disclosure cover both where people can get guidance on applying the organisation’s responsible business rules and where they can report concerns about conduct?
Reveal model answer →

The draft says employees can contact their line manager, but contractors and suppliers use a different ethics mailbox. The preparer is unsure whether one channel is enough to describe the process.

QHow should the preparer present the organisation’s arrangements if different groups use different routes?
Reveal model answer →

A draft paragraph says concerns can be raised, but it does not say whether the organisation also has a way to seek advice before a decision is made. The team wonders if that is acceptable because the hotline can be used for both.

QCan the preparer rely on one hotline description without making clear that it serves both purposes?
Reveal model answer →

The organisation has an online form, a phone line, and an ombuds-style contact point. The preparer is deciding whether to list every detail or keep the disclosure high level.

QWhat level of detail is appropriate when describing the mechanisms for advice and concern reporting?
Reveal model answer →
Framework references

Related framework references

How this disclosure maps across the major reporting frameworks.

GRI
GRI 2-26
within GRI 2: General Disclosures
Open official source →
Primary
Related & explore
FAQ

Questions this page answers

GRI 2-26 advice channels and concern reporting routes: what should I collect before drafting the disclosure?+
How do I use the GRI 2-26 step-by-step preparation section to build the disclosure?+
What evidence do I need for GRI 2-26 advice channels and concern reporting routes if I want the file to be assurance-ready?+
How do I use the 4 assurance claims on the GRI 2-26 page to test my draft?+
What should I put in the GRI 2-26 evidence pack for advice channels and concern reporting routes?+
Who should own the GRI 2-26 data for advice channels and concern reporting routes in practice?+
How do I avoid common mistakes when reporting GRI 2-26 advice channels and concern reporting routes?+
Can I use the GRI 2-26 synthetic example disclosure to draft my own wording?+
How do I turn the GRI 2-26 data into a draft disclosure and content-index line?+
What is the best way to use the GRI 2-26 Prep & Assurance workbook and printable Library Card?+
More questions this page can help with
GRI 2-26 advice channels concern reporting routes workbook: what should I fill in first?GRI 2-26 evidence pack: how do I build an audit trail for advice channels and concern reporting routes?GRI 2-26 common mistakes: what do practitioners usually miss when drafting this disclosure?GRI 2-26 synthetic example: how do I adapt the example without copying it?GRI 2-26 draft output: what narrative starters are on the page?GRI 2-26 content index line: how do I write one from the page?GRI 2-26 assurance claims: what are the four claims and how do I test them?GRI 2-26 advice channels: what counts as the datapoint I need to collect?GRI 2-26 concern reporting routes: how should I scope the routes included in the disclosure?GRI 2-26 from company reports table: how do I use the linked published reports as examples?GRI 2-26 printable Library Card PDF: when should I use it instead of the workbook?GRI 2-26 plain-language explainer: how do I use it to brief HR or the data owner?