How to Publish on the Spanish Public Procurement Platform (PLACSP)

1. What PLACSP is and why it is mandatory

The Spanish Public Procurement Platform (PLACSP) is the official portal run by the Directorate-General for State Heritage, on which the contracting activity of every entity in the Spanish public sector is published. Since LCSP 9/2017 came into force, every tender must be published on this channel, regardless of amount or procedure, with very narrow exceptions for reserved contracts.

For local councils, PLACSP replaces —or aggregates— the traditional "contracting profile" previously hosted on the municipal website. Today, the contracting profile of any local entity must be hosted on or aggregated with PLACSP to be legally valid.

This has an important practical consequence: if publication is not carried out correctly on the platform, the notice has no legal effect, deadlines do not start running, and the tender can be appealed for lack of publicity.

2. Legal framework: LCSP Third Additional Provision

The legal basis is the Third Additional Provision of Law 9/2017 on Public Sector Contracts, which establishes the mandatory nature of PLACSP. It is complemented by article 63 LCSP (contracting profile), article 135 LCSP (tender notice) and article 347 LCSP (Public Procurement Platform itself).

At regulatory level, ministerial orders from the Treasury govern the technical operation of the platform and the exchange formats with DOUE. All these rules are published and kept up to date on PLACSP itself, in the "Regulations" section.

3. Organisation registration and user profiles

Before publishing anything, the organisation must be registered. For local councils, registration is requested by the legal representative (mayor or delegated person) through the entity registration form available in the "Organisation registration request" section of PLACSP. The request is electronically signed with a recognised certificate and processed via the electronic register.

Once the entity is registered, user profiles are defined: body administrator, file manager, publisher and viewer. In small councils it is common for the secretary-interventor to hold several roles, but the recommended approach is to separate the drafter (manager) from the person authorising publication (administrator or head), as an internal control.

4. Notice types: prior, tender, award, formalisation

PLACSP distinguishes between several notice types, each with its own workflow:

• Prior information notice (art. 134 LCSP): voluntary, announces planned contracts for the next 12 months. Useful to shorten minimum tender periods.
• Tender notice (art. 135 LCSP): formally opens the procedure. From publication, submission deadlines start running.
• Award notice (art. 151 LCSP): publication of the award decision, within 15 days of the decision.
• Formalisation notice (art. 154 LCSP): closes the cycle, published after contract signature.

Omitting any of these notices —especially the formalisation one— is one of the most frequent defects detected by General Intervention audits and the Court of Auditors.

5. Uploading the file: specifications, annexes and tenderer communication

The tender notice must include the complete documentary set: Administrative Clauses (PCAP), Technical Specification (PPT), Justificatory Report and the necessary annexes. PLACSP accepts PDF and ODF/OOXML formats, with a maximum file size indicated on the platform at upload time.

Communication with tenderers during the procedure also flows through the platform: questions during the consultation period, clarification requests, tender committee notifications, award notifications. Email communication outside PLACSP has no legal effect.

6. DOUE integration for EU-regulated contracts

Contracts subject to EU regulation (SARA) —those exceeding the Community thresholds set by the European Commission and updated periodically by ministerial order— must also be published in the Official Journal of the European Union (DOUE) using the standardised eForms.

PLACSP has automatic integration with DOUE: when the officer publishes a tender notice and ticks the "SARA contract" box, the platform generates the eForms submission to DOUE and manages synchronisation. There is no need to publish manually on both channels.

7. ROLECE and tenderer verification

The Official Register of Tenderers and Classified Companies of the Public Sector (ROLECE) centralises information on firms eligible to contract with the public sector: legal personality, representation, economic and technical solvency, classification (in works and services where applicable) and declaration of not being subject to any contracting prohibition.

From PLACSP, the officer can directly consult the ROLECE record of any tenderer who has submitted an offer. This replaces much of the supporting documentation previously required in the administrative envelope. For SARA contracts, registration is mandatory for tenderers; for below-threshold contracts it is optional but highly recommended.

Before formalising the award, always: verify that the awardee remains active on ROLECE, that its data has not expired, and that it does not appear on the list of companies barred from contracting.

8. Common errors that invalidate publication

The defects that most often cause rejections and incidents on PLACSP are technical, not regulatory:

• PDFs password-protected or signed with expired certificates
• Incorrect CPV or one incompatible with the declared contract type
• Tender budget in the form that differs from the PCAP uploaded
• Contract duration in the form that differs from the PCAP
• Lots declared in the notice but not reflected in the envelope structure
• Submission deadline below the legal minimum for the procedure type

9. Deadlines: counting from publication

The submission deadline runs from the day following effective publication on PLACSP (or DOUE where applicable, for SARA contracts, taking the later date). Legal minimum deadlines vary by procedure: 15 calendar days for simplified open procedure, 35 days for ordinary open procedure, with reductions available if there was a prior notice or if electronic submission is accepted.

Deadlines are counted in calendar days, save for specific exceptions. The cut-off time is set in the notice and must be observed strictly; PLACSP prevents submissions after the stated time.

10. Best practices to avoid technical incidents

Most of the trouble experienced on PLACSP is not regulatory but operational. Some practices that work:

• Do not publish on Friday afternoons or on the eve of a bank holiday: if an incident occurs there is no immediate support.
• Keep at least two users with active publication rights.
• Renew digital certificates at least 30 days before expiry.
• Save a local copy of the full file before uploading.
• Take a screenshot of the publication receipt.
• Keep a specification template reviewed annually, aligned with the PLACSP form fields.

To go deeper into the frequent specification errors that later surface on PLACSP, see the guide on common procurement specification errors. To understand when AI can automate consistency between PCAP, PPT and the platform form, see LicitadIA features or request a demo.

Frequently asked questions