GRESB runs the ESG benchmark that institutional real estate and infrastructure investors report into. Participants submit performance data, GRESB validates it, and the resulting scores move real capital allocation decisions.
GRESB runs the ESG benchmark that institutional real estate and infrastructure
investors report into. Participants submit building performance data, GRESB
validates it, and the resulting scores feed real capital allocation decisions.
When a score looks wrong to a participant, somebody has to explain why it is not.
That was me.
Highlights
First point of contact on the support queue alongside Customer Success, working
assessment and technical-solution tickets in Front.
Took the hardest ticket type. Participants wrote in disputing their energy,
water and waste badges, and I walked each one through every consideration that
went into the assessment, at whatever level of technical detail that particular
participant needed.
Roughly 50% of the participants I explained the methodology to went back and
amended their own reported values. Not a response rate to an outreach campaign.
A customer changing their own submitted data after a conversation.
Then automated the cause. Co-designed an IQR-based anomaly detection module in
Python and R, deployed inside the GRESB Real Estate product as a live
in-product workflow. The sequence matters: I answered the same ticket
repeatedly, then built the detection for the thing generating it.
Wrote PRDs and feature specs, and partnered with Product on ESG Portal
prioritisation.
Validated building performance data covering energy, water, waste and
greenhouse gas emissions against GHG Protocol-aligned rules.
Refined prompts that turned unstructured reviewer notes into structured JSON.