Why most supplier data requests fail
A supplier emissions template usually fails for one of two reasons: it asks for a number the supplier's finance or sustainability team has never calculated, or it asks for the right number in a format so ambiguous that three people on the same team would fill it in three different ways. Neither failure looks like refusal. It looks like a blank field, a rough estimate pulled from a competitor's public report, or a response that arrives four months late and gets discarded because nobody can reconcile the units.
If your goal is to move Scope 3 categories like Purchased Goods & Services or Upstream Transportation & Distribution up the GHG Protocol's data quality hierarchy — from spend-based estimates toward supplier-specific primary data — the template is the single highest-leverage document in that effort. Get it wrong and you generate work for both sides without generating better data.
Start from what suppliers already track, not what you want
The instinct is to design the template around your inventory's needs: total emissions per unit sold, allocated by revenue share, categorized by your own product taxonomy. That's the wrong starting point. Suppliers rarely track emissions in the shape a customer's inventory needs them. What they do track, reliably, is activity data tied to their own operations and cost centers: kilowatt-hours purchased, liters of fuel consumed by delivery fleets, tonnes of a given material produced, kilometers shipped by mode.
A template that asks for "emissions associated with goods supplied to us" forces the supplier to do your carbon accounting for you, often without the calculation methodology or emission factors to do it consistently. A template that asks for the underlying activity data — energy consumed, fuel burned, production volumes, transport distances and modes — asks for numbers the supplier's operations or procurement team can pull from existing records. You then apply your own emission factors on the back end, which also gives you control over methodology consistency across hundreds of suppliers who would otherwise each pick their own factors.
This is the same logic behind the hybrid and supplier-specific tiers of the data quality hierarchy: primary data collection works best when it captures activity data close to the source, not a pre-calculated emissions figure the supplier had to guess at.
Standardise units before you standardise anything else
Unit ambiguity is a quieter killer than blank fields, because it produces answers that look complete but aren't usable. "Fuel consumption: 40,000" means nothing without knowing whether that's liters, gallons, or MMBtu, and whether it covers a calendar year, a fiscal year, or a rolling twelve months. Multiply that ambiguity across a supplier base spanning multiple countries and unit conventions, and a data team can lose weeks reconciling values that should have taken minutes to compare.
The fix is mechanical but often skipped: every quantitative field in the template should have its unit pre-specified and locked, not left as an open text box next to a number. Where a supplier's internal systems use a different unit, ask them to state the conversion rather than silently converting on your end — that keeps an audit trail and catches errors on their side before the data reaches your inventory.
Reducing ambiguity beyond units
Units are the most visible ambiguity, but not the only one. A template should also fix, explicitly and in writing:
- The reporting period (calendar year, and whether partial-year data is acceptable if the supplier's fiscal year differs)
- The organizational boundary (the specific facility, business unit, or legal entity the data should cover, especially for suppliers with multiple sites)
- Whether requested figures are for total operations or only the share allocated to your company's purchases
- The category the request maps to — Purchased Goods & Services, Upstream Transportation & Distribution, or another — so the supplier's contact understands why the figure matters and isn't guessing at relevance
Each of these, left undefined, produces a different kind of unusable answer: right number, wrong period; right period, wrong boundary; a total that can't be allocated back to your specific volume.
Where this sits in a broader engagement effort
A well-designed template raises response quality, but it doesn't replace an engagement program. Response rates improve further when the request is paired with a short explanation of why the data is being collected, what happens to it, and a realistic deadline — and when a follow-up sequence exists for suppliers who don't respond to the first request. Suppliers who provide primary activity data in one cycle are also the ones worth prioritizing for a supplier-specific emission factor in the next cycle, since that's a meaningfully stronger data point than an average-data estimate applied uniformly across a category.
A simple test before you send it
Before sending a template to a supplier base, run it past someone who has no visibility into your GHG inventory. If they can't tell, from the form alone, what unit each field expects, what period it covers, and which of their existing records would answer it, the template needs another pass. The goal isn't a comprehensive questionnaire — it's one that a supplier's existing operational data can answer without a special data-gathering exercise on their end. That's what turns a data request into a data response.