Capture and formulate a call for proposals

What it's for

Take a public grant call from the moment it appears in Radar to when your organization submits and justifies it, without losing traceability from one module to the next.

Before you start

• Role: operator with access to Radar and Gestión de ayudas.
• Your organization has at least one BDNS connector active in Radar.
• Your organization has defined the canonical project types in Gestión de ayudas.
• Estimated time: this flow covers weeks or months in real time; what is documented here is the journey.

Who is involved

This flow crosses three typical roles in a third-sector organization:

• Fundraising officer: monitors Radar, decides which calls for proposals merit moving forward.
• Formulation technician: drafts the narrative, budget, and administrative documentation in Gestión de ayudas.
• Project coordinator: manages execution once the grant is awarded.

One person can take on all three roles in smaller organizations. The shape of the flow does not change.

Step 1: Radar identifies the call for proposals

Every morning, a Radar daily cron queries the BDNS and downloads new calls for proposals. BDNS covers national and regional calls in a single source. European calls via Funding & Tenders are in the process of being enabled. [VERIFY: cierre credencial SEDIA]

What Radar does for you overnight:

• Filters calls by sectors, territories, and typologies that match your organization’s profile.
• Calculates the fit score (0 to 100) combining compliance with formal requirements and alignment with the expected evaluation criteria.
• Enriches each record with amount, deadline, regulatory bases (url_terms), eligible beneficiaries, and raw BDNS data.
• Marks with a traffic light: green from 80, yellow from 50, red below.

In the morning, Radar delivers a daily digest with the candidates with upcoming deadlines and the best fit scores.

Step 2: Triage in the Radar inbox

1. Open Radar → Inbox from the Futuh main menu.
2. Filter by traffic light (green + yellow if you want to keep some margin) and by Critical deadline if fewer than 15 days remain.
3. Click on the title of each candidate to see the full record: amount, deadline, regulatory bases, expected co-financing.
4. Discard what does not apply (co-financing above 30% if your organization cannot cover it, excluding beneficiary type, etc.). Mark the ones that pass triage as Follow up.

What remains after the morning triage is typically a short list of 2 to 5 candidates worth a more careful review during the week.

Step 3: Handover to Gestión de ayudas

When a call for proposals is ready to start being formulated, it moves from Radar to Gestión de ayudas. This is the canonical stitching point between the two modules.

1. Open the call’s record in Radar.
2. Click the Send to Gestión de ayudas button.
3. Confirm the action in the confirmation modal.
4. The view moves to the newly created project in Gestión de ayudas, with stage Planning.

What happens technically: Radar creates a project.project record with stage Planning (confirmed as canon by the Gestión de ayudas module maintainer), copies the canonical fields from the call, and establishes a bidirectional link so that the project keeps a reference to the original Radar call.

Canonical entry stage

Planning is the only Gestión de ayudas stage confirmed as the canonical destination for the Radar handover. The subsequent stages in the Gestión de ayudas cycle (formulation, submission, execution, justification, closure) are pending closure with the module maintainer. [VERIFY: nombres canon stages posteriores Gestión de ayudas pendientes.]

For the technical detail of the handover, see Send a call to Gestión de ayudas.

Step 4: Formulation in Gestión de ayudas

As soon as the project appears in Planning, the flow leaves Radar and develops inside Gestión de ayudas:

• The formulation team is assigned.
• The descriptive narrative and detailed budget are drafted.
• Administrative documents are prepared (certificates, responsible declarations, cooperation agreements).
• Formal requirements are cross-checked against those flagged by Radar in the automatic regulatory-base analysis.

During this phase, the Plataforma de Recepción Inteligente may come into play to collect documents from consortium partner entities (when the call requires joint submission). Each partner receives their own upload link; documents are classified by AI and made available to the technician closing the file.

Step 5: Submission, execution, justification, closure

The subsequent cycle remains inside Gestión de ayudas. The planned stages are submission of the application, execution of the project if awarded, intermediate and final justification to the funder, and administrative closure. The canonical stages after Planning are pending closure with the module maintainer.

Throughout the entire cycle, the connection with Radar allows you to consult the original call from the project. If BDNS publishes a deadline extension or a change to the regulatory bases, Radar reflects it and it remains visible from the project in Gestión de ayudas.

How this flow fits with the rest

Module	What it contributes to the flow	Detail
[[Radar]]	Identifies, scores, and delivers the call for proposals	Radar de ayudas
[[Gestion_de_ayudas]]	Receives the project from Planning and manages the formulation, execution, and justification cycle	Gestión de ayudas
[[Plataforma_de_Recepcion_Inteligente]]	Collects documents from partner entities in consortia	Plataforma de Recepción Inteligente
[[Federacion_Futuh]]	Feeds canonical BDNS data (analyzed regulatory bases, awards, administrative templates)	Federación Futuh
[[Silvio]]	Queries calls and project status in natural language	Silvio

Learn more

• Send a call to Gestión de ayudas for the technical detail of step 3.
• Use Radar as an operator for the day-to-day work before the handover.
• Synchronize with the Federation to understand how canonical BDNS data reaches your instance.
• Glossary for the canonical terms: call for proposals, fit score, project, stage.