Back to the blog

Polish Whistleblowing Records: What You Can Give an ESG Auditor

For companies operating in Poland, learn what an ESG auditor can receive instead of the whistleblowing register and how to prepare a nine-element report.

Polish Whistleblowing Records: What You Can Give an ESG Auditor

An ESG auditor or major business partner asks for evidence from your Polish whistleblowing system. The deadline is Friday. The internal reports register is available in the system—but you cannot simply send it to the auditor, or even give an extract to your own ESG department.

This is a common challenge in sustainability assessments, business partner audits, and supply chain due diligence. Refusing the request without an alternative may leave a questionnaire unanswered. Disclosing the register may breach Polish law.

The practical alternative is an aggregated report: a separate document prepared for the assessment, rather than an export or screenshot from the reporting system. It can show that the channel operates without exposing individual reports or the people involved.

Key terms for readers outside Poland

Term Meaning
Internal reports register A register maintained by the legal entity under Article 29 of Poland’s Whistleblower Protection Act. It includes, among other things, report numbers, the subject matter of alleged breaches, details of the whistleblower and the person named in a report, report dates, and follow-up information. Access is restricted to authorized persons.
Aggregated report A separate document prepared for an audit or questionnaire. It presents statistics, such as the number of reports in a period, in a way that does not identify individuals. It is not an extract from the reporting system.
Breaches committee The body responsible for handling reports. It may be internal, external—for example, a law firm—or a combination of both. In the model discussed here, its formally authorized members handle register data.
Unauthorized person Someone who has not been formally authorized to access the register. Being employed by the company is not enough: ESG staff, HR staff outside the committee, administrative staff, and, in many arrangements, management board members may all be unauthorized.
ESRS G1 The European Sustainability Reporting Standard on business conduct. In relation to whistleblowing, the provision discussed below concerns reporting channels and employees’ awareness of and trust in them; it does not mandate a numerical whistleblowing metric.

Why the register must stay restricted

What the Polish Act says

The Whistleblower Protection Act of June 14, 2024 (Journal of Laws of 2024, item 928), effective September 25, 2024, addresses three points relevant to the register:

  1. Maintaining the register: Article 29(1)(1) places this duty on the legal entity that acts as data controller.
  2. Restricting access: Under Article 29(6), only persons authorized by that legal entity may access the register.
  3. Retaining records: Article 29(5) provides for retention for three years after the end of the calendar year in which follow-up actions or related proceedings were concluded.

The register contains more than a count of reports. It can include the subject matter of an alleged breach, identifying details of the whistleblower and the person named in the report, the whistleblower’s contact address if provided, and information about follow-up actions.

Confidentiality and data-protection consequences

Article 56 of the Act provides for criminal liability for unlawfully disclosing the identity of a whistleblower, a person assisting with a report, or a person connected with the whistleblower. The potential penalties are a fine, restriction of liberty, or imprisonment for up to one year (parliamentary text).

An improper disclosure may also be a personal data breach, potentially leading to proceedings before Poland’s Personal Data Protection Office (UODO) and an administrative fine under Article 83 of the GDPR. Giving an auditor or business partner the register without a legal basis may therefore engage both the Act and the GDPR.

Who inside the company may be unauthorized?

For access to the internal reports register, the following are not automatically authorized:

  • ESG or sustainability staff;
  • HR staff who are not members of the breaches committee;
  • administration and office management staff;
  • management board members who have not been formally authorized; and
  • external auditors and business partners.

Under the arrangement described here, access belongs to members of the internal, external, or hybrid breaches committee who have been formally authorized by the legal entity. A sustainability specialist asking for “the number of reports” should therefore not receive a register extract or system screenshot—even when acting on the employer’s instructions.

A comparable restricted-access approach appears in Poland’s Anti-Money Laundering Act. Its Article 80 addresses designated persons receiving reports and communication methods that protect information from access by unauthorized persons.

If you are unsure who can see your register, contact us to review your access rights map.

The line between register data and an aggregated report

The distinction is between disclosing an individual case and reporting information that does not identify anyone.

Information Protected register or case information? Appropriate to give an auditor in this form?
Content of an individual report Yes No
Information identifying the whistleblower Yes No
Information about the person named in a report Yes No
Description of an individual case’s facts Yes No
Number of reports during a period Not in itself Yes, subject to re-identification risk
Generic description of outcomes Not in itself Yes, if individuals cannot be identified
Follow-up information without identifying details Not in itself Yes, if individuals cannot be identified

A count for a reporting period can be disclosed as aggregated information where it does not identify anyone. Do not provide it by exporting the register. Have the authorized committee prepare a separate, purpose-built report.

Small numbers can still identify people

A report is not necessarily anonymous just because names have been removed. Recital 26 of the GDPR concerns information from which a person cannot be identified by means reasonably likely to be used. UODO also notes that aggregation and removal of identifiers do not, by themselves, establish effective anonymization.

Suppose a small organization received one report. A recipient who knows the organization may be able to connect a published count of “1” with a particular person. Before issuing the report, ask:

  1. Could the count, reporting period, and organizational scope together identify the whistleblower?
  2. Does the recipient—a rating platform or business partner, for example—hold other information that could be combined with the report?
  3. Could successive reports, such as “0” followed by “1,” narrow the possible individuals?

If re-identification is a real risk, consider combining categories, reporting a range such as “0–5 reports,” or extending the reporting period. Apply the same care to generic outcomes and follow-up descriptions.

Nine elements to include in the report

A useful aggregated report should be identifiable, cover a defined period, and demonstrate what happened at a general level without describing individual cases.

No. Element What to include Purpose
1 Date and place of preparation The place and date on which the document was prepared Establishes that this is a report prepared as of a stated date, not a system extract
2 Full company name The name recorded in Poland’s National Court Register (KRS), where applicable; a logo is optional Identifies the entity being assessed
3 Reporting procedure The name of the internal reporting procedure Identifies the formal procedure behind the channel
4 Implementation date The date the procedure was put in place Shows when the system began operating
5 Reporting period The period since the previous report through the date of preparation Allows the auditor to assess continuity
6 Number of reports A specific count, such as “0” or “1,” where disclosure does not create a re-identification risk Provides a concise statistical result
7 Generic outcome For example, “rejected for not meeting the procedure’s requirements” Indicates the outcome without case facts or personal details
8 Follow-up actions For example, “contact with the reporting person was attempted; no response was received,” where this cannot identify anyone Shows that reports are handled, not merely received
9 Committee signature A signature on behalf of the breaches committee rather than the employer Identifies the body preparing the report from the records it handles

Before drafting, ask the auditor three practical questions: Whose letterhead should be used—the company’s or the committee’s (or external law firm’s)? Must one committee member sign or all of them? Is a handwritten signature, electronic signature, or Polish trusted profile accepted? Clarifying these points early reduces the risk of having to reissue the document close to the deadline.

How to report a period with zero reports

“0” is a result, not a blank field. State it expressly and explain what it means.

Article 47(1) of the Whistleblower Protection Act requires public authorities to submit annual statistical reports on external reports, including the number received (parliamentary text). That obligation applies to public authorities, not private companies. It nevertheless illustrates the practical distinction between reporting a count of zero and omitting the count.

For a zero-report period:

  1. Identify the reporting period and organizational scope.
  2. Confirm that the reporting channels were available throughout that period—for example, that the online form worked and the telephone line was active.
  3. Provide appropriate evidence of operation, such as availability logs, form tests, or communications to employees.
  4. Identify awareness or training activities concerning the procedure.
  5. State that “0” means no reports were registered, not that no breaches occurred.

Keep consecutive reporting periods continuous. A gap can prompt questions about whether the channel operated or was managed during the missing months. Maintain a dated record of report versions so each new report covers the period since the previous one.

What ESRS G1 calls for—and what may help an auditor

Under ESRS G1-1, paragraph 10(d), the provision discussed here does not require a mandatory numerical metric for whistleblowing reports. It concerns disclosure of whether and how the undertaking assesses whether employees:

  • know about the reporting channels;
  • trust those channels; and
  • can use them to raise concerns and have those concerns addressed.

The aggregated report is therefore supporting evidence, not a substitute for explaining how the channels work. An auditor may also need:

  • a description of written and oral reporting options, including telephone and in-person channels;
  • the rules protecting reporting persons from retaliation;
  • records of training and internal communications;
  • results of employee awareness or trust assessments, such as surveys; and
  • aggregated information on reports and follow-up actions.

A practical evidence package might look like this:

Evidence Format Usual preparer
Internal reporting procedure Internal document Compliance team or legal counsel
Description of channels and protection rules Procedure excerpt or separate document Compliance team or legal counsel
Aggregated report Separate document prepared as of a specified date Breaches committee
Training confirmation Attendance list, agenda, and date HR or compliance team
Trust survey results Survey report HR or ESG team

The same underlying package can support a business partner questionnaire, a bank audit, or a rating platform assessment. A reusable report template helps, but check each recipient’s formal requirements before issuing a document.

Five common mistakes

1. ESG staff export the report list themselves

Speed is not a justification for giving an unauthorized employee access to the register or sending its contents to an auditor. An improper disclosure may engage Article 56 of the Act. It may also be a personal data breach requiring documentation in the breach register under Article 33(5) of the GDPR and, potentially, notification to UODO.

2. The company refuses without offering an alternative

A refusal may protect the register but leave an audit question unanswered. Offer an aggregated report and other evidence that the channel is operating.

3. Reporting periods have gaps

If one report ends in April 2025 and the next starts in January 2026, the intervening eight months are unexplained. An auditor may read the gap as a sign that the system was not operating. Track report dates and cover the periods between them.

4. The document omits the company or the period

A count with no clearly identified entity or reporting period may not be accepted as evidence. Include those details and the committee signature from the outset.

5. No one knows how to commission the report

The ESG team may need the document without being authorized to instruct an external committee or receive register data. Decide in advance who, on the company’s side, confirms the instruction to prepare the report.

Implementation checklist

Priority Action
High Create a standard aggregated-report template with the nine elements and store it in the compliance repository.
High Map register access by name. Record the authorized committee members and confirm in writing which ESG, HR, administration, and management board personnel do not have access to report content.
High Route external requests for reporting data to the breaches committee rather than asking ESG staff to retrieve data.
High Maintain dated report versions and consecutive reporting periods without gaps.
Medium Train ESG, HR, and administrative staff on the distinction between disclosable aggregated information and protected case content or personal details.
Medium Establish who can confirm an instruction to an external adviser or committee to prepare a report.
Low Review the internal reporting procedure and add a process for aggregated reporting for external assessments if it is missing.

An existing personal data processing authorization record can provide a model for the access rights map. Record the authorization number, name, scope, date granted, date revoked, and signature, rather than building the structure from scratch.

How we can help

We support companies with internal reporting procedures that need to respond to ESG audits, business partner questionnaires, and supply chain due diligence requests.

Option Scope Suitable for
Procedure review and report template Review the reporting procedure, prepare an aggregated-report template, and establish the reporting period Companies with an implemented procedure facing their first ESG audit
Template, access map, and training The above, plus a register access rights map and training for ESG, HR, and administrative teams Companies with an external committee or a more complex structure
Full-service support The law firm acts as the breaches committee, maintains the register, and handles recurring aggregated reporting Companies seeking to outsource the process

In each option, the breaches committee—not the ESG department—prepares the aggregated report. Your ESG team does not need to handle register data. Once instructed, we can have the document ready the next day.

Prepare before the next questionnaire

An ESG auditor, business partner, or bank may ask the same operational question: Does your reporting channel work? Answering it does not require disclosing the internal reports register.

Prepare the nine-element template, establish who can access the register, and agree on a route for commissioning reports. That makes the next request easier to answer without sacrificing confidentiality. To check whether your procedure is ready for an upcoming audit, contact us. We can review it and identify what needs to change.

Frequently asked questions

Can I email the auditor only the number of reports?
The number alone can be aggregated information, provided it does not permit identification in context. The practical problem is evidentiary: an email without the company name, reporting period, and committee signature may not meet the auditor’s requirements. A short, identifiable report is safer than having to prepare one again under deadline pressure.

What if the auditor insists on descriptions of individual reports?
Decline to provide case descriptions and explain that Article 29(6) restricts register access to authorized persons; Article 56 addresses unlawful disclosure of protected identities. Offer a more detailed aggregated report with generic outcomes and follow-up information that does not identify individuals. The ESRS G1 provision discussed above does not mandate descriptions of individual cases or a numerical reporting metric.

Can ESG staff have “numbers-only” access to the system?
That depends on the system configuration and the scope of formal authorization. If the system genuinely limits the view to aggregated statistics, without access to report content or personal details, such access is formally permissible where the ESG employee is authorized for that scope. Asking the committee to prepare the report is often the safer arrangement because it reduces the risk of accidental access to protected information.

Does a zero count look suspicious?
Not if it is clearly reported and supported. Show the period covered, evidence that the channels were available, and relevant communications or training. Explain that zero means no reports were registered—not that no breaches occurred.

Can one report serve both a business partner questionnaire and a bank audit?
The same nine-element template can be used for both. Confirm any different requirements for letterhead and signatures with each recipient before issuing the report.

What if register data has already been sent to an auditor?
An unlawful disclosure of a whistleblower’s identity may constitute an offense under Article 56, carrying a fine, restriction of liberty, or imprisonment for up to one year. The incident may also require documentation under Article 33(5) of the GDPR and potentially notification to UODO. Consult legal counsel to assess what was disclosed and determine the appropriate remedial steps.

RECOMMENDED

this could be interesting to you

Real work, real outcomes - compliance, technology, transactions, and the everyday legal support businesses run on.