An earlier article said that reviewing a certificate means asking who verified it. So which names come back?
Put the published programmes side by side and it looks like this.
- DP World's UK carbon inset programme — Bureau Veritas (Unifeeder, DP World Southampton), Verifavia (Svitzer)
- 123Carbon platform, MOL's issuance — Verifavia
- 123Carbon platform, from 2026 — SCS Global Services
They overlap
Verifavia appears in two of them. Separate programmes, built by different operators, using the same verifier.
What that means in practice
First, the range of names that can come back is already narrow. A body you have never heard of is itself a signal to check.
Second, preparing once mostly carries. These bodies each have their own procedures and document requests, but those requests do not differ greatly from one programme to the next. Records built to satisfy one will mostly satisfy another.
Which is to say the preparation does not have to be redone per programme.
※ This article cites published material. The companies and bodies named have no contractual relationship with us.
This article expands one section of LCS EAC special report 3, Who Vouches for It. The full report works from published material by 123Carbon and DP World and from SBTi's Corporate Net-Zero Standard V2.0 as primary sources, and does not fill in values that were never published.
Who Vouches for It
A certificate is verified before it is issued, not after
PDF · 4 pp. · 0.6 MB
