Senseible

Is it acceptable to use rough Scope 3 data in the first year?

Yes, if you label it. The GHG Protocol's Scope 3 guidance expects relatively low quality data in a company's first years, replaced with better data as it becomes available, starting where quality is low and emissions are high. Say how you will improve it.

What the standard accepts

The Scope 3 Standard says higher uncertainty is acceptable as long as the data supports your goals and keeps the inventory relevant: good enough to see which activities are large and to track the trend year to year.

Two things are required in return: a description of data quality for each category, and the share of each category calculated from supplier or partner data.

Grade each figure on five indicators

Table 7.6 of the standard gives the checks. In Indian terms:

What to improve first

The Technical Guidance says to prioritise activities with relatively low data quality and relatively high emissions. In most factories that is the main raw material bought by spend. Moving it from rupees to tonnes, then to supplier data, does more than polishing a small line.

When better data arrives

If the better data changes the estimate significantly, the base year has to be recalculated with the new source so the trend compares like with like. If it cannot be applied to past years, say so in the report rather than mixing old and new methods silently.

What rough does not mean

Example: one supplier's data replacing a spend estimate

Figures are an example. The 10% threshold is the example the Scope 3 Standard gives; your own policy sets yours.

What Senseible does here

Senseible reads quantities and units from purchase invoices, which moves a line from a spend estimate to quantity-based data, and labels any spend-based estimate as such, so the rough part of your Scope 3 stays visible to you and your buyer.

Sources: GHG Protocol Technical Guidance for Calculating Scope 3 Emissions (2013), introduction, GHG Protocol Scope 3 Standard (2011), section 7.3 and table 7.6

Last reviewed 2026-10-31.