Ga naar hoofdinhoud
Terug naar inzichten
Reporting and Communications

Things Suppliers Should Prepare for in Sustainability Reporting

Keslio Team
Last updated: May 7, 2026
8 min. leestijd
Abstract editorial illustration for Things Suppliers Should Prepare for in Sustainability Reporting

Last updated: May 30, 2026. Suppliers are increasingly pulled into sustainability reporting because their customers need value-chain data. The request may not look like a formal sustainability report. It may be a buyer questionnaire, CDP or EcoVadis invitation, Microsoft or other enterprise supplier request, Scope 3 data request, due-diligence checklist, packaging declaration, or evidence upload.

Short answer: suppliers should prepare a compact response file before the next customer deadline arrives. The most useful starting point is not a long ESG report. It is a practical pack with company details, reporting boundary, emissions data, policies, evidence files, methodology notes, and owners for annual refreshes. That makes it easier to answer customer requests quickly, consistently, and credibly.

Why suppliers should prepare before the request arrives

Supplier sustainability requests often arrive with short deadlines and unclear ownership. The request may be forwarded to finance, operations, HR, procurement, legal, account management, or a founder. By the time the team understands what the buyer is asking for, the deadline may already be close.

Preparing in advance does not mean building a full ESG program before there is a customer need. It means organizing the documents and data that customers most often ask for. A supplier that can respond with clear emissions data, policies, evidence, and methodology will usually look more credible than one that sends broad statements without support.

This is especially important when the customer is a large enterprise. Buyers may ask suppliers for information because of CSRD, Scope 3 accounting, CDP supply-chain requests, procurement scoring, climate targets, human-rights due diligence, product compliance, or buyer-specific sustainability programs.

1. Keep the original customer request

The first file to save is the request itself. Keep the email, portal screenshots, questionnaire, contract clause, supplier guide, deadline, contact person, and any uploaded templates. Do not rely on a summary forwarded by someone else.

The exact wording matters. A request for company-level Scope 1 and Scope 2 emissions is different from a request for product carbon footprint data, service-level accounting, Scope 3 categories, independent assurance, or a consultant letter. The request wording determines the response path.

If the request is already in front of you, Keslio's supplier request support can start by reviewing the wording and turning it into a workplan.

2. Prepare basic company and boundary information

Most sustainability requests need basic reporting context. Suppliers should keep a simple profile covering:

  • legal entity name and trading name;
  • locations and facilities included in the response;
  • reporting period;
  • employee count or full-time equivalent count;
  • business activity, service lines, or product categories;
  • customer, contract, service, or project boundary where relevant;
  • organizational boundary, such as operational control or financial control; and
  • contact owners for finance, operations, HR, procurement, legal, and sustainability.

This sounds basic, but it prevents inconsistent answers across different customer portals. It also helps when the customer asks whether data covers one entity, one site, a group, a service line, or all operations.

3. Collect Scope 1 and Scope 2 emissions data

Emissions data is one of the most common customer asks. Suppliers should start with the data needed for Scope 1 and Scope 2 calculations:

  • electricity bills or meter readings;
  • purchased heat, steam, or cooling data where relevant;
  • fuel invoices for company vehicles, generators, boilers, or machinery;
  • refrigerant service records and top-up quantities;
  • facility lists, floor area, and lease information;
  • energy supplier information and renewable electricity certificates where applicable; and
  • supporting evidence for any market-based electricity claim.

For a deeper explanation of the accounting categories, see Keslio's guide to Scope 1, Scope 2, and Scope 3 emissions. For a calculation project, see GHG emissions calculations.

4. Screen relevant Scope 3 categories

Scope 3 is where many supplier responses become more difficult. A customer may ask for Scope 3 because it needs supplier data for its own value-chain emissions, or because the supplier's product or service is material to the customer's footprint.

Suppliers should prepare a first screen of the 15 Scope 3 categories, noting which are relevant, not relevant, estimated, or missing data. Common starting points include purchased goods and services, capital goods, fuel-and-energy-related activities, transportation and distribution, waste, business travel, employee commuting, leased assets, and use of sold products.

A first screen does not need perfect data. It should make the gaps visible and help prioritize the categories that matter for customer requests.

5. Build an evidence folder

Customers increasingly ask for support behind the answer, not just the answer itself. Suppliers should keep evidence files organized by reporting period and topic. Useful evidence can include:

  • utility bills, meter records, and energy contracts;
  • fuel, fleet, travel, logistics, and waste records;
  • procurement spend exports and supplier lists;
  • policies on ethics, labour, human rights, health and safety, environment, and responsible sourcing;
  • supplier codes of conduct and supplier onboarding materials;
  • training records, grievance mechanism documents, audit results, and corrective-action records;
  • product specifications, packaging data, certificates, and declarations; and
  • calculation files, emission factor sources, assumptions, exclusions, and methodology notes.

Evidence does not need to be perfect to be useful. But it should be findable. A response that cannot be refreshed next year is expensive every year.

6. Prepare policy and due-diligence materials

Not every supplier request is about emissions. Customers may ask about human rights, working conditions, health and safety, anti-corruption, grievance channels, forced labour, child labour, responsible sourcing, data privacy, or environmental management.

The EU Corporate Sustainability Due Diligence Directive targets large companies, but it can still affect suppliers indirectly because large companies need to identify and address human-rights and environmental impacts in their operations, subsidiaries, and business relationships. Suppliers may therefore be asked for policies or evidence even if they are not directly in scope.

Suppliers should avoid uploading generic policies that do not match actual practice. If the policy says the company audits suppliers, trains staff, or runs a grievance mechanism, the evidence folder should support that claim.

7. Prepare for CSRD-linked value-chain requests

CSRD-linked requests can be confusing because the supplier may not itself be directly covered by CSRD. Under the 2026 Omnibus I changes, the EU introduced a value-chain cap intended to reduce excessive trickle-down reporting burden for value-chain companies with 1,000 employees or fewer when the information is required for CSRD reporting purposes.

The European Commission's May 2026 guidance explains that the voluntary standard for smaller companies is not mandatory for value-chain companies, but it can shape what CSRD-reporting companies can require under the value-chain cap. Buyers may still ask for additional information for non-CSRD purposes, but the request should be read carefully.

For suppliers, the practical response is usually not a full ESRS report. It is a proportionate data pack that can answer the customer's specific request.

8. Prepare for portals and annual refreshes

Many requests come through portals such as CDP, EcoVadis, RBA-Online, customer procurement systems, or proprietary supplier platforms. Portal responses are easier when the supplier already has:

  • a current emissions calculation;
  • a policy and evidence folder;
  • standard company and boundary information;
  • a list of prior-year answers;
  • owners for each topic; and
  • a method for tracking changes year to year.

CDP's 2026 cycle, for example, asks companies to disclose environmental information through questionnaires and guidance in the CDP Portal, with large purchasing organizations using request lists to gather supplier information. Suppliers that wait until the portal opens are usually slower and less consistent.

9. Know when the request is buyer-specific

Some customer requests need a buyer-specific response path. Microsoft supplier GHG requests may involve total-company emissions, service-level accounting, methodology documentation, consultant-letter support, or independent assurance. Other buyers may focus on CDP, renewable electricity, supplier due diligence, product carbon data, RBA reporting, or third-party review.

Suppliers should not assume that one sustainability answer works for every customer. The same emissions calculation may support multiple responses, but the final wording, evidence, and deliverables can differ by buyer.

If the request is Microsoft-specific, see Keslio's Microsoft supplier GHG reporting support.

What suppliers should prepare first

If your team has limited time, start with this shortlist:

  • the original request and deadline;
  • basic company, entity, location, and reporting-period information;
  • Scope 1 and Scope 2 activity data;
  • a first Scope 3 category screen;
  • energy, travel, waste, logistics, procurement, and employee commuting data where relevant;
  • key policies and evidence for labour, human rights, health and safety, ethics, environment, and responsible sourcing;
  • product, packaging, or service-level data if commonly requested by customers;
  • methodology notes, assumptions, and source documents; and
  • an annual refresh owner.

Common mistakes to avoid

  • Writing a broad sustainability report when the customer asked for a focused data response.
  • Preparing emissions totals without boundaries, methodology, or evidence.
  • Ignoring Scope 3 until a customer asks for it.
  • Using old answers across portals without checking the current wording.
  • Confusing service-level emissions, product carbon footprinting, and company-level emissions.
  • Uploading policies that do not match actual practice.
  • Assuming consultant support is the same as independent assurance.
  • Leaving the response with one person instead of assigning finance, operations, HR, procurement, and legal owners.

How Keslio can help

Keslio helps suppliers prepare practical, customer-ready sustainability responses. Support can include request review, data checklists, emissions calculations, Scope 3 screening, methodology notes, evidence packs, service-level accounting, consultant-letter support where applicable, and annual refreshes.

For a broader overview of the types of requests suppliers receive, see Keslio's guide to supply chain reporting requirements suppliers need to know.

Need help preparing before the next supplier request?

If your team expects more customer sustainability, GHG, CDP, EcoVadis, or due-diligence requests, Keslio can help organize the data and evidence before the next deadline turns it into a scramble.

Customer sustainability request?

Has a customer asked you for sustainability data?

Keslio helps suppliers respond to enterprise customer requests for emissions data, CDP or EcoVadis information, clean-energy evidence, reduction plans, and supporting documentation.

Customer-specific responseFixed-fee quote after review
View supplier request support

Best fit when a customer request, portal instruction, scorecard, or deadline is already in front of you.

Klaar om te beginnen?

Ontdek wat Keslio voor u kan betekenen

Zet de volgende stap in uw duurzaamheidstraject door samen te werken met ons team