Last updated: May 31, 2026. A supplier sustainability questionnaire usually arrives at the wrong moment. It may come from a customer portal, a procurement team, a contract renewal, CDP, EcoVadis, a tender, or an account manager who forwards it with a short note: can we fill this in by Friday?
The difficult part is not always the questionnaire itself. It is working out what the customer expects from the answer. Some questions are asking for facts. Some are asking for documents. Some are asking whether you have a policy, target, calculation, certificate, process, or improvement plan. Some look simple but create risk if you answer too confidently without evidence.
Short answer: if a customer sends you a supplier sustainability questionnaire, do not answer it line by line straight away. First confirm the deadline, scope, requesting customer, platform, required evidence, and whether the questionnaire is asking for emissions data, policies, due-diligence evidence, certifications, targets, or a portal response. Then collect the evidence you actually have, mark gaps honestly, explain assumptions, and keep a reusable response file for future customer requests.
Start by slowing the questionnaire down
The first mistake is to treat the questionnaire like ordinary admin. Someone opens the portal, answers from memory, uploads whatever documents are easiest to find, and hopes the customer accepts it. That may be fine for low-risk questions. It is less fine when the answers cover emissions, labor practices, human rights, renewable electricity, anti-corruption, supplier due diligence, product claims, or targets.
Before answering, save a copy of the request. Keep the email, portal screenshots, deadline, customer name, legal entity, requested reporting period, help text, and any scoring guidance. If it is a platform request, identify whether the customer is asking for a full assessment, a light screening questionnaire, a CDP response, an EcoVadis rating, a buyer-specific scorecard, or a one-off file upload.
This matters because the response path changes. A short onboarding questionnaire may only need policies and basic company information. A CDP supply-chain request may ask for environmental disclosure in a standardized format; CDP says approximately 45,000 suppliers were requested to disclose through its Supply Chain program in 2025. EcoVadis explains that its questionnaires are customized by company profile and that supporting documents are used to validate answers. A customer-specific questionnaire may ask for exactly the same topics, but with a different level of evidence and a different deadline.
Work out what the customer is really asking for
Most supplier sustainability questionnaires are trying to answer a few practical questions about your company. The wording varies, but the underlying themes are usually consistent.
First, the customer wants to understand your company boundary. Which legal entity, site, region, service line, or reporting year does the answer cover? A group-level policy may not answer a site-level question. A global emissions figure may not answer a customer asking about the service delivered to them.
Second, the customer wants to know whether you have actual data. That may include Scope 1 and Scope 2 emissions, relevant Scope 3 categories, electricity use, fuel use, water, waste, travel, freight, packaging, renewable electricity, or product-related information.
Third, the customer wants evidence. A questionnaire answer without evidence can look weak even when the answer is true. Evidence might be a policy, calculation workbook, utility bill, certification, board-approved target, supplier code, training record, risk assessment, audit report, or methodology note.
Fourth, the customer wants to understand whether your company manages the issue, not just whether you can write about it. A policy is useful, but a policy plus owner, process, data, and recent activity is stronger.
Finally, the customer wants to know what happens next. If you do not have complete data yet, they may still accept a clear answer that explains what is available, what is estimated, what is missing, and when the gap will be addressed.
Build the answer from evidence, not ambition
A good response is usually specific and modest. It says what is true today, what evidence supports it, and what is still being improved. That is better than trying to sound more mature than the company really is.
For example, if the questionnaire asks whether you calculate greenhouse gas emissions, do not simply answer "yes" because someone once estimated electricity emissions for a proposal. Check the boundary, reporting year, scopes, emission factors, calculation file, and whether the number was reviewed. If the calculation is only Scope 1 and Scope 2, say that. If Scope 3 is still being screened, say that. If the customer asks for service-level emissions, do not send a company-wide footprint without explaining the allocation method.
The same principle applies to policies and commitments. If you have a policy, upload the current signed version and make sure the answer matches the policy. If the policy is informal, outdated, or only covers one office, do not describe it as a global management system. If you do not have a target, it is usually better to say that a target has not yet been set than to invent one during the questionnaire.
Use a simple response file
You do not need a large ESG report to respond to most supplier questionnaires. What you need is a practical response file that gathers the common evidence in one place.
A useful supplier questionnaire response file usually includes:
- the original customer request, deadline, portal link, and contact person;
- company details, legal entity, sites, reporting period, and ownership boundary;
- Scope 1 and Scope 2 emissions data, with methodology notes and source files;
- a screening view of relevant Scope 3 categories, especially purchased goods, transport, travel, waste, and outsourced services where relevant;
- environmental, labor, human rights, ethics, data privacy, and procurement policies where available;
- certificates, audit reports, training records, risk assessments, or management-system evidence;
- answers to common customer questions, with notes on evidence and limitations;
- a gap list showing what still needs to be improved or collected for the next request.
The file should be reusable. Many suppliers receive similar questions from different customers. If every response starts from scratch, the company loses time and may give inconsistent answers. A response file helps finance, operations, HR, procurement, legal, and account teams answer from the same evidence base.
Be careful with "yes", "no", and "not applicable"
Questionnaires often force neat answer choices onto messy reality. Be deliberate.
Use "yes" only when the answer is true for the requested scope and period. Use "no" when the company does not have the policy, process, data, target, or evidence. Use "not applicable" only when the topic genuinely does not apply to your business or the assessed entity, and add a short explanation where the portal allows it.
"Partially" or a free-text explanation can be helpful when the company has started but is not complete. For example, you might have calculated electricity and fuel emissions but not yet screened Scope 3. You might have an anti-bribery policy but no formal supplier due-diligence process. You might have ISO certification for one site but not all sites. These distinctions matter.
A practical answer does not need to make the company look perfect. It needs to be accurate, supportable, and clear enough for the customer to understand the current state.
What usually goes wrong
The most common problem is over-answering. A supplier receives a narrow request and turns it into a broad ESG exercise. The team starts drafting a sustainability strategy, searching for software, and writing policies before confirming what the customer actually needs.
The second problem is under-documenting. The company may have reasonable practices, but the answer is not backed by evidence. A customer reviewing a questionnaire often cannot credit a claim unless the document, calculation, policy, or methodology is attached.
The third problem is inconsistency. One customer receives one emissions number, another receives a different number, and nobody can explain the difference. This usually happens when requests are handled by different teams without a shared calculation file or response register.
The fourth problem is treating every platform the same. CDP, EcoVadis, customer portals, tender questionnaires, and procurement scorecards can overlap, but they are not identical. Each has its own scope, scoring logic, evidence requirements, visibility rules, and deadlines.
If the data is incomplete, say so clearly
Incomplete data is normal, especially for suppliers responding for the first time. The goal is not to pretend otherwise. The goal is to give the customer the best available answer and explain how it was prepared.
If you used estimates, say which assumptions were used. If a site was excluded, explain why. If Scope 3 is not complete, say which categories have been screened and which are not yet available. If an answer is based on a group policy, say whether it applies to the entity or site in the questionnaire. If the customer asks for assurance or verification and you do not have it, do not call a consultant note or internal review "assurance".
Many customers prefer an honest, well-documented partial response over an ambitious unsupported one. It gives them something they can review, and it gives your team a clear path for annual improvement.
When to ask for help
You can often handle a simple questionnaire internally. It becomes more useful to get support when the request is tied to a major customer, a short deadline, a platform such as CDP or EcoVadis, a request for emissions calculations, a service-level allocation, a consultant letter, independent assurance, or a tender where the answer may affect commercial scoring.
Support is also useful when no one internally owns sustainability. In many suppliers, the request lands with finance, operations, HR, legal, sales, or a founder. A focused review can help the team interpret the questionnaire, collect the right evidence, avoid overclaiming, and prepare a response that can be reused next year.
FAQ
Do we need a full sustainability report to answer a supplier questionnaire?
Usually no. A focused response file with the right evidence is often more useful than a broad sustainability report. Some customers may ask for a published report, but many are asking for specific data, policies, or supporting documents.
What if we do not have all the policies requested?
Do not invent them during the questionnaire. Answer honestly, explain what exists, and identify priority gaps. If a policy is commercially important, create it properly with the right owner and scope rather than rushing a generic document.
What if the customer asks for emissions data inside the questionnaire?
Treat the emissions section as its own workstream. Confirm the reporting period, scopes, activity data, emission factors, methodology, evidence files, and whether the customer wants company-level or service-level data. If the emissions request is substantial, start with the customer request itself before calculating; Keslio's customer emissions data request guide walks through that first-read process.
Can we reuse the same answers for every customer?
You can reuse the same evidence base, but you should still check each customer's wording. A question about group-level sustainability practices is different from a question about the specific service, site, contract, product, or reporting year.
Have a supplier questionnaire in front of you?
Keslio can help review the request, map the evidence needed, prepare emissions data where required, and turn the response into a reusable file for future customer requests. View supplier request support.
