What it is and where it comes from
The operative definition comes from part I of the CTE (Código Técnico de la Edificación, the Spanish building code) and its design content annex: the proyecto básico is the stage of the work that precisely defines the general characteristics of the works through the adoption and justification of concrete solutions. Its characteristic content comprises the descriptive report, with the agents, the prior information and the description of the building; the planning justification, which demonstrates conformity with the urban plan; the general drawings, location, siting, floor plans, elevations and sections to scale; and an estimated budget by chapters or by area.
What the rules leave out defines the document as much as what they include: no construction detail drawings, no complete development of services, no specifications and no bill of quantities. The básico defines the what; the how belongs to the proyecto de ejecución (detailed design).
What it serves for: the key to permitting
The central legal function of the proyecto básico is to enable the works licence application. With the básico submitted, the municipality has everything needed for the control within its remit, planning conformity, without the developer having yet invested in the complete development of the design. This arrangement has a calendar consequence that well-managed operations exploit systematically: the licence processing and the drafting of the detailed design can advance in parallel, compressing the total timeline by the months the municipal procedure takes.
The counterpart is a coherence rule: the detailed design may not depart from the licensed básico in what the licence controlled. Changes altering planning parameters, areas, heights, coverage, use, require modifying the licence, with its cost in time; the developments and refinements inherent to moving to execution level do not. Drawing that boundary well in each project is craft, and drawing it badly is the typical cause of unplanned licence modifications.
What the básico does not allow
The negative list is short and its consequences serious. With a proyecto básico the works cannot start: the start requires the detailed design and the construction phase documentation. One cannot contract rigorously: without quantities, any price is a bet on an undefined volume. And one should not sell on it without safeguards: the areas and qualities of the básico are still provisional, and differences with what is finally built feed purchaser claims.
The underlying error summarising all three is treating the básico as a cheap design instead of a deliberately incomplete one. Its documentary economy is a virtue for processing quickly, not an invitation to skip the next stage.
The economic definition of the básico
The budget of the proyecto básico is an estimate, and the rules demand no more of it. But the difference between any estimate and a professional estimate is, at this stage, the difference between steering and waiting. Serious practice accompanies the básico with an economic envelope built by ratios on areas and chapters, checked against market references, with a declared range and the assumptions in writing: intended structural system, quality level, site conditions. That envelope is what allows a well-founded decision on whether the project proceeds, adjusts or is rethought before investing in the complete development.
The relationship between this estimate and the complete quantities of the detailed design is one of progressive refinement, not substitution: each stage narrows the previous range, and deviations between stages are management information, not noise. An anomalous jump between the básico's estimate and the detailed design's budget almost always signals an ungoverned scope change.
Básico and ejecución: one document or two deliveries
Two formats coexist in professional practice. The básico as a separate delivery, followed by the detailed design as its development, is the classic format when the calendar rules: it allows processing as soon as possible. The combined basic-and-detailed design in a single delivery is frequent in smaller commissions or without licence urgency, and saves a documentary iteration in exchange for delaying the application until the whole is ready.
The choice is one of calendar and risk strategy: separating accelerates but exposes coherence between deliveries; combining simplifies but chains the licence to the complete document. In externally financed operations, separation has an added advantage: the licence obtained on the básico is a risk-reduction milestone that improves the conditions of financial close.
Risk reading for the developer
| Decision on the básico | Risk if done badly |
|---|---|
| Level of definition submitted | Municipal requirements and longer timeline |
| Coherence with the urban plan | Refusal or licence modifications |
| Associated economic envelope | Detailed design out of budget |
| Boundary with the detailed design | Unplanned licence modification |
| Communicated areas and qualities | Purchaser claims |
The synthesis is one: the proyecto básico is a risk management document disguised as a formality. Every hour invested in its completeness and coherence is recovered multiplied in the processing, and every serious cost estimate attached to it avoids a detailed design condemned to be redone.
Frequent errors
The first is submitting an incomplete básico to gain weeks: the correction requirements return them with interest. The file stops until the correction arrives complete.
The second is licensing an optimistic básico, with areas or parameters at the limit, that the detailed design will not sustain without modifying the licence. Modifying the licence costs more time than applying for it properly.
The third is omitting the economic envelope and discovering the real cost with the detailed design's quantities, when the cheap levers no longer exist. The estimate is checked against the básico rather than the detailed design.
The fourth is neglecting traceability between básico and detailed design: every difference must be explainable, because someone, municipality, financier or purchaser, will end up asking about it. Differences are documented as they arise.
Note: the required content of the proyecto básico is that of the design content annex of part I of the CTE and whatever the applicable regional and municipal regulations specify at each location.