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.
Sample values, to show the shape of the record.
“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.
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.
- 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.
- 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.
- 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.
- 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.
- 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.
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.
- 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.
- 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.
- 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.
- 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.
- 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.
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 versioningPlatformEvery result carries the method and dataset version it was computed under
- Recalculation on updatePlatformSuperseded factors trigger a re-run of exactly the affected products, not a full rebuild
- Audit trailPlatformAny published number traces back to its document, its factor, its reviewer and its date
- Audits & corrective actionsBothFindings tracked to closure with an owner and a date, rather than living in a spreadsheet
- Supplier scorecardsBothData quality tracked by supplier over time, so you know which relationship to work on next
- Third-party audit supportPeopleOur team sits with your assurance provider and answers from the record
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.

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.
The other parts of the method.
Where the number came from, what it arrived with, who signed for it, and what keeps it true afterwards. Each has a page of its own.