PCAP: How to Draft the Administrative Clauses Specification

1. What the PCAP is and its role in the file

The PCAP (Pliego de Cláusulas Administrativas Particulares, Administrative Clauses Specification) is the document that sets the legal, economic and administrative rules governing a specific public contract from tender to termination. Together with the Technical Specification (PPT) and the Justificatory Report, it forms the core of the procurement file.

Its practical importance is twofold. First, the PCAP binds the contracting body and the awardee once the contract is formalised: any ambiguous clause will be interpreted in litigation in favour of the contractor (contra proferentem principle). Second, it is the document most frequently challenged in administrative appeals: poorly drafted award criteria, unclear modification clauses and disproportionate guarantees appear year after year among the most common grounds for upholding special procurement appeals.

A well-drafted PCAP is not a mere formality: it is a legal insurance policy for the contracting organisation.

2. Difference between PCAP, PCAG and Technical Specification

The three documents are often confused. The PCAG (General Administrative Clauses) is a common specification approved by the Council of Ministers or regional government that regulates generic aspects for a whole contract category (e.g. supplies or services). The PCAP details the conditions of the individual contract.

The Technical Specification (PPT) exclusively describes the technical aspects of the object: what is to be supplied, what features it must have, what methodology will apply. It does not cover legal aspects, award criteria or guarantees: those belong in the PCAP.

3. Regulatory framework: article 122 LCSP and related rules

Article 122 of Law 9/2017 on Public Sector Contracts is the key provision. It states that PCAPs shall contain the agreements and conditions defining the rights and obligations of the contracting parties, together with any other requirements demanded by the LCSP itself and its implementing regulations.

That baseline is supplemented by the General Regulation of the LCAP (Royal Decree 1098/2001) in the parts still in force, RD 817/2009 on classification and procedure, and guidance from the State Advisory Committee on Public Procurement. At European level, Directive 2014/24/EU on public procurement and Directive 2014/23/EU on concessions remain mandatory references.

Finally, most regional governments and many local authorities have approved standard templates for recurring contract categories. Using them as a starting point is advisable, but never as an excuse to skip adapting the PCAP to the specific contract.

4. Section 1: Contract identification and legal regime

The first block of the PCAP must unequivocally identify the contract. It includes: literal object, CPV code, contract type (works, services, supplies, concession), lots where applicable, duration, tender base price broken down with VAT, estimated value, budget allocation, contracting body, contractor's profile and applicable legal regime.

The estimated contract value (article 101 LCSP) deserves special attention: it determines the applicable procedure, publication obligations and the appeal regime. A miscalculation can invalidate the entire tender.

5. Section 2: Procedure, award criteria and solvency

This block defines how the contract will be awarded. It must specify the procedure (open, simplified open, restricted, negotiated without publicity, competitive dialogue), the processing route (ordinary, urgent or emergency) and whether harmonised regulation applies.

The award criteria (article 145 LCSP) must be linked to the object, formulated objectively and with a detailed scoring scale. Criteria assessed via formula (price, improved timelines) must express the exact formula. Criteria subject to value judgement must specify which aspects are valued and how they translate into points, without leaving room for arbitrariness.

Economic and technical solvency (articles 87-95 LCSP) must be proportionate to the object and value of the contract. Requiring annual turnover of three times the contract value, or prior experience in identical contracts of much higher value, are recurring formulations that the Central Administrative Tribunal for Contractual Appeals (TACRC) systematically upholds as improper.

6. Section 3: Guarantees (provisional, definitive, complementary)

The provisional guarantee (article 106 LCSP) is exceptional and must be expressly justified in the file; it is not required by default. The definitive guarantee is mandatory and equals 5% of the final award price, excluding VAT, save for specified exceptions. A complementary guarantee may be required in special cases, not exceeding an additional 5%.

The PCAP must indicate the accepted forms (cash, guarantee, surety insurance, securities), the deadline for constituting it, the consequences of failing to do so and the regime for return at the end of the contract, generally triggered after satisfactory performance and expiry of the warranty period.

7. Section 4: Timelines, extensions and modifications

The execution timeline must be expressed precisely (months, planned start date) and aligned with the PPT and the Report. If an extension is envisaged, the PCAP must state it explicitly: an unagreed extension is null. For service and supply contracts, maximum duration with extensions is generally five years (article 29 LCSP), with exceptions.

Foreseen modifications (article 204 LCSP) must delimit conditions, scope and maximum limits. Non-foreseen modifications (article 205 LCSP) are restricted to specified cases and may not exceed 50% of the initial price. An ambiguous modification clause is a frequent source of disputes during execution.

8. Section 5: Penalties, termination and subcontracting

Penalties for non-compliance (article 192 LCSP) must be itemised in the PCAP: delays, defective performance, breach of commitments made in the bid. Their amount may not exceed 10% of the contract price. Disproportionate or undetermined penalties are appealable.

Termination grounds (articles 211-213 LCSP) combine statutory grounds with any conventional ones the PCAP adds. Subcontracting (article 215 LCSP) must be expressly regulated: maximum subcontractable percentage, non-subcontractable parts, obligations of the main contractor towards the subcontractor, and direct payment regime where applicable.

9. Standard PCAP templates: when to use and when to draft bespoke

Article 121.3 LCSP allows the approval of standard templates for contracts with common features. Many provincial councils, large municipalities and regional governments have approved models for recurring contracts (cleaning, security, maintenance, routine supplies). The advantage: time savings, legal consistency and reduced risk of formal errors.

That said, a template must never be applied mechanically. Each specific file requires adjusting: precise object, amount and breakdown, real timelines, contract-specific award criteria and foreseen modifications. Using a template without adaptation is one of the causes behind the "copying specifications without updating references" error covered in our companion guide on common errors in public procurement specifications.

10. Errors that generate the most appeals

The grounds for successful appeal most commonly linked to the PCAP, according to TACRC and regional tribunal doctrine, are: subjective award criteria without concrete sub-criteria, solvency disproportionate to the contract object, ambiguous modification clauses, omission of the justification for the provisional guarantee when required, and discrepancies between PCAP and PPT regarding timeline, object or amount.

On top of these substantive grounds come serious formal defects: references to repealed legislation (specifications with references to Law 30/2007 still exist), incorrect budget line, or failure to break down the tender base price by component (article 100 LCSP). All of these are, in practice, preventable with a rigorous cross-review.

11. How AI accelerates PCAP drafting

Drafting a PCAP from scratch typically takes between 6 and 15 hours of technical work depending on contract complexity. Public procurement AI tools reduce that time by 60–80%, but the real value is not only in the speed: it is in integrated regulatory validation.

LicitadIA builds on the organisation's own documentary history, ensuring that the generated PCAP is consistent with previously approved specifications and with the procurement service's consolidated legal criteria. Final legal responsibility still rests with the officer and body that signs, but now with an additional layer of control before publication.

If you want to see how this would apply to your council's standard contracts, the most direct route is to request a free demo.

Frequently asked questions