Rejected document on desk
August 1, 2025

What Happens When You Submit to GRESB With Incomplete Data

The GRESB submission deadline passes. The data has been compiled, reviewed internally, and uploaded. The team celebrates. Then the results arrive — and assets are rejected for data incompleteness. The consequences cascade quickly: the rejected submission cannot be resubmitted until the next cycle, which means 12 months lost. The submission fees are non-refundable. And the investors who expected a GRESB rating for their quarterly reporting now receive an explanation instead of a score.

For institutional funds, a failed GRESB cycle isn't just an administrative inconvenience — it's a material event. LP reporting depends on GRESB scores to demonstrate ESG commitment. Investor confidence is directly tied to the fund's ability to deliver on its sustainability promises. In some cases, GRESB ratings are written into fund mandates or side letters. A missing rating can trigger questions from investment committees, affect refinancing terms, and create friction in capital raising conversations.

The data issues that cause rejection are almost always fixable. Coverage below 75%, missing structural fields, incomplete time periods — these are not complex technical problems. They're data collection gaps that accumulate over years of informal processes and fragmented systems. The tragedy is that they're discoverable in 48 hours but typically only surface after 12 months of work culminating in a failed submission.

The cost of not knowing your data readiness before submission is always higher than finding out. A pre-submission EDRA scan costs a fraction of the GRESB submission fee. It takes 48 hours, not 12 months. And it produces specific, actionable findings: which assets are ready, which have gaps, what those gaps are, and how long they take to fix. The fund manager can then make an informed decision — submit the ready assets, remediate the others, and avoid the reputational damage of a blanket rejection.

Every failed GRESB submission represents the same pattern: data assumptions that weren't verified before the deadline. The fix isn't better ESG strategy or more expensive platforms. It's a systematic data readiness check that runs before the submission cycle begins — not after it ends.

Case Study

A Canadian pension fund's real estate arm submitted 40 assets to GRESB. 12 were rejected for data incompleteness — coverage gaps in tenant-metered spaces and structural field issues in property type classifications. EDRA would have flagged all 12 assets in 48 hours, giving the team 8 weeks to remediate before the submission deadline.

Download Case Study (PDF)