KEY ESG allows fund managers to create and manage custom frameworks across reporting years — both for your own self-assessment and for the frameworks you issue to your portfolio companies.
Automatic Framework Versioning
Each custom framework maintains distinct year-specific versions under a single parent framework, so you can preserve the exact reporting configuration you issued to your portfolio in a given year, while evolving requirements for new years. When cloning or saving a framework for a new reporting year, the new version is automatically made year-compatible.
One-Click Version Cloning
Clone any previous framework version, with automatic standard framework updates, to roll out a new reporting year across your portfolio in seconds:
Click Clone on any framework version.
The system auto-updates standard frameworks to the current year.
Yellow warning triangles flag any mismatches for quick correction before you send the framework out to portfolio companies.
How to use it
For a new data request setup (self-assessment or portfolio company request):
Ensure you're in your new reporting year, and start your data request.
Clone last year's framework, so portfolio companies see a consistent, comparable set of metrics year over year.
Resolve any yellow warnings with the quick-fix options.
Add or remove any metrics before issuing the updated framework to your companies.
For framework maintenance: access all versions from the dropdown menu. Draft versions can be edited freely; issued versions (i.e. those already sent to portfolio companies) require explicit confirmation to change. Delete unused drafts to keep your workspace clean.
Why this matters for portfolio consistency
Versioning keeps each year's framework distinct, so changing this year's metric selection won't affect the comparability of prior years' portfolio company submissions. This is especially useful when preparing multi-year, portfolio-wide data for LP reporting or SFDR PAI disclosures, where consistency of definitions year over year matters.
FAQs
If I remove metrics from this year's version, will it remove data from previous years' portfolio company submissions?
No — framework versioning keeps frameworks from different years distinct. If you attempt to save changes to a custom framework with active portfolio company submissions, the platform will warn you.
Do I have to re-issue my framework to portfolio companies every reporting year?
We recommend cloning a previously issued framework version each year, so it's updated to the newest standard framework version before you send it out.
How does this save me time?
Instead of rebuilding your framework from scratch for every portfolio company data request, you can clone the previous year's version and adjust it centrally, ensuring consistency across your whole portfolio.