Which tool when
Collecting data, analysing it, writing a brief, engaging people, deciding, monitoring: which PoliRural+ tool helps at each step, and where its how-to guide is.
Which PoliRural+ tools support which steps of preparing a Regional Action Plan, and how does a pilot choose among them?
D4.1 maps six RAP steps to tools: data collection (Vulture, Magpie), integration and analysis (JackDaw, Magpie, rural attractiveness tools), policy briefs (the Advisor), stakeholder engagement (MAA tool, MapWhiteboard, JackDaw), decision-making (Advisor, JackDaw, MapWhiteboard) and monitoring (attractiveness tools, JackDaw). Each pilot names its planning challenge first and then selects only the Beta services it needs.
- D4.1 links six RAP steps to named tools
- Pick by the object of the question: a place, a document corpus, or people and targets
- Onboarding starts with the planning challenge, then the selection of services
- Pilots combine different bundles; no pilot uses everything
Which tool when: matching PoliRural+ tools to the steps of a RAP
main tellingdepth: intro..standard3 min markdown
A Regional Action Plan moves through D3.1’s three phases: preparation, foresight and the plan itself, then follow-up. D4.1 splits the same work into six steps and names the tools for each. The table puts both together, with what is actually usable in the Beta (D4.2) and a link to each how-to guide.
| RAP step (D4.1) | Mainly in D3.1 phase | Tools named in D4.1 | What to open in the Beta | How-to |
|---|---|---|---|---|
| 1. Data collection | I Preparation | Vulture, Magpie, personal information stream processing | Vulture for your own e-mails and pages; Magpie search now runs inside Raven; the Hub library | Vulture, Raven and Magpie, Hub |
| 2. Data integration and analysis | I–II | JackDaw, Magpie, Rural Attractiveness Explorer, a data extraction and analysis tool | JackDaw for any drawn area; the 1 km innovation potential grid on the Czech-Bavarian border | JackDaw, Attractiveness |
| 3. Policy brief preparation | II | PoliRural+ Advisor, LLMs, Vulture | The Advisor over the project corpus | Advisor |
| 4. Stakeholder engagement | I–III | MAA tool, MapWhiteboard, JackDaw | MAA tool (300+ users in the Beta); simplified MapWhiteboard | MAA tool, MapWhiteboard |
| 5. Decision-making and strategy | II | Advisor, JackDaw, MapWhiteboard, Vulture | Advisor, plus the Agent Builder for repeated assessments; MapWhiteboard for spatial choices | Advisor, MapWhiteboard |
| 6. Monitoring and evaluation | III Follow-up | Rural Attractiveness Explorer, JackDaw, a data extraction and analysis tool | Objectives, indicators and inputs in the MAA tool; dashboards for indicators | MAA tool |
Before step 5, look at what other regions have already tried: the Atlas guide.
A quick rule for choosing
Ask what the question is about:
- A place (land, climate, people, businesses in a territory): JackDaw; MapWhiteboard when a group has to discuss it.
- A body of documents (policies, deliverables, pilot reports): the Advisor; Vulture only for your private stream.
- People and commitments (who takes part, which targets, how far): the MAA tool.
How pilots actually choose
D4.2’s onboarding has five steps. The pilot names its regional planning challenge first and only then selects the Beta services. After that come workspaces and roles, data and metadata, and testing in real meetings and workshops (§6.1). The bundles differ. Monaghan worked with dashboards, the MAA tool and the Hub. The Czech-Bavarian pilot used JackDaw and the attractiveness grids. Mallusjoki combined the MAA tool, the Advisor, JackDaw and Raven (Table 7).
The D4.1 column comes from the design stage. Some tools it names have changed role since then: Magpie’s function moved into Raven, and Vulture became less central (D4.2 §3.4–3.5). The guides that follow describe the Beta as it is.
Related
- Builds on: Regional Action Plans (RAPs)