Spanish tender documents: PCAP and PPT

The PCAP (pliego de cláusulas administrativas particulares, the administrative clauses document) governs the legal and financial relationship between the parties. Its typical content includes:

Two clauses deserve priority reading. The award criteria clause, because it determines the entire bidding strategy (analysed in detail in the article on award criteria and their weighting). And the penalties and special execution conditions clause, because that is where the financial risk of the construction phase hides: delay penalties above the default rule, penalised interim milestones, social or environmental obligations whose breach is sanctioned.

The PPT (pliego de prescripciones técnicas, the technical specifications document) defines the work itself: technical characteristics, material quality standards, reference norms, and measurement and payment conditions where the contract particularises them. In works contracts it coexists with the approved design, which contains the report, drawings, budget and quantities; the PPT usually refers to it and completes it.

One rule protects bidders: technical specifications may not mention specific brands, patents or origins except with exceptional justification, and in that case must accept equivalents ("or equivalent"). If a PPT de facto requires a single product without justifying it, it can be challenged.

Contradiction between PCAP and PPT is more frequent than it should be: a different deadline in each document, a standing requirement appearing only in the technical part, a scoring criterion slipped into the specifications. The general rule of procurement case law is clear: the PCAP prevails over the PPT in everything concerning the legal regime of the tender, and the PPT cannot regulate matters reserved to the administrative document, such as award criteria. A scoring criterion hidden in the PPT is void.

For bidders, the practical consequence is twofold. Faced with a contradiction detected before bidding, the right move is to request clarification through the platform within the query period: the published answer binds everyone. Faced with a contradiction discovered afterwards, the prevalence of the PCAP is the core argument of any defence.

Tender documents can be challenged, but with a decisive time limit: a company that submits a bid without challenging the documents accepts them, and cannot question them later against the award (save for radical nullity defects). If a standing clause unjustifiably excludes the company, or a price formula neutralises competition, the moment to react is during the submission period, through the special review where the contract falls within its scope. The mechanics are developed in the article on the special procurement review.

With tenders allowing 20 or 26 calendar days, reading the documents has to be efficient. A proven method, in four passes:

First pass, quick disqualification (10 minutes): required standing or classification, guarantees, execution period, base budget. If the company does not meet the eligibility bar or the contract does not fit, the analysis ends here.

Second pass, the financial equation (30 minutes): scoring criteria and formulas, abnormality parameters, price revision, penalties. This produces the first discount hypothesis.

Third pass, technical risk (with the design at hand): quantities and quality standards in the PPT checked against the company's own cost study, special execution conditions, interim milestones.

Fourth pass, the formal layer: bid form template, envelope structure, required documentation, means of proof. Formal defects are the most avoidable cause of exclusion of all.

A contractor studying a sports hall refurbishment spots two anomalies. First: the PCAP sets a 12-month execution period, but the PPT mentions 10. Second: the PPT announces that "the contractor's experience in sports facilities will be positively valued", a criterion that does not appear in the PCAP's criteria table.

The correct reaction, within the query period: raise both questions in writing through the platform. The authority's answer (published and binding on all bidders) confirms the PCAP's 12-month period and clarifies that the PPT's mention is not an award criterion, because criteria can only be set in the administrative document.

The value of the move is twofold. The company bids on certain data (its works programme uses the real 12 months, not the erroneous 10), and the published clarification neutralises the risk of the committee de facto scoring an unlawful criterion. Had the answer been unsatisfactory (for instance, confirming the hidden criterion), the company would still have had the option of challenging the documents before the deadline expired, the only moment when that challenge is fully effective.

Modern PCAPs are structured in two pieces: a body of general clauses (often the authority's standard template, identical from tender to tender) and a cover sheet or characteristics table (carátula) that particularises each contract: budget, duration, standing, criteria, guarantees, penalties. The operational data almost always sits in the cover sheet; the body provides the regime. Reading the full cover sheet first, then only the body clauses it refers to, is the efficient way to process documents from recurring authorities.

The annexes deserve the same discipline: the financial bid form (which must be reproduced without alterations, because modifying it is a classic ground of exclusion), the declaration templates, the budget breakdown and, at times, special execution conditions developed outside the body. A set of documents has not been read until its annexes have: more than one staffing requirement (a site manager with minimum qualifications and experience, specific machinery) lives only in an annex and is discovered, badly, at the documentation request stage.