Who Owns Carbon on EPC Projects?

Carbon on an EPC project does not sit neatly in one department, one contract, or one emissions scope. It moves through design decisions, purchase orders, temporary power plans, fabrication yards, chartered vessels, commissioning fuel, and supplier data systems.

That is why the question “who owns carbon?” is not just an ESG reporting question. It is a project governance question. It is also a contracting, procurement, engineering, commercial, and project-controls question.

On major capital projects, responsibility for emissions often splits among the asset owner, EPC contractor, subcontractors, original equipment manufacturers, suppliers, freight providers, temporary facilities operators, and commissioning teams. Each party may control part of the emissions profile. Few control the whole.

The result is predictable. Some emissions are counted twice. Some are not counted at all. Some are reported at corporate level but never managed at project level. Some are assigned to a party that can't practically reduce them.

That creates exposure. Not only disclosure exposure under frameworks such as the GHG Protocol, ISO 14064-1, ISO 14067, IFRS S1 and IFRS S2, and sector guidance. It also creates commercial exposure through claims, variations, tender non-compliance, lender requirements, customer commitments, and poor decision-making during execution.

Carbon ownership starts with control, but control is split

Most carbon accounting systems start with organizational boundaries and operational boundaries. The GHG Protocol Corporate Standard sets out approaches based on equity share, financial control, or operational control. ISO 14064-1 also addresses organizational and reporting boundaries for greenhouse gas inventories.

That works reasonably well for a corporate inventory. It becomes harder on an EPC project.

An EPC contractor may control site execution. The asset owner may control the design basis, performance requirements, land, permits, executive schedule, and final operating model. OEMs may control equipment design and manufacturing processes. Steel, cement, cable, chemicals, and modular packages may come through multiple supplier tiers. Logistics contractors may manage port operations, heavy-lift vessels, trucking, and last-mile delivery.

No single party owns all the decisions that generate emissions.

A simplified split looks like this:

Emissions source: a rental company provides and operates the generators?	Who may control the activity	Who may need the data?
Permanent equipment design	Owner, EPC contractor, OEM	Owner, EPC contractor, lender, regulator
Embodied carbon in materials	Suppliers, OEMs, EPC procurement	Owner, EPC contractor, customer
Temporary power and fuel	EPC contractor, site subcontractors	EPC contractor, owner
Construction plant and equipment	Subcontractors, EPC contractor	EPC contractor, owner
Freight and logistics	EPC contractor, freight forwarders, suppliers	Owner, EPC contractor
Commissioning fuel and chemicals	Owner, EPC contractor, operations team	Owner, EPC contractor
Purchased electricity during construction	Site operator, utility, EPC contractor	EPC contractor, owner
Waste treatment and disposal	Waste contractor, EPC contractor	EPC contractor, owner

This split matters because carbon management depends on three different kinds of ownership.

Operational ownership sits with the party directing or performing the activity.

Data ownership sits with the party that can measure, collect, verify, and transmit emissions information.

Accountability for reduction sits with the party that can change the decision without causing an unmanaged impact on safety, cost, scope, quality, or schedule.

Those three forms of ownership often sit with different organizations.

For example, the EPC contractor may specify a lower-carbon concrete mix only if the owner accepts the technical basis, the project specification allows it, local supply exists, and schedule risk is acceptable. The concrete supplier may provide the environmental product declaration. The owner may report the embodied carbon in its Scope 3 capital goods category. The EPC contractor may report fuel used by its own equipment as Scope 1, but subcontractor fuel may fall under Scope 3, depending on the reporting boundary.

The emissions exist once. The reporting paths multiply.

This is where many projects get into trouble. They ask suppliers for carbon data after placing purchase orders. They add carbon KPIs after baseline design is frozen. They require EPC contractors to “support ESG reporting” without defining activity data, emission factors, assurance rights, data formats, timing, ownership, or change control.

That is not carbon management. It is late-stage data chasing.

Scope 1, Scope 2, and Scope 3 Boundaries Blur on Real Projects

The GHG Protocol definitions are clear at the corporate level. Scope 1 covers direct emissions from sources owned or controlled by the reporting organization. Scope 2 covers indirect emissions from purchased electricity, steam, heating, or cooling. Scope 3 covers other indirect emissions across the value chain.

The challenge is not the definition. The challenge is applying it to a project where several organizations share control across the project lifecycle.

A few practical examples show the problem.

If an EPC contractor operates diesel generators for temporary power on a construction site it controls, those emissions may be the contractor’s Scope 1. If a rental company provides and operates the generators under a service contract, the reporting treatment can change depending on control and inventory rules. The asset owner may also include the same construction emissions in its Scope 3 capital goods or project-related value chain emissions.

If the owner buys grid electricity for construction power and recharges it to the EPC contractor, the owner may report Scope 2. If the EPC contractor contracts directly with the utility, the contractor may report Scope 2. The owner may still need the data for project-level reporting, lender reporting, or internal carbon budgets.

If OEMs manufacture pumps, turbines, switchgear, offshore modules, rail systems, or process packages overseas, the manufacturing emissions usually sit in the OEM’s Scope 1 and Scope 2 inventory. For the project owner, they may be Scope 3 purchased goods and capital goods. For the EPC contractor, they may also fall into Scope 3 purchased goods, depending on whether the contractor procures them on its own account or as an agent for the owner.

Freight adds another layer. Fuel burned by a shipping company is Scope 1 for the carrier. It may be Scope 3 transportation and distribution for the EPC contractor or owner. If the owner nominates the carrier, the contractor may not control the emission source but may still need to collect freight emissions data.

None of this means the rules fail. It means project teams need boundary decisions early.

The GHG Protocol Scope 3 Standard recognizes the need to identify relevant indirect emissions across value chains and, where possible, avoid double counting within a company’s inventory. At the same time, double counting between companies is common in Scope 3 because one party’s direct emissions become another party’s value chain emissions. That is expected. The problem is not always double counting itself. The problem is unmanaged double counting, where more than one party treats the same project emissions as reductions, or where no party takes responsibility for data quality.

IFRS S2, issued by the International Sustainability Standards Board, also puts pressure on companies to disclose climate-related risks and opportunities that could reasonably affect prospects. Many jurisdictions are still deciding how to adopt or align with ISSB standards, but the direction is clear. Climate disclosure is becoming more connected to governance, risk management, strategy, metrics, and targets.

For EPC projects, that means project emissions data must withstand greater scrutiny. It can no longer live in a side spreadsheet owned by the sustainability team.

Fragmentation Happens at the Interfaces

EPC projects are interface machines. Design passes into procurement. Procurement passes into fabrication. Fabrication passes into logistics. Logistics passes into site installation. Construction passes into commissioning. Commissioning passes into operations.

Carbon accountability often breaks at the same interfaces.

The project may have a carbon target in the owner’s business case. The EPC contract may include general ESG language. Procurement may ask for supplier emissions data. The project controls team may track cost and schedule but not carbon. The construction team may track diesel usage for cost recovery but not for emissions reporting. The commissioning team may burn fuel or vent gases under approved procedures, but those activities may sit outside the construction carbon baseline.

Each group is doing its job. The system still loses carbon.

The Project Management Institute and the Association for Project Management both treat governance, roles, risk, change control, and benefits realization as core project management disciplines. Carbon now needs the same discipline on projects where emissions are material. It cannot be bolted onto monthly ESG reporting.

Contracts Can Allocate Responsibility, But Vague Clauses Create Weak Control

Many EPC contracts now include sustainability obligations. Some require compliance with owner policies. Some require emissions reporting. Some include carbon reduction targets, supplier questionnaires, or obligations to support owner disclosures.

These clauses often fail because they do not answer basic execution questions.

Who must calculate the baseline? Who approves the methodology? Which emissions factors apply? Are supplier-specific factors required where available? Are estimates allowed before purchase orders are finalized? Who updates the carbon forecast after design changes? What happens if a low-carbon material creates cost or schedule impact? Does the contractor carry that risk, or does it become a variation?

A contract that says “the contractor shall report project emissions” is not enough.

A stronger contract will define:

• the emissions boundary for project purposes

• minimum data requirements by work package, supplier, and activity

• accepted calculation standards and emission factor hierarchy

• assurance and audit rights

• timing of submissions and correction rules

• responsibility for subcontractor and supplier data

• treatment of design changes, substitutions, and variations

• consequences for non-compliance or poor data quality

  
  

The contract should also distinguish between reporting responsibility and responsibility for reductions. A party can report emissions it does not control. A party should not be held accountable for reductions it cannot influence unless the commercial model gives it the tools to act.

For example, if the owner specifies a particular OEM package, the EPC contractor may be responsible for collecting embodied carbon data from that OEM. But the contractor may not be responsible for reducing those manufacturing emissions unless the contract allows alternative suppliers, redesign, material substitution, or commercial negotiation.

Procurement Decides Much of the Carbon Before Construction Starts

By the time site fuel is being counted, many high-impact carbon decisions have already been made.

Design and procurement decisions largely shape embodied carbon in steel, cement, concrete, asphalt, cable, glass, insulation, process equipment, tanks, vessels, turbines, transformers, batteries, and modules. ISO 14067 provides principles and requirements for product carbon footprinting. Environmental product declarations, often prepared under product category rules and standards such as ISO 14025 and EN 15804 in construction contexts, can support more consistent product-level information.

They are not a cure-all. EPDs vary in scope, assumptions, geography, age, and product specificity. Some cover cradle-to-gate. Others include wider life cycle stages. Some are site-specific. Others are industry averages.

That means EPC procurement documents should state what kind of carbon data is required, not just ask suppliers to “provide sustainability information.”

For major packages, tender documents can require:

• product-specific emissions data where available

• declared life cycle stages and boundaries

• source of emission factors and calculation method

• material quantities and recycled content assumptions where relevant

• manufacturing location and energy basis

• freight mode, distance, and routing assumptions

• right to request supporting evidence or third-party assurance

  
  

Commercial teams also need evaluation rules. If carbon has no weighting in bid evaluation, suppliers will treat it as paperwork. If carbon has weighting but no common methodology, bid comparisons become unreliable.

A lower-carbon offer with weak evidence may beat a higher-integrity offer with transparent data. That creates both procurement risk and reporting risk.

Subcontractor Data Quality is Often the Weak Link

Subcontractors control many site emissions. Earthworks contractors burn diesel. Marine contractors operate vessels. Heavy lift contractors use cranes and transporters. Electrical contractors use temporary power. Coating contractors use fuel, solvents, and compressed air. Waste contractors move and process waste.

Yet smaller subcontractors may not have mature carbon systems. They may track fuel for billing rather than by equipment class or work package. They may provide spend-based estimates when activity data is needed. They may lack evidence for biofuel claims or renewable electricity certificates. They may not understand whether the project needs gross emissions, net emissions, well-to-tank emissions, tank-to-wheel emissions, location-based Scope 2, or market-based Scope 2.

This is where project controls can help.

Many projects already track fuel for cost, productivity, inventory control, and theft prevention. Projects already track equipment hours for earned value and progress measurement. Deliveries are already tracked for logistics. Teams already collect waste tickets for compliance. Carbon data should be connected to these existing control points, not run as a separate sustainability exercise.

The Energy Institute, IOGP, and other sector bodies have published guidance and methods relevant to emissions measurement and reporting in energy and industrial operations. The World Bank and IFC Environmental, Health, and Safety Guidelines also reinforce the expectation that projects identify, manage, and monitor environmental impacts. Details differ by sector, but the management principle remains consistent. Data quality improves when measurement is embedded in operational controls.

Missing Emissions Are as Dangerous as Double Counting

Double counting gets attention because it can overstate emissions or overstate reductions. Missing emissions can be worse because they hide risk.

On EPC projects, emissions go missing for predictable reasons.

Some sit outside the formal contract boundary. Owner-furnished equipment may be excluded from EPC reporting. Early works may be let under a separate contract. Temporary roads, camps, worker transport, marine spreads, dredging, quarrying, water treatment, and enabling works may fall into separate reporting channels.

Some emissions disappear in commercial handoffs. A supplier includes freight in the product price, but nobody captures transport emissions. A subcontractor provides lump-sum equipment services, but doesn't report fuel use. A fabrication yard reports utility use at facility level but not by project. A logistics provider reports distance but not weight, vessel type, load factor, or fuel basis. A commissioning team records consumables for operations readiness, not project carbon.

Some emissions disappear because corporate and project boundaries do not match.

A corporate sustainability report may aggregate emissions by legal entity, region, or business unit. A project carbon report may aggregate by work breakdown structure, facility, package, or asset. Both can be valid. They answer different questions.

The issue arises when leaders assume they reconcile automatically.

They rarely do without a mapping process.

A single offshore wind, LNG, mining, rail, water, or utility project may involve joint ventures, special purpose entities, multiple EPC packages, owner-furnished equipment, government interfaces, and regulated utility reporting. Corporate Scope 1, Scope 2, and Scope 3 emissions may cut across these structures in ways that do not align with the project execution model.

That creates three common failures.

The first is incomplete project reporting. The project carbon footprint excludes owner-directed items because the EPC contractor did not procure them.

The second is inconsistent corporate reporting. Business units use different assumptions for the same project activity.

The third is weak reduction governance. The project reports emissions after the decisions that caused them have already been made.

A better approach is to create a carbon responsibility matrix early. This should sit alongside the responsibility assignment matrix, interface register, procurement schedule, basis of design, and project controls plan.

A practical matrix should show:

Project area	Data owner	Control owner	Reporting recipient	Assurance method
Structural steel	Steel supplier, EPC procurement	Designer, EPC, owner specifications	Owner and EPC	Mill data, EPDs, quantity takeoff checks
Concrete	Batch plant, civil contractor	Civil designer, EPC, owner specifications	EPC and owner	Mix design records, delivery tickets, supplier declarations
Temporary power	Site services contractor	EPC construction team	EPC and owner	Meter readings, fuel invoices, generator logs
Marine logistics	Marine contractor, freight forwarder	Logistics lead, owner or EPC depending on charter	Owner and EPC	Voyage data, fuel data where available, transport records
Commissioning fuel	Commissioning team	Owner and EPC commissioning manager	Owner and EPC	Procedures, fuel records, metering, test logs

The matrix shouldn't be a sustainability appendix nobody reads. It should be part of project governance.

Clear Accountability is Built Through Normal Project Controls

Carbon accountability improves when you manage it through familiar project mechanisms. That means scope definition, contracting, specifications, procurement, scheduling, cost control, risk management, interface management, assurance, and change control.

Tender Documents Should Define the Carbon Problem

Tendering is the last good chance to set expectations before commercial positions harden.

Owners should state the project carbon objectives, required standards, reporting boundaries, data hierarchy, expected supplier obligations, and evaluation approach. If the owner has corporate commitments or lender requirements, translate them into contract language delivery teams can execute.

Contractors should price the obligation properly. Collecting granular emissions data from a multi-tier supply chain costs money. Switching materials may affect specifications, warranties, approvals, or schedule. Metering temporary power requires planning. Assurance requires evidence. None of this should be hidden inside a generic ESG clause.

If owners want credible carbon performance, they need to make it a defined deliverable.

If contractors accept carbon obligations, they need to treat them as controlled scope, not goodwill.

Specifications Should Allow Lower-Carbon Choices Where Safe and Compliant

Many projects lock in carbon through specifications that are more conservative than necessary or copied from older assets. That does not mean standards should be weakened. In high-risk industries, safety, reliability, regulatory compliance, and lifecycle performance come first.

It does mean specifications should not block credible lower-carbon options without a technical reason.

Examples include performance-based concrete specifications where appropriate, approved alternative materials, modular design choices that reduce rework, efficient equipment sizing, better logistics planning, and design for constructability. Engineering institutions and construction bodies have long emphasized that early design decisions strongly influence whole-life performance. Carbon follows the same pattern.

The owner, engineer, and contractor need a process to assess alternatives. Review carbon reduction proposals through technical, commercial, risk, and schedule lenses. If a proposal affects cost or program, the change mechanism must handle it.

KPIs Need to Measure Both Emissions and Management Quality

A single project carbon number is useful, but it is not enough.

Good KPIs distinguish between emissions performance and data performance. A project with low reported emissions and poor data may be a risk. A project with higher reported emissions and strong evidence may be better managed.

Useful KPIs may include:

• percentage of major suppliers providing product-specific carbon data

• percentage of construction fuel supported by invoices, meter readings, or equipment logs

• temporary power emissions per major construction phase

• freight emissions coverage by mode and major package

• number of approved carbon reduction proposals and their evidence basis

• percentage of high-impact materials covered by EPDs or equivalent documentation

• data quality rating by package or subcontractor

  
  

These measures should be part of routine project reporting. They should be reviewed with cost, schedule, safety, quality, and risk.

Assurance Should Happen Before The Year-End Reporting Rush

Assurance fails late when evidence was never collected early.

If an owner expects to use project emissions data in external reporting, lender reporting, customer reporting, or regulated disclosure, the project needs an assurance plan. That plan should define records, retention, sampling, audit rights, responsible parties, and correction processes.

This does not mean every invoice or supplier declaration needs third-party assurance. It means material data streams need a clear evidence trail.

For example, a project may accept different assurance levels for different data types. Supplier-specific EPDs for high-impact equipment may require supporting documentation. Low-value consumables may use accepted secondary data. Construction fuel may require reconciliation between fuel deliveries, tank records, and equipment logs. Purchased electricity may require utility meter data and the Scope 2 calculation method.

The assurance plan should also address claims. If a project claims reductions from renewable electricity, alternative fuels, recycled materials, or efficient logistics, the evidence must support the claim. Recognized standards and guidance can help, but the project still needs contract rights to obtain the evidence.

Change control must include carbon impact

Major projects change. Design develops. Quantities move. Suppliers fail. Materials are substituted. Logistics routes change. Schedule pressure triggers air freight. Temporary power demand rises. Commissioning takes longer than planned.

If carbon is excluded from change control, the project loses control of its emissions forecast.

A carbon-aware change process should ask:

• Does the change alter material quantities, equipment type, construction method, transport route, energy use, or commissioning activity?

• Does it move emissions between owner, EPC contractor, subcontractor, or supplier boundaries?

• Does it change Scope 1, Scope 2, or Scope 3 reporting treatment for any party?

• Does it affect carbon targets, permit commitments, lender requirements, or customer commitments?

• Who updates the project carbon forecast and supporting evidence?

  
  

This does not require turning every field change into a climate workshop. It requires adding carbon to the same disciplined process used for cost, schedule, safety, quality, and technical risk.

The Leadership Questions That Make Ownership Clear

Senior project and commercial leaders do not need to become carbon accountants. They do need to ask sharper questions.

The following questions expose whether carbon ownership is real or only implied.

Who owns the project carbon baseline?

If sustainability owns the baseline but design, procurement, and construction don't use it, it will not drive decisions.

Who owns the emissions data model?

The project needs clear data fields, sources, calculation methods, emission factors, units, and version control.

Who validates supplier data?

Procurement can request data. Technical teams, sustainability specialists, and assurance teams may need to validate it. The responsibility should be named.

Who is accountable for subcontractor reporting?

The EPC contractor may need to flow requirements down into subcontracts. The owner should know where gaps remain.

Who can approve lower-carbon substitutions?

If approvals take too long, lower-carbon options die in the schedule.

Who pays when carbon reduction changes cost or risk?

Commercial silence discourages action. The contract should say whether reductions are priced, incentivized, shared, or treated as variations.

Who decides whether emissions belong in Scope 1, Scope 2, or Scope 3 for each reporting party?

The project manager is not always the decision-maker. It may require corporate reporting judgment. The decision should be documented.

Who prevents double counting of reductions?

Several parties may report the same emissions. Without clear rules, they should not all claim the same reduction.

Who captures emissions at handover?

Commissioning and start-up can fall between project and operations. Handover should include emissions data, assumptions, and open issues.

Who signs off the final project carbon account?

Treat closing the account like closing cost, schedule, quality, and HSE records.

These questions are commercial controls. They reduce uncertainty, prevent reporting disputes, and support better capital decisions.

They also protect relationships. Carbon disputes often arise because parties assume different things. The owner assumes the EPC contractor captured supplier emissions. The contractor assumes OEM data is outside its scope. The supplier assumes generic factors are acceptable. The reporting team assumes project data aligns with corporate boundaries.

Clear ownership prevents those assumptions from becoming claims.

The Professional Takeaway

A reporting team can't fix carbon ownership on EPC projects at year-end with a spreadsheet. By then, the design may be frozen, suppliers selected, materials manufactured, fuel burned, freight completed, and commissioning finished.

The practical answer is to establish ownership early.

Define the carbon boundary during scope definition. Translate it into tender documents and contract schedules. Put data requirements into procurement packages. Flow obligations into subcontracts. Build carbon into project controls, assurance, and change management. Decide who owns the data, who validates it, who can reduce it, and who reports it.

That is the only workable way to answer the real question behind the title, Who Owns Carbon on EPC Projects?

On complex projects, carbon belongs to the party that controls the decision, holds the data, and must report the result. Those parties are not always the same. The job of good project governance is to make the split visible before execution starts, not to reconstruct it after the emissions have already happened.