GHG Monitoring Process Explained: Step-by-Step Carbon Accounting Workflow

A carbon footprint report is not difficult to produce once. The challenge is producing it accurately, consistently, and on time every year—especially when multiple sites, multiple departments, and multiple emission sources are involved. That consistency comes from a defined and repeatable carbon accounting workflow.

This blog explains the practical GHG accounting steps that organizations should follow to implement a monthly monitoring cycle, maintain evidence discipline, and produce a year-end inventory that is defensible in audits and customer reviews.

If your organization is still building factory-level data ownership and source mapping, refer to GHG monitoring for factories. And for the bigger disclosure framework, refer to GHG reporting. If you want a ready-to-implement workflow setup with formats and controls, explore our Carbon footprint monitoring support.

Why you need a defined GHG monitoring process (not only a spreadsheet)

Most failures in carbon accounting happen due to process gaps, not due to calculation formulas.
Typical failure points include:

– missing monthly data (because ownership is unclear)
– inconsistent units and conversions
– bills collected but operational logs missing
– Scope classification errors (DG fuel, logistics, refrigerants)
– weak evidence organization, causing audit delays
– year-end rush leading to assumptions and errors

A standard monitoring workflow avoids these problems by creating:

– clear responsibilities
– fixed cadence (monthly close)
– QA/QC checkpoints
– evidence indexing and traceability
– controlled emission factor usage
– documented assumptions and approvals

Step-by-step GHG accounting workflow (monthly cycle)

Step 1: Confirm boundaries and scope mapping (once, then review quarterly)

Before monthly monitoring begins, confirm:

– sites/entities included (organizational boundary)
– Scope 1/2/3 mapping table (operational boundary)
– ownership of leased assets and outsourced operations
– baseline methodology and emission factor sources

Output: Boundary note + scope mapping matrix + owner list.
Why it matters: prevents year-end scope disputes and double counting.

Step 2: Define data owners and submission timelines (RACI-style)

A monitoring process fails when everyone assumes “ESG Consultant team will do it.”

Assign owners by stream:

– Utilities/Maintenance: electricity bills, meter readings, DG/boiler logs
– Stores/Production: fuel issue records, operational hours, process notes
– EHS: refrigerant, waste, water and treatment records
– Procurement/Accounts: supplier invoices, spend data, capital goods
– Logistics: transporter data, dispatch weights, distances
– ESG/IMS Lead: consolidation, controls, reporting outputs

Best practice: Create a fixed monthly submission deadline (e.g., by the 5th working day).

Step 3: Collect activity data (the “inputs”)

This is the core monthly collection step. You capture activity data with consistent units and references.

Typical inputs:

– electricity consumption (kWh)
– fuels (liters/kg/Nm³) for DG/boiler/process
– refrigerant top-ups (kg)
– transport (distance, weight, ton-km)
– waste (kg/ton by disposal method)
– purchased materials (quantity/spend, supplier)

Control requirement: Every entry must have a document reference (bill/invoice/log ID).

Step 4: Validate data quality (QA checks before calculation)

Before you convert data into emissions, apply practical checks:

A) Completeness checks

– Are all sites covered?
– Are all meters captured?
– Are DG/boiler logs available for the month?

B) Unit and consistency checks

– liters vs kg vs Nm³ applied correctly
– conversion factors documented
– no mixed units without conversion

C) Variance checks

– month-on-month consumption movement
– consumption vs operating days
– consumption vs production levels (where applicable)

D) Reconciliation checks (especially for fuel)

– purchase vs consumption vs closing stock
– DG run-hours vs diesel consumption reasonableness

Output: A variance log with explanations and approvals for anomalies.

Step 5: Lock the month (monthly close discipline)

Once checks are completed:

– freeze the month’s dataset
– store final files in a controlled folder
– ensure document references are complete
– capture approvals (email or sign-off) for estimates or unusual variances

This “monthly close” concept is what makes carbon accounting reliable—similar to finance close.

Step 6: Apply emission factors and calculate emissions

Once activity data is validated, apply emission factors consistently:

– Electricity: location-based factors (and market-based, if applicable)
– Fuels: fuel-specific emission factors
– Refrigerants: gas-specific GWP values
– Transport: mode-specific factors (distance/ton-km based)
– Purchased goods: spend-based or supplier-specific factors (depending on maturity)

Critical control: Maintain an emission factor register with revision control. If you update factors, document the change and apply it consistently.

Step 7: Prepare monthly outputs (management-ready format)

A strong monthly monitoring process produces more than a tCO₂e number. Minimum outputs:

– Scope 1 and Scope 2 monthly totals
– hotspot drivers (top fuels, electricity, etc.)
– emission intensity KPI (if production data is available)
– variance commentary (why changed vs last month)
– data gaps and corrective actions list

This output becomes your internal dashboard and your foundation for year-end reporting.

Step 8: Quarterly review and improvement actions

Every quarter, review:
– which sources are recurring hotspots
– which data streams are weak (missing evidence, delayed owners)
– where metering or sub-metering is required
– Scope 3 maturity improvements (supplier data improvements)

This is where monitoring becomes a reduction enablement tool, not only reporting.

Step 9: Year-end inventory consolidation and reporting pack

At year-end, you consolidate monthly datasets into:

– annual Scope 1/2 totals
– selected Scope 3 totals by category
– site-wise and source-wise breakdowns
– base year comparisons and intensity movement
– evidence pack index for audit sampling

If you follow the monthly workflow, year-end becomes consolidation—not reconstruction.

A simple role-based workflow that works (example)

– Maintenance: electricity + boiler + DG data by Day 3
– Accounts: fuel invoices + vendor invoices by Day 4
– EHS: refrigerants + waste + water by Day 4
– Logistics: transport summary by Day 5
– ESG Lead: QA checks + calculation by Day 7
– Management: monthly dashboard review by Day 10

This cadence makes monitoring stable and predictable.

Common process failures (and the fix)

– No fixed monthly deadline – Fix: set a monthly close date and enforce it.

– No variance log – Fix: maintain a variance register with explanations and approvals.

– Evidence scattered across teams – Fix: central evidence folder + naming convention + document index.

– Emission factors changed without traceability – Fix: register with revision and a recalculation rule when material.

– Monitoring treated as a yearly task –  Fix: monthly cycle with quarterly improvement review.