Case study·Healthcare REIT

ESG / EPRA / GRESB evidence assembly

From a quarterly evidence scrambleto a managed disclosure workflow

118
Evidence items mappedEach linked to its source export, certificate or workbook record
It turned ESG reporting into a managed evidence workflow.
ESG Lead · UK healthcare real-estate investor
01Pilot envelope
Pilot length8 weeks
First signal12 days
First ROI50 days
Team alongside7 seats · 3 colleagues

8-week reporting pilot; mapped required disclosures to source evidence; outputs used as the internal evidence pack, not the final submission.

02What it owns
Reports toESG Lead, dotted line to Head of Investor Relations on disclosure narrative.
Owns
  • Disclosure-to-evidence map — every required EPRA sBPR and GRESB indicator linked to its source export, certificate or workbook record
  • Energy and emissions data set — EPC ratings, operator utility consumption and intensity calculations sourced and reconciled per asset
  • Open disclosure gap queue — every unresolved item carries a named owner and a target close date
  • Quarantined internal evidence pack — every section drafted into a SharePoint review folder for the ESG team to approve before it informs the submission
  • Pre-submission readiness brief — top-line coverage summary surfaced to the ESG Lead and IR 48 hours before sign-off
Does not do
  • Submitting to GRESB or signing the EPRA pack — drafts only; the ESG Lead and Head of Investor Relations approve and submit
  • Methodology or boundary decisions — escalates to the ESG Lead
  • Restating prior-period numbers — surfaces variances; finance closes the restatement
Done looks like

The ESG team opens the cycle with a reviewable disclosure-to-evidence map, not a folder hunt. Every open gap has a named owner, and the internal evidence pack is reviewer-approved on the first pass before the human-written submission goes out.

03The team
AI teammates3
NatalieReads the GRESB portal exports, the EPRA checklist, the EPC register and the operator utility workbooks each cycle, and links every required disclosure to its source evidence record.
TheoCompares the live disclosure-to-evidence map against the prior-period pack, surfaces unresolved gaps and assigns each one a named owner and a target close date.
IrisDrafts the internal evidence pack section by section into a SharePoint quarantine folder, with every claim linked to source, ready for the ESG and IR teams to review before the human-written submission.
Human team7
  • ESG LeadESG
  • Head of Investor RelationsInvestor relations
  • 3 Asset managersAsset
  • Finance leadFinance
  • Data ownerData
  • 2 ESG analystsESG
  • Legal reviewerLegal
04Connected stack
GRESBEPRAEPC registerSharePointExcelPower BIMicrosoft Teams
05What it returned
118Evidence items mappedEach linked to its source export, certificate or workbook record
43%Unresolved disclosure gaps downVersus the prior reporting cycle baseline
58%Reporting evidence prep downHours spent assembling the internal evidence pack
  • Day 0
    Co-ordinator sessionESG Lead, IR, finance, data owner and a sample asset manager align on the disclosure list, evidence types and the first three answerable questions.
  • Day 12
    First signalNatalie completes a read-only pass over the GRESB exports, the EPRA checklist and the EPC register; the first 118 evidence items are mapped to required disclosures for review.
  • Day 25
    Read-only quarantine liveDaily disclosure gap list lands in the ESG team's SharePoint quarantine folder; analysts correct two evidence-type mappings and three asset identity matches.
  • Day 38
    Approval-gated pack draftsIris drafts the internal evidence pack into the quarantine folder; the ESG Lead approves the energy, emissions and governance sections in turn.
  • Day 50
    ROI reviewSponsor signs off the three baseline metrics; the internal pack is approved as the input to the human-written submission for this cycle.
  • Day 56
    Cycle closedESG Lead and Head of Investor Relations submit the final pack; the disclosure-to-evidence map is rolled forward as the baseline for the next cycle.
Get started

Want this for your team?

Each design-partner pilot starts the same way: one workflow, the minimum useful context, and a first ROI signal measured in days.