Supplier surveys vs data-first: which fills your Scope 3 gap faster?

The default Scope 3 plan is a questionnaire: build the survey, send it to every supplier, chase for a quarter, and hope the responses cover enough spend to stand behind. The alternative is to start from what suppliers have already published and only ask about the gap. This page compares the two on the published record, and is straight about where a survey is still the right tool.

DitchCarbon provides verified emissions data for over 2 million organisations, so procurement, sustainability and finance teams can measure and act on supply chain and portfolio emissions from one source. That is the data-first half of this comparison, so read this page knowing who wrote it, and check every figure against its named source.

Why do supplier surveys dominate Scope 3 programmes?

Because asking feels rigorous, and because the discipline grew up around disclosure requests. If the number has to come from the supplier, the reasoning goes, then the way to get it is to ask the supplier. The premise fails quietly: thousands of suppliers have already answered, in annual reports, sustainability statements and regulatory filings, and a survey asks them again anyway. The question a buyer actually needs answered is not "will you tell me your emissions" but "what is already known about you, and is it right", and those are different instruments. DitchCarbon exists because the second question turns out to have an answer for most of a typical supplier list.

What does a survey campaign actually collect?

Self-reported numbers, at whatever quality the responding supplier can manage, on the requester's deadline rather than the supplier's reporting cycle. The figures arrive without the context a published disclosure carries: no source document, often no assurance status per scope, and no change history when the supplier later restates. Every response still has to be checked, mapped to the right legal entity, and reconciled with whatever the same company published elsewhere, because a survey answer that contradicts the annual report is a data quality question, not a data point. None of that work disappears because the channel was a form. DitchCarbon does the same reconciliation, but against the published record, where the source document comes attached.

What does the published record say about getting supplier data by asking?

The buyer-side evidence is published, and it comes from the organisations already doing the asking. The Science Based Targets initiative's corporate survey with BCG, February 2023, from 230 responding organisations, found 85% saw data access as a barrier to a usable baseline, 59% named limited time and resource as a constraint, 94% were relying on secondary data, and only 6% of emission factors in use were supplier-specific. Those are not the barriers of teams that have not tried; they are what running an engagement programme feels like from the inside.

One honesty note on the number this section is expected to contain: no primary-sourced, generalisable response rate exists for private supplier questionnaires, and the figures that circulate do not survive a provenance check, so this page does not quote one. The planning assumption the published record does support is more modest and more useful: a substantial share of any list will not answer on your timetable, and the inventory has to be closed anyway. That closing work, for every non-respondent, is exactly what DitchCarbon starts with rather than falls back on.

What does survey fatigue look like from the supplier's side?

The same company answering the same questions for every customer, each on a different portal, each in a slightly different format, each with its own deadline. A supplier with fifty corporate customers can face dozens of overlapping requests a year for numbers it has already published once, properly, in its own report. The rational response is triage: answer the biggest customers, ignore the rest, and the smaller the share of the supplier's revenue you represent, the further down the pile your questionnaire sits. Non-response is usually not resistance; it is arithmetic. Any approach that adds another portal to that pile is competing for the supplier's patience, which is the resource the whole model is running out of, and it is the resource a data-first approach, like DitchCarbon's, is designed not to spend.

What is a data-first approach?

Start from what already exists before anyone is asked. DitchCarbon matches a supplier list or portfolio against company emissions data covering over 2 million organisations, so the disclosed part of the list is already matched and scored on day one, before a single request is sent. Where a figure needs improving, the request goes out prepopulated with what that organisation has already published, so the supplier is confirming or correcting a real number rather than starting from a blank form. And where nothing has been disclosed, a generic factor closes the inventory and the gap is shown rather than hidden, so the unanswered part of the list is a visible, ranked workstream instead of a silent hole in a published number.

What happens to the survey itself?

It shrinks and sharpens rather than disappearing. Instead of asking everyone everything, you ask a short list a specific question: here is what you published, is it still right, and can you go one level deeper. Suppliers who have already disclosed are never bothered for what is already public, which is most of what a conventional questionnaire asks. The ask lands only where an answer would actually change the inventory, which is a request a supplier can see the point of. And because the answer lives on the supplier's profile rather than in one buyer's portal, the supplier answers once instead of once per customer, which is the only durable fix for the fatigue problem the previous section describes. That is the shape of engagement DitchCarbon runs.

What if you are the one being surveyed?

The same logic works in reverse, and this page is as likely to be read by a team drowning in questionnaires as by a team about to send one. Claiming your DitchCarbon profile is free and self-serve: you review what has already been found about your organisation, correct it, answer once, and every customer or investor looking you up reads the same answer instead of sending you the same survey in a different order. Answering once in public is the exit from answering everyone separately.

When is a survey still the right tool?

When the data has genuinely never been published anywhere. Activity-level detail, product carbon footprints, allocation questions specific to one trading relationship, forward plans, and anything a private company has simply never put in the public domain: no amount of reading finds what was never written down, and a direct request is the honest instrument for it. The concession cuts the other way too: a data-first approach narrows the survey to exactly those cases rather than eliminating it, and a narrow, prepopulated, obviously purposeful request is easier to answer and more likely to be answered than page one of a blank questionnaire. DitchCarbon is not the end of asking suppliers questions; it is the end of asking them questions the public record already answers.

Which fills the gap faster?

They run on different clocks. A survey campaign is bounded by the response window and the chase, and runs on an annual rhythm: build the questionnaire, send it, remind, extend the deadline, collect what came back, then do it again next year. A data-first start is bounded by matching, which is measured in days: in a recent DitchCarbon deployment, about 60% of a large supplier base carried matched, scored figures within 2 weeks, before anyone had been asked anything. The campaign that follows targets the remainder, with prepopulated requests, instead of carpet-bombing the whole list and waiting.

The practical test costs nothing and settles it for your own list: send a sample of your supplier list or portfolio to the coverage check and see how much of the survey you were about to run has already been answered in public.

Last reviewed September 2026.