Document control
Versions, approvals and distribution with read receipts.
Software for ISO 14064
Quantification, monitoring and verification of greenhouse gas emissions, with the inventory and evidence a verifier asks for.
ISO 14064 is the standard for quantifying and reporting greenhouse gas emissions. It has three parts: the first for organisation-level inventories, the second for reduction projects and the third for verification. The 2018 edition of part 1 replaced the scope terminology with direct and categorised indirect emissions, although in practice people still speak of scope 1, 2 and 3.
Versions, approvals and distribution with read receipts.
Publish and version documents by connecting to OneDrive, Google Drive or SharePoint, without duplicating folders.
Annual program, checklists per standard, findings linked to actions.
Root cause, action, owner, deadline and effectiveness check.
Process objectives fed with real operating data.
A register of legal and other requirements, with validity and compliance evaluation per standard.
Root cause, action, owner, deadline and effectiveness check, all linked to the nonconformity.
Improvement opportunities with an owner and tracking, beyond just fixing what already failed.
A pre-built report with indicators, audits and nonconformities, ready for the meeting.
Scope 1, 2 and 3 with documented emission factors.
Evidence ready for the verifier, year after year.
Emission factors and methodology documented and traceable by source.
Reduction targets with an owner and tracking per emission source.
Requirements covered
Standards covered
Templates and records
Which clause of ISO 14064 calls for each record, which fields it needs, a completed example and what the auditor usually flags.
How to document the organisational boundaries of a GHG inventory under ISO 14064-1 (5.1): control or equity…
How to decide which indirect emissions go into the inventory under ISO 14064-1 (5.2.3): prior criteria…
How to list the sources and sinks of a GHG inventory under ISO 14064-1 (6.1): facility, category, gas…
How to record activity data for each emission source under ISO 14064-1 (6.2.2 and 8.2): value, unit…
How to document the emission factors and global warming potentials in an ISO 14064-1 inventory (6.2.3)…
How to choose and document the base year of a GHG inventory under ISO 14064-1 (6.4): rationale, reference…
How to assess inventory uncertainty under ISO 14064-1 (8.3): activity data and factors, quantitative or…
What a greenhouse gas report must contain under ISO 14064-1 (9.3): boundaries, emissions by category, base…
How to record a carbon footprint verifier’s findings: errors, omissions, materiality, the correction made…
How to document an emissions reduction plan: five-year target, actions, owners and monitoring, in line with…
Frequently asked questions
The edition in force is ISO 14064-1:2018. When the issuing body publishes a new one, a transition period opens; once it closes, certificates issued against the previous edition stop being valid.
Yes. Your existing system — processes, documents, records, audit history — is loaded in and kept alive from day one. Nothing needs redesigning and the certification cycle does not restart.
Yes, provided they are traceable, controlled and able to show who did what and when. No standard requires paper; every standard requires reliable evidence, and a properly controlled electronic record provides it better than a folder.
Yes, and that is the sensible route. The common Annex SL structure lets a single integrated system share the process map, document control, internal audits, nonconformities and indicators between ISO 14064 and the rest, leaving only the standard-specific parts separate.
It depends on the starting point. An organisation already working with written procedures is usually ready in two or three months; one starting from scratch needs longer. The bottleneck is rarely the tool — it is the availability of the people who know the processes.
It is migrated. Existing procedures, forms and records are loaded with their version and approver, so the history is not lost and the system starts with the memory the organisation already had.
Yes. They are given read-only access with a defined scope and an expiry date. It is more comfortable for both sides than preparing a folder of screenshots and exports.
A major one compromises the system's ability to meet a requirement — a required process missing altogether, systematic failure, or a failure affecting the product — and usually blocks certification until it is closed. A minor one is a specific lapse resolved with an action plan.
Yes, from the data the processes themselves generate. That is the difference between a dashboard that reflects what is happening and a spreadsheet somebody fills in the week before the management review.
Yes. The model is multi-company and multi-site: what makes sense to share is shared, and what belongs to each location stays separate — including the certificate scope where it differs.
We'll show you the module running with data similar to yours.
Keep exploring
Free learning path on ISO 14064: greenhouse gas quantification and verification explained with examples and…
Record which regulations apply to you, get alerted when they change and assess compliance regularly, with…
Living documentation, planned audits, non-conformities with an owner, and indicators that calculate…
Analysis certificates, data sheets and declarations built from the real batch data, published on the…
Kimobox is a software for ISO 14064 that digitizes the requirements of the standard: inventory of direct and indirect emissions, documented emission factors and calculation method, regular monitoring per emission source, a reduction plan with objectives and owners, with full traceability and evidence ready for the auditor.
The platform lets you run an integrated management system that combines ISO 14064 with other ISO standards and sector protocols, sharing the process map, document control, internal audits, non-conformities and KPIs.