---
id: ch5-guide-maa
type: spine
title: "How to use the MAA tool: from a stakeholder list to tracked objectives"
readingTime: 2
standalone: true
core: false
teaser: "Register who takes part, say what you want to achieve, and feed the progress in: the MAA tool workflow in seven steps."
parent: null
diagram: fig-guide-maa
recallQ: "In the MAA tool, how does an objective get a measurable value that the pilot can track?"
recallA: "The objective is created in the programme, assigned to a work entity and linked to an indicator that defines its data type, direction (increasing or decreasing) and whether the value is static or variable. Inputs, each with a date and an optional comment, then update the value, so stakeholder work becomes a traceable record."
highlights:
  - "Get invited and confirm your e-mail: a pending user becomes active"
  - "WP5 uses its own depth: work packages, then pilots, then activities"
  - "An indicator sets data type, direction and value type; inputs carry a date"
  - "Ramon drafts stakeholders and objectives from documents; nothing is created without your confirmation"
status: accepted
concept: maa-tool
lang: en
lens: generic
depth: standard
formalism: none
visuality: balanced
lengthBand: standard
genre: worked-example
state: edited
carriers: prose|diagram
---

**When to use it:** your pilot needs one shared record of who takes part, what they committed to, and how far it has got.

## What you need

- **An invitation.** The pack gives no public address. Users are tied to an e-mail address; someone can create you as a "representative" user and invite you by e-mail, and you stay "pending" until you confirm it (D5.1 §4.2). Ask your pilot lead or the WP5 team.
- Your pilot's stakeholder list (pilots' T2.1 stakeholders were imported at set-up, D5.1 §4.3), its objectives and pilot documents.

## Steps

1. **Confirm your account** and open the PoliRuralPlus programme. Its work entities mirror the work packages; WP5 uses the depth "work packages → pilots → activities" instead of "action plans → actions → tasks" (D5.1 §4.2).
2. **Register stakeholders** in your pilot's work entity: classify them and assign roles and permissions (D4.2 §3.9). A public stakeholder can be found and invited by other programmes; a private one cannot (D5.1 §4.2).
3. **Fill in the extra attributes** the programme defines, such as sector, organisation size or urban/rural profile. They drive the distribution charts.
4. **Define objectives** (KPIs, goals or milestones) and assign them to work entities.
5. **Link an indicator** to each non-aggregated objective: integer or decimal, increasing or decreasing, static or variable value (D5.1 §4.2).
6. **Record inputs**: each new value with a date and an optional comment. These updates move the objective forward.
7. **Let Ramon draft, then decide.** The built-in AI assistant extracts candidate stakeholders and objectives from pilot documents; you validate them before anything is created (D4.2 §3.9, §6.3).

## What you get

Searchable stakeholder and member registers, pilot and work-package views, objective progress tables, attribute-based charts and a communication history. D4.2 names them as evidence for RAP documentation, engagement summaries and testing reports (§3.9). In the Beta workspace this already covers more than 300 users, 40 work entities and 49 objectives.

## Watch out

- **Social spaces** appear in the menu but are still empty at programme and WP5 level.
- Stakeholder assignments are not yet complete in the same way across all nine pilots, and there is **no common attribute vocabulary** yet, so compare charts between pilots with care.
- Fuller WP5 validation evidence and export functions are planned for D4.3 (D4.2 §3.9).

A recorded online workshop (22 July 2024) walked pilots through the application; ask WP5 for it (D5.1 §4.4.1). The method behind the tool: [the multi-actor approach](#c/multi-actor-approach).

**Sources:**
- D4.2 PoliRuralPlus Platform Beta, §3.9 Multi-Actor Approach tool; §6.1 Testing methodology and pilot onboarding; §6.3 Usability observations. [PDF](https://www.poliruralplus.eu/docs/421/D4.2_PoliRuralPlus_Platform_Beta.pdf)
- D5.1 Prepared pilot by Stakeholder Multi-Actor Approach, §4.1–4.4 The Multi-Actor Approach Tool. [PDF](https://www.poliruralplus.eu/docs/150/D5.1_Prepared_pilot_by_Stakeholder_Multi-Actor_Approach_v1.0.pdf)