> For the complete documentation index, see [llms.txt](https://inclusivity.toolkit.citiobs.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inclusivity.toolkit.citiobs.eu/outreach-and-engagement/how-can-we-maintain-energy-in-our-co/the-energy-diagnosis-chart.md).
# The Energy Diagnosis Chart
The Energy Diagnosis Chart was developed in response to the needs expressed by Citizen Observatories participating in the CitiObs project as front-runner and fellow cases, to support them in understanding and strengthening their participation models. It provides a participatory diagnostic tool that maps the vitality and sustainability of a citizen science initiative or community project across 12 dimensions of health, organized into four domains: *Task Effort & Support*, *Team & Social Connection*, *Growth & Continuity*, and *Impact & Outcomes*.
**What It's For**
To surface how "alive" and sustainable an initiative feels in real time—not through external evaluation, but through the eyes of the people running it. The radar reveals which areas are thriving (close to 5) and which feel stuck or draining (closer to 0), offering a non-judgmental snapshot of initiative health.
**Key Features**
* **12 interconnected dimensions** (e.g., task difficulty, team coordination, leadership renewal, policy engagement, data use)
* **0–5 scale** on each spoke: from deficit ("difficult/complex") to strength ("easy/well-supported")
* **Visual profile**: Connecting the dots creates a shape that groups can immediately "read"—spiky, lopsided, or well-rounded
* **Action companion**: A second page ("From Energy to Action") turns diagnosis into strategy, asking *what to change, with whom, and how*
**Workshop Use**
1. **Shared Sense-Making** (\~20 min): Individual or small-group mapping to generate conversation about initiative realities and contextual factors, and share insights with each other
2. **Pattern Spotting** (\~15 min): Compare shapes across groups or time. Does everyone see the same bottlenecks? What surprises?
3. **Systems Thinking**: Use mismatches to surface interdependencies—e.g., "We have great social connection but no impact visibility—that's demotivating."
4. **Action Planning**: Move directly from "what's stuck?" to "what can we shift?"—and with whom—using the second page
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://inclusivity.toolkit.citiobs.eu/outreach-and-engagement/how-can-we-maintain-energy-in-our-co/the-energy-diagnosis-chart.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
