How to organise a project application before you submit it
A well-organised application prevents a missing document, an invalid signature or two figures that disagree. The council’s own list is the one that counts. Documents are sorted by when they go in: with the application, before work starts or at completion. Before signing, the same figure has to read the same in every document.

In this article
The short version
This guide draws on Spain’s building code, the Building Act, Act 39/2015 on administrative procedure and the regulations under Andalusia’s planning act. For the local level it follows a planning permit bylaw approved in September 2025, because its annex sorts each document by stage. Your town will have another list, though the method holds.
Three lists: the nearest one wins
An application answers to three levels of rules at once. Each one adds to the last:
| Level | What it sets | Where |
|---|---|---|
| National | What a project contains, “without prejudice” to what the competent authorities require. Partial projects are integrated as separate documents under the lead designer’s coordination. | Part I, art. 6.1 and Annex I, Building Act, art. 4.2 |
| Regional (Andalusia) | What the application identifies, the technical project, the georeferenced plan and prior authorisations. | LISTA Regulations, art. 299 |
| Local | Any further documents and the standard forms, by bylaw. | LISTA Regulations, art. 299.3, each town’s bylaw |
That gives the first step: download the council’s form and list on the day work on the application begins. If an authority sets a specific form for a procedure, it is mandatory (Act 39/2015, art. 66.6). And bylaws change: the one we follow here dates from late 2025, so a list inherited from an earlier application may already be out of date.
What each document contains is covered in the guides to permit documents and the project report. This one is about how it all fits together.
Organise by stage, not by subject
In Andalusia the basic project is enough to apply for the permit. Work, however, cannot start without the construction project, certified by the professional body where national rules require it (LISTA Regulations, art. 299.1.a). Annex I marks the basic project’s minimum with an asterisk: in the report the parties, prior information, description, performance, foundations and fire safety, plus the general drawings and the approximate estimate.
That bylaw turns this into a table: its article 30 and Annex II.1 split the documents into three stages, each document with its own box.
| Stage | What goes in (a selection for works with a project) |
|---|---|
| Application (“prior to grant”) | Form, proof of fee, location plan, proof of representation if any, land registry extract, basic project with its georeferenced plan, sectoral authorisations required. |
| Effect (“conditional”: before work starts) | Construction project, statement that it matches the basic project, health and safety study, site direction and construction management appointment certificates, statistics form and, where relevant, telecoms project or fire separata. |
| Completion | Self-declaration of occupation or use with the documents in annexes II.9 and II.10. |
A self-declaration changes the split. According to the FAQ on that bylaw, only the form is filed and the listed documents are kept during the works and for at least six years after, available to the planning office on request. With less to hand in, order matters more: it is what gets shown when someone asks. Which works take which route is explained in self-declaration or permit in Andalusia.
A structure that makes sense without opening anything
The rules cited here do not impose file names or a folder order on the applicant. The numbered index in article 70.2 of Act 39/2015 belongs to the file the authority forms when it sends it on. What follows is a working proposal, not a requirement. If your council sets another structure, use that one:
| Folder | What it holds | What to check on closing it |
|---|---|---|
| 00 Index | Numbered list of everything submitted, with version and date. | That each line matches a real file. |
| 01 Application | Form, fee, representation. | That the form is the current one and signed. |
| 02 Property | Land registry extract, location plan, photographs. | The date on the extract. |
| 03 Project | Report, drawings, specifications, quantities and estimate, by stage. | That the report cites the partial projects it integrates (Annex I, point 3). |
| 04 Annexes and studies | Calculations, services, quality control, waste, health and safety. | That their version matches the drawings. |
| 05 Authorisations | Reports and authorisations from other authorities. | That all those required before the permit are there. |
| 06 Professionals | Registration, standing, insurance, appointment certificates. | One for each professional involved. |
Within each folder, a name saying what it is and which version is enough, for example 03-02 Drawings v2.pdf. One detail that is easy to miss: among the minimum contents of technical documents, that bylaw also asks for a planning justification annex and a separate annex of sensitive data (art. 10.3). Pieces like this only turn up if you read the bylaw.
Signature, certification and format
These are the easiest problems to avoid, because they have nothing to do with the design:
- Electronic filing. It is compulsory for those practising a profession that requires registration, for legal entities and for those representing them (Act 39/2015, art. 14.2). If one of them files on paper, they are asked to correct it and the filing date becomes the date of the correction (art. 68.4).
- Certification comes first. The construction project for building work that needs a project under the Building Act must be certified by the professional body before it is submitted: later certification is not possible (RD 1000/2010, arts. 2.a and 6.2). In other cases it is voluntary (LISTA Regulations, art. 300.1).
- Electronic signature, not a scan. In the bylaw we follow, anything not needing certification is filed with the professional’s electronic signature and handwritten or scanned signatures are not accepted. It also needs a statement of registration, standing and insurance or the certificates that replace it (Annex II, formal requirements, point 2).
- What goes with it is certified too. Where certification is compulsory, that bylaw also wants it on the separatas, the health and safety study, the statement of match and the appointment and completion certificates (point 3). And all technical documents go in as PDF (point 4).
Since any later change means signing and possibly certifying again, the signature comes last, once the check below is finished.
What expires and what depends on others
An application can be complete on Monday and stop being so a month later. These pieces are best prepared by counting back from the filing date:
| Item | What to watch | Source |
|---|---|---|
| Land registry extract | Under three months old, in the bylaw we follow. | Annex II.1 |
| Sectoral reports and authorisations from other authorities | They must be in place before the permit. A permit cannot be conditional on obtaining them later. | LISTA Regulations, art. 299.2 |
| Documents already filed with an authority | They need not be filed again: it is enough to state when and with which body. | Act 39/2015, art. 28.3 |
In protected buildings, the heritage authorisation has to be allowed for as well, covered in its own guide. And there is one more reason not to file half an application: under that bylaw, the procedure starts counting when the complete documents reach the register (arts. 9.3 and 31.1).
The last pass: everything says the same
The council’s technical report checks compliance with planning and that all required documents are there (LISTA Regulations, art. 302.1). Before signing, it pays to read the application the same way, one item at a time:
- Developer: the same on the form and in the report’s parties section. If they are not the owner on the registry extract, the relevant authorisation.
- Location: address and cadastral reference identical on the application, report, drawings and extract.
- Works: use, type of work and number of dwellings described the same way on the application, report and drawings.
- Areas: the report’s schedule agrees with the drawings. The usual mistakes are in the guide to the area schedule.
- Estimate: the construction cost is the same in the report, estimate and application. The detailed one includes quality control and health and safety (Annex I, V). More in how to review the BC3.
- Versions: the report and annexes cite the drawings actually being filed.
- Stage: the construction project does not lower the basic project’s performance or alter the uses and conditions of the permit (Part I, art. 6.1.3.b).
- Professionals: names and qualifications identical in the report, the certificates and the signatures.
Where Archelo helps
Archelo helps you group the project’s documents into folders, see what is missing from the application and compare report, drawings and estimate: areas, construction cost and descriptions, with the document and page of each difference. More on AI for architects.
Frequently asked questions
Which list of documents counts for an application?
That of the council where it is filed, with its standard forms. It adds to what the building code and regional rules set and it can change, so it is best downloaded on the day work on the application begins.
Is the basic project enough to apply for a permit in Andalusia?
Yes, though work cannot start without the construction project, certified where national rules require it (LISTA Regulations, art. 299.1.a).
Who has to file electronically?
Those practising a profession that requires registration, legal entities and those representing them (Act 39/2015, art. 14.2). If one of them files on paper, the filing date becomes the date of the correction (art. 68.4).
What should be checked before signing?
That the same item reads the same in every document: developer, location, use, areas, construction cost, drawing versions and the names of the professionals.
















