GRI 305 Emissions Disclosure Calculator | 305-1 to 305-4

What GRI 305 requires — the four disclosures this tool computes

GRI 305: Emissions is the topic standard within the GRI environmental standards that governs how an organisation reports greenhouse gas emissions and significant air emissions. It contains seven disclosures. The calculator on this page computes the first four. That boundary is deliberate, and the reasoning is in the next section.

What distinguishes GRI 305 from a pure accounting standard is that it does not define a calculation methodology. It defers the arithmetic to the GHG Protocol Corporate Standard and instead specifies a disclosure surface: alongside every number, GRI requires you to state the consolidation approach, the gases your figures include, the base year and its rationale, the source of the emission factors, and the GWP source and rates applied. A correct number with an incomplete disclosure surface is a non-conformance. This is the failure mode the conformance checker exists to catch.

• 305-1 — Direct (Scope 1) GHG emissions. Six mandatory sub-clauses, including the consolidation approach (305-1-f) and biogenic CO₂ reported separately (305-1-c).
• 305-2 — Energy indirect (Scope 2) GHG emissions. Five mandatory sub-clauses. Location-based is required; market-based is required where the information is available.
• 305-3 — Other indirect (Scope 3) GHG emissions. Five mandatory sub-clauses, including 305-3-d, which requires you to account for the categories you included and to explain those you did not.
• 305-4 — GHG emissions intensity. An organisation-specific ratio, disclosed with its denominator, the scopes included, and the gases included.

What this calculator does not compute — 305-5, 305-6, 305-7

Three of the seven GRI 305 disclosures are absent from this engine. Each omission has a specific cause, and stating the cause plainly is more useful than a coverage claim we could not stand behind.

The GRI 305 Emissions methodology documents how each computed disclosure (305-1 to 305-4) is quantified, the GWP and consolidation choices, and the conformance checks behind this tool.

305-5 — Reduction of GHG emissions

305-5 asks for the GHG emissions reduced as a direct result of reduction initiatives, in tCO₂e. That is an attribution question, not an arithmetic one. It requires you to isolate the effect of a named initiative — a lighting retrofit, a fuel switch, a process change — from every other force that moved your inventory in the same period: output volume, weather, grid decarbonisation, divestment, a factor-set revision. No calculator can perform that decomposition from a line ledger, because the ledger does not know why any line changed.

The engine does surface a base-year comparison, and the distinction between that comparison and 305-5 is the subject of a later section. Conflating the two is one of the more common errors in GRI reporting, and it is a material one.

305-6 — Ozone-depleting substances, and 305-7 — NO_x, SO_x, and other significant air emissions

305-6 requires production, imports, and exports of ODS in metric tonnes of CFC-11 equivalent. 305-7 requires significant air emissions — nitrogen oxides, sulphur oxides, persistent organic pollutants, volatile organic compounds, hazardous air pollutants, particulate matter — in kilograms or multiples.

Neither is a greenhouse-gas quantity, and neither is backed by a verified factor set in the MasterBrain. There are no ozone-depletion-potential rows and no air-pollutant emission factors in the data layer this calculator reads. We could produce plausible numbers by importing an unversioned factor table from a secondary source. We do not, because a number without a traceable, versioned provenance chain is worse than no number in an assurance context — it survives internal review and fails external scrutiny.

Both disclosures are user-sourced. Draw ODS figures from your refrigerant and fire-suppressant registers under the applicable regulatory regime, and air-pollutant figures from your environmental permits, continuous emissions monitoring, or a regulator-published factor set. Report them alongside the output of this tool.

How the ledger works — direct entry versus activity data

The calculator holds a single consolidated inventory as a ledger of line items. You add lines to the Scope 1, Scope 2, and Scope 3 buckets; each line carries an entry mode, an optional label, and a data-quality tier. The disclosure totals are the sums of their buckets. There is no entity dimension — if your reporting boundary contains subsidiaries, consolidate them before entry.

Line emissions (tCO₂e) = Activity quantity × Published CO₂e factor ÷ 1,000

The division by one thousand converts the published factor’s kilogram basis to tonnes. In direct mode the line bypasses the formula entirely and the entered tCO₂e figure is used as supplied.

Data-quality tier

Every line carries a tier — primary, secondary, estimated, or proxy — which the engine aggregates into a weighted data-quality percentage. The tier is descriptive and does not alter the arithmetic. It exists because GRI 305 requires you to disclose the source of your emission factors, and because a total assembled from proxies deserves a different level of confidence than one assembled from metered primary data. A high absolute figure carried at 58% weighted quality is a different disclosure from the same figure at 95%.

“Gases included” is a disclosure checklist, not a calculation input

GRI 305-1-b requires the reporter to state the gases included in the calculation: CO₂, CH₄, N₂O, HFCs, PFCs, SF₆, NF₃, or a subset. The seven checkboxes in this calculator populate exactly that statement, and nothing else.

This is the point most reporters get wrong, and the misconception is understandable. It seems natural that a tool asking which gases you include would then report emissions by gas. It does not, and cannot, because the published emission factors it consumes are already aggregated. When DEFRA publishes a natural-gas factor of 0.18231 kg CO₂e per kWh (gross calorific value), that single number already contains the CO₂, CH₄, and N₂O components, each multiplied by its GWP and summed. Recovering the constituents would require reading a per-gas component breakdown and re-applying GWPs — arithmetic this engine deliberately does not perform.

There is a practical consequence. If your Scope 1 ledger contains a fugitive-refrigerant line entered in direct mode, your figures cover HFCs, and the HFC box should be ticked — even though no HFC-specific arithmetic happened inside this tool. Conversely, if your organisation operates no electrical switchgear and no semiconductor process, SF₆ and NF₃ are legitimately absent, and leaving those boxes clear is the accurate disclosure. The checklist describes the inventory, not the engine.

The GWP source selector is a declared label

GRI 305 requires disclosure of the GWP source and rates used. The calculator offers IPCC AR6 or AR5, both on a 100-year time horizon. Selecting one sets what appears in the disclosure table. It does not change a single computed figure.

The engine reads no GWP table. It applies published emission factors exactly as the publisher expressed them, and each published factor carries its own native GWP basis fixed at publication. The DEFRA fuel factors and the UK grid factor in the MasterBrain are natively AR5-100. Selecting AR6 does not convert them; it merely declares AR6 in the table above numbers computed on an AR5 basis.

The mixed-GWP-basis consistency check

The engine detects this and says so. Where at least one factor’s native basis differs from your selection, it raises a Mixed GWP basis consistency check identifying the mismatch. It flags; it does not reconcile, does not blend, and does not silently convert. Silent conversion is the behaviour that produces an unreproducible number, and an unreproducible number is the thing assurance exists to find.

Two clean paths

The asymmetry itself is not a defect. DEFRA maintains an AR5 basis by design, for continuity across its own multi-year factor series, while corporate reporting has broadly migrated to AR6. Both positions are coherent. The error is pretending they are the same position.

Consolidation approach — declared, not resolved

GRI 305-1-f requires disclosure of the consolidation approach for emissions: equity share, financial control, or operational control. The selector in this calculator populates that field. It is a first-class disclosure input and it is the single most consequential thing you will declare, because the same physical asset can be in your Scope 1 under one approach and outside your boundary entirely under another.

The boundary choice affects 305-1 far more than it affects 305-2. Scope 2 follows purchased electricity, and the entity purchasing electricity is usually the entity operating the site, so the three approaches tend to converge. Scope 1 follows combustion and process chemistry at assets whose ownership and operatorship frequently diverge — which is exactly where equity share and operational control part company.

Scope 2 dual reporting — one computed, one declared

The GHG Protocol Scope 2 Guidance requires dual reporting: a location-based figure reflecting the average emissions intensity of the grid you draw from, and a market-based figure reflecting the emissions attributable to the contractual instruments you have purchased. GRI 305-2 carries both forward. The calculator handles them asymmetrically, and the asymmetry is worth understanding.

Location-based is computed. Enter your consumption in kWh and select the grid, and the engine reads the location-based grid factor from the MasterBrain and computes the line. Alternatively enter a tCO₂e total in direct mode.

Market-based is declared. It is a single user-entered tCO₂e total. The engine reads no residual-mix rows and no energy-attribute-certificate data, and it does not construct a market-based figure from your instruments.

That is a deliberate constraint rather than a gap. A defensible market-based figure requires the full Scope 2 Quality Criteria hierarchy to be worked through — energy attribute certificates matched to consumption in the same market and period, supplier-specific rates, then residual mix for the unmatched remainder — with each instrument tested against the criteria before it can be claimed. That analysis belongs upstream of a disclosure calculator, in the contractual-instrument accounting your energy team maintains. Build it there, bring the total here.

Biogenic CO₂ — memo track, never in a total

GRI 305-1-c and 305-3-c require biogenic CO₂ emissions to be reported separately from the gross figure. The calculator provides three optional entries — Scope 1, Scope 2, Scope 3 — feeding a memo panel that sits outside the disclosure totals.

The separation is absolute. A biogenic figure never enters 305-1, never enters 305-3, never enters the location-based or market-based total, and never enters the 305-4 intensity numerator. It is displayed, labelled, and excluded.

The structural discipline here mirrors the treatment of avoided emissions in financed-emissions accounting: a decision-useful figure, disclosed in parallel, firewalled from the total it might otherwise be used to reduce. In both cases the guardrail exists because netting the two would let an organisation report a number that describes something other than what it emitted.

305-4 — building a defensible intensity ratio

GRI 305-4 asks for an organisation-specific GHG emissions intensity ratio. It does not prescribe the denominator. That freedom is why intensity ratios are the most comparable-looking and least comparable numbers in sustainability reporting.

305-4 intensity = Selected-scope absolute emissions ÷ Denominator value

Choosing the denominator

The calculator offers revenue (£m, €m, or $m), full-time-equivalent employees, floor area in square metres, and unit of product. Each answers a different question, and the right choice follows from what the ratio is for.

What must be disclosed alongside the ratio

A bare intensity figure is not a GRI 305-4 disclosure. The standard requires the denominator, the scopes included in the numerator, the gases included, and the types of emissions in the ratio. The scope checkboxes in the calculator default to all three; the gases inherit the global checklist from 305-1-b.

Base-year comparison is not GRI 305-5

The calculator accepts a base year, an optional base-year gross figure, and a base-year rationale, and returns a comparison: the absolute change in tCO₂e and the percentage change. That comparison is a useful disclosure and it is not GRI 305-5.

305-5 requires the emissions reduced as a direct result of reduction initiatives. The base-year delta is the net movement of the whole inventory across every cause: reduction initiatives, yes, but also production volume, weather-driven heating demand, grid decarbonisation you did not cause, acquisitions, divestments, boundary changes, and factor-set revisions. An organisation that grew output by 20% while running a successful efficiency programme may show a base-year increase and a genuine 305-5 reduction in the same year. Reporting the base-year delta in the 305-5 field describes the wrong quantity.

The trajectory above shows the base-year comparison the worked example produces: 41,000 tCO₂e in the 2019 base year against 35,644 tCO₂e in FY2025, a reduction of 5,356 tCO₂e or 13.1%. What it does not show — because no ledger can — is how much of that 13.1% Northwind caused. Answering that is 305-5, and it is analytical work performed outside this tool.

What triggers a base-year recalculation

• Structural change — mergers, acquisitions, divestments, or outsourcing that transfers emissions across the boundary rather than reducing them.
• Change of consolidation approach — moving between equity share, financial control, and operational control.
• Methodology or factor-set change — a material revision to calculation method, or a GWP-basis migration, that changes the base-year figure itself.
• Discovery of a material error, individually or cumulatively.

The calculator does not perform recalculation. It records the base year, the base-year figure, and the rationale you supply — three of the fields GRI requires — and computes the delta. Recalculating the base year against a significance threshold your policy defines remains your work.

The conformance checker — nineteen mandatory items

The engine tracks nineteen mandatory requirements across the four disclosures it computes, and reports how many you have met. This is the feature that distinguishes a disclosure calculator from an emissions calculator. An emissions calculator returns a number. A disclosure calculator returns a number and tells you whether you are permitted to publish it under the standard you claim to be following.

Each disclosure carries its own conformance count — 305-1 shows 6/6 when all six mandatory sub-clauses are satisfied, 305-2 shows 5/5, 305-3 shows 5/5, and 305-4 completes the set. The counts respond live to what you have entered. A gross figure with no consolidation approach declared leaves 305-1 at 5/6. An intensity ratio with no denominator unit leaves 305-4 short.

The commonly missed item — 305-3-d

Of the nineteen, one fails more often than the rest. Disclosure 305-3-d requires you to account for the Scope 3 categories included in the calculation and to explain those excluded. Reporters routinely enter their two or three best-measured categories, see a total appear, and publish. The standard’s requirement is not that you cover all fifteen categories; it is that you account for all fifteen — either with a figure, or with a stated reason for exclusion.

The readiness output is a summary judgement across the nineteen, expressed as a plain-language grade with the count beneath it. It is a self-assessment aid, not an assurance opinion, and it tests conformance with the disclosure requirements — not the accuracy of the figures you entered.

Worked example — Northwind Manufacturing plc, FY2025

This example reproduces exactly against the live calculator. Northwind Manufacturing plc is a single consolidated reporting entity. Reporting period is FY2025, annual. Consolidation approach is financial control. Base year is 2019. GWP source selected is AR6 — deliberately, so that the mixed-basis consistency check fires and can be read as a teaching case rather than hidden. Gases included: CO₂, CH₄, N₂O, HFCs, PFCs, SF₆.

Inputs

Scope 3 categories 14 and 15 are dispositioned as “Not relevant” rather than left silent. The intensity denominator is 120 £m revenue, with the ratio taken over Scope 1 and Scope 2.

Disclosure table

Portfolio composition

The metric strip

The biogenic memo runs alongside, never netted into the totals above:

Reading the result

Three things in this output deserve attention, and none of them is the headline figure.

The mixed-GWP-basis check fired. AR6 was selected, but the natural-gas factor and the UK grid factor are natively AR5-100. The engine applied them as published, declared AR6 in the disclosure table because that is what was selected, and raised the consistency check. Northwind’s options are to select AR5 and align the label with the data, or to keep AR6 and disclose the mismatch. What it cannot do is publish an AR6-labelled figure and stay silent about the AR5 factors underneath it.

Readiness is 18 of 19, and the missing item is 305-3-d. Northwind addressed four of fifteen Scope 3 categories — two with figures, two dispositioned as not relevant — giving 27% coverage. Under 305-3-d, the remaining eleven categories require a stated disposition before the Scope 3 disclosure conforms. This is why 305-3 shows 4/5 rather than 5/5 while every individual number in it is sound. The fix is documentation, not measurement.

Weighted data quality is 58%, graded “largely estimated.” Scope 3 contributes 70% of the gross total and its two lines were entered in direct mode from a spend-based analysis and a travel-management extract. The absolute figure is not wrong, but the confidence attaching to seven-tenths of it is materially lower than the confidence attaching to the metered gas and electricity in Scopes 1 and 2. An intensity ratio drawn over all three scopes would inherit that weakness; the ratio Northwind published, taken over Scopes 1 and 2, does not — which is a defensible reason for the scope selection, provided the selection is disclosed.

Reporting context — GRI, GHG Protocol, ESRS E1, IFRS S2, CDP, ISO 14064-1

GRI 305 rarely travels alone. Most organisations reporting against it are simultaneously in scope of at least one mandatory disclosure regime, and the figures are largely shared. What differs is the materiality lens through which each framework asks for them.

The GRI-to-ESRS interoperability question

GRI and EFRAG have published interoperability material mapping GRI disclosures to ESRS datapoints, and GRI 305-1 through 305-4 map substantially onto ESRS E1-6. The mapping is not an equivalence. ESRS E1 demands datapoints GRI does not — a gross total, intensity per net revenue on a prescribed basis, and disaggregation GRI leaves to the reporter. Treat the GRI 305 disclosure as the foundation of an ESRS E1-6 submission, not a substitute for one, and expect to add fields rather than merely relabel them.

ISO 14064-1 as the verification companion

Where GRI 305 tells you what to disclose, ISO 14064-1 tells you how to build an inventory that will withstand a verification engagement: quantification methodology selection, uncertainty assessment, documentation of the inventory design, and the information a verifier requires. The two are complementary. An organisation seeking limited or reasonable assurance over its GRI 305 disclosure will find the assurance provider working to ISO 14064-3 against an inventory expected to conform to ISO 14064-1.

Data sources, factor versioning, and MasterBrain-miss behaviour

Every factor this calculator applies is read live from the MasterBrain canonical-row keyspace at the moment of calculation. Nothing is cached in the page, and nothing is compiled into the engine.

What happens when a factor is missing

This engine carries no built-in fallback values. That is a departure from several sibling calculators on this site, which hold built-in floors if live data is unavailable, and it is intentional here.

On a MasterBrain miss, the affected line is skipped, an em-dash renders where its value would appear, and an amber warning surfaces. The calculation does not throw, the other lines compute normally, and no substitute value is used. A disclosure calculator that silently swapped in a stale fixed factor would produce a number that reconciles to nothing — neither to the live data layer nor to any documented source. An em-dash is an honest output. A wrong number is not.

Validation elsewhere is deliberately soft. A blank field leaves its line idle. A non-numeric or negative entry causes the line to be skipped rather than the calculation to fail. Only the year fields carry hard bounds. The engine is built to degrade visibly rather than break.

What’s next — completing your environmental disclosure

GRI 305 is one topic standard within the GRI environmental series, and this calculator computes four of its seven disclosures. Completing the picture means building the underlying scope figures upstream and sourcing the three deferred disclosures independently.

Once the inventory is complete and conformant, target setting follows. The SBTi Corporate Net-Zero Standard takes the base-year figure this calculator records as the starting point for near-term and long-term reduction targets — and its validation process asks the same questions the conformance checker does about consolidation approach, base-year rationale, and Scope 3 coverage.

Frequently asked questions

Methodology notes and limitations

Disclosure coverage. The engine computes GRI 305-1, 305-2 (location-based and market-based), 305-3, and 305-4. It does not compute 305-5 (reduction of GHG emissions), 305-6 (ozone-depleting substances), or 305-7 (NO_x, SO_x, and other significant air emissions). 305-5 requires initiative-level attribution; 305-6 and 305-7 are not backed by a verified factor set in the MasterBrain and are user-sourced.

Single consolidated entity. The calculator maintains one inventory as a line ledger with no entity dimension. Consolidate subsidiaries, joint ventures, and multiple sites against your chosen approach before entry.

No per-gas arithmetic. Lines are entered as tCO₂e aggregates, or computed as activity quantity × published CO₂e factor ÷ 1,000. Published factors are consumed as-is and never decomposed. The “gases included” control is a disclosure checklist under 305-1-b and produces no per-gas output.

GWP source is declared, not applied. The engine reads no GWP table. Factors carry their native basis, fixed at publication. Selecting AR6 or AR5 sets the disclosed label. Where basis and label diverge, the engine raises a Mixed GWP basis consistency check. It does not blend, convert, or reconcile.

Consolidation approach is declared, not resolved. The selector populates 305-1-f. It performs no equity partitioning, applies no control test, and moves no line between scopes.

Market-based Scope 2 is user-entered. A single tCO₂e total. The engine reads no residual-mix rows and no energy-attribute-certificate data, and constructs no market-based figure from contractual instruments.

Biogenic CO₂ is a memo track. Reported separately per 305-1-c and 305-3-c. Never summed into 305-1, 305-3, either total, or the 305-4 intensity numerator.

Base-year comparison is not 305-5. The engine records the base year, base-year gross figure, and rationale you supply, and computes the delta. It does not perform base-year recalculation and does not attribute the delta to reduction initiatives.

Factors are read live; there are no fallback values. All factors are read from window.gcMasterBrainV3.factors on every calculation. On a miss, the line is skipped and an amber warning surfaces. No built-in floor is substituted. Validation is otherwise soft: blank fields idle, invalid entries skip their line, and the calculation does not throw.

Conformance is not assurance. The nineteen-item readiness check tests conformance with GRI 305’s disclosure requirements. It does not test the accuracy of the figures you entered, does not constitute an assurance opinion, and should not be presented as one. Organisations seeking limited or reasonable assurance should expect a provider working to ISO 14064-1 and its verification companion, reconciling the ledger against primary source documents line by line. The GRI 305 emissions methodology covers how the disclosure is built in full.