4 requirements evaluated: 4 supported.
Supported
Requirement evaluated: The platform must apply emission factors from maintained, versioned libraries and document the methodology selection for each factor, including the factor source, version date, and the rationale for choosing it over alternatives. This must replace the undocumented factor application in the current spreadsheet model and be accessible to third-party assurance providers without requiring a consultant intermediary.
For a publicly traded company replacing an undocumented consultant spreadsheet, Watershed directly addresses this requirement through three interlocking mechanisms. First, the platform maintains a library of over 500,000 emission factors — including its proprietary CEDA database of 60,000 spend-based factors across 148 countries and 400 industries — that receives annual updates, replacing static spreadsheet factor application with a maintained, versioned source. Users can access the library of more than 500,000 emissions factors, benchmarks, and methodologies and see how every number was calculated. …
Limitations: While Watershed documents factor sources, version dates, and calculation lineage at the calculation level, the specific per-record field showing 'rationale for choosing factor A over alternative factor B' is described at the methodology and database level rather than as an inline annotation on each individual calculati …
Supported
Requirement evaluated: The platform must maintain a complete, immutable audit trail covering every data input, emission factor selection, calculation step, methodology change, and user action, sufficient to support third-party limited assurance engagements without supplemental documentation from the buyer. The audit trail must be exportable in a format that an external assurance provider can independently review, directly addressing the buyer's stated problem that the current spreadsheet is not auditable.
For a publicly traded company replacing an unauditable spreadsheet, Watershed maintains complete audit trails for all carbon data, recording how every emissions figure was calculated and which emission factors were applied. The mechanism has two layers: first, the platform's data lineage engine traces each calculation from raw activity data input through emission factor selection to final output, making the chain inspectable within the platform; second, external auditors can be granted direct read access to view data lineage, inspect supporting evidence, review calculation chains, and verify audit trails without relying on supplemental buyer documentation (Watershed CSRD blog, watershed.com/ …
Limitations: The technical architecture of the audit log (for example, whether entries are cryptographically hashed or append-only at the database level) is not publicly documented, so a buyer requiring the highest-evidence immutability guarantees for a reasonable-assurance engagement should ask Watershed to demonstrate the specifi …
Supported
Requirement evaluated: The platform must apply emission factors from maintained, versioned libraries and document the methodology selection for each factor, including the factor source, version date, and the rationale for choosing it over alternatives. This must replace the undocumented factor application in the current spreadsheet model and be accessible to third-party assurance providers without requiring a consultant intermediary.
For a publicly traded company replacing an undocumented consultant spreadsheet, Watershed directly addresses this requirement through three interlocking mechanisms. First, the platform maintains a library of over 500,000 emission factors — including its proprietary CEDA database of 60,000 spend-based factors across 148 countries and 400 industries — that receives annual updates, replacing static spreadsheet factor application with a maintained, versioned source. Users can access the library of more than 500,000 emissions factors, benchmarks, and methodologies and see how every number was calculated. …
Limitations: While Watershed documents factor sources, version dates, and calculation lineage at the calculation level, the specific per-record field showing 'rationale for choosing factor A over alternative factor B' is described at the methodology and database level rather than as an inline annotation on each individual calculati …
Supported
Requirement evaluated: The platform must maintain a complete, immutable audit trail covering every data input, emission factor selection, calculation step, methodology change, and user action, sufficient to support third-party limited assurance engagements without supplemental documentation from the buyer. The audit trail must be exportable in a format that an external assurance provider can independently review, directly addressing the buyer's stated problem that the current spreadsheet is not auditable.
For a publicly traded company replacing an unauditable spreadsheet, Watershed maintains complete audit trails for all carbon data, recording how every emissions figure was calculated and which emission factors were applied. The mechanism has two layers: first, the platform's data lineage engine traces each calculation from raw activity data input through emission factor selection to final output, making the chain inspectable within the platform; second, external auditors can be granted direct read access to view data lineage, inspect supporting evidence, review calculation chains, and verify audit trails without relying on supplemental buyer documentation (Watershed CSRD blog, watershed.com/ …
Limitations: The technical architecture of the audit log (for example, whether entries are cryptographically hashed or append-only at the database level) is not publicly documented, so a buyer requiring the highest-evidence immutability guarantees for a reasonable-assurance engagement should ask Watershed to demonstrate the specifi …