Disclosure Interoperability
CDP has a strategic opportunity to use Discloser Profiles as part of a broader interoperability layer for disclosure. The idea is to let CDP connect a discloser’s identity, uploaded evidence, structured datapoints, and standards mappings so that the suggestion service can retrieve approved datapoints in the same way it retrieves uploaded documents.
The business reason is clear: organizations are increasingly asked to disclose environmental information through other routes, including direct reporting to governing bodies, jurisdictions, regulators, standards bodies, investors, customers, and procurement systems. CDP needs a compelling reason for organizations to disclose through CDP even when those other disclosure routes exist. The strongest reason is that CDP can help them provide data once, map it across standards, reuse it in CDP disclosure, and preserve an evidence trail.
Public CDP positioning already supports this. CDP describes its framework-alignment approach as “write once, read many” and says Framework Alignment Tags in the Disclosure Portal help disclosers understand how CDP datapoints connect to different standards and frameworks. CDP also publishes or references mappings and alignments for ISSB / IFRS S2, ESRS E1, TNFD, GRI, GHG Protocol, and cities/states/regions frameworks.
Product Thesis
The product goal is not just to add another AI chat feature. The goal is to make CDP the trusted translation layer between an organization’s source evidence and multiple disclosure destinations.
| Step | What should happen |
|---|---|
| 1. Identify the discloser | Use Discloser Profiles to resolve the organization, place, CRM record, hierarchy, geography, and stable identifiers. |
| 2. Capture evidence | Accept uploaded documents, prior answers, structured forms, CRM-linked records, or other approved organization material. |
| 3. Extract datapoints | Turn relevant evidence into structured disclosure datapoints with source links, reporting year, unit, owner, and review status. |
| 4. Map standards | Attach CDP question references and external framework tags such as ISSB / IFRS S2, ESRS E1, TNFD, GRI, or GHG Protocol where validated. |
| 5. Suggest responses | Let the suggestion service retrieve both uploaded-document evidence and structured datapoints when drafting CDP responses. |
| 6. Preserve review trail | Show citations, confidence, reuse permissions, human review state, and any standard-specific caveats before submission. |
Why Discloser Profiles Matters
Discloser Profiles could become the identity anchor for this workflow. A reusable datapoint is only useful if CDP can answer which organization or place it belongs to, what reporting boundary applies, which parent or child entities it may relate to, and whether the record is current enough to reuse.
Key responsibilities for this layer could include:
- stable discloser identity for companies, cities, regions, public authorities, and other reporting entities;
- links between CRM records, organization names, geographic entities, GERS identifiers, and disclosure platform records;
- parent-child and hierarchy context for group reporting, subsidiaries, regions, cities, or jurisdictional relationships;
- coverage checks that show whether a discloser has sufficient profile, boundary, and source evidence to support reuse;
- a safe join point between uploaded evidence, structured disclosure datapoints, and framework mappings.
Strategic Boundary
This should not be presented as automatic regulatory compliance. The safer positioning is evidence reuse, drafting support, standards-alignment visibility, and better disclosure workflow efficiency, with human review and specialist validation before formal submission.