Transparency

“Information can be public and still be impossible to see. ”

Transparency is frequently measured by volume. Organisations publish policies, dashboards, supplier lists, methodologies and annual reports, then assume openness has been achieved. Yet information can be technically available while remaining inaccessible, incomplete, outdated or impossible to interpret. Disclosure is an activity.

Transparency is the condition that allows others to understand and evaluate what the information means. ISEAL's Credibility Principles describe transparency as making important information publicly available and easily accessible while protecting confidential and private information. The purpose is not publication for its own sake.

Stakeholders need enough information to understand processes, decision-making, results and impacts, participate in decisions and raise concerns. Accessibility has practical dimensions.

A 300-page report in one language may satisfy a formal publication requirement and exclude affected communities. A supplier list containing internal identification codes may be downloadable but unusable without location, ownership or date information. A methodology can be public while critical assumptions are hidden in technical annexes. Transparency depends on the intended user. Relevance requires selection.

Publishing everything can obscure what matters through information overload. Organisations should explain boundaries, methods, limitations, changes and material uncertainties. A concise table that exposes the denominator behind a percentage can be more transparent than thousands of unstructured records. Timeliness also matters. Data released two years after an impact may be unsuitable for decision-making or remedy.

Policies published promptly but performance data withheld until attention has moved on create an incomplete picture. Transparency should follow the pace at which stakeholders need to act, not only the organisation's reporting calendar. Negative information is the stronger test.

Many organisations publish targets and achievements while treating missed milestones, complaints, data corrections or adverse findings as exceptions to communication. Selective openness produces a curated account rather than transparency. Users need to see material setbacks and the response to them. Confidentiality creates legitimate limits.

Personal data, security-sensitive information, traditional knowledge and commercially sensitive material may require protection. Transparency does not mean exposing people or surrendering every trade secret. It does require explaining what has been withheld, why, under which rule and whether aggregated or independently reviewed information can meet the accountability need. Transparency does not equal accountability.

An organisation can disclose poor performance and take no action. Nor does visibility automatically create power. Stakeholders may lack resources, expertise or authority to challenge what they see. Effective transparency therefore connects information to participation, complaints, oversight and consequences. The design of data matters.

Machine-readable formats, stable identifiers, version histories and clear metadata support reuse and comparison. Silent changes undermine trust. If an organisation corrects a deforestation figure or supplier count, users should be able to see what changed, when and why. Transparency can also become performance. Dashboards, traceability maps and live counters create an appearance of precision.

If source data are duplicated, estimates are unlabelled or coverage is partial, the interface may increase confidence while reducing understanding. Visual polish should never substitute for data lineage and uncertainty. The discipline is to ask whether a reasonable stakeholder can find, understand, compare and challenge the information needed to evaluate the claim or decision.

The organisation should not be the only party capable of interpreting its disclosure. Transparency begins when information travels beyond publication into usable scrutiny.

Practical application

Identify the information different stakeholders need to evaluate governance, methods, performance, costs, complaints and claims. Publish it in accessible languages and formats with definitions, dates, boundaries, denominators, uncertainty and change logs. Create rules for confidentiality and explain justified omissions. Test disclosures with intended users, including affected groups.

Link information to feedback, grievance and correction processes so that scrutiny can influence decisions.

Why it matters

Sustainability claims often concern distant activities that users cannot observe directly. Transparency enables participation, comparison and challenge. It also disciplines internal decision-making because assumptions and failures must be explained outside the organisation.

Common misconception

Transparency is often equated with publishing more data. Information is transparent only when relevant users can access, understand and use it. Volume without context can hide as effectively as secrecy.

Connections

Public Disclosure is the formal act of releasing information. Data Quality and Interoperability determine whether published data can be trusted and reused. Credibility Principles, Stakeholder Engagement and Complaints & Appeals connect openness to accountability.

A question worth asking

Which important fact about your sustainability performance is technically public but still too difficult for an affected person or informed critic to find, interpret or challenge?

Selected references

ISEAL Alliance. 2021. ISEAL Credibility Principles, Version 2. Global Reporting Initiative. 2021. GRI 1: Foundation 2021. Heald, D. 2006. Varieties of Transparency. In Transparency: The Key to Better Governance? Fung, A. , Graham, M. and Weil, D. 2007. Full Disclosure: The Perils and Promise of Transparency. OECD. 2023. OECD Guidelines for Multinational Enterprises on Responsible Business Conduct.