> For the complete documentation index, see [llms.txt](https://wiki.beabee.io/community-journalismus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.beabee.io/community-journalismus/english/community-centred-methods/crowd-investigations/crowd-investigations-in-5-steps/analysis-phase.md).
# Analysis Phase
As soon as the crowd investigation for the community starts, the analysis phase begins for you. While the campaign is running, you look at the first responses. You can check evidence, read the information provided, or contact the people who have given you permission to get in touch. The responses reveal patterns and provide research leads that you can then follow up on.
Once the campaign is complete, you evaluate all the data you have collected, follow up on every single lead and, ideally, identify structural problems behind the individual cases. This results in articles and posts that you share with the community — because you owe them these research results.
***
## An example — 'Achtung, Schulweg!' 🎒
On the topic of school routes, for example, statements that identified a specific route as a problem or named a specific issue were interesting. For example, that a school route along a side street is used as a detour in the morning due to traffic jams on the main road.
This enabled us to write very specific, individual stories in which those affected had their say, whose contact details we already had thanks to crowdsourced research. If a particular problem occurred frequently, then a story that pointed to a systemic problem such as a lack of 30 km/h zones, poor bicycle traffic planning for new school buildings, or a lack of structural restrictions on car traffic was interesting.
***
Get involved:
Ask a question or Make a contribution or Give feedback
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://wiki.beabee.io/community-journalismus/english/community-centred-methods/crowd-investigations/crowd-investigations-in-5-steps/analysis-phase.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.