Every customer ESG questionnaire starts the same way: someone searches old emails for energy bills, asks HR for headcount they supplied six months ago, and looks for an environmental policy that probably exists somewhere. The deadline arrives while the information is still being assembled.
A response system removes that search. It is not software and not a consultant. It is five organized components and a short routine that keeps them current. Once it exists, a questionnaire is a compilation exercise.
| Component | What it is | What it replaces |
|---|---|---|
| Master data file | One spreadsheet with all current ESG figures and methodology notes | Hunting through bills and HR exports |
| Policy library | One folder of current, signed policy PDFs | "I think we have one somewhere" |
| Standard answer library | Pre-written answers to the questions every questionnaire asks | Rewriting the same paragraph for each customer |
| Response archive | One folder per customer with what you sent and when | Starting from zero with a repeat customer |
| Data collection routine | Monthly, quarterly, and annual entries | Reconstructing a year from invoices |
What the system has to do
Three things. Hold current ESG data where it can be found. Hold the evidence a questionnaire will ask for. Make the next response start from the last one.
Everything below serves those three. If a component does not, leave it out.
1. Master data file
One spreadsheet containing all your current ESG data. Five tabs:
Company profile. Legal name, address, industry codes. Employee count, total and by location. Revenue range. Ownership structure. ESG contact.
Environmental. Energy consumption by type (electricity kWh, natural gas, fuel). Calculated Scope 1 and 2 emissions with methodology notes. Water consumption if tracked. Waste volumes by disposal route. Certifications and expiry dates.
Social. Headcount breakdown (FTE, contractors, by location). Safety metrics (incidents, lost-time injury rate, near misses). Training hours. Turnover. Diversity metrics if tracked.
Governance. Board or ownership composition. Policy list with file names and review dates. Certifications and standards. Compliance notes.
Tracking notes. What is measured versus estimated. Methodology. Where each source lives. Known gaps and the plan to close them.
Update it monthly or quarterly. Most questionnaire answers come from this file. Its categories line up with the EFRAG VSME standard, which an increasing number of EU customers use as their request format, so the same file covers those requests.
2. Policy library
One folder containing the current version of each policy:
- Environmental policy
- Health and safety policy
- Code of conduct / ethics policy
- Supplier code of conduct
- Anti-corruption / anti-bribery policy
- Data protection / privacy policy
- Equal opportunity / non-discrimination policy
- Quality policy
- Anything else relevant to your sector
Naming convention: [Policy Name]_v[version]_[YYYY-MM].pdf. Example: Environmental_Policy_v2_2025-09.pdf.
When a questionnaire asks "Do you have an environmental policy?", the answer is yes and the file is ready to upload.
3. Standard answer library
One document of pre-written answers to the questions every questionnaire asks. ESG questions repeat. "Describe your environmental policy" in an EcoVadis assessment wants the same information as "What is your approach to environmental management?" in a customer spreadsheet. The substance is identical; the phrasing differs. When several customers ask in different formats, this library stops you rewriting the same paragraph five times.
Organize it by topic, in the order questionnaires usually run:
- Company overview — description, activities, locations, structure
- Environmental — policy, management approach, energy, emissions, waste, water, targets, certifications
- Health and safety — policy, management system, risk assessment, incident handling, training, performance
- Labor and human rights — working conditions, training and development, diversity, grievance mechanism, due diligence
- Ethics and governance — code of conduct, anti-corruption, whistleblowing, data protection, oversight
- Supply chain — supplier code of conduct, how you assess suppliers, engagement
- Targets and commitments — what you have committed to and progress against it
Keep each answer at three lengths, because platforms impose different limits.
Short (one or two sentences) — for yes/no questions with a comment field:
We maintain a documented Environmental Policy covering energy efficiency, waste reduction, and pollution prevention, signed by senior leadership and reviewed annually.
Medium (one paragraph) — for standard description fields:
Our Environmental Policy establishes our commitment to minimizing environmental impact across all operations. It covers energy efficiency, greenhouse gas reduction, waste minimization, water conservation, and pollution prevention. The policy is signed by our Managing Director, communicated to all employees, and reviewed annually. Implementation is overseen by our Operations Manager, with environmental performance reviewed quarterly at management meetings.
Long (two or three paragraphs) — for platforms that want the full picture. Add when the policy was established and last updated, who holds day-to-day responsibility, how employees are trained on it, and how performance is tracked and reviewed.
Write only what is true. A standard answer describing a quarterly management review you do not hold becomes a problem when an auditor asks for the minutes. Where a number belongs in the text — emissions, headcount, incident rate — take it from the master data file rather than typing it, so the library never disagrees with the spreadsheet. If the emissions figures are missing, the free carbon calculator produces Scope 1 and 2 numbers you can reuse in every answer; state the GHG Protocol methodology once and reuse that too.
Using the library is roughly 80% copy and 20% adaptation. Match the customer's wording ("stewardship" versus "management"). Reformat bullets to prose or back. Add anything new since you wrote it. Do not paste unchanged; the question asked is rarely the question you wrote for. Do not rewrite from scratch; that is the scramble the system exists to end.
Check the topic list against the ESG response checklist before you write, so a category does not surprise you later.
4. Response archive
One folder per customer:
- The original questionnaire
- Your completed response (export or screenshots)
- Correspondence about it
- A note on what was difficult and what you learned
/Customer Responses
/CustomerA
/2025
- Original_questionnaire_2025.xlsx
- Our_response_2025.pdf
- Notes_2025.txt
/2026
...
/CustomerB
...
A repeat questionnaire from the same customer then starts from last year's answers.
5. Data collection routine
The routine keeps the master data file current. Without it the file is a snapshot that ages.
Monthly. Log utility consumption from bills as they arrive. Note any safety incidents. Flag significant changes (new hires, new site).
Quarterly. Update headcount and turnover. Review safety statistics year to date. Check certification expiry dates. Note completed improvement projects.
Annually. Calculate emissions from the logged energy data. Compile year-end summaries. Review and update policies. Refresh the training summary.
For the annual emissions step, the free carbon calculator converts logged energy and fuel data into Scope 1 and 2 figures consistent with the GHG Protocol. No spreadsheet formulas needed.
Setting it up
Week 1: gather and organize
Days 1–2: collect. Utility bills for the past twelve months. HR data exports. Safety incident logs. Every policy document you can find. Previous questionnaire responses. Certifications and audit reports. Do not evaluate yet. Put everything in one temporary folder.
Days 3–4: structure. Create the folders:
/ESG System
/Master Data
/Policy Library
/Customer Responses
/Source Data (raw bills, reports)
/Standard Answers (the answer library, plus email templates)
Day 5, morning: populate the master file. Work through each tab with the collected material. Write gaps down explicitly. Do not leave fields blank without a note. The ESG response checklist is a field-by-field starting point.
Day 5, afternoon: draft the standard answers. If you have any previous questionnaire response, harvest it; every narrative answer you wrote is a first draft. Otherwise write the short version of each topic first. Medium and long versions can follow as questionnaires demand them.
Week 2: fill gaps
Policies you need but do not have. Write the essential ones. Basic policies do not require legal review for most companies. A one-page environmental policy signed by leadership is legitimate and useful. The ESG policy template guide covers what to include and provides the environmental policy as a download; the supplier code of conduct template provides that document.
Data you should have but have not tracked. Decide what to track from now. You cannot recreate history. Note "tracking begins [month year]" in the master file where relevant.
Information held by colleagues. Request it from HR, finance, and operations. Enter it.
Week 3: routines
Set calendar reminders for the monthly, quarterly, and annual entries. Assign one owner; others contribute, one person keeps it current. Then test it: take an old questionnaire and answer it using only the system. Wherever you get stuck is the next gap to close.
Using the system when a questionnaire arrives
- Log and assess. Record customer, platform, deadline. Scan for scope.
- Map. Note which master-file tab or standard answer covers each question. Flag the ones the system does not cover.
- Populate. Numbers from the master file, narrative from the answer library, adapted to their wording.
- Handle gaps. Request specific data if it exists somewhere; otherwise write "not tracked" with an explanation.
- Attach. Policies and evidence from the library.
- Review and submit. Accuracy check; leadership sign-off if required.
- Archive and harvest. Save the response to the customer folder. Any question answered from scratch becomes a new entry in the answer library.
The work becomes compilation rather than archaeology: desk time, not days of chasing colleagues.
Keeping it working
The system fails in predictable ways.
Entries lapse. Monthly logging stops; six months later it is bill-hunting again. Fix: calendar reminders that are not dismissed.
Policies age. The 2019 safety policy is still the one in the library. Fix: annual policy review on a fixed date.
The archive gets untidy. Responses saved inconsistently; last year's answers cannot be found. Fix: the naming convention, kept.
Standard answers drift from reality. The library still says "reviewed quarterly" two years after the review stopped. Fix: read the library against what actually happened once a year; update the answer or restart the practice.
Ownership is vague. "Someone" maintains it, so no one does. Fix: name the person and put it in their role.
Fifteen minutes a month prevents days of crisis work. That is the whole case for the system.