> For the complete documentation index, see [llms.txt](https://action.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://action.toolkit.citiobs.eu/reflection.md).

# Reflection

A crucial part of any community-led or citizen-led action is the thoughts and considerations put into it. It allows us to pause, look back, and ask: “*Did we create the impact we hoped for? What worked well? What could be done differently next time?”.* This chapter is about deepening our understanding, improving future actions, and making the invisible impacts of our efforts more visible and shareable.

To effectively do this, we need to measure and manage impact in a thoughtful way. This includes:

* Tracking outcomes with clear indicators
* Reviewing the results
* Adjusting our approach where needed

Impact reflection also allows us to communicate our progress with transparency and purpose, whether to our community, potential funders, or broader networks.

In this chapter, you’ll find tools and guidance to support the reflective phase of your action. Whether your initiative is large and ongoing or small and temporary, reflection helps to give meaning to your work, amplify its relevance, and prepare the ground for what's next.


---

# 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://action.toolkit.citiobs.eu/reflection.md?ask=<question>&goal=<user_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.
