Can the ESG Report We Just Built Be Reused for the Next Request?

You spent two weeks getting through your first ESG document request. Six months later, a different buyer sends a similar one.

The previous submission exists somewhere — but you don’t know where. It’s in someone’s personal folder, or that person left and took it with them, or you can’t tell which version is the latest. So you start from scratch.

This post covers how to structure ESG data so it can actually be reused and how to make sure institutional memory survives a personnel change.

Why every request feels like the first one

Three reasons it keeps happening:

Reason 1: The data lives in someone’s personal folder. “I built it, so it’s in my drive” is the most common pattern. The moment data becomes a personal file rather than an organizational asset, it disappears the moment that person is unavailable.

Reason 2: File names and versions aren’t managed. EcoVadis_final.xlsx, EcoVadis_final_revised.xlsx, EcoVadis_final_actually_final.xlsx — nobody knows which one was actually submitted.

Reason 3: Every buyer uses a different format. Buyer A wants Excel. Buyer B uses a portal. Buyer C wants PDF. The formats are different, but the underlying data is mostly the same — even if it doesn’t feel that way.

The format differs; the data is the same

This is the key insight.

European ESG requests differ in form by buyer. The EcoVadis questionnaire, the VSME template, the buyer-specific survey — they look different, but the data they want is largely overlapping.

Strategy: Don’t build one report per buyer. Build a single source of ESG data and pull it into whatever format the next buyer requests.

Building a reuse-ready ESG data structure

Core idea: separate the data store from the submission packages

[ESG data store]
├── Environmental data (by year)
│   ├── Electricity: 2023 → 480,000 kWh / 2024 → 510,000 kWh
│   ├── Scope 1·2:  2023 → 261 tCO₂eq / 2024 → 274 tCO₂eq
│   └── Water:      2023 → 1,200 m³  / 2024 → 1,150 m³
├── Workforce data (by year)
│   ├── Total headcount: 2023 → 78  / 2024 → 82
│   └── Workplace incidents: 2023 → 1 / 2024 → 0
└── Document store
    ├── CE certification (expires 2026.03)
    ├── ISO 9001 (expires 2025.11)
    └── Business registration (no expiry)

                    ↓ on buyer request

[Submission package generation]
├── Buyer A — EcoVadis package (submitted 2024.06)
├── Buyer B — VSME package    (submitted 2025.01)
└── Buyer C — Custom survey   (submitted 2025.03)

With this structure in place, a new request becomes “pull from the data store, repackage to match the buyer’s format” — about 10–20% of the effort of starting from scratch.

Minimum-viable version (Excel structure)

You don’t need a system. An Excel file with this structure already makes a meaningful difference.

Tab 1: ESG data (by year)

Tab 2: Document registry

Tab 3: Submission history

Surviving a personnel change

The reason an ESG owner’s departure leads to data loss is that the data was attached to a person, not the organization. The fix is making sure the data belongs to the organization.

Three principles

Principle 1: Shared folder, not personal drive. No personal Google Drive, no personal PC. Use a company shared drive (Google Shared Drive, internal server) where every relevant person can access.

Principle 2: Standard file naming.

Format: [buyer]_[format]_[reference year]_[submission date]_[version]
Example: BuyerA_VSME_2024_20250115_v1.xlsx
         BuyerA_VSME_2024_20250120_v2_final.xlsx

Principle 3: A handover checklist. Pre-build the list of items the outgoing owner needs to transfer.

ESG handover checklist

Document expiry: the avoidable embarrassment

Pulling out a document for a buyer submission and finding it expired is a real problem. Re-issue takes 1–2 weeks; meanwhile you’re either missing the deadline or sending an apologetic email to the buyer. This is preventable.

Documents to track for expiry

Minimum expiry tracking

Method 1: Excel registry + calendar reminders. Add expiry dates to your document tab and set calendar reminders 60 and 30 days before expiry.

Method 2: Quarterly review. First week of each quarter, open the document tab and identify anything expiring in the next 3 months.

Annual update routine

ESG data needs annual updates. The most efficient setup is to lock in a yearly cadence so renewal requests don’t catch you cold.

Recommended annual routine

[Week 1, January] — Pull together prior-year data
  - General Affairs: collect annual electricity / gas / water totals
  - HR: workforce snapshot as of December 31
  - EHS: incident count, waste tonnage

[Week 3, January] — Update and recalculate
  - Recalculate Scope 1·2 (using latest emission factors)
  - Update ESG data store

[February] — Document review
  - Identify documents expiring this year
  - Schedule CE / ISO renewal audits

[Year-round] — Log submissions
  - When a buyer requests something, log file and date immediately

Once this routine is in place, a renewal request can be turned around in 1–2 weeks.

Do you have to manage this alone?

You can build and maintain this structure in Excel. But when a single person owns ESG and ESG isn’t their primary role, the routine often slips and files end up scattered again.

What matters is having a system. The tool can be Excel or a dedicated platform. The point is the data belongs to the organization, not to a person, and the next request doesn’t restart from zero.

Coming next

The final post covers the 2025–2026 EU ESG regulation changes. The CSRD scope was narrowed by the Omnibus Package — what does that actually mean for your business? What should you do now vs. defer?

→ Episode 6: 2025–2026 EU ESG Regulatory Changes — What’s the Impact?