Skip to main content

How Features Connect

Understanding how EXO.G features integrate is key to unlocking the platform's full potential.

Integration Architecture​

EXO.G is built on a modular architecture where features are:

  • Independent - Each works standalone
  • Interconnected - Share data seamlessly
  • Complementary - Better together than separate

Data & Reports integration patterns​

Pattern 1: ESG data as foundation​

The Reports & Data Input module provides data to all other features.

How it works:

  1. Enter data in Reports & Data Input
  2. Data becomes available to Monitoring & Improvement, Materiality, Value Chain
  3. No duplication needed

Example:

Enter GHG emissions in Core
  ↓
Performance calculates trends
  ↓
Materiality flags as material
  ↓
Value Chain requests supplier data

Pattern 2: Cross-Feature Workflows​

Features work together in complete workflows.

ESG Report Workflow:

  1. Materiality - Identify what to report
  2. Core - Collect relevant data
  3. Performance - Analyze trends
  4. Value Chain - Include supply chain
  5. Risk - Assess ESG risks
  6. Core - Generate comprehensive report

Supply Chain Assessment:

  1. Value Chain - Map suppliers
  2. Collaboration - Invite suppliers
  3. Core - Collect supplier data
  4. Performance - Track Scope 3
  5. Risk - Assess supply chain risks

Pattern 3: Collaboration Enablement​

Collaboration provides access control for all features.

How it works:

  • Authentication gates all access
  • Roles control what users can do
  • Permissions apply across features

Example:

User assigned "Data Manager" role
  ↓
Can edit data (Core)
Can view dashboards (Performance)
Cannot manage stakeholders (Materiality)

Feature-to-Feature Connections​

Reports & Data Input ↔ Monitoring & Improvement​

Direction: Reports & Data Input → Monitoring & Improvement

Data: All ESG metrics

Purpose: Calculate KPIs, visualize trends

Use Case: Track emissions reduction over time

Learn more: Reports & Data Input | Monitoring & Improvement

Reports & Data Input ↔ Materiality​

Direction: Bidirectional

Data: Material topics ← → Focused data collection

Purpose: Prioritize data collection, inform assessments

Use Case: Material topic guides which data to collect

Learn more: Reports & Data Input | Materiality

Performance ↔ Materiality​

Direction: Performance → Materiality

Data: Performance metrics and trends

Purpose: Inform materiality scoring

Use Case: Rising emissions increase climate topic materiality

Learn more: Performance | Materiality

Materiality ↔ Value Chain​

Direction: Bidirectional

Data: Material topics ← → Value chain impacts

Purpose: Extend materiality to supply chain

Use Case: Labor rights material → Engage suppliers on labor

Learn more: Materiality | Value Chain

Value Chain ↔ Risk​

Direction: Bidirectional

Data: Supply chain data ← → Risk assessments

Purpose: Identify and manage supply chain risks

Use Case: High-risk supplier triggers mitigation plan

Learn more: Value Chain | Risk Management

Risk ↔ Reports & Data Input​

Direction: Risk → Reports & Data Input

Data: Mitigation actions

Purpose: Track risk response activities

Use Case: Climate risk mitigation becomes project action

Learn more: Risk Management | Reports & Data Input

Common Integration Scenarios​

Scenario 1: First ESG report​

Objective: Create a complete sustainability report

Feature Sequence:

  1. Reports & Data Input - Set up project, enter baseline data
  2. Collaboration - Invite team members
  3. Materiality - Conduct materiality assessment
  4. Monitoring & Improvement - Review metrics
  5. Reports & Data Input - Generate report with insights

Timeline: 4-6 weeks

Scenario 2: Supply chain engagement​

Objective: Understand and improve value chain impacts

Feature Sequence:

  1. Value Chain - Map suppliers
  2. Materiality - Include suppliers in assessment
  3. Collaboration - Invite suppliers to platform
  4. Reports & Data Input - Collect supplier data
  5. Monitoring & Improvement - Follow emissions over time
  6. Risk - Assess supply chain vulnerabilities

Timeline: 2-3 months

Scenario 3: Climate risk assessment​

Objective: Complete a climate disclosure

Feature Sequence:

  1. Monitoring & Improvement - Analyze emissions trends
  2. Materiality - Confirm climate as material
  3. Risk - Identify climate risks (physical + transition)
  4. Value Chain - Assess supply chain climate exposure
  5. Reports & Data Input - Document governance and strategy
  6. Reports & Data Input - Generate the report

Timeline: 6-8 weeks

Scenario 4: Continuous improvement​

Objective: Ongoing ESG management

Feature Sequence:

  1. Monitoring & Improvement - Monthly data review
  2. Risk - Quarterly risk updates
  3. Materiality - Annual reassessment
  4. Value Chain - Continuous supplier engagement
  5. Core - Regular reporting
  6. Collaboration - Team coordination throughout

Timeline: Ongoing

Data Flow​

Input Sources​

Data enters EXO.G through:

  • Manual entry - Forms in Reports & Data Input
  • Stakeholder surveys - Materiality assessments

Data Processing​

Data flows through features:

Output Destinations​

Processed data goes to:

  • Reports - The ESG report you build in the editor
  • Dashboards - Visualizations inside the platform

Integration Best Practices​

Start simple​

  • Begin with Reports & Data Input (data foundation)
  • Add Monitoring & Improvement (analytics)
  • Expand to other features gradually

Think Workflows​

  • Don't think in individual features
  • Think in complete workflows
  • Map your process to features

Maintain data quality​

  • Enter data once in Reports & Data Input
  • Let features consume automatically where applicable
  • Review at integration points

Collaborate effectively​

  • Set up proper access controls
  • Assign feature owners
  • Communicate across features

Troubleshooting Integrations​

Data Not Appearing​

Symptom: Data entered in Core not showing in Performance

Check:

  • Is data saved successfully?
  • Is reporting period correct?
  • Are calculations running?
  • Do you have view permissions?

Permissions Issues​

Symptom: Can't access a feature

Check:

  • User role and permissions
  • Project-level access
  • Organization settings
  • Contact admin if needed

Sync Delays​

Symptom: Changes not reflected immediately

Note: Most updates are real-time, but some calculations may take minutes.

Check:

  • Refresh browser
  • Check calculation status
  • Review system status

Next Steps​

Need Help?​