Quality assurance

A number that was right last year has to still be right this year.

Quality assurance is everything that happens after sign-off. Methods are updated, factors are superseded, suppliers change hands, and a footprint nobody revisits quietly stops being true while still sitting on a product page.

Audit trailNumber → documentwith reviewer and date Expert verified
Method versionRecordedon every result
Re-run on updateAffected onlyscoped, not rebuilt
Products assessed100k+across 200+ companies

Sample values, to show the shape of the record.

The question this page answers

“What happens when your method or your factors change?”

The affected results are re-run, the change is restated where the figure is published, and the previous version stays on the record. A correction nobody can see is indistinguishable from an error nobody caught.

The standing checks

Five cadences, from every entry to every audit.

Assurance runs all year. These checks run at different frequencies for a reason: the cheap checks run constantly so the expensive ones stay rare.

  1. On every entry

    Automated validation at the point of capture

    Units, ranges, duplicates and impossible values are caught as the record is created, not in a clean-up sprint before a reporting deadline when nobody can remember what the source said.

  2. On every result

    The measured share is recomputed

    Whenever an input moves up a tier or a gap closes, the proportion of the result that came from primary data is recalculated. It is a live property of the figure, not a caption written once at launch.

  3. On every method update

    Affected products re-run and versioned

    When a factor is superseded or the method advances, we identify exactly which products and reports are affected and re-run those. Results carry the method version they were computed under, so two figures are never silently incomparable.

  4. On every reporting cycle

    Product and company figures reconciled

    The corporate inventory is reconciled against the product footprints underneath it, because Scope 3 and the product library disagreeing with each other is the single fastest way to lose an auditor’s confidence.

  5. On every audit

    The evidence pack, already assembled

    Values, source documents, factors, versions, reviewers and dates, exported together. It is assembled as the work happens rather than reconstructed under time pressure the week the assurance provider arrives.

Corrections

What we do when something turns out to be wrong.

Every organisation that measures anything at scale gets something wrong eventually. What distinguishes them is entirely what happens next.

  1. 01

    It gets found

    By our own standing checks, by your auditor, or by a supplier correcting themselves. All three routes lead to the same process, and the third is the one worth protecting: a supplier who is punished for a correction stops making them.

  2. 02

    The blast radius is measured

    Which products, which orders, which reports, which passports already published. The scope of a correction is established before anything is changed, not discovered afterwards.

  3. 03

    It is re-run

    The affected results are recomputed under the current method, and any published surface reading from them (a DPP, an ecoscore, a store widget) updates from the same dataset.

  4. 04

    It is restated visibly

    The change is stated where the figure lives, with the previous version retained. It is the step an assurance provider looks for first.

  5. 05

    The cause is closed

    Whatever check would have caught it earlier joins the standing set. A correction that does not change the process is just an apology.

What keeps it true

The machinery behind the trail.

Each one is tagged with which half of the work it is: the software, our team, or the place the two meet.

  • Method versioningPlatform
    Every result carries the method and dataset version it was computed under
  • Recalculation on updatePlatform
    Superseded factors trigger a re-run of exactly the affected products, not a full rebuild
  • Audit trailPlatform
    Any published number traces back to its document, its factor, its reviewer and its date
  • Audits & corrective actionsBoth
    Findings tracked to closure with an owner and a date, rather than living in a spreadsheet
  • Supplier scorecardsBoth
    Data quality tracked by supplier over time, so you know which relationship to work on next
  • Third-party audit supportPeople
    Our team sits with your assurance provider and answers from the record
Expertise

A method published in the peer-reviewed literature.

Keeping a figure defensible for years is a different discipline from producing it once. It is the reason the CSO sits on the account rather than on the methodology alone.

Prof. Dr. Kannan Muthu
Chief Sustainability Officer, Green Story
253peer-reviewed publications
4,550citations
36h-index
1,000+LCAs delivered
A review session with Green Story specialists and a supplier team around printed evidence
Where assurance stops

Assurance is not certification. We are not an accredited third-party verification body, and we will not offer our own review as a substitute for one where a scheme or a customer requires it. What we do is make that audit short and boring: the evidence, the factors, the versions and the reviewers are already assembled, and every number can be traced to the document it came from without anyone going hunting.

Start with one of your products

See the method run on something you sell.

Bring one product to the first call. We will take it from the purchase order to the figure: where each factor comes from, the evidence behind each input, and who signs it off.