Skip to main content

ESG Data Snapshot — Form Schema (v1.0)

Purpose: 5-minute in-platform inventory served in SP-T1 module 5. Captures availability of data sources — never values, never uploads. Output seeds the personalized starting checklist in Tier 2 (Supplier Data Foundations).

Answer enum (every item): HAVE ("I have this") · DONT_HAVE ("I don't have this") · UNKNOWN ("I don't know") Default state: unanswered (null). Form submittable only when all items answered — "I don't know" is always a legitimate answer, so completion is never blocked by uncertainty.

Gating: completing the Snapshot is required before the Tier 2 checklist personalizes, but is NOT part of the SP-T1 completion gate (quiz only). If a supplier reaches Tier 2 without a Snapshot, Tier 2 opens with the generic checklist and a prompt to complete the Snapshot (2-minute detour, then personalizes).


Field list

Section E — Environmental sources

idLabel (EN master)Helper text
e_energy_billsElectricity / energy billsFrom your energy supplier — paper or digital, last 12 months
e_fuel_recordsFuel or vehicle recordsFuel receipts, fuel cards, or vehicle logs
e_heatingHeating recordsGas, oil, district heating, or similar — if separate from electricity
e_waste_invoicesWaste collection invoicesFrom your waste contractor — often shows weights or container sizes
e_water_billsWater billsFrom your water supplier
e_travel_recordsBusiness travel recordsFlights, hotels, mileage claims — expense system counts

Section S — Social sources

idLabel (EN master)Helper text
s_headcountEmployee headcount recordsPayroll or HR list — number of employees, contract types
s_safety_logAccident / safety logWorkplace incident register, however simple
s_training_recordsTraining recordsAny record of staff training completed
s_working_conditions_policyWorking-conditions or HR policyWritten rules on working hours, leave, conduct — an employee handbook counts

Section G — Governance sources

idLabel (EN master)Helper text
g_org_responsibilitiesOwnership / responsibility overviewWho owns the company and who is responsible for what — an org chart or a simple written note
g_code_of_conductCode of conduct or ethics policyYour own, or one you signed for a customer
g_supplier_overviewList of your own main suppliersAny list — accounting system export counts
g_certificatesCertificatesISO, industry, or product certificates — any kind
g_insurance_docsBusiness insurance documentsCurrent policy documents

Total: 15 items · 3 sections · target completion time ≤ 5 minutes.


Data contract

{
"snapshot_version": "1.0",
"supplier_eco_number": "string",
"completed_at": "ISO-8601",
"answers": {
"e_energy_bills": "HAVE | DONT_HAVE | UNKNOWN",
"...": "..."
}
}
  • Keyed to the supplier's E-C-O Number (entity-level, survives user changes).
  • Immutable per submission; resubmission creates a new version (Tier 2 reads latest). Version history retained — a later DONT_HAVE → HAVE transition is itself progress worth surfacing.
  • Snapshot answers do not affect the ESG score (stated in the form UI to keep answers honest: "This inventory never changes your score — answer honestly, it only shapes your checklist.").

Tier 2 checklist mapping

Snapshot answerTier 2 checklist behavior
HAVEItem appears as "Ready to enter — you have the source" (fast lane, listed first)
UNKNOWNItem appears as "Find out — here's where this usually lives" with locate-it hint
DONT_HAVEItem appears as "Set up — simplest way to start collecting this" with minimal-setup guidance

Sequencing rule in Tier 2: fast-lane items first (early wins → momentum), then UNKNOWN, then DONT_HAVE. The three behavior texts above are Tier 2 course content — flagged here so the Tier 2 spec includes locate-it hints and minimal-setup guidance for all 15 items.

UI notes

  • Render as three collapsible sections (E/S/G) with progress indicator (answered / 15).
  • Three-state segmented control per row; helper text always visible on mobile (suppliers will do this on phones).
  • On submit: confirmation with count summary ("You already have 9 of 15 common sources — better than most companies at this stage") — count-based encouragement only, no scoring language.
  • Localize labels + helper texts with course languages (same batch as SP-T1 translation).
GitHub RepoRequest for Change (RFC)