Digitalisation of Public Procurement: A Guide for Local Councils

1. The current state: paper, PDF and emails in small councils

In many councils under 20,000 inhabitants the daily reality of procurement is that the officer downloads a Word template from a shared folder, manually adapts it to the new file, converts it to PDF, signs it with a certificate, uploads it to PLACSP and emails the auditor. If the contractor has questions, they phone. If there is an audit, things get printed.

This hybrid model formally meets the electronic tender obligation but leaves out a large share of the file: the justificatory report, internal reports, auditor observations, queries to municipal services, partial awards and monitoring after signing. All of that lives in emails, shared folders and drawers.

The consequence is familiar to any council secretary: when an audit or objection arrives, rebuilding the complete file takes hours or days, and part of the trail is missing. Digitalising procurement is, above all else, making that file exist in a single traceable place.

2. The regulation that mandates digitalisation

The regulatory basis for mandatory digitalisation rests on three laws. Law 39/2015 regulates common administrative procedure and imposes the electronic file as the ordinary processing mode. Law 40/2015 sets the electronic operation of the public sector, interoperability and electronic seats. LCSP 9/2017 requires fully electronic tendering for all procedures except limited cases (article 347).

On top of this, the National Interoperability Framework (RD 4/2010) and the National Security Framework (RD 311/2022) prescribe how systems must communicate and which security levels must apply to those handling administrative information.

3. PLACSP: what it digitalises and what it does not

The Public Sector Procurement Platform (PLACSP), managed by the Ministry of Finance, is free for local entities and covers the public part of the process well: notice publication, electronic bid submission, envelope opening, award publication and formalised contract publication. Its use is mandatory for tender publicity.

What PLACSP does not do: it does not draft the specification, it does not generate the report, it does not manage internal audit, it does not store head of service observations, it does not integrate technical reports, it does not track execution and it does not control contract-linked invoicing.

It is a publicity and tender layer, not a file management platform. Saying "we are digitalised because we use PLACSP" confuses one link with the whole chain.

4. Integrated platforms: Plyca, Vortal, Gestiona, Pixelware

To cover what PLACSP does not, the Spanish market offers several integrated procurement file management platforms. They are not interchangeable; each has a natural customer profile.

Plyca: long-standing Nexus IT product, deployed in many local entities and several autonomous communities. Covers the whole cycle from report to contract signing, with direct PLACSP integration.

Vortal: platform of Portuguese origin with a significant footprint in the Spanish central administration and large councils. Its strength is multi-organisation management and the tenderer side.

Gestiona (espublico): procurement module within the e-administration suite most widely used in small and medium councils, with native integration with the rest of the entity's administrative file.

Pixelware: platform with strong PLACSP and signature system integration, used by several ministries and autonomous communities. Also available for local entities.

5. The AI layer: what it solves that traditional platforms do not

The platforms above digitalise the flow: they make the file travel between the different actors without paper and without emails. But they do not help the officer with the most costly part of the job, which is drafting the specification. An integrated platform gives you an in-browser Word editor; an AI assistant generates the draft from the council's own documentary history.

The AI layer, typically built on a RAG system, is deployed on top of the existing management platform. It does not replace it: it adds a function the platform does not have today. The officer drafts faster and with more consistency, and the system can validate against current regulation before publication.

6. Roadmap for a council of 5,000 to 50,000 inhabitants

Not every council starts from the same point. A realistic roadmap rests on three sequential, not parallel, phases. Skipping the order produces frustration and abandoned projects.

Phase 1 — Base electronic file. If the council still processes on paper, the first step is to deploy an e-administration platform (Gestiona or equivalent) with its procurement module. In this phase the objective is that a single traceable file exists, not that it is efficient.

Phase 2 — PLACSP integration and electronic audit. Once the internal platform is consolidated, the bidirectional integration with PLACSP is configured and the audit and electronic signature circuit is digitalised between auditor and secretary.

Phase 3 — AI layer. When the electronic file is a working reality and the documentary history of recent years is indexable, the AI assistant for drafting and validation is added. Starting here without the two previous phases resolved gives poor results.

7. Real cost: budget, training and impact on staff

The cost of digitalisation is not just the software licence. Three line items are usually underestimated in the project's own procurement specification: initial configuration consulting, documentary history migration and real end-user training.

Training is critical and is often the first thing cut. A secretary, two officers and the auditor need between 15 and 30 hours of hands-on training spread over several weeks, with support through the first real files. Without that support, the platform becomes a PDF repository and people go back to working locally.

The impact on staff is positive but delayed. In the first three to six months the processing pace drops because the system has to be learnt. From the second half onwards, productivity exceeds the previous model and, above all, audit traceability improves.

8. Funding: MRR funds and grants for local digitalisation

Since 2021 the Recovery and Resilience Mechanism (MRR), within NextGenerationEU, has been the main funding source for local digitalisation in Spain. Calls are channelled through the Ministry of Territorial Policy, the State Secretariat for Digitalisation and the provincial councils, which often act as a window for the councils in their demarcation.

Eligible projects include e-administration platforms, PLACSP integrations, historical archive digitalisation and, in more recent calls, artificial intelligence solutions applied to administrative management. Co-financing percentages and per-project caps change each year, so it is essential to check the active call before budgeting.

9. Common mistakes in municipal digitalisation projects

After years of seeing digitalisation projects in local entities, the failure patterns repeat. It is worth knowing them before drafting the specification.

Contracting software without an internal governance team. A digitalisation project without a functional lead at home turns into an endless incident list with the vendor. You need a person (secretary, officer, auditor) with protected time dedicated to the project.

Starting with the flashiest part. Some councils have tried to deploy AI without a base electronic file resolved. The result is an assistant without a history to learn from and without integration into real workflow.

Insufficient or concentrated training. Two training days at the start of the project are not enough. Training must be spread over time and accompany the first real files, with accessible support when questions arise.

Ignoring the historical archive. If the archive is not migrated or indexed, the system starts empty and takes years to accumulate critical mass. In procurement, where the value of templates lies in reuse, this is especially critical.

10. How to measure success (real KPIs)

A digitalisation project without metrics ends up evaluated by the team's subjective feeling, which tends to be negative in the first months because of the learning cost. To avoid losing the project in that critical phase, clear indicators should be set from the outset.

The AI layer fits in once the previous phases are consolidated. You can see how LicitadIA sits alongside an existing management platform in the solution overview and in the end-to-end workflow description. If you are weighing the AI addition to a wider digitalisation project in your council or provincial council, a short call to review your specific starting point is the best next step. You can request a free demo or an exploratory call.

Frequently asked questions