Map customer ESG questions to the people who can support and approve the answer
Break a bundled customer question into the decisions it actually requires. A facilities manager may substantiate a consumption figure, while someone else must interpret an assurance statement, authorise an attachment or approve a future commitment. Keep those decisions linked so a supported fact does not accidentally become an unsupported promise.
This guide is for suppliers coordinating an incoming customer questionnaire across business functions. It shows how to divide one question, resolve conflicting answers and put the parts back together. The routing approach is optional and should fit the organisation's actual authority arrangements.
Preserve the question before dividing it
Keep the customer's question ID, exact wording, instructions and version. Save any definitions, reporting dates, attachment requirements and declaration that affect its meaning. Add internal sub-identifiers without rewriting the original or silently changing its scope.
Nominate a coordinator to assemble the response and keep customer clarifications together. That coordination role does not automatically carry authority to approve figures, release records or make commitments.
For each sub-question, record the requested scope, supporting record, proposed answer and unresolved decision. Name the people needed for four distinct checks:
Evidence: who can supply and explain the relevant source records, coverage and gaps? Several contributors may be needed.
Interpretation: who can decide whether those records answer this question and settle the technical meaning, or identify a clarification needed from the customer?
Release permission: who can authorise the particular information or attachment for the actual recipient, purpose and channel?
Response decision: who can approve the final wording within the company's authority arrangements, including qualifications and any new commitment?
A person can perform more than one function, but record each decision separately. Technical ownership alone does not establish disclosure permission. Approval to release a file does not establish that every statement in the answer is supported. A final approver must obtain any additional commitment authority they do not hold.
In its GHG-data context, GHG Protocol's Supplier Engagement Guidance, pages 4–5, addresses data-use restrictions and identifying people responsible for preparing and disclosing supplier data. OECD's Due Diligence Guidance, section II 1.2 and question 16, supports responsibilities and communication across relevant functions. Neither prescribes this four-check questionnaire workflow.
Work through one fictional customer question
Every business, record, quantity and decision in this example is invented. It is not a Nitium client case, a customer-approved response or evidence of anyone's performance.
Original Q17: “For Site Cedar, which supplies PX-8 to us, provide purchased electricity for 1 April 2025 to 31 March 2026; confirm this figure is independently assured; upload the supporting bills; and confirm that all electricity used to make our products will be renewable from 1 April 2027.”
The coordinator keeps that wording intact and adds four internal parts. The first asks for site activity, the second for an assurance claim, the third for disclosure and the fourth for a future product-related commitment. The switch from site scope to “our products” needs attention.
Q17-A Provide the electricity figure
Facilities supplies schedule E-04, covering Site Cedar's complete meter list for April 2025 to February 2026. It supports 88,500 kWh. Finance confirms that the March record is missing and also offers a group calendar-year dashboard. That dashboard covers other sites and a different period.
The energy reporting lead handles interpretation. The group dashboard cannot fill the missing site month without additional evidence. The supported answer is an eleven-month site subtotal, with March unresolved. The lead also asks the coordinator to clarify whether the reference to PX-8 merely identifies the supplying site or requests an allocation to the customer's products.
The release owner must approve sharing the subtotal and its scope explanation. The response approver can consider a clearly qualified partial answer; they cannot turn it into a full-year or product-allocated result by approving the wording. Facilities owns obtaining the missing record, while the coordinator owns obtaining the customer's scope clarification.
Q17-B Confirm the assurance claim
The sustainability team supplies statement AS-02. In this example, it covers specified group GHG emissions for calendar 2025; its scope does not include the Site Cedar electricity subtotal in E-04. The internal assurance liaison checks the actual statement, covered information, period and limitations. They do not issue an assurance opinion.
The proposed answer therefore says that AS-02 does not establish independent assurance of the requested figure. A salesperson's description of the group report as “assured” cannot resolve the mismatch. If the statement's coverage were unclear, interpretation would remain open until clarified with the appropriate specialist.
GRI 2: General Disclosures 2021, Disclosure 2-5, distinguishes what has been assured, the basis, level and limitations. Disclosure 2-14 addresses review and approval of sustainability reporting. These are references within GRI reporting; they do not require board approval of every customer questionnaire or convert internal review into external assurance.
Q17-C Upload the supporting bills
Finance holds the bills and can explain their contents. The disclosure authoriser checks the named customer's intended use and portal audience. In this fictional case, that authoriser permits an identified extract of the available records for the customer's reporting reviewer, and the customer confirms that this evidence route is acceptable. Permission does not extend to full bills or public reuse.
The coordinator records the approved extract version, recipient, purpose and channel beside Q17-C. The full records stay controlled. Q17-A remains partial even though an extract can be shared: disclosure approval does not supply March's missing consumption. Use the confidential supplier-evidence guide for the separate task of choosing and checking a disclosure route.
Q17-D Confirm the future commitment
Operations has a feasibility note about renewable electricity. Procurement has no completed arrangement supporting the customer's requested date, and management has not approved the proposed commitment. The coordinator sends the precise decision to the manager authorised to make such commitments, with operational and procurement input.
The note supports discussion, not the requested confirmation. The authorised manager decides that no commitment can be confirmed at this stage. Any later proposal must specify the covered sites or products, meaning of the claim, timing, dependencies and approval. The response approver preserves the current decision rather than replacing it with “in progress” if that would imply a commitment exists.
Recombine the answers without losing the qualifications
Read the four parts against the original Q17. Check cross-references such as “this figure” and “supporting bills”: the assurance answer and permitted extract must refer to the same quantity and period as the factual answer. Resolve conflicts before assembling the final response.
For this fictional exercise only, assume the customer clarifies that Q17-A requires whole-site electricity with no product allocation, accepts a qualified partial answer and agrees to the extract route above. The required internal owners approve that exact scope and wording. The coordinator could then assemble:
“Site Cedar's purchased electricity for 1 April 2025 to 28 February 2026 was 88,500 kWh. March 2026 remains unavailable, so this is not the requested full-year total. AS-02 does not cover this site electricity subtotal, and we cannot confirm it as independently assured. The agreed extract supports the available period and is approved for your named reporting reviewer through the agreed portal route. We cannot confirm the renewable-electricity commitment requested from 1 April 2027.”
This illustrative wording gives four outcomes, rather than one blanket “yes”. It makes no promise about a date for closing the remaining gap. If the customer's format cannot preserve these qualifications, keep the submission decision pending and resolve the format with the authorised contact. The supplier questionnaire response guide covers that broader submission process.
Keep the dependency and approval record usable
Attach the final wording to the unchanged parent question and its internal parts. For each part, retain the evidence version, interpretation decision, release permission, response approval and open next action. Record who decided, when and what their decision covered. An approval labelled only “Q17 approved” is ambiguous if it omits the partial-period qualification or the attachment restriction.
When the March record arrives, reopen Q17-A and the linked evidence-release decision for the revised attachment. Recheck Q17-B against the revised figure; a more complete consumption schedule does not expand AS-02's scope. Q17-D changes only when the authorised commitment decision changes. Keep superseded answers and approvals linked so nobody reuses the earlier version as current.
Other ESG questions need their own topic expertise. A workforce question may need HR evidence and privacy review; a product claim may need technical and commercial decisions. Route the specific question, rather than assigning every item containing “ESG” to one department.
Organise a reviewable customer response
Nitium's value-chain ESG reporting support helps coordinate partner information, responses, coverage and data gaps within an agreed scope. Discuss a customer-response handover using a non-confidential description of the question and the decisions holding it up.
Sources checked 13 October 2026. References are the GHG Protocol Supplier Engagement Guidance, OECD's 2018 Due Diligence Guidance and GRI 2: General Disclosures 2021. This suggested workflow does not determine legal obligations, authorise disclosure, guarantee customer acceptance or provide certification or independent assurance.
Comments