Navigating the risks of greenwashing in the voluntary carbon market
On a dark tabletop, a green line separates two clear trays. One contains a machined metal component and papers. The other contains a binder and ruled sheet. No legible product or registry identifiers are visible.
Diagram text description
Greenwashing risk rises when a public carbon credit statement implies a result the evidence cannot support. A buyer can hold valid paperwork for one purchase and still mislead readers if the wording suggests that an entire product or company has no climate impact. Check the impression created by the headline, images and nearby qualifications as well as the literal sentence.
Follow the claim through four questions. Which entity, activity and period does it cover? What project evidence supports the credit's stated outcome? Which units can the business show it bought or retired for that use? Does the final wording stay within those records? A missing answer changes what the company can responsibly say.
Run that review early enough to change the transaction or the proposed message. A seller may be able to supply a missing project document. An inventory team may need longer to collect product data. Neither should be pressed into approving a broader statement just because a launch date has been set.
Map the claim before the transaction
Write the claim and name its channel before procurement. A sentence on a corporate reporting page may be read differently from the same words printed beside a price or on a product label. Identify who will see it, which product or organisation it refers to, the period and which emissions the reader is likely to think it covers.
Consider this fictional example. Moorline Lighting plans to put “Our 2025 desk lamp range is carbon neutral” above the buy button. Its file contains a 2025 inventory of 190 metric tonnes of carbon dioxide equivalent from fuel and purchased electricity at one assembly plant. It has no footprint for the range. It has yet to measure the impacts of purchased components, transport, use and end of life. A paid invoice and a matching registry transfer show the business bought 60 issued credits from the fictional Fenbank project.
The headline invites shoppers to infer a conclusion about the lamps across their life cycle. The plant inventory covers one part of one business and the purchase record proves a separate transaction. Neither supplies the missing product boundary. The reviewer removes the headline from the product page.
A narrower statement for the company's report is “In 2025 Moorline Lighting bought 60 issued carbon credits from the Fenbank project. We record the purchase separately from emissions from fuel and electricity at our assembly plant.” That description fits the records in the example. It makes no retirement claim and provides no conclusion about the lamps' total impact.
The fictional proposed carbon-neutral lamp claim implies a life-cycle outcome for the range. The 2025 evidence is a plant-boundary inventory and the purchase of 60 issued Fenbank units. Review the exact claim, project, registry status and audience before choosing company-report wording.
Diagram text description
The UK voluntary integrity principles encourage accurate terminology and disclosure, and UK consumer claims guidance asks businesses to consider the full life cycle and the overall impression. Those sources guide the review. The fictional decision establishes an evidence mismatch rather than a finding that a particular law has been breached. Check the actual market, channel and applicable rules for a live claim.
Examine credit-level integrity
A credit programme name identifies the rules to investigate. It gives the buyer a starting point for checking the project, method version, monitoring period and verified outcome. Ask how the project assessed additionality, how it chose its baseline, what quantities were measured or estimated, and what the verifier actually reviewed. Record the safeguards evidence and any unresolved impact on communities or ecosystems.
Monitoring and durability questions depend on the mechanism. Compare the records for the actual project and offered batch instead of assigning one risk score to all forest or engineered activities.
| Evidence question | Forest carbon project | Engineered removal with geological storage |
|---|---|---|
| What was monitored? | Ask how the project estimates carbon stocks and checks changes across the included land | Ask how the project measures captured and stored carbon and accounts for process emissions |
| What could change the outcome? | Ask how the project handles fire, harvest, disease and activity moving outside its boundary | Ask how the operator tracks storage and responds to possible leakage or interrupted monitoring |
| What evidence belongs in the file? | Method, monitoring and verification for the offered period, plus safeguards and reversal arrangements | Method and verification for the offered batch, plus energy, transport and storage evidence where relevant |
Table 1, shown one row at a time. Every field is retained.
Row 1
- Evidence question
- What was monitored?
- Forest carbon project
- Ask how the project estimates carbon stocks and checks changes across the included land
- Engineered removal with geological storage
- Ask how the project measures captured and stored carbon and accounts for process emissions
Row 2
- Evidence question
- What could change the outcome?
- Forest carbon project
- Ask how the project handles fire, harvest, disease and activity moving outside its boundary
- Engineered removal with geological storage
- Ask how the operator tracks storage and responds to possible leakage or interrupted monitoring
Row 3
- Evidence question
- What evidence belongs in the file?
- Forest carbon project
- Method, monitoring and verification for the offered period, plus safeguards and reversal arrangements
- Engineered removal with geological storage
- Method and verification for the offered batch, plus energy, transport and storage evidence where relevant
For the forest mechanism, examine estimated carbon stocks, land and the response to fire, harvest or other reversals. For engineered removal with geological storage, examine measured capture and storage, associated emissions and tracking of leakage or storage integrity. Verify the evidence for the offered batch.
Diagram text description
Use the table to ask for evidence rather than to infer a storage lifetime or preferred project type. For either offer, check whether the quantified outcome and vintage match the units being sold. If the supplier cannot explain a material assumption, keep that uncertainty visible in the buying decision and in any proposed wording.
Check market infrastructure and ownership
Match the offer and contract to the issued batch, then follow its unit references through the registry records. Ask who holds the account, what rights the contract transfers, whether any restrictions apply and who can request retirement. For a supplier retirement service, require evidence of the beneficiary and designated use. Keep the invoice alongside those records because the documents answer different questions.
Continue the fictional Moorline example. A marketing team wants to add “We retired 60 credits for our desk lamps” to the product page. Its approval file identifies the offer and paid purchase as 60 Fenbank units and the incoming transfer as the same 60. ML-201 to ML-260 are fictional internal references. In a real file they would be mapped to the programme's identifiers.
| Review item | Recorded evidence | Decision |
|---|---|---|
| Offer and title | Contract and transfer match ML-201 to ML-260 in the buyer's account | Purchase record reconciles to 60 units |
| Registry status | ML-201 to ML-240 show retired status and ML-241 to ML-260 remain active | Only 40 have a retirement record |
| Beneficiary and use | The retirement export for the 40 names a distributor and omits the intended use | Beneficiary and use for Moorline remain unresolved |
| Proposed product wording | The team asks to attribute all 60 to the lamp range | Hold the wording and block allocation |
Table 2, shown one row at a time. Every field is retained.
Row 1
- Review item
- Offer and title
- Recorded evidence
- Contract and transfer match ML-201 to ML-260 in the buyer's account
- Decision
- Purchase record reconciles to 60 units
Row 2
- Review item
- Registry status
- Recorded evidence
- ML-201 to ML-240 show retired status and ML-241 to ML-260 remain active
- Decision
- Only 40 have a retirement record
Row 3
- Review item
- Beneficiary and use
- Recorded evidence
- The retirement export for the 40 names a distributor and omits the intended use
- Decision
- Beneficiary and use for Moorline remain unresolved
Row 4
- Review item
- Proposed product wording
- Recorded evidence
- The team asks to attribute all 60 to the lamp range
- Decision
- Hold the wording and block allocation
In the fictional registry, ML-201 to ML-240 are retired and ML-241 to ML-260 remain active. The retirement export names a distributor and omits the intended use. Hold the lamp claim and block allocation until registry evidence and the product scope support it.
Diagram text description
The registry records owner asks the account holder to explain the discrepancy and obtain authoritative evidence of the beneficiary and use. Procurement checks the agreed rights and remedy. The claim approver keeps the statement on hold until both the registry evidence and the product scope support it. The active units stay outside the retirement figure. The 40 retired units stay out of Moorline's allocation unless the records establish that use. The allocation check also prevents a customer, intermediary or another team from using the same unit references to substantiate a separate quantity.
Keep reductions and credits separate
Keep the inventory and progress report separate from the credit register. The inventory records emissions for the defined entity and period. The progress record explains actual operational changes and which emissions they affect. The credit register records purchases, status, beneficiary and intended use. The reader should be able to see each number and what it measures.
| Record | What the fictional business can show |
|---|---|
| Gross inventory | 190 metric tonnes of carbon dioxide equivalent for 2025 fuel and purchased electricity at the assembly plant |
| Operational progress | Any change requires comparable inventory data and an explanation of its cause |
| Credit activity | 60 issued units bought, 40 retired with beneficiary unresolved and 20 active |
Table 3, shown one row at a time. Every field is retained.
Row 1
- Record
- Gross inventory
- What the fictional business can show
- 190 metric tonnes of carbon dioxide equivalent for 2025 fuel and purchased electricity at the assembly plant
Row 2
- Record
- Operational progress
- What the fictional business can show
- Any change requires comparable inventory data and an explanation of its cause
Row 3
- Record
- Credit activity
- What the fictional business can show
- 60 issued units bought, 40 retired with beneficiary unresolved and 20 active
The 190 tonnes remain the measured boundary in this example. Reporting the purchase beside it leaves the gross figure and excluded stages visible. If the business later uses credits in a claim about compensation, explain the applicable framework, the boundary and which units support it. A contribution statement can describe the purchase on its own terms. Decide which statement the business is making before calculating or displaying any combined number.
A similar check applies when internal results improve. A lower total could reflect a change in production volumes, a reduction project or a measurement change. Explain the cause only to the extent supported by the records.
Create an evidence-to-claim table
Put each proposed phrase into a review table and record what it means to the audience. Keep the evidence reference and limitation near the wording so the person approving it can see which qualifiers matter.
| Proposed phrase | Meaning and supporting record | Limitation | Approver |
|---|---|---|---|
| Bought 60 issued credits in 2025 | Paid invoice and matching transfer for Fenbank units | Purchase only | Procurement lead |
| Plant fuel and electricity emissions | Inventory file for the named assembly plant and year | No product life cycle result | Inventory owner |
| Retired for the lamp range | Retirement, beneficiary and product allocation would all need evidence | Status and scope gap in the fictional file | Registry owner and claim approver |
| Carbon neutral range | An overall product conclusion needing evidence for the full impression | The available file cannot support the words | Claim approver with applicable legal and method review |
Table 4, shown one row at a time. Every field is retained.
Row 1
- Proposed phrase
- Bought 60 issued credits in 2025
- Meaning and supporting record
- Paid invoice and matching transfer for Fenbank units
- Limitation
- Purchase only
- Approver
- Procurement lead
Row 2
- Proposed phrase
- Plant fuel and electricity emissions
- Meaning and supporting record
- Inventory file for the named assembly plant and year
- Limitation
- No product life cycle result
- Approver
- Inventory owner
Row 3
- Proposed phrase
- Retired for the lamp range
- Meaning and supporting record
- Retirement, beneficiary and product allocation would all need evidence
- Limitation
- Status and scope gap in the fictional file
- Approver
- Registry owner and claim approver
Row 4
- Proposed phrase
- Carbon neutral range
- Meaning and supporting record
- An overall product conclusion needing evidence for the full impression
- Limitation
- The available file cannot support the words
- Approver
- Claim approver with applicable legal and method review
This table identifies the basis for a narrow purchase statement and makes the broader claims easy to hold. Remove unsupported adjectives and reconsider imagery or icons that could reintroduce the same impression. A qualification hidden in a download may do little to change how the headline reads. Review the full page or label as the audience will encounter it.
Give the approved version a date, channel and owner. Link the actual wording to the evidence files, so a later reader can tell what was approved and why. Recheck a changed headline or a move to a different channel against the same table.
Monitor after publication
A claim can need reassessment after publication. Assign someone to monitor the project and registry for changes relevant to the batch, and have the claim owner track changes to the method, audience or applicable requirements. A reversal, revised verification result or significant concern about project safeguards should prompt a review of what the published statement actually says.
When a change arrives, record the date and affected claim, pause any new use of the wording if its basis is unclear, and decide whether to update or withdraw what is already public. Correct the affected channels openly. Preserve the old wording, the evidence used at the time, the reason for the change and the approval of the replacement. The diagram shows the path from a change in evidence to a traceable new decision.
Document the changed fact or requirement, review the affected wording and correct or withdraw unsupported claims in the affected channels. Retain the previous wording, evidence and decision alongside the new response.
Diagram text description
The action should match the scope of the problem. A changed fact about a project may affect statements about its outcomes without changing the fact that the company bought units. Identify which words depend on the changed evidence before deciding how much to amend. Record who will follow up if the evidence remains incomplete.
Trace product evidence to the right version
A credible product statement starts with the product evidence. Keep the item and revision, bill of materials and supplier records together with the calculation method and the boundary. The owner should be able to trace a reported quantity to the input, period and unit behind it.
For example, the power supply in a new lamp revision may differ from the one covered by last year's supplier record. Ask which revision the data describes and what use assumptions the calculation makes. Record an evidence gap if the new component cannot be matched. That gap belongs in the product assessment. The registry file can identify a credit transaction, but it supplies no data about electricity used by the lamp.
Keep project diligence with the people assessing the project and credit evidence. Keep wording approval with the people accountable for the actual claim and audience. A better product record helps narrow uncertainty within its own boundary and gives the reviewer a clearer basis for deciding what can be said.
Hold wording that exceeds the evidence
A sceptical reader should be able to trace a carbon credit statement to a boundary, project record, unit status and accountable decision. Start with the sentence the audience will see and check those records in order. Hold any part that depends on an unresolved fact.
Moorline's purchase can be described within the evidence available. Its product headline and claimed retirement remain on hold for separate reasons. The inventory team needs product data, and the registry owner needs reliable beneficiary and use evidence. When those owners return with new information, revisit the words and the channel before making a different claim. Keep the earlier decision so a reviewer can see what changed.
