Skip to content

Coordinate policy advocacy with impact data

  • Advocacy technician: prepares briefings, agendas, and position papers for public representatives.
  • Project coordinator: collects field data from KoboToolbox and tracks M&E indicators.
  • Communications lead: translates raw data into advocacy messages with citable figures.

The two modules involved in this flow are at very different points in the product lifecycle. It is worth knowing this before attempting to automate anything.

  • Incidencia Política (coop_advocacy) has an advanced MVP: canonical models for advocacy actions, parliamentary targets, advocacy processes, and follow-up agenda. It is being used in an internal pilot. [VERIFY: primera versión estable publicada en organización GitHub Futuh pendiente.]
  • Datos M&E is in the pre-implementation spec phase: KoboToolbox bridge planned, project-and-country aggregated indicators in backlog, funder reporting in design. [VERIFY: spec inicial pendiente, contenido v1 esperado tras primera ronda de empaquetado del bundle cooperación.]

This means the flow described here is documented by anticipation: when Datos M&E enters production, this is the canonical pattern foreseen for stitching with Incidencia Política. Today the Datos M&E side is referential.

  1. Open Incidencia Política → Actions.
  2. Click New action.
  3. Fill in the context: topic (for example, Development cooperation in the 2027 general budget), type (bilateral meeting, public appearance, written briefing, public intervention), target actor (specific parliamentarian or committee).
  4. Associate the action with one or more advocacy processes currently active in your organization.

The action is recorded with its initial state (planning, in_progress, done) and enters the advocacy technician’s follow-up inbox.

Step 2: Identify the project or projects backing the action

Section titled “Step 2: Identify the project or projects backing the action”

A convincing policy advocacy action usually draws on data from your organization’s real projects. If you are going to argue before a MEP that development cooperation in rural areas produces measurable impact, the strongest case is citing the specific project where you demonstrated it.

  1. In the action record, open the Associated projects field.
  2. Search for the Gestión de ayudas projects whose results you want to cite.
  3. Associate them to the action. The system saves the bidirectional link.

From here, the action is connected to the projects whose M&E data you will use as backing.

When the Datos M&E module enters production, this is the canonical pattern foreseen. The projects associated with an advocacy action are worked in parallel in Datos M&E:

  • The project coordinator defines monitoring and evaluation indicators expected by the funder (AECID, AACID, UNHCR, EU).
  • Field data is collected with KoboToolbox and synchronized to your Futuh instance through the bridge planned in the module.
  • Raw data is aggregated by project, by country, by budget line.
  • Technical reports for funders are generated from the aggregation.

For the module detail, see Datos M&E. [VERIFY: bridge KoboToolbox y reporting técnico pendientes de implementación.]

Once you have quantitative impact data on the backed projects, you return to the advocacy action to cross-reference it.

  1. Open the action record in Incidencia Política.
  2. In the Evidence tab, click Import from Datos M&E.
  3. Select the indicators you want to cite (territorial coverage, number of beneficiaries, executed budget, measured results).
  4. The system creates an evidence section within the action with a verbatim citation of the indicator and a link to the originating project.

[VERIFY: integración Import de Datos M&E pendiente de implementación cuando el módulo M&E entre en producción.]

With the action documented and the evidence cross-referenced, you generate the briefing you will bring to the bilateral meeting, the public appearance, or send as a written document.

  1. In the action record, click Generate briefing.
  2. Choose a template (canonical document templates come from the federated Hub Central).
  3. Review the generated document: topic, your organization’s position, quantitative evidence, concrete proposed action.
  4. Export to PDF or send directly from Futuh.

The briefing is archived as an attachment on the action, along with the date and recipient.

Once the action has been executed (meeting, appearance, submission), record the outcome:

  1. Open the action.
  2. Set state to done.
  3. Record the result in the Follow-up notes field: what the interlocutor said, what commitment they made, what next steps you agreed on.
  4. If the action triggers relevant parliamentary votes, associate the votes with the advocacy process for quantitative follow-up. [VERIFY: integración HowTheyVote / parlamento.eu pendiente.]

This closes the cycle: the action is recorded with its context, its quantitative backing, its briefing, and its outcome.

ModuleWhat it contributes to the flowDetail
[[Incidencia_Politica]]Canonical model of actions, briefings, parliamentary trackingIncidencia Política
[[Datos_M_y_E]]M&E indicators, KoboToolbox bridge, aggregation by projectDatos M&E
[[Gestion_de_ayudas]]Projects whose data backs the advocacyGestión de ayudas
[[Federacion_Futuh]]Canonical document templates for briefings, canonical parliamentary contactsFederación Futuh
[[Silvio]]Queries open actions, lists evidence, suggests positions based on dataSilvio