top of page

How to answer a customer's supplier ESG questionnaire

Writer: Divya Khatwani
Divya Khatwani
Oct 4
6 min read

Updated: Oct 19

When a customer sends an ESG questionnaire, start by clarifying what it is asking about. The same form can contain questions about your whole company, a particular factory, a product supplied to that customer and policies that apply across a group. Answering all of them using one convenient set of figures can create a misleading response.

This guide is for suppliers, including smaller businesses, preparing an evidence-based customer response. The aim is a clear, reviewable submission that states what is supported, what needs explanation and what is still unavailable. A completed questionnaire does not guarantee customer approval or a particular supplier rating.

Clarify the request before collecting more data

Read the instructions and ask the customer to resolve material ambiguities. Confirm:

  • Which legal entity, sites and products the questions cover

  • The reporting period and submission date

  • Whether figures should be company-wide or allocated to the customer's business

  • Required definitions, units and calculation methods

  • Which questions are mandatory and whether qualified answers are accepted

  • Who can access supporting records and whether the response will be published

Keep the customer's clarification with the final response. If the form requires a number that you cannot support, ask how to report a gap. Do not use zero or “not applicable” simply because a portal will not accept a blank field.

A buyer's request can arise from its procurement process, contractual expectations or reporting needs. Do not assume that receiving it makes your business directly subject to the buyer's reporting obligation. SEBI's January 2026 master circular, Chapter IV-B distinguishes a listed entity's BRSR requirements from its value-chain disclosures. Assess your own obligations and contracts separately.

Sort questions by the type of answer required

A practical review uses four groups. Policy questions ask what has been approved and whom it covers. Performance questions ask what happened during a period. Process questions ask how a control operates. Commitment questions ask what the business intends or agrees to do.

Each group needs different evidence. A signed policy may support a question about the existence of that policy; it does not establish that every worker received training. An attendance record supports participation, while evidence of effectiveness may require another review.

Route questions to the person who can substantiate them. Operations might own energy and waste information, HR workforce definitions and training records, and management public targets or commitments. Have someone check the response as a whole so definitions remain consistent across sections.

Use a response register before filling the portal

Create one row per question with these fields:

  1. Customer question ID and exact wording

  2. Entity, site, product and period requested

  3. Proposed answer and unit, where relevant

  4. Evidence reference and calculation method

  5. Coverage, exclusions and explanation

  6. Status: supported, needs clarification, unavailable or not applicable with a reason

  7. Data owner, reviewer and approval date

  8. Customer follow-up and final submitted version

This is an optional working structure, not a customer-approved form. Preserve the buyer's required format when submitting. The register gives your team a controlled place to reconcile answers before copying them into that format.

Link to supporting records rather than duplicating confidential material in every version. For HR-related questions, consider whether aggregate figures or redacted evidence meet the need. Confirm authorised recipients and disclosure permissions before sharing employee-level or commercially sensitive information.

Test whether the evidence answers the actual question

Try these three checks before copying an approved answer from a previous questionnaire. The examples are fictional and show response preparation, not a customer-approved scoring method.

  • Training coverage. The buyer asks whether every employee in the supplying site's defined year-end population completed a particular course. The controlled attendance record supports 42 of 50 employees, with eight outstanding. The supported result is 84% for that population and course. A group training policy does not justify selecting “all employees trained”. Check joiners, leavers, duplicate attendance and the buyer's population definition before using the percentage.

  • Certificate coverage. A certificate names Factory A, while the order is supplied from Factory B. Record the actual holder, scope, site and validity. Ask whether the buyer wants the supplying site's status or a group-level statement; do not use Factory A's certificate as proof that Factory B is certified.

  • Data type. A meter schedule supports electricity consumption, but the buyer asks for a product footprint. Retain the kWh as activity data and ask for the required product boundary and method. A company energy record is an input, not a completed product result.

Put the proposed answer, qualification and evidence locator next to each other. If the qualification changes the meaning of a yes/no response, resolve that before submission.

Answer emissions questions at the right level

First check whether the customer wants activity data, corporate emissions, a product footprint or an allocation. Electricity consumption in kWh is different from emissions in tonnes of CO2e. A corporate inventory also answers a different question from the footprint of one product.

The GHG Protocol Scope 3 Standard overview distinguishes corporate value-chain accounting from product accounting. Its supplier-data guidance supports clear requests, activity data where appropriate, and documentation of methods, assumptions and exclusions.

If you have reliable energy records but no completed inventory, explain that position. Ask whether the customer can accept the activity data for its stated purpose. Do not relabel the records as verified emissions or divide a company-wide total by sales without checking the requested allocation method.

A hypothetical partial-period response

This example is illustrative, not a Nitium client case or a recommended substitute for the customer's methodology.

A supplier has electricity records for April to December totalling 90,000 kWh. The customer's form asks for April to March consumption. The supported response is a nine-month total with the missing months identified. It is not an annual total of 90,000 kWh.

If an estimate is permitted and operationally justified, a simple annualisation would be 90,000 × 12 ÷ 9 = 120,000 kWh. That arithmetic assumes the missing period resembles the observed period. Seasonal demand, shutdowns or production changes could make the assumption unsuitable. Label any estimate, explain its basis and replace it when the missing records arrive.

When the portal cannot capture the supported answer

A forced numeric or yes/no field is a submission problem to resolve, not permission to invent a fact. Use this escalation sequence:

  1. Save the question, field instructions, allowed options and any validation message.

  2. Check the current question-specific guidance and whether a comment or evidence field can preserve the qualification.

  3. Describe the exact mismatch to the customer's named contact: what is requested, what is supported and what the form cannot express.

  4. Request an accepted way to state the gap, a permitted supporting schedule or a revised response deadline. Do not promise a completion date that your data owner has not confirmed.

  5. Keep the response pending until the authorised business owner approves an accurate submission route. Retain the customer's clarification with the final version.

For a platform-specific questionnaire, use that platform's current instructions. For example, CDP provides question-level and column-level reporting guidance. A workaround accepted for one buyer or platform should not be assumed acceptable elsewhere.

Review claims and commitments before submission

Check words such as “all”, “zero”, “fully”, “certified” and “verified”. Ask whether the evidence supports the complete scope implied. A certificate should be described using its actual holder, covered sites, scope and validity, without extending it to unrelated activities.

Read any declaration at the end of the form. A submission may ask management to confirm accuracy, accept supplier obligations or commit to future action. Route those decisions to the authorised person. Do not backdate a policy or promise a target merely to close a questionnaire field.

Retain the submitted file or portal export, attachments, approvals and material correspondence. Record when a response needs updating, particularly after changes to sites, reporting periods or methods. Reuse approved evidence in later questionnaires, but recheck that each new request asks the same question.

Final submission check

  • Every material answer uses the requested entity, site, period and unit, or explains the difference.

  • Measured figures, estimates, unsupported answers and reasoned non-applicability remain distinguishable.

  • Each attachment supports the statement made and can be shared with the actual recipients.

  • Qualifications survived the transfer from the working register into the portal.

  • Management approved new declarations, commitments and any public disclosure.

  • The saved response, attachment versions and approval record match what was submitted.

If a material error is found later, record the affected question and supporting correction, inform the authorised owner and follow the customer's amendment process. Keep the original submission and the corrected version linked rather than silently replacing your internal record.

Get help organising the response

Nitium's supplier and customer ESG response support can help structure responses, track evidence and make limitations clear. Discuss a customer questionnaire with its scope, deadline and the records already available. Share a non-confidential outline first if the request contains restricted information.

If you are collecting information from your own partners, our value-chain reporting guide covers request design and reporting coverage from the buyer's perspective.

Sources and substantive additions checked 5 October 2026. This guide is practical preparation support, not legal advice, certification or independent assurance.

Managing requests to your own suppliers? Use the supplier ESG response tracker and editable workbook to keep replies, evidence quality and reporting coverage separate.

 
 
 

Comments


bottom of page