Org Structure & Multi-Site Management

Build your organisation's carbon accounting structure from the ground up. NetNada's node-based system handles everything from single offices to global enterprises with multiple subsidiaries, regions, and facilities.

How It Works

Organisational structure forms the foundation of accurate carbon accounting. Nodes represent different levels of your organisation—from the parent company down to individual facilities—and determine where emissions are attributed and how data rolls up for reporting.

1

Create Your Top-Level Organisation

Start by defining your organisation node—the top-level legal entity. This represents your company as a whole and serves as the parent for all subsidiary structures.

2

Add Regions and Business Units

Create region nodes for geographical divisions (Australia, APAC, Americas) or business unit nodes for operational divisions (Manufacturing, Retail, Corporate). Assign parent relationships to build hierarchy.

3

Define Facilities and Sites

Add facility nodes for specific physical locations—offices, warehouses, factories, stores. Each facility can have its own emission sources, utility accounts, and data collection tasks.

4

Create Project Nodes (Optional)

For temporary initiatives with distinct emissions (construction projects, events, one-off activities), create project nodes. These capture emissions separately from ongoing operations.

5

Visualise and Verify Structure

Use the Node Map for visual hierarchy representation or Node Table for detailed list view. Verify parent-child relationships align with your reporting requirements and operational control boundaries.

Why Use Org Structure & Multi-Site Management

Accurate Emission Attribution

Every emission is tied to a specific node. Know exactly which facility, region, or business unit generated each tonne of CO₂. No more guessing where emissions come from.

Flexible Hierarchy

Whether you're a single-site SME or a multi-national with 500 facilities, the node system adapts. Add structure as you grow without redesigning your carbon accounting approach.

Roll-Up Reporting

Emissions automatically aggregate up the hierarchy. Report at facility level, regional level, or consolidated organisation level—all from the same underlying data.

Site-Level Benchmarking

Compare emissions across facilities. Identify high-performing sites, understand why some locations emit more, and apply best practices across your portfolio.

Operational Control Clarity

Nodes define what you control operationally. This maps directly to GHG Protocol boundary requirements, ensuring your structure supports compliant reporting.

Distributed Data Collection

Assign data collection tasks to specific nodes. Site managers collect site data; regional managers oversee regional rollups. The structure enables distributed ownership.

Who Needs Org Structure & Multi-Site Management

Multi-Site Organisations

Companies with multiple locations need per-site emission tracking and consolidated reporting. Retail chains, hospitality groups, logistics companies—all benefit from structured node management.

Companies with Regional Operations

Organisations spanning multiple states or countries need regional aggregation. Track emissions by geography while maintaining consolidated corporate totals.

Franchise Businesses

Franchises need to track franchisee emissions while rolling up to franchisor reporting. Node structure supports both individual franchise and network-wide views.

Corporate Groups with Subsidiaries

Holding companies and corporate groups track subsidiary emissions separately while consolidating for parent company disclosure. Node hierarchy mirrors legal structure.

Project-Based Organisations

Construction, events, and consulting firms with project-based emissions need temporary nodes that capture project footprints without mixing with ongoing operations.

Org Structure Features

Four Node Types

Organisation (top-level legal entity), Region (geographical divisions), Facility (specific physical sites), and Project (temporary initiatives). Each type has appropriate attributes.

Node Table View

Detailed list view for quick searching, filtering by type, and performing administrative actions. Ideal for managing large numbers of nodes.

Node Map Visualisation

Visual tree representation showing your company's hierarchical structure. Choose vertical or horizontal layouts to understand reporting relationships at a glance.

Parent-Child Relationships

Define hierarchy through parent node assignment. Emissions from child nodes automatically roll up to parents for aggregated reporting.

Location Attributes

Assign country and state/region to nodes. Location determines applicable emission factors and supports geographic analysis.

Create and Edit Nodes

Add new nodes as your organisation grows. Edit existing nodes to update names, locations, or parent relationships. Archive nodes no longer in use.

Boundary Integration

Nodes connect to Emission Boundaries configuration. Define which emission sources exist at each node for accurate task generation.

Dashboard Filtering

All dashboards support node filtering. View emissions for specific facilities, regions, or roll up to organisation-wide totals.

Real Results from Real Users

See how companies are transforming their sustainability reporting

Merivale Group
Sustainability Manager, Sustainability Manager
"100+ venues across Sydney—each with different utility accounts, waste contracts, and operational profiles. Node structure let us track venue-by-venue emissions while rolling up to a single Merivale total. Essential for our scale."
Impact:
  • 100+ venue nodes with individual tracking
  • Regional roll-ups for management reporting
  • Consolidated view for corporate disclosure
Precision Group
CFO, CFO
"We have three distinct business units with very different operations. Setting up business unit nodes under our parent organisation let us track each unit's footprint separately while maintaining group-level reporting for investors."
Impact:
  • 3 business units tracked independently
  • Parent company consolidation automated
  • Investor reporting simplified
ICC Sydney
Events Director, Events Director
"As a venue, we have ongoing operational emissions plus event-specific footprints. Project nodes for major events let us report event emissions to clients while keeping venue operations separate."
Impact:
  • Venue and event emissions tracked separately
  • Client-specific event reporting enabled
  • Clear distinction for carbon neutral event certification

Frequently Asked Questions

Everything you need to know about Org Structure & Multi-Site Management

What's the difference between Organisation, Region, Facility, and Project nodes?
Organisation is your top-level legal entity. Region represents geographical or business divisions (states, countries, business units). Facility is a specific physical location (office, warehouse, store). Project is a temporary initiative with distinct emissions (construction, events). Use the type that matches each entity's nature.
How many nodes can I create?
Node limits depend on your NetNada plan. Most plans support significant node counts for multi-site organisations. Contact sales if you need to manage hundreds of facilities or have complex subsidiary structures.
Can I change node structure after setup?
Yes. You can add, edit, and archive nodes as your organisation evolves. When you change parent relationships, emissions data automatically re-aggregates. Historical reporting maintains the structure active at that time.
What happens if I create duplicate nodes?
Duplicate nodes can cause double-counting in reports. The system warns about potential duplicates. If duplicates exist, consolidate them by merging data into a single node and archiving the duplicate.
Can I delete a node?
Nodes with active emission boundaries or associated data cannot be deleted immediately—this prevents data loss. First remove the boundary links and data associations, then the node can be archived or deleted.
How do nodes relate to emission boundaries?
Emission Boundaries reference nodes. When you define that 'Facility X has Scope 1 natural gas', you're linking an emission source to that facility node. Nodes must exist before they can be referenced in boundary configuration.
Can different users see different nodes?
Role-based access can restrict which nodes users see and manage. A regional manager might only see nodes within their region, while corporate sustainability sees all nodes. Discuss access configuration with your account manager.
How do I handle acquisitions and divestitures?
Acquisitions: Add new nodes under appropriate parents. Divestitures: Archive nodes that are no longer under your operational control. The GHG Protocol provides guidance on base year recalculation—NetNada's structure supports these adjustments.

Build Your Carbon Accounting Foundation

Structure. Scale. Report.

Whether you have one office or hundreds of facilities, NetNada's node-based structure supports accurate emission attribution and flexible reporting at any scale.

View pricing