Improve supplier response rates by finding where requests stall
Before sending another reminder, identify the step that is blocked. A request may have missed the responsible person, asked an unclear question, required records that do not exist or reached a supplier whose answer is waiting for your own team's clarification.
This guide is for procurement and sustainability teams managing an issued ESG collection round. It offers six diagnostic routes and a fictional cohort example. The aim is to choose a useful next action and report progress honestly. It provides no benchmark or guaranteed response-rate improvement.
Start with the last confirmed event
For each unresolved request, read the latest exchange and record the last event you can substantiate. Distinguish “sent”, “responsible recipient confirmed receipt”, “request-specific reply received” and “reviewed as usable for the stated purpose”. A delivery notification or email-open signal alone does not establish that the correct person owns the request.
Keep the reason for delay as unknown until there is evidence. Record an observed problem separately from a suspected explanation. For example, an expired invitation is observable; “the supplier is unwilling” is an interpretation that the invitation failure does not support.
GHG Protocol's Supplier Engagement Guidance, pages 5–7, recommends identifying the person responsible for supplier data, explaining the collection arrangements, offering support and resolving questions. Its context is GHG inventories. The diagnostic routes below are an original collection-management approach, not a mandatory ESG scoring system.
Choose the action that addresses the obstacle
1. The request has not reached its owner
Look for a rejected message, expired invitation, departed contact or a recipient who says another function owns the information. Ask your procurement relationship owner to verify the responsible business contact through an authorised channel. Retain the request ID when it is re-routed so that one request does not become two in the count.
The next milestone is confirmation from the responsible recipient. Copying more people or repeatedly sending to the same unverified address does not resolve ownership.
2. The recipient cannot tell what answer is needed
Identify the exact ambiguity. “Energy data” might mean purchased electricity, total energy or an emissions result. Clarify the specific field, requested entity, period and unit, and show one relevant example of an acceptable answer format.
Keep the clarification with the request version. If you materially change the scope or acceptance criteria, flag that change in the progress comparison. A shorter request can be sensible, but accepting less information should not appear as improved completion of the original request.
3. The records or preparation capacity are missing
Ask what already exists and what work is needed to answer the unresolved part. Separate an unavailable record from a record that exists but needs extraction, calculation or review. Agree a proportionate next step with the data owner rather than demanding an unsupported number.
Check whether a previously prepared response or common schedule can meet the same need. OECD's Due Diligence Guidance, questions 12 and 28, discusses common reporting approaches to reduce duplicated effort and undue burden. It does not make an existing assessment sufficient for every new request. Reuse still needs a fit-for-purpose check.
4. The answer exists but disclosure is restricted
Identify who must approve release, the intended recipient and use, and the unresolved restriction. Let the authorised owners decide whether an agreed extract, aggregate or controlled review can meet the need. Do not move restricted information to a personal inbox or broaden access just to finish the collection.
The confidential supplier-evidence guide covers the disclosure decision in detail. Log the permission dependency here without copying sensitive records into the progress register.
5. The submission channel prevents an accurate answer
Record the affected field and the actual error or constraint. Examples include an inaccessible invitation, a blocked file type or a forced yes/no field that cannot preserve a qualification. Have the authorised system or reporting owner resolve the problem and confirm the accepted submission route.
A portal problem does not justify selecting an unsupported answer or bypassing a security control. Preserve the qualification and response version when an approved alternative channel is used.
6. Timing or buyer-side review is holding the request
Check whether the supplier is waiting for a definition, an answer from your reviewer or approval of its proposed evidence route. Assign that dependency to your own team. If the supplier needs preparation time, establish the outstanding task and a date its owner can support.
Keep the original due date alongside any agreed revision. Arrange the next check around the unresolved task; repeated reminders before a promised milestone can add noise. Escalate the reporting consequence internally if the remaining gap threatens your cutoff, without labelling the supplier non-compliant or inventing contractual consequences.
Count the same cohort at both cutoffs
Every supplier, event and number in this example is fictional. The buyer issued one unchanged request to each of 20 suppliers. No request was added, withdrawn or replaced between Cutoff 1 on 1 September 2026 and Cutoff 2 on 15 September 2026. The request and review criteria stayed the same.
For this example, define three cumulative milestones:
Reached: the responsible recipient confirmed receipt. A request-specific reply also establishes receipt.
Substantive reply: a request-specific answer, clarification question or explanation that data are unavailable. Automatic acknowledgements are excluded.
Usable for the stated purpose: the reviewer accepted the response for the defined reporting need after the required scope, period, evidence and quality checks. An unavailable-data explanation can be a substantive reply without satisfying this test.
The milestones overlap: usable responses are included in replies, and replies are included in reached requests. Do not add the three milestone counts.
Cutoff 1
Of 20 requests, 16 are reached, 10 have substantive replies and 6 are usable. With the fixed denominator, those rates are 80%, 50% and 30% respectively.
For a non-overlapping work queue, split the same 20 requests into four groups:
4: reach unconfirmed.
6: reached, no substantive reply.
4: replied, not yet usable.
6: usable for the stated purpose.
The check is 20 = 4 + 6 + 4 + 6. Each request appears in one group. The four replied-but-not-usable requests need individual diagnosis; a clarification awaiting the buyer, unavailable records and an unreviewed submission require different actions.
Cutoff 2
Two previously unconfirmed requests now have confirmed receipt. Four requests that were reached without a substantive reply now have one. Three earlier replies have completed the required review and are usable. All six previously usable responses remain usable.
The cumulative totals are therefore 18 reached, 14 substantive replies and 9 usable responses: 90%, 70% and 45% of the same 20 requests.
The new disjoint work queue is 2 reach unconfirmed, 4 reached without a substantive reply, 5 replied but not yet usable, and 9 usable. The check is 20 = 2 + 4 + 5 + 9.
The substantive reply rate rose by 20 percentage points, from 50% to 70%. The usable rate rose by 15 percentage points, from 30% to 45%. The review backlog grew from 4 to 5 because four new replies entered it while three older replies became usable. That directs attention to review capacity as well as supplier contact.
These invented movements demonstrate the arithmetic. They do not prove that a reminder, training session or other intervention caused an improvement. None of the rates measures spend coverage, emissions coverage, sustainability performance or compliance.
Turn the diagnosis into one owned next action
For every open item, retain the last confirmed event, evidence of the obstacle, next action, responsible owner, dependency and agreed check date. Mark whether the next move belongs to the buyer or supplier. Where the cause is still unknown, make establishing it the next action.
The supplier ESG response tracker can hold the exchange and review record. Its published response measure uses active sent request rows. Keep this guide's fixed-cohort diagnostic snapshot separately, with its own substantive-reply definition; do not silently relabel the workbook's measure or drop difficult requests to improve the rate. Report additions and withdrawals alongside any revised operational denominator.
Before marking a response usable, complete the topic-specific review. For Scope 3 data, the GHG Protocol Scope 3 Standard, section 7.3, addresses technology, time and geography, completeness and reliability, with quality sufficient for the inventory's purpose. File arrival or administrative closure does not establish that review outcome.
Make the next collection decision clearer
Nitium's value-chain ESG reporting support helps organise partner responses, reporting coverage and evidence gaps within an agreed scope. Discuss a stalled supplier collection round with a non-confidential outline of the request and the unresolved step.
Sources checked 13 October 2026. References are the 2011 GHG Protocol Supplier Engagement Guidance and Scope 3 Standard, and the 2018 OECD Due Diligence Guidance. This practical workflow does not provide a legal opinion, supplier rating, certification or independent assurance conclusion.
Comments