Skip to main content
Skip table of contents

Joint Venture Assets Submission to GRESB

Joint venture assets are often set up in Envizi as Locations belonging to different reporting Groups. However when submitting asset (location) data to GRESB, GRESB requires each asset to have a different asset id when the same asset (location) is being reported under a different GRESB reporting entity, which also has a different entity id.

It is imperative that before any API submission to GRESB, both asset id and entity id shall be set up and interpreted correctly by the platform.

Step 1: Review all Groups' GRESB Active flag status

The ‘All Groups Settings’ page under Group → GRESB sub menu allows you to review all Groups that have Entity Ids entered and their GRESB Active Status.

It is expected that for any joint vention location, only one of its parent Groups should have the flag set to ‘Active’ and all the other Groups shall be set to ‘Inactive’. Make necessary changes here if required.

Step 2: Review and confirm Active Group’s Entity Id has been recorded correctly in Envizi

This can be done on the same ‘All Groups Settings’ page. Make necessary changes here if required.

Review other settings such as Reporting Period Starting Month and Floor Area unit on the same page.

Step 3: Review Location’s Asset Id has been recorded correctly in Envizi and it matches with correct parent entity id which the upcoming API data submission is meant for.

This can be done on either Location’s ‘GRESB Location Settings’ page, or Group’s ‘Asset Characteristics’ grid page.

GRESB Location Settings

(Group) Asset Characteristics

Step 4: Submit data to GRESB using either the ‘GRESB Asset Summary (with API)’ for individual asset, or the ‘GRESB Group Reivew (with API)’ page for all assets under the same reporting entity (Group).

Before API submission, you should check and confirm both entity id and asset id have been populated properly. This can be done on either page.

GRESB Asset Summary

GRESB Group Review

Step 5: If required, repeat the above steps by adjusting parent Groups' Active Flags and Location’s Asset Id for data submission to another GRESB reporting entity (if using the same data from the same location). It is expected that Groups that do not need to be submitted should have their GRESB report flag set to ‘Inactive’.

How does the platform determine Active Parent GRESB Group

When submitting data to GRESB, at any time there could be only one active reporting entity. If multiple parent Groups of the same location all have the GRESB flag set to ‘Active’, the platform will consider the Group that was set to ‘Active’ most recently, as the Group whose Entity Id will be used for submission.

The check is done based on the ‘Updated_On’ time stamp when the flag was set to ‘Active’.

The ‘Active parent GRESB Group’ column in the ‘GRESB Group Review’ grid page, and ‘Current - Envizi’ column in the ‘GRESB Asset Summary’ page, will be showing the platform determined active Group to be used for API submission.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.