> 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/community-engagement-through-surveys/developing-editorial-priorities-through-surveys/how-the-bristol-cable-discovers-new-research-approaches.md).

# How The Bristol Cable Discovers New Research Approaches

*"Report more on the impacts of climate change in Bristol!"* was a repeated request from members of The Bristol Cable. The editorial team decided to involve the community from the very beginning in planning the new thematic focus.

Lucas Batt, then Membership Coordinator at The Bristol Cable, explained to us step by step how he and the team planned, conducted, and analyzed the survey. Here is an overview of the steps:

{% stepper %}
{% step %}
**Develop a strategy: How can the community contribute to the topic of climate change?**
{% endstep %}

{% step %}
**Create and publish a questionnaire, survey, and communication plan**
{% endstep %}

{% step %}
**Analyze initial responses and gather further feedback from participants**
{% endstep %}

{% step %}
**Adjust the survey and send it out again**
{% endstep %}

{% step %}
**Evaluate the responses**
{% endstep %}

{% step %}
**Thank participants for their involvement**
{% endstep %}
{% endstepper %}

***

## **Conducting the survey**

#### **1. Develop a strategy: How can the community contribute to the topic of climate change?**

In the first step, the team defined the purpose of the engagement and documented it in a goal:\
*"We want to bring together freelance journalists, environmental activists, Cable members, and readers to help us produce a series of articles on climate change."*

This led to the question of what the members and other readers could contribute. The team recorded the responses on a digital board:

<figure><img src="https://3104887601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhbO2Qj4wcNeF31vh6RNL%2Fuploads%2FMxXqzPl6pBEKJE09VXBP%2Fgrafik.png?alt=media&amp;token=64b4e09a-7c50-4813-b806-fbde3389ccab" alt=""><figcaption></figcaption></figure>

&#x20;                               *The digital board where the Cable team recorded the ideas.*

The team also identified potential collaborators in advance, such as freelance journalists who had already worked on environmental topics and local climate protection organizations.

In the long term, the aim was also to create an "infrastructure" to generally improve The Cable’s reporting on environmental issues. Lucas documented all goals like this, as well as potential collaborators, in an engagement strategy.

***

#### **2. Create the questionnaire, survey, and email**

Based on the engagement strategy, Lucas developed the questionnaire and formulated a total of five questions:

* What would you like to know about Bristol’s role in climate change, for example how Bristol’s businesses contribute or how the city is addressing it? (open-ended)
* What questions do you have about the impact climate change will have on Bristol? (open-ended)
* Are there specific topics or issues related to climate change that you think we should report on? (open-ended)
* Are you an expert on climate change, or have you personally experienced its effects? (Yes/No)
* Would you like to receive regular updates on climate and environmental topics via email? (Yes/No)

The completed survey was then sent to all newsletter subscribers of The Bristol Cable.

<figure><img src="https://3104887601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhbO2Qj4wcNeF31vh6RNL%2Fuploads%2FeYNJXwfeOm751TrOqvYW%2Fgrafik.png?alt=media&amp;token=97a23df7-c641-4612-b3af-b458917fc5d6" alt="" width="303"><figcaption></figcaption></figure>

&#x20;                                                     *Die E-Mail mit dem Link zur Umfrage.*

***

#### **3. Analyze initial responses and gather feedback**

In the first 24 hours, the initial responses began coming in, primarily from members. The same happened after a reminder in The Bristol Cable’s weekly newsletter two days later.

The team around Lucas started analyzing the survey immediately with the first responses. Lucas paid particular attention to:

* Questions and ideas for reporting
* Identification of experts

At the same time, the team sent a feedback survey to especially engaged members of The Bristol Cable. The goal was to find out how the survey could be further optimized. Was the survey easy to understand? Was it easy to answer the questions asked?

***

#### **4. Adjust and send out again**

Feedback from the engaged Cable members showed that the survey was very well received. However, one issue was that most people had simply overlooked or forgotten to participate.

The team therefore drafted a new email and sent the survey out again – unchanged – but only to those who had not yet participated.

***

#### **5. Evaluate the responses**

A total of around 118 people responded to the survey. Lucas compiled their answers in a long document, organized them by topic, and highlighted notable points.

In the end, the document was about 30 pages long, making it too extensive for practical use in the newsroom. Lucas therefore created a short version, summarizing the key topics and most frequently asked questions on just two pages.

Lucas provided us with the short version of his analysis (click on the image to enlarge):

<figure><img src="https://3104887601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhbO2Qj4wcNeF31vh6RNL%2Fuploads%2FS2uptGFM4zczaYZoxXWc%2Fgrafik.png?alt=media&amp;token=3b171821-4dfc-44f9-8f42-b3afba468054" alt="" width="188"><figcaption></figcaption></figure>

<figure><img src="https://3104887601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhbO2Qj4wcNeF31vh6RNL%2Fuploads%2FN3pkeNPHlcLN1emr873j%2Fgrafik.png?alt=media&amp;token=7681bb2a-794f-4a77-8139-73fe72b442d3" alt="" width="188"><figcaption></figcaption></figure>

***

#### **6. Thank participants for their involvement**

Shortly after the callout, the editorial team sent an email to everyone to thank them for participating and to explain what would be done with the responses. Participants with expert knowledge or unique stories were contacted separately, for example via email or phone.

***

## **The Result**

A total of 118 people participated. Based on the extensive collection of community questions and suggestions (a total of 30 pages), the editorial team was able to initiate investigations and report on the climate change topics that truly mattered to the community. One of the most frequently asked questions, for example, was when and how sea level rise would affect the port city of Bristol.

The Bristol Cable was also able to connect with several experts who are knowledgeable about specific aspects of climate change and could assist with research. In their member database (beabee), the Bristol Cable team tagged these individuals accordingly to be able to find them again later.

***

## **General tips from The Bristol Cable**

* **Good planning is everything:** It’s important to carefully consider what the community can and should contribute. If this is clear from the start, it saves a lot of time during the analysis. Smaller teams in particular should think carefully about their goals and what they can realistically achieve to avoid overextending themselves.
* **Analysis is time-consuming:** Ask only as many questions as you can actually analyze, but make sure they are the right ones. Another option is to delegate the analysis to someone else – perhaps volunteers from the community or students looking to earn a little extra.
* **Don’t be afraid to try a second time:** Even with good preparation, if the questions or email approach don’t work, it may be worthwhile to revise everything and send it out again. The same applies if the survey received little attention.
* **Quantity is secondary:** In total, fewer than 5% of Bristol Cable members participated in the survey. The results are primarily valuable qualitatively. After all, the editorial team now has multiple starting points for investigations and contacts with several experts.
* **It’s also about the process:** Community members who did not participate in the callout still know that the newsroom is listening and that the reporting reflects the collaboration with the community. Part of the newsroom’s work now also includes consistently highlighting community participation in the articles.

***

<p align="center"><strong>Get involved:</strong></p>

<p align="center"><a href="https://starthub.correctiv.org/crowdnewsroom/your-question-for-our-wiki" class="button secondary" data-icon="message">Ask a question</a> or  <a href="https://starthub.correctiv.org/crowdnewsroom/your-contribution-to-our-wiki" class="button secondary" data-icon="pencil">Make a contribution</a> or  <a href="https://starthub.correctiv.org/crowdnewsroom/your-feedback-for-our-community-journalism-wiki" class="button secondary" data-icon="comments">Give feedback</a></p>


---

# 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://wiki.beabee.io/community-journalismus/english/community-centred-methods/community-engagement-through-surveys/developing-editorial-priorities-through-surveys/how-the-bristol-cable-discovers-new-research-approaches.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.
