Sending a call to Gestión de ayudas

What it does

This page describes the handover: how to send an interesting call from Radar to the Gestión de ayudas module to start formulating, without losing the back-link to the source call.

Before you start

• Role: operator with access to both Radar and Gestión de ayudas.
• The call is in your Radar inbox and you have already reviewed it.
• Your organization has the Gestión de ayudas module active.
• Estimated time: 1–2 min per handover.

Before you start

It is worth making one decision before executing the handover: once sent to Gestión de ayudas, the call moves into the formulation workflow and leaves the active Radar inbox (it is marked as in management). It is not destructive (you can always return to Radar to consult the source call), but it does change the working location.

Make sure that:

• The call has enough time left to formulate.
• You have reviewed the regulatory bases (the url_terms link in the record).
• You have checked the fit score traffic light and understand why it matches.
• Your organization is in a position to apply (co-financing, team, deadlines).

Step 1: Identify the call in Radar

1. Open Radar → Inbox.
2. Locate the call you want to send. You can use sector or fit-score filters to narrow down.
3. Click its title to open the full record.

Step 2: Launch the handover

1. In the call record, click the Send to Gestión de ayudas button.
2. Confirm the action in the confirmation modal.
3. The view moves automatically to the project just created in Gestión de ayudas.

What happens technically at this step: Radar creates a project.project record with Planning stage, copies the canonical fields (name, description, estimated requested amount, deadline, funder) from the call, and establishes a bidirectional link so that the Radar source remains associated with the project.

Step 3: The call appears in Gestión de ayudas with Planning stage

The project appears in the first column of the Gestión de ayudas kanban. The column is called Planning and is the canonical entry stage for any newly received call.

From here, the formulation workflow unfolds in Gestión de ayudas: team assignment, narrative drafting, detailed budget, administrative templates.

Step 4: Verify the back-link to Radar

The project created stores a reference to the source call so you can consult it at any time.

1. Open the project from Gestión de ayudas.
2. In the record, locate the Source Radar call field.
3. You will see a link to the original Radar record. Click to open it in a new tab.

The field is internally named radar_convocatoria_id and connects the project.project to the source radar.convocatoria. This means that any subsequent change to the source call (for example: a deadline extension published in BDNS) is visible from the project.

What happens next in Gestión de ayudas

Once in Planning stage, the project follows the formulation cycle managed by the Gestión de ayudas module. [VERIFY: nombres canon de los stages posteriores a Planning pendientes de cierre con el mantenedor del módulo Gestión de ayudas.] The full cycle (formulation, submission, execution, reporting, closure) is outside the scope of Radar and is documented in Gestión de ayudas.

Retrieving the Radar source from Gestión de ayudas

If you need to go back to the Radar call while working on the project:

1. Open the project in Gestión de ayudas.
2. Click the Source Radar call field or the View in Radar button.
3. The original Radar record opens with its full context: calculated fit score, regulatory bases, raw BDNS data.

This is useful when a team member asks why this call was chosen, or when a specific piece of data needs to be checked during formulation.

Troubleshooting

• The “Send to Gestión de ayudas” button does not appear. Your user does not have permissions for the Gestión de ayudas module, or the module is not installed on your instance. Contact your administrator.
• The project is created but the “Source Radar call” field does not appear. Your version of Gestión de ayudas predates the Radar integration. Ask your administrator to update the module to the version that includes the bidirectional link.
• The back-link points to a call that no longer exists. The source call was accidentally deleted. It is not recoverable from the interface; keep the project information.

Next steps

• Use Radar as an operator to review the day-to-day process before the handover.
• Gestión de ayudas to understand the full cycle from Planning onwards.
• Understand what Radar is if you need context on the source module.