Organisation structure ·
Set under Consolidation approach (GHG Protocol) further down this page, this field mirrors it. Choosing equity share adds an ownership % beside each entity in the structure.
Clients open on this year. Advance it only when you're ready to collect the next financial year, earlier years stay editable via “Change year”. (A December year-end client keeps filling FY2026 in early 2027 until you advance it here.)
Report branding
Add this client's logo to the cover of the generated PDF report so it reads as their board document. PNG, JPG, WebP or SVG, a transparent background works best. Large images are scaled down automatically.
Client support contact
Shown to this client when they click Contact JRC in the sidebar. Usually the lead consultant for this account. Leave blank to use the JRC general inbox.
Employee categories (platform-wide)
Drive every "by category" indicator. Within each category, gender and age each total 100%.
Lost time incident rate (LTIR) basis
The constant used in LTIR = injuries × constant ÷ hours worked. Bursa and GRI commonly report per million hours; 200,000 matches the OSHA 100-full-time-worker convention.
Intensity denominator
Used by the auto-calculated intensity metrics (GRI 302-3): energy ÷ denominator. Revenue is read from GRI 201-1 and employees from the workforce matrix automatically; floor area and production volume are entered here per financial year.
Age groups
Age bands for the workforce diversity matrix. Leave as the standard three for exact FTSE/GRI mapping, or set your own, whatever you configure here is what clients enter and what appears in exports.
Display & workflow
How numbers are shown and whether the client approval step is used. Full precision is always stored, the decimal setting only changes what's displayed and exported.
When off, the approval button on each indicator and the “Approved only” filter are hidden. Any approvals already recorded are kept and reappear if you switch it back on.
The report can open with an auto-generated scope-and-boundary paragraph (entities included, N/A entities excluded, consolidation approach, scopes, methodology). Turn off to omit it.
Emission-factor methodology
Which published factor set converts activity data (fuel, travel, water, waste…) into CO₂e. This choice applies to Scope 1 combustion and Scope 3; anything a method doesn't cover falls back to DESNZ, the report's Basis of Preparation states the mix.
Scope 2 electricity is not affected by this choice. It always uses the Grid Emission Factors published by Suruhanjaya Tenaga (Energy Commission) for the grid each site sits on: Peninsular Malaysia, Sabah or Sarawak, which are separate, unconnected grids with very different intensities. None of the three methodologies below publishes a Malaysian grid factor: DESNZ withdrew overseas electricity factors entirely and now points users to the IEA.
We recommend DESNZ (UK DEFRA) for Scope 1 and Scope 3. It is published annually and free to use, and it is the only one of the three that also covers the Scope 3 categories most clients report, business travel, employee commuting, water and waste, so your inventory draws on fewer separate sources. Choose US EPA or IPCC if a specific reporting requirement asks for them.
Consolidation approach (GHG Protocol)
How each entity's greenhouse-gas emissions roll up to the group. Operational control and financial control include every in-scope entity at 100%. Equity share weights each entity's Scope 1/2/3 (CO₂e) by your ownership interest, energy, water, waste and other metrics are always reported at 100%.
Set each entity's ownership % under Organisation structure below. HQ is always 100%.
Change alerts & team routing
When a client edits an indicator you've marked used (finalized for the report), JRC is alerted instantly by email and in the app. Choose who gets alerted for this client.
Economic value distributed, categories (GRI 201-1)
These are the stakeholder groups for "Direct economic value distributed". Edit to match how your company reports (e.g., LBS / Mah Sing). Economic value retained is calculated automatically.
⚠ Offboard & delete client
Permanently deletes and everything we hold for it, data entries, configuration, evidence files (the actual uploaded documents), in-app snapshots, audit history, and the client's user logins. This cannot be undone. Use it only when offboarding a client at the end of an engagement.
- required, full-scope Excel with the calculation audit
- Type the exact client name to confirm:
Frameworks & industry ·
Industry-specific indicators only appear when a matching industry is set.
Choose your GRI sector for sector-specific disclosures (e.g., Oil & Gas, Mining), or “General” for universal GRI only. Enables GRI automatically.
FTSE indicators, sector or uploaded review files
Use the company's FTSE industry sector, or upload the client's FTSE review files (ESG + Climate). The platform reads each file (column H applicability = “YES”, column C indicator code), matches the codes to the library, and builds a custom FTSE list for this client, flagging any codes that need to be created as custom indicators.
SASB Standard, one or more industries
Pick one or more SASB industries this company reports against. Choose the disclosure topics below; clients only see and complete the metrics under the topics you enable.
Indicator availability
Custom indicators
Add client-specific indicators. Give it a pillar and a framework reference (e.g. FTSE, SASB) with a code, then add one or more fields, each can be a number (with unit), percentage, currency, or text. Mix numbers and text in the same indicator if a question needs both. They appear in data entry, company data and exports like any other indicator.
People & permissions
Each person is tied to an entity and sees only assigned pillars. They receive an email invitation to set their own password. Need finer control than pillars? After inviting, click edit access on their row to limit them to specific indicators (show only, or hide, a chosen list) and to assign multiple entities.
Assurance & year lock
Backups
Your data is backed up automatically by the secure managed cloud database (daily backups with point-in-time recovery). There's nothing to manage here. To roll back a specific change, the audit trail below shows who changed what and when.