How Sustin Works

From requirements to a traceable response

This page expands the five-step workflow from the home page and explains, in plain words, how the data fits together and who does what.

Five stages

  1. Requirements: what applies, by edition, financial year, undertaking size and request purpose.
  2. Evidence: source, period and coverage for each item.
  3. Gaps: what is missing or does not match.
  4. Reuse: where the same evidence serves other frameworks, through shared concepts.
  5. Response: a traceable answer, kept current as editions change.

The worked example: evidence and response

For one fictional supplier: how the answer to Q4 adds up from its records, and the response pack that goes back to the customer. The five steps are on the home page.

Evidence trail · Q4

What was your total energy consumption in 2027, in MWh?

Electricity · E1 Electricity invoices1,184 MWhGas · E2 Gas invoices612 MWhFuel · E3 Fuel log116 MWhTotal energy consumption1,912 MWh

Your traceable response pack

  • Request items: 14 questions, each with its purpose: 9 within the cap, 3 beyond it, 2 for other purposes.
  • Evidence: 5 documents, each with source, period and coverage, linked to the answers they support.
  • Gaps: 4 open, each with its reason, such as hours worked missing for the accident rate.
  • Reuse relationships: 22 reviewed relationships between the Voluntary Standard and GRI, through shared concepts.
  • Limits between standards: Where definitions, units or boundaries differ, for example accidents counted as events and injuries counted per person.
  • Review status: All Human-reviewed; Approved needs a second, independent reviewer; none yet.
See the response pack in the worked example

Explore the full worked example

The building blocks

1. Framework

A standard, regulation or set of principles.

2. Edition

A version of a framework, with the period in which it applies. Amendments and consolidated texts are tracked as editions; provisions mapped earlier stay linked to the text they were reviewed against until they are re-reviewed.

3. Provision

A requirement, clause or datapoint within an edition.

4. Concept

A shared meaning that several frameworks address, such as greenhouse-gas emissions.

5. Mapping

A relationship between a provision and a concept, with its type and review status.

6. Evidence

A document or record that supports a provision for a given period.

What each part does for the customer

PartWhat it does for the customer
Sustin engineShows how requirements relate, which evidence may be reused, and where differences and gaps lie
Sustin profileKeeps the organisation's own records, manages access, and holds the work and its organisation-level results
i5BenchmarkAn optional, separate framework for organisations that want an Industry 5.0 assessment

AI proposes relationships and drafts summaries, always labelled; named people review them. Organisations and their auditors make compliance conclusions. On the site this reads as one continuous experience, while data and responsibilities stay separate behind it. A relationship between two frameworks always runs through shared concepts, so each link can be checked on its own.