CARBON ACCOUNTING & GHG EMISSIONS
Product Carbon Footprint (PCF)
Turn product data into a reviewable carbon footprint. Make assumptions and gaps visible.
AIGreen Plus can help a Malaysian manufacturer define a product system boundary, collect activity evidence and document a reproducible PCF calculation approach. The engagement is a scoped consultancy proposal, not installed software, certified assurance or a promise of lower emissions.
Human review retainedCurrent-source check is conditionalFictional dashboard concept
See the review dashboard ↓
Photo by Yetkin Ağaç · Source: source page · Licence: Pexels License · Resized proportionally and converted to WebP; original content retained. Displayed in a landscape frame.
Product Carbon Footprint consultancy estimates greenhouse-gas emissions for a defined product and functional unit across agreed life-cycle stages. We help teams map materials, manufacturing, logistics, use and end-of-life data, record factors and evidence, and prepare a transparent calculation pack for authorised review. The method, boundary, factor choices and any external verification remain subject to client approval and qualified advisers.
01 / SEE THE REVIEW OUTPUT
Illustrative PCF evidence review
FICTIONAL SAMPLE / three product-system workstreams. This screen is a static illustration for discussion, not a connected customer system.
PROPOSED DASHBOARD CONCEPT
FICTIONAL SAMPLE / three product-system workstreamsIllustrative PCF evidence review
Illustrative open gaps by workstream
Fictional sample values · Bars compare fictional administrative follow-up items, not tonnes of emissions or environmental performance.
Unit: evidence gaps
| Workstream | Received records | Complete records | Open gaps | Example boundary note |
|---|---|---|---|---|
| Purchased materials | 8 | 6 | 2 | Cradle-to-gate candidate |
| Factory conversion | 7 | 5 | 2 | Site process data pending review |
| Packaging and dispatch | 6 | 5 | 1 | Outbound stage assumption logged |
AI-assisted draft / requires verification
Fictional sample: 21 activity records are listed, 16 are provisionally complete and five need follow-up. The draft highlights evidence questions only; it does not infer a hotspot, final footprint or reduction opportunity.
02 / FIVE REVIEW STAGES
Five steps, with an accountable owner.
Evidence, assumptions and open questions move through a human review route. No certification or automatic conclusion is implied.
- 01↓
Define product boundary
Agree purpose, unit and lifecycleDocument the product, reference flow, functional unit, lifecycle stages, cut-off rules and intended audience.
OWNER / CONTROLConsultant / authorised client sponsor - 02✓
Collect activity evidence
Request traceable source recordsStructure approved data for materials, energy, yield, transport, packaging, use and end-of-life where included.
OWNER / CONTROLClient data owners / consultant - 03≡
Build calculation basis
Record factors and assumptionsMap each activity to a selected unit, factor, source, version and date, keeping gaps and estimates visible.
OWNER / CONTROLConsultant / technical reviewer - 04◎
Qualify and review
Challenge completeness and consistencyRun reconciliation and sensitivity questions, distinguish lifecycle stages from organisational Scope 1, 2 or 3 labels, and route exceptions.
OWNER / CONTROLClient process owner / qualified reviewer - 05↗
Handover and roadmap
Leave a usable evidence trailDeliver the reviewed calculation pack, limitations register and prioritised next-step questions without claiming assurance or reductions.
OWNER / CONTROLConsultant / client approver
If a check fails: Hold the record for its owner, correct the source and preserve the approved manual fallback.
03 / RESPONSIBILITIES
Organise the work. Keep conclusions with people.
The proposed support can structure records and questions; responsible owners still assess evidence, applicability and decisions.
| Review point | Common starting position | Proposed consultancy support | Responsible reviewer |
|---|---|---|---|
| Set product system boundary and functional unit | Different teams keep scope notes in email and spreadsheets. | Proposed consultancy template centralises boundary decisions and evidence status. | Authorised sponsor approves purpose, inclusions, exclusions and method. |
| Reconcile activity records to product output | Analysts cross-check purchasing, production and logistics records by hand. | Proposed structured workbook flags missing units, periods and yield questions. | Process owners validate quantities, allocation and product reference flow. |
| Maintain factor provenance | Factor files and citations are difficult to trace across versions. | A proposed evidence register records factor, unit, source, version and date. | Technical reviewer selects and approves factors for the agreed method. |
| Explain gaps and sensitivity | Review comments are scattered and may mix assumptions with findings. | Proposed review pack separates evidence gaps, scenarios and unresolved choices. | Qualified reviewer decides what can be reported and what requires more evidence. |
Make the boundary explicit
Facilitate a written system boundary, functional unit and lifecycle inclusion register for one agreed product or family.
Create a traceable data trail
Organise approved records with owners, periods, units, allocation notes and evidence references.
Expose calculation assumptions
Prepare a factor log with source, version, date, unit and rationale for client review.
Prepare a defensible handover
Provide a transparent calculation pack and limitations register that can support future qualified review or verification decisions.
04 / HONEST HYPOTHETICAL FIGURES
Show the working behind a planning example.
These figures are modest arithmetic for discussion, not customer evidence, forecasts, emissions claims, payroll promises or guaranteed outcomes.
HYPOTHETICAL WORKED EXAMPLE / NOT CUSTOMER RESULTS
90 → 55 combined labour minutes for the same task.
12 one product-activity evidence batch checked against the agreed PCF template units per month × 35 minutes less per unit.
9 → 4 per 100 checked error-affected administrative pcf entries, not emissions reductions, incidents, accidents, disease or product-defect outcomes (5.0 percentage points).
See assumptions and calculations
| Measure | Illustrative calculation | Meaning and limit |
|---|---|---|
| Labour effort | (90 − 55) ÷ 90 × 100 = 38.9% | Same workload and expected review quality; includes ongoing exception checks as scoped. |
| Time capacity | (90 − 55) × 12 ÷ 60 = 7.0 hours | Released time is not payroll savings or guaranteed job reduction. |
| Admin checks | (9 − 4) ÷ 100 = 5.0 percentage points; 55.6% relative | Separate hypothetical like-for-like administrative check of missing or inconsistent fields; not a certification, assurance, compliance or environmental-performance guarantee. |
Hypothetical same-workload scenario: before means a client analyst gathers and checks one batch using separate files; after means a consultant-supported template, client review and exception follow-up cover the same batch. Both figures include review effort and do not represent headcount, payroll or carbon savings.
Scenario figures are illustrative arithmetic, not benchmarks, forecasts, actual customer results or guarantees. Measure a like-for-like pilot with the same definitions before making a claim.
05 / PROPOSED DELIVERY
Agree the evidence and review route before work starts.
Scope workshop
Confirm product purpose, functional unit, reference flow, lifecycle stages, organisational boundary distinctions and decision rights.
What you receiveBoundary and assumptions registerEvidence template
Design proposed structured fields for product/system boundary, life-cycle stage, activity, selected unit, activity data, factor plus unit, source/version/date and evidence owner.
What you receiveApproved/anonymised PCF data request and evidence registerCalculation review
Reconcile activity data, document allocation and yield questions, and test selected factors and gaps with client reviewers.
What you receiveWorking calculation pack with assumptions and exception logHandover briefing
Walk through limitations, unresolved evidence, future refresh triggers and the distinction between readiness and independent verification.
What you receiveReview-ready PCF dossier and next-step roadmap06 / BEFORE YOU INVEST
Inputs, boundaries and ownership should be clear.
These lists are a starting point. Final scope, access, professional responsibility and outputs require written agreement.
What to prepare
- Approved product specification, bill of materials and functional-unit proposal from product engineering
- Material, packaging and supplier quantity records with period and unit from procurement
- Production output, yield, scrap and process-energy records from operations and utilities owners
- Transport, distribution, use and end-of-life assumptions or evidence from logistics and product teams
- Chosen emission-factor files with factor unit, source, version, publication date and approval status from the sustainability lead
What to agree in writing
- This is scoped consultancy and a proposed template, not an installed application, live data map, IoT integration or automatic inventory.
- Client owners approve product boundaries, functional units, allocation rules, factors, estimates and any external communication before use.
- PCF lifecycle stages are not automatically organisational Scope 1, 2 or 3 categories; mapping is made only where the selected method and boundary justify it.
- Confidentiality, access roles, retention, anonymisation and transfer arrangements require written agreement; provide least-necessary approved data.
- Readiness documentation is not certified assurance, legal or tax advice, regulatory conformity, an accredited AIGreen Plus result or a promised carbon reduction.
Make activity, units and evidence easy to check.
Product and embedded-carbon records use the agreed product/system boundary, functional or declared unit, allocation rules and applicable method. They are not automatically equivalent to an organisational Scope 1/2/3 inventory. CBAM product boundaries and reporting rules need a separate applicability check.
Product boundary first
Proposed fields: product specification, functional/declared unit, system boundary, life-cycle stage, bill of materials, process inputs, energy, transport, allocation, exclusions and intended use. For EPD work, applicable product-category rules and independent programme requirements must be confirmed separately.
| Field group | Example contents / selections | Review check |
|---|---|---|
| Record identity | Site/entity, reporting period, activity owner and source record ID | Keep the agreed boundary and period consistent. |
| Activity/source | Fuel invoice, electricity meter, shipment, supplier record or process record | Identify the evidence and whether the value is measured or estimated. |
| Quantity and selectable unit | Examples: litres, kg, kWh, km, tonne-km or units of product | Choose a unit appropriate to the method; do not interchange units without a documented conversion. |
| Emission factor and factor unit | Numeric factor field; example unit kgCO₂e/kWh or kgCO₂e/litre | No default or approved factor is supplied here. The factor denominator must match the activity unit. |
| Factor provenance | Source, version/year, publication date, geography, gas/GWP basis and method | Qualified reviewers approve applicability, conversion and any licensed factor data. |
| Evidence and reviewer | Document reference, estimation basis, data-quality flag, owner and approval status | Trace each calculation to approved records and retain unresolved exceptions. |
This is an educational proposal panel, not a form, upload feature, factor database, live integration or calculated emissions result. Numerical dashboard values elsewhere are fictional; approved source data and qualified review are required for an actual engagement.
Confidence comes from traceable evidence.
Set definitions, boundaries, source ownership and review responsibility before interpreting a result. A qualified responsible person decides whether a finding is applicable.
07 / CLEAR ANSWERS
10 questions. Practical answers.
Clear answers
Frequently asked questions.
Ten practical answers about scope, sources, review and responsible use.
What does a Product Carbon Footprint engagement cover?
It covers one agreed product or product family, its functional unit, system boundary, lifecycle stages, activity data, factor provenance, assumptions, evidence gaps and review pack. The scope is agreed before work begins and does not automatically cover every SKU, site or market claim.
What data should a Malaysian manufacturer prepare first?
Start with the product specification and bill of materials, production output and yield, material and packaging quantities, process energy, logistics, and any included use or end-of-life assumptions. Each record should have a period, unit, owner and evidence reference where available.
Which method or standard will you use?
The method is selected during scoping. The GHG Protocol Product Standard supports full life-cycle product emissions accounting, while ISO 14067:2018 may be relevant for product carbon-footprint quantification and communication. We will not claim conformity to a standard without the required review and evidence.
Who signs off the boundary and final numbers?
The authorised client sponsor approves purpose, boundary, functional unit, assumptions and communication use. Process, procurement and sustainability owners validate their records. A qualified reviewer should challenge the calculation, and any independent verification is a separate decision and service.
Is this certification or independent assurance?
No. The engagement can improve readiness by documenting methods, evidence and limitations, but it is not an AIGreen Plus accreditation, certificate or assurance opinion. If a customer or programme requires verification, the organisation must appoint an appropriately qualified external body.
Are the dashboard figures and time scenario actual results?
No. Dashboard rows and scenario minutes are fictional planning illustrations. They are not customer measurements, benchmarks, headcount reductions, payroll savings, energy savings or carbon reductions. A client would need approved records and an agreed method to calculate its own result.
How are confidentiality and access handled?
Use approved and, where possible, anonymised records. Access roles, retention, transfer and confidentiality terms are agreed in writing with the client. We do not imply a compliance certification or unrestricted access to factory, supplier or employee systems.
Can this work with our existing spreadsheets or systems?
Yes, discovery can use exports or controlled spreadsheets when they contain suitable fields. This page does not promise integrations, an existing software product, live maps or IoT connectivity. Interface design, testing, licences and any implementation are separate written scopes.
How long will the PCF work take?
Timing depends on product complexity, boundary decisions, supplier evidence, factor review and client availability. We will propose milestones after discovery rather than invent a duration. Delayed or estimated data can change the review sequence and the confidence of the working result.
What affects the quotation and ongoing support?
Scope, number of products and sites, lifecycle coverage, data quality, workshops, factor research, language, review depth and handover needs affect a quotation. Recurring refreshes, training, external verification and system support are optional scopes with separately agreed terms; no price or 24/7 support is promised here.
START WITH ONE CLEAR QUESTION
Discuss this outline ↗Discuss Product Carbon Footprint (PCF)
Share a high-level question and the type of evidence involved—not confidential records. We can discuss discovery, scope and a written way to review the work.
08 / SOURCE NOTES
Check the current public material.
These references support an initial discussion only. They do not make AIGreen Plus an accredited or certified verifier.
Public official material — not accreditation.
- GHG Protocol Product Standard
The Product Standard addresses full life-cycle product emissions, including raw materials, manufacturing, transport, storage, use and disposal, and distinguishes product-level accounting from corporate Scope 3 accounting.
- ISO/TS 14067:2013 official ISO record and revised-version notice
The official record describes principles, requirements and guidelines for quantifying and communicating product carbon footprints, including partial footprints, climate change as the impact category and exclusion of offsetting; it notes the 2013 technical specification is withdrawn and points to ISO 14067:2018.
These official pages support the bounded lifecycle-accounting and communication framing only. The applicable method, edition, product boundary, data quality and any verification requirement must be confirmed for the organisation, product and reporting period with qualified advisers; this consultancy page is not legal, tax or assurance advice.
Dashboards and numerical scenarios are fictional planning examples. The services are proposed consultancy scopes, not certification, accreditation, assurance, legal advice, regulatory approval or a promise of emissions, cost, staffing, safety, quality or market outcomes.
