CO₂ Emissions Monitoring Solution Pathway

https://do-data.github.io/CO2-Emissions-Pathway/

The **Climate Compass (Klimakompasset)** is a Danish climate accounting tool based on the international Greenhouse Gas (GHG) Protocol. In the original Do Data pilot, Climate Compass data was: - Collected from companies - Reused in a **shared data infrastructure** - Visualised to support **benchmarking** and **climate planning** When considering a solution similar to Do Data, you can: - Continue to use the Climate Compass (if relevant in your context), **or** - Use a comparable climate calculator in your own country (with similar data structures) When using the Climate Compass **outside Denmark**, national emission factors should be used for: - Electricity mix - Heating systems - Waste treatment - Transport patterns - Agriculture and land use - Sector-specific Scope 3 emissions This means: - The **methodology and structure** can be reused - Some of the **default Danish data** must be replaced with **national or regional data** [[See national data requirements for adapting the method->NationalDataRequirements]] [[Go to municipality / public partner pathway->MunicipalityIntro]] [[Go to business / SME pathway->BusinessIntro]] [[Back to start->Start]]

**Do Data – for a Greener Future** is one example of a climate and emissions data solution that: - Was co-developed between a **municipality**, a **technical development partner such as an RTO (Research and Technology Organisation – the Danish GTS system)**, and **local businesses** - Reuses climate data (e.g. Climate Compass data) to create insights - Provides dashboards for **municipal planners** and **businesses** - Supports collaboration on local climate action In this learning tool, Do Data is used as a **reference case**: - If you want to **continue the development of Do Data**, the pathway helps you structure that work. - If you want to **develop a similar solution** in your own country or region, you can treat Do Data as an example of *“a municipal–technical development partner–business emissions monitoring platform”*. If your goal is to work with a solution in this family, then: - Use the **[[Roadmap->RoadmapOverview]]** to understand phases and decisions. - Use the **[[Do Data Cook Book->DoDataCookBook]]** for practical, hands-on guidance on concrete tasks, governance and technical setup relating specifically to Do Data. [[Go to municipality / public partner pathway->MunicipalityIntro]] [[Go to business / SME pathway->BusinessIntro]] [[Back to start->Start]]

Benchmarking and shared insights in a Do Data-like solution can help you: - Understand whether your emissions per unit (e.g. per employee, per turnover, per m²) are **high, medium or low** compared to similar companies - Identify where **improvements will have the biggest effect** - See which **actions** are common among companies that perform better - Strengthen your story towards **customers and partners** with data-based documentation You can also: - Give feedback to the municipality and the technical development partner on which indicators are **actually useful** - Co-design new views or tools that support your **business decisions** [[Back to business start->BusinessIntro]] [[Back to start->Start]]

The **Climate Compass** (or a similar tool) typically guides you through: - Direct emissions (Scope 1) - Purchased energy (Scope 2) - Selected indirect emissions (Scope 3) You enter your data (e.g. energy, transport, waste, materials), and the tool: - Calculates your emissions - Provides a structured overview - Allows exporting or sharing data with partners In a Do Data-like project: - Your climate data can be reused (with your consent) in a shared solution - You can get **dashboards and benchmarks** - You can help shape which indicators and views are actually useful for businesses If your company is **outside Denmark**, national emission factors should be used so your results are accurate. [[How we might submit data into a Do Data-like solution->BusinessSubmittingData]] [[Back to business start->BusinessIntro]] [[Back to start->Start]]

You are exploring the pathway as a **business / SME** – a potential **end user and co-developer** of a Do Data-like solution. With a solution in this family, you can: - Calculate and understand your **climate footprint** (e.g. via Climate Compass or a similar tool) - Benchmark against **similar companies or sectors** - Identify **emission hotspots** - Discover which **climate actions** others are taking - Strengthen communication with **customers, suppliers and authorities** Your role can be: - A **pilot company** helping to shape and test the solution - A **regular user** of the dashboards - A **partner** providing feedback and improvement ideas Where are you in your climate and data journey? [[We are new to climate accounting->BusinessNew]] [[We already use the Climate Compass or a similar tool->BusinessUsingClimateCompass]] [[We mainly want benchmarking and insights->BusinessBenchmarking]] [[Back to start->Start]]

You have little or no experience with climate accounting. If you want to participate in the development of a Do Data-like solution, your first step is to create a **basic climate inventory**. Typical data you need: - Energy bills (electricity, heating) - Fuel use for company vehicles - Business travel and commuting patterns (if possible) - Waste management (volumes and types) - Major purchased goods and services The municipality, technical development partner or business network may help you: - Use the **Climate Compass** or another climate accounting tool to enter your data - Understand your main emission sources - Interpret the visualisations in the future **shared solution** [[How the Climate Compass (or similar) works->BusinessClimateCompassExplained]] [[How we might submit data into a Do Data-like solution->BusinessSubmittingData]] [[Back to business start->BusinessIntro]] [[Back to start->Start]]

Once you have created or updated your climate inventory, your data can be: - Exported or transferred to a **shared solution** (like Do Data) - Aggregated with other companies in your sector - Used to generate dashboards for **benchmarking and insights** This allows you to: - See how your emissions compare over time and versus others - Track the effect of your climate actions - Use data-based documentation in communication with customers and partners In a collaborative project with municipality and the technical development partner: - You can help define what **you want in return** for sharing data (e.g. specific indicators, reports, or tools). [[What are the benefits of benchmarking and shared insights?->BusinessBenchmarking]] [[Back to business start->BusinessIntro]] [[Back to start->Start]]

You already use the **Climate Compass** or a similar climate accounting tool. In that case, a Do Data-like solution can become a **multiplier**: You gain: - Sector-level **benchmarks** - Comparison with similar companies on selected indicators - Overview of your **energy mix and hotspots** - Inspiration from typical **climate actions** in your sector - A way to communicate your progress to stakeholders and customers If your country is not Denmark, make sure your climate accounting uses **national or sector-specific emission factors**, so any benchmarks are meaningful. [[See benchmarking benefits->BusinessBenchmarking]] [[Back to business start->BusinessIntro]] [[Back to start->Start]]

''Do Data Cook Book — Recipes & Checklists'' This Cook Book provides hands-on methods and ready-made “recipes” for building, running and scaling a Do Data-like solution. It is the practical counterpart to the roadmap and intro content in this guide. ''Recipe 1 - Create organisational readiness'' Goal: Ensure your organisation is ready to build or extend a Do Data-like solution. *Ingredients:* - Climate strategy or action plan - Basic data governance practices - Internal capacity (data, digital, project) - Willing partners (e.g. businesses, RTOs) *Steps:* 1. Map internal roles (data, IT, climate). 2. Identify existing datasets (Climate Compass, energy, business data). 3. Assess skills maturity (basic analytics, digital tools). 4. Identify partners — internal and external. 5. Clarify scope: What should the solution do in v1? *Checklist:* - [ ] We have a climate plan using emissions data - [ ] We have contact to businesses - [ ] We understand basic data sources - [ ] We have a project owner - [ ] We have a technical partner or internal IT ''Recipe 2 - Build the foundational data infrastructure'' Goal: Establish a minimum viable data pipeline. *Ingredients:* - Access to Climate Compass or similar - Emission factors (national or EU) - Open data sources - Technical developer or RTO-partner *Steps:* 1. Define required datasets and metadata. 2. Build the ingestion pipeline. 3. Implement data cleaning rules (validation, deduplication). 4. Apply emission factors or formulas. 5. Store the data in a structured model. 6. Test with 3–5 companies. *Checklist:* - [ ] We can ingest Climate Compass exports - [ ] We can store structured emissions data - [ ] We can apply emission factors - [ ] We can generate basic analytics - [ ] We can run the pipeline repeatedly ''Recipe 3 - Build the MVP dashboard'' Goal: Enable core visualisation before full-scale development. *Ingredients:* - Defined KPIs (scope 1, 2, optional 3) - UI sketches or wireframes - Developer or dashboard tool (open source recommended) *Steps:* 1. Choose 3–5 core KPIs for MVP. 2. Create a simple company dashboard (emissions, hotspots). 3. Create a municipal overview (aggregated view). 4. Add basic benchmarking. 5. Test with end users. *Checklist:* - [ ] We have wireframes - [ ] We have KPI definitions - [ ] We have a first dashboard - [ ] Users can navigate it - [ ] The insights make sense to users ''Recipe 4 - Start co-development with businesses'' Goal: Work with businesses to shape the solution. *Ingredients:* - Pilot businesses (3–8) - Workshop format - Example dashboards *Steps:* 1. Select businesses that already use or plan to use Climate Compass. 2. Hold a workshop about needs and pains. 3. Show early prototypes. 4. Collect user feedback. 5. Prioritise features for the next iteration. *Checklist:* - [ ] Pilot businesses selected - [ ] Workshop plan created - [ ] Early prototypes ready - [ ] Feedback documented - [ ] Feedback integrated in roadmap ''Recipe 5 - Plan for scaling and collaboration'' Goal: Prepare the solution for use beyond the initial municipality. *Ingredients:* - Open source components - Documentation - Inter-municipal collaboration setup - Simple governance model *Steps:* 1. Ensure open standards and avoid vendor lock-in. 2. Document data models, APIs and components. 3. Align with national or European data space principles. 4. Prepare onboarding materials for other municipalities. 5. Identify funding opportunities for scale-out. *Checklist:* - [ ] Data model documented - [ ] API documented - [ ] Open source applied - [ ] Governance structure ready - [ ] Scaling plan defined [[Back to start->Start]]

Your **digital maturity** and **partnership experience** influence how you can continue or replicate a Do Data-like solution. Indicators of readiness: - Ability to **reuse structured datasets** (climate, energy, business data) - Experience with **open-source tools** or shared platforms - Internal or external **IT development capacity** - Existing **data governance policies** (roles, responsibilities, quality) - Basic **data analytics skills** (spreadsheets, BI tools, GIS) - Prior collaboration with **research and technology partners (e.g. RTOs)** and **business networks** If most of these are: - **Low or missing** → you need a **foundational readiness plan** before committing to a Do Data-like project. - **Medium to high** → you can move faster to **concrete development planning** with partners. For the practical steps of assessing readiness, you can: - Use the **[[Do Data Cook Book->DoDataCookBook]]** as a source of checklists and example questions. [[Develop a foundational readiness plan->MunicipalityReadinessPlan]] [[See technical and data-related requirements->MunicipalityTechnicalRequirements]] [[Back to municipality start->MunicipalityIntro]] [[Back to start->Start]]

As a municipality or region, you are a **public partner** and **service provider** for local businesses. If you want to continue Do Data or develop a similar solution, you will need to: - Invite SMEs to use the **Climate Compass** or a similar climate accounting tool - Support them in entering and understanding their climate data - Provide access to **dashboards and insights** as part of the new solution - Organise workshops, training or guidance on climate action planning - Share examples of **successful climate actions** from pilot companies - Collect feedback from businesses to inform **further development** If you lack internal capacity for engagement, consider: - Cooperation with **business associations** - **Chambers of commerce** or regional business organisations - **Climate networks** and innovation hubs - The technical development partner as a facilitator or trainer [[We are ready to scale or deepen a Do Data-like solution to more businesses->MunicipalityScaling]] [[Back to municipality start->MunicipalityIntro]] [[Back to start->Start]]

A solution similar to Do Data is designed so that **municipalities mainly see aggregated data**, not detailed company-level emissions in a way that enables direct ranking or shaming. Still, you must consider: **Ethics** - How do we avoid unintentionally exposing individual companies? - How do we communicate clearly what is shared and what is aggregated? - How do we ensure the solution is used to support learning and improvement, not punishment? **Legal** - Are there any **personal data** involved (e.g. contact persons, logins)? - Do we need a **Data Protection Impact Assessment (DPIA)**? - Are we compliant with national and EU rules on **data processing, public sector data and open data**? - How do we structure **agreements** between municipality, technical development partner and businesses? The **[[Do Data Cook Book->DoDataCookBook]]** can point to typical legal and ethical documents and work processes used in the original Do Data context. [[Engaging and supporting local businesses as end users->MunicipalityEngagingBusinesses]] [[See overall roadmap->RoadmapOverview]] [[Back to municipality start->MunicipalityIntro]] [[Back to start->Start]]

At this stage, you are asking: *“Is it relevant for us to further develop Do Data, or to develop a similar solution together with a technical development partner and businesses?”* Key questions: - Do we have a **climate action plan** that relies on emissions data? - Do we already support local businesses in using **Climate Compass or similar tools**? - Do we have **basic data governance structures** across departments? - Which actors must be involved in co-development? → Climate / environment, business services, IT, data/analytics, technical development partner (e.g. RTO), and representative businesses If your digital and organisational capacity is unclear, start by assessing your **digital maturity** and **collaboration readiness**. [[Assess our digital maturity and collaboration capacity->MunicipalityDigitalMaturity]] [[Reflect on organisational anchoring and partnership roles->MunicipalityOrganisationalAnchoring]] [[See overall roadmap->RoadmapOverview]] [[Back to municipality start->MunicipalityIntro]] [[Back to start->Start]]

You are exploring the pathway as a **municipality or regional authority** – a *public partner* and potential **taker** of a solution like Do Data. Your position could be: - You want to **continue** the Do Data solution after the original pilot, or - You want to **co-develop a similar solution** with a technical development partner (e.g. an RTO) and local businesses in your own context. In both cases, you need to consider: - **Digital and organisational readiness** - **Ethical and legal** reflections - **Technical** requirements - **Collaboration model** with the technical development partner and businesses - Your **roadmap** for further development and scaling Where are you right now? [[We are just exploring whether a Do Data-like solution fits us->MunicipalityExploring]] [[We are preparing for concrete development / implementation->MunicipalityPreparing]] [[We already have a pilot and want to scale or deepen it->MunicipalityScaling]] [[See overall roadmap for a Do Data-like solution->RoadmapOverview]] [[Back to start->Start]]

Whether you continue Do Data or develop a similar solution, success depends on **clear roles and responsibilities** across partners. Typical roles: - **Climate Lead (municipality)** Responsible for climate objectives, use of insights, and alignment with climate action plans. - **Business Services Lead (municipality / business promotion agency)** Coordinates contact with local SMEs, communication, and support in using the solution. - **IT / Digitalisation Lead (municipality or shared IT organisation)** Responsible for hosting, security, updates, and integration with municipal systems. - **Data Governance Lead (municipality)** Ensures data quality, access rules, interoperability and alignment with data strategies. - **Technical Development Partner Lead (e.g. RTO)** Coordinates technical development, methods, and knowledge transfer. - **Business Representatives / Pilot Companies** Contribute requirements, test the solution, and provide feedback from real use. If these roles are not clearly assigned, development and scaling of a Do Data-like solution will be fragile. [[Ethical and legal reflections->MunicipalityEthicalLegal]] [[Engaging and supporting local businesses as end users->MunicipalityEngagingBusinesses]] [[Back to municipality start->MunicipalityIntro]] [[Back to start->Start]]

You are in a phase where you have decided that a Do Data-like solution is relevant, and you are preparing practical development and implementation with partners. Focus areas: - Finalising your **readiness plan** (organisational, legal, technical) - Agreeing on a **collaboration model** with the technical development partner and business stakeholders - Choosing **hosting and operations model** (internal, shared regional, external provider) - Aligning with existing **digital and climate strategies** - Planning **business engagement** and communication activities For the operational parts of this phase, the **[[Do Data Cook Book->DoDataCookBook]]** can provide: - Step-by-step guidance - Example governance models - Templates for workshops and documentation [[Review digital maturity and readiness plan->MunicipalityDigitalMaturity]] [[Check technical requirements->MunicipalityTechnicalRequirements]] [[Plan engagement with businesses->MunicipalityEngagingBusinesses]] [[See overall roadmap->RoadmapOverview]] [[Back to municipality start->MunicipalityIntro]] [[Back to start->Start]]

A **foundational readiness plan** helps you decide whether and how to: - Continue the development of the existing Do Data solution, or - Launch a new, similar project in your own region. Consider four dimensions: **Organisational** - Who owns climate-data use in the municipality? - How will climate, business services, IT and data governance work together? - How will you formally involve a **technical development partner (e.g. RTO)** and **representative businesses**? **Ethical** - How do we ensure transparency for businesses about how their data is used? - How do we avoid unfair treatment of sectors or individual companies? - How do we ensure that the solution is used to **support**, not punish, businesses? **Legal** - Do we process any **personal data** as part of the solution? - Do we need a **Data Protection Impact Assessment (DPIA)**? - Do we have appropriate **contracts** and **data processing agreements** with the technical development partner and other organisations? **Technical** - Can we host or connect to a Do Data-like open-source solution? - Do we have access to **Climate Compass data** (or similar) via API or export? - Can we integrate **national emission factors** instead of Danish ones? For concrete examples of documents and workflows, you can refer to the **[[Do Data Cook Book->DoDataCookBook]]**. [[See technical implementation requirements->MunicipalityTechnicalRequirements]] [[Reflect on organisational anchoring and partnership roles->MunicipalityOrganisationalAnchoring]] [[Back to municipality start->MunicipalityIntro]] [[Back to start->Start]]

You already have a pilot or a first version and now want to **scale or deepen** a Do Data-like solution. Scaling options: - Involving **more sectors** (e.g. industry, retail, tourism, logistics) - Extending use to the **whole municipality or region** - Collaborating with **neighbouring municipalities or regions** - Using the solution as part of **sectoral or regional climate agreements** - Sharing the solution in **national or EU-level data spaces** Key reflections: - How do we ensure **long-term funding and maintenance**? - How do we keep **data quality** high when more actors join? - How do we manage **versioning and further development** of the solution? - How do we share experiences, code and methods with others (e.g. open-source communities)? The **[[Do Data Cook Book->DoDataCookBook]]** can support this phase with: - Scaling scenarios - Lessons learned - Example governance for multi-municipal setups [[See overall roadmap->RoadmapOverview]] [[Back to municipality start->MunicipalityIntro]] [[Back to start->Start]]

If you want to develop a solution similar to Do Data or continue Do Data, your technical environment should be able to: - Host the open-source **frontend and backend**, or work with a hosting partner - Handle **API connections** to Climate Compass or comparable tools - Store **aggregated climate data** securely - Manage **user access** for municipal staff, the technical development partner and businesses - Implement **GDPR-compliant** security measures - Support **national emission factors** if you are outside Denmark - Integrate with your existing **data platforms** (e.g. data warehouse, BI tools) If you have: - A dedicated **IT department** → development and maintenance can be handled internally, in collaboration with the technical development partner. - Limited IT capacity → consider regional IT collaboration or external vendors (with clear open-source and governance requirements). The **[[Do Data Cook Book->DoDataCookBook]]** can provide more detailed guidance on: - Reference architectures - Example data flows - Integration patterns [[Organisational anchoring and partnership roles->MunicipalityOrganisationalAnchoring]] [[Ethical and legal reflections->MunicipalityEthicalLegal]] [[Back to municipality start->MunicipalityIntro]] [[Back to start->Start]]

If you want to develop a solution similar to Do Data, or continue the development of Do Data in another country or region, you should adapt the underlying emissions data. Typical national/regional data sources include: - **Electricity emission factors** → From national energy agencies, Eurostat or the European Environment Agency - **Heating system factors** (district heating, gas, oil, heat pumps) - **Transport data** → Typical commuting patterns, fuel mix, vehicle types - **Waste management** → Local recycling rates, landfill, incineration methods - **Agriculture** → National agricultural inventories or IPCC default factors - **Scope 3 data** → Sector-specific databases and EU-level guidance With these adaptations, the **structure** of Climate Compass-style accounting and the **visualisation approach** used by Do Data remain relevant and useful across EU regions. [[Back to Climate Compass overview->AboutClimateCompass]] [[Back to start->Start]]

**Do Data Roadmap Overview** If you want to develop a solution similar to Do Data, or continue the development of Do Data, you can think in terms of **seven steps**: 1. **Foundations** Climate strategy, climate action plans, and basic understanding of climate and emissions data, including the Climate Compass or similar tools. 2. **Data Infrastructure** Access to relevant data sources, including climate accounting data, national emission factors, and open data. 3. **Organisational Governance and Partnership Model** Clear roles across municipality, technical development partner and businesses; agreements on how to work together. 4. **Technical Setup and Architecture** Hosting, integration of components, APIs, security and GDPR compliance. 5. **Onboarding Businesses and End Users** Communication, guidance and support for SMEs and other users. 6. **Scaling and Collaboration Beyond the Pilot** Extending use to more sectors, municipalities or regions, and connecting to wider data spaces. 7. **Continuous Improvement and Learning** Monitoring data quality, updating methods, refining dashboards and collecting feedback. For many of the practical tasks in each step, you can use the **[[Do Data Cook Book->DoDataCookBook]]** as a more detailed implementation guide. Choose a step to explore further: [[Step 1 – Foundations->RoadmapStep1]] [[Step 2 – Data Infrastructure->RoadmapStep2]] [[Step 3 – Governance and Partnership Model->RoadmapStep3]] [[Step 4 – Technical Setup and Architecture->RoadmapStep4]] [[Step 5 – Onboarding Businesses and End Users->RoadmapStep5]] [[Step 6 – Scaling and Wider Collaboration->RoadmapStep6]] [[Step 7 – Continuous Improvement and Learning->RoadmapStep7]] [[Back to start->Start]]

**Step 1 – Foundations** Key questions: - Do we have a **climate action plan** with clear targets and priorities? - Do we want to use **emissions data and visualisations** to monitor progress and guide decisions? - Are we ready to work with **businesses and a technical development partner** as co-creators, not just as “data providers”? A Do Data-like solution supports these foundations by: - Turning company climate and emissions data into **shared insights** - Connecting **municipal planning** with **business action** - Showing where local climate action can have the biggest effect For concrete examples of how Do Data approached this step, you can look into the **[[Do Data Cook Book->DoDataCookBook]]**. Continue to next step: [[Step 2 – Data Infrastructure->RoadmapStep2]] [[Back to roadmap overview->RoadmapOverview]] [[Back to start->Start]]

**Step 2 – Data Infrastructure** Key elements: - Access to a **climate accounting tool** (Climate Compass or similar) - Ability to integrate **national emission factors** and context-specific data - Use of **open data** where relevant (e.g. energy, mobility, geography) - Agreements on how data flows between **businesses, municipality and the technical development partner** - Choices about **data storage**, formats and interoperability In a Do Data-like project: - The technical development partner often plays a key role in designing the **data model** and **pipelines**. - The municipality defines which **insights** are needed for climate planning. For more operational guidance on data flows and formats, see the **[[Do Data Cook Book->DoDataCookBook]]**. Continue to next step: [[Step 3 – Governance and Partnership Model->RoadmapStep3]] Go back to previous step: [[Step 1 – Foundations->RoadmapStep1]] [[Back to roadmap overview->RoadmapOverview]] [[Back to start->Start]]

**Step 3 – Governance and Partnership Model** This step is about: - Defining **who does what** across: - Municipality / region - Technical development partner (e.g. RTO) - Businesses and business networks - Clarifying **decision-making structures** for further development - Agreeing on **funding**, maintenance and support - Ensuring **transparency and trust** around data use A strong partnership model makes a Do Data-like solution: - Robust - Scalable - Attractive to new partners and regions The **[[Do Data Cook Book->DoDataCookBook]]** can include example governance models and meeting structures that worked in the original project. Continue to next step: [[Step 4 – Technical Setup and Architecture->RoadmapStep4]] Go back to previous step: [[Step 2 – Data Infrastructure->RoadmapStep2]] [[Back to roadmap overview->RoadmapOverview]] [[Back to start->Start]]

**Step 4 – Technical Setup and Architecture** Decisions in this step include: - Where and how the solution will be **hosted** (local, shared, cloud) - How to secure **API connections** and data flows - How users (internal and external) will **log in** and access dashboards - How to document the technical architecture, so it can be **maintained and reused** - How to align with **national or EU data space initiatives** In a Do Data-like context, the technical development partner often: - Designs and documents the architecture - Builds and tests components - Supports handover and capacity building The **[[Do Data Cook Book->DoDataCookBook]]** can provide: - Example architecture diagrams - Typical technology choices - Lessons learned from implementation. Continue to next step: [[Step 5 – Onboarding Businesses and End Users->RoadmapStep5]] Go back to previous step: [[Step 3 – Governance and Partnership Model->RoadmapStep3]] [[Back to roadmap overview->RoadmapOverview]] [[Back to start->Start]]

**Step 5 – Onboarding Businesses and End Users** Key activities: - Informing local SMEs about the **purpose and benefits** of sharing climate and emissions data - Providing **practical guidance** on using the Climate Compass or similar tools - Helping companies interpret their **dashboards and benchmarks** - Co-designing indicators, dashboards and services with end users - Collecting feedback to improve both the solution and the support offers This step turns a Do Data-like solution into: - A **real service** for the local business community - A **dialogue tool** between public and private actors The **[[Do Data Cook Book->DoDataCookBook]]** can suggest: - Workshop formats - Communication materials - Example onboarding journeys. Continue to next step: [[Step 6 – Scaling and Wider Collaboration->RoadmapStep6]] Go back to previous step: [[Step 4 – Technical Setup and Architecture->RoadmapStep4]] [[Back to roadmap overview->RoadmapOverview]] [[Back to start->Start]]

**Step 6 – Scaling and Wider Collaboration** Once a first version is running, you can: - Extend the solution to **new sectors** or geographical areas - Collaborate with **other municipalities or regions** - Share code, experiences and documentation in **open-source communities** - Connect your solution to **national or European data spaces** in the climate or sustainability domain In this step, you are asking: - What is our **minimum viable product**? - What is our **scaling strategy**? - How do we avoid **lock-in** and keep the solution open? The **[[Do Data Cook Book->DoDataCookBook]]** can include: - Scaling scenarios - Collaboration models between multiple municipalities and technical development partners - Suggestions for national or EU-level alignment. Continue to next step: [[Step 7 – Continuous Improvement and Learning->RoadmapStep7]] Go back to previous step: [[Step 5 – Onboarding Businesses and End Users->RoadmapStep5]] [[Back to roadmap overview->RoadmapOverview]] [[Back to start->Start]]

**Step 7 – Continuous Improvement and Learning** Continuous improvement includes: - Monitoring and improving **data quality** - Updating **emission factors**, indicators and methodological assumptions - Refining dashboards and user journeys based on **feedback** - Documenting lessons learned and sharing them with other regions and sectors - Training new staff and partners as they join A Do Data-like solution is not a one-off project, but part of a **longer learning process**. The **[[Do Data Cook Book->DoDataCookBook]]** can help you: - Structure retrospectives and learning loops - Capture experiences - Plan the next iteration of your solution. Go back to previous step: [[Step 6 – Scaling and Wider Collaboration->RoadmapStep6]] [[Back to roadmap overview->RoadmapOverview]] [[Back to start->Start]]

Welcome to the **CO₂ Emissions Monitoring Solution Pathway**. This interactive guide is designed to help you explore what it would take to: - **Continue the development of the existing “Do Data – for a Greener Future” solution**, or - **Develop a new solution similar to Do Data** in your own context. Throughout the pathway, *Do Data* is used as an example of a solution co-developed between: - A **municipality or regional authority** - A **technical development partner, such as an RTO (Research and Technology Organisation – the Danish GTS system)** - **Local businesses and SMEs** You can read each step as: > “If we wanted to develop a solution similar to Do Data, or continue the development of Do Data, then we would need to…” Please choose how you want to explore the pathway: [[I am a municipality or regional authority (taker / public partner)->MunicipalityIntro]] [[I am a business / SME (end user / private partner)->BusinessIntro]] [[Learn more about using Do Data as an example->AboutDoData]] [[Learn more about the Climate Compass->AboutClimateCompass]]