Spain's procurement platform and electronic tendering

The Plataforma de Contratación del Sector Público (PLACSP, Spain's public procurement platform) hosts the contracting profiles of the state public sector and, through aggregation or direct hosting, those of most regions and local authorities. Some regions maintain their own platforms (Catalonia, the Basque Country and Andalusia, among others), whose notices are aggregated into the state one. The practical consequence: the PLACSP is the central search point, but a bidder working in territories with their own platform must verify where the bid is to be submitted, because publication may be aggregated while submission is required through the regional tool.

Each tender publishes on its profile the notice, the complete documents, the design in works contracts, the answers to queries, the committee minutes, the evaluation reports and the reasoned award. Everything is freely accessible without registration.

With 20 or 26 calendar day deadlines, spotting a tender on its publication day is worth money. The PLACSP offers subscriptions by criteria (CPV codes, geographic scope, contracting authority, value) that send daily email alerts. An effective setup for a contractor combines:

A useful complement is subscribing to the specific contracting authorities the company already works with: town councils, provincial councils, consortia. Their profiles also announce preliminary market consultations and annual procurement plans, information that anticipates tenders months in advance.

Bids are submitted through the PLACSP's bid preparation and submission tool (or the corresponding regional tool). The process downloads a configurator with the envelope structure defined by the documents, the bidder attaches files to each envelope, signs electronically and submits. The system generates a receipt with a timestamp and an electronic fingerprint of each document.

The technical requirements are what fail under pressure: a valid electronic certificate for the company representative, an up-to-date Java or desktop application, per-file size limits respected, and enough time for the upload (a works bid with a technical submission, annexes and drawings can weigh hundreds of megabytes). The golden rule is not to cut it fine: submit the day before the deadline, not in the final hour.

The case law of the review tribunals sketches a stable catalogue of submission errors:

Submitting late due to a technical incident. The deadline expires at the exact stated time. Platform incidents can justify admission if evidenced (screenshots with the time, incident code, immediate communication to the authority), but incidents on the bidder's own equipment do not. Documenting any problem in real time is the only defence.

Placing documents in the wrong envelope. Including financial data in the technical envelope breaks the secrecy of proposals and leads to exclusion without any possibility of cure. A cross-check of envelopes by a second person before signing is a cheap control.

Invalid signature or unregistered proxy. The signature must correspond to a representative with a valid power of attorney, ideally registered in the ROLECE. An expired certificate discovered on the last day has no fix.

Confusing the submission platform. Submitting on the PLACSP when the documents require the regional tool (or vice versa) amounts to not submitting at all.

Notifications (cure requests, requirements, award) arrive through electronic appearance, with deadlines running from the moment they are made available. Checking the electronic mailbox daily during the tender is part of the job: a cure request unanswered within three working days, or the article 150 documentation requirement unanswered within ten, ends with the best bid excluded.

A contractor starts submitting its bid at 13:20 for a deadline expiring at 14:00. On submission, the tool returns a server communication error. The team applies the incident protocol it had written down:

First, immediate screenshots of the error with the system clock visible and of the platform's status. Second, a check of the PLACSP's own incident notices (when the incident is general, the platform publishes it and an extension is usually granted). Third, an immediate email to the contracting authority describing the incident, attaching the screenshots and proof that the envelopes were prepared and signed before the deadline. Fourth, continuous retries until submission succeeds, at 14:22.

The committee admitted the bid: the incident was evidenced as outside the bidder's control, reported in real time, and submission was completed as soon as possible. The same case without screenshots or email would have ended in exclusion, because the burden of proving the incident lies with whoever alleges it. The operational moral does not change: the protocol saved the bid, but submitting the day before would have saved it better.

A company's first electronic bid should not coincide with its first real tender. The infrastructure is prepared cold, weeks in advance:

Electronic certificates. A valid legal-representative certificate, installed on more than one machine, with its expiry date noted in the company calendar two months ahead. A second empowered representative with their own certificate removes the single point of failure of holidays and sick leave.

Registrations. A company user on the PLACSP with subscriptions configured; ROLECE registration underway (registration timelines are not immediate and the simplified procedure requires it); accounts on the regional platforms of the company's working territory.

Dress rehearsal. The envelope preparation tool allows practising without a real tender: install it, sign a test document, verify that the machine, the browser and the signature coexist. First contact with the tool on a real deadline day is the classic recipe for an avoidable disaster.

None of this scores in any bid, and all of it decides bids: electronic infrastructure is to the bidder what scaffolding is to the trade, invisible when it works and very expensive when it is missing. Certificates and access are best prepared before the first tender rather than during it.