Construction · service #5 · class B

AI CTE/LOE design-compliance checker for construction projects in Spain

Between the college visado and the municipal report, nobody checks a project's technical compliance with the codes. The system answers a question about a design solution with a quote from the norm itself — DB, clause, edition, date — and builds a discrepancy report before the técnico takes over. The opinion and the signature are always his.

1,500+ pages — the CTE corpus · Parte I + 6 DBs with commentary [estimate from codigotecnico.org PDFs]
12 mo average permit wait · against the legal three — ASPRIMA/EY [I]; 2025: 6–24 months
DB · clause every answer with a quote · the norm's edition and date, always stated
verbatim a quote, not a paraphrase · Citations: the pointer leads to a real fragment of the document

Where projects get stuck, and why

01 · Problem
codigotecnico.org, 2026; volume — [estimate]
1,500+

pages across six PDFs

Parte I, six Documentos Básicos, ministry commentary; DB-HE alone has six editions. Finding the clause in force by hand takes hours — and isn't always the right one.

RD 1000/2010, art. 2
visado

doesn't check the CTE

The college certifies the completeness of the paperwork and the author's credentials — technical compliance with the codes is outside the visado. Until the municipal report, nobody looks at the project against the CTE.

ASPRIMA/EY, 2020 [I]; ASPRIMA, 2025
reset

of the clock after a subsanación

Permits already take 12–24 months. Every requerimiento de subsanación means reworking the project and waiting again.

A code error surfaces at the most expensive point — in the requerimiento, when the project is filed, the fee is paid and the clock starts over.

Compliance checking is a management process

02 · The process we close
design solution (memoria · drawings · details) selection of applicable DBs and clauses check with a quote (DB · clause · edition) discrepancy report and «review» flags opinion of the técnico / dirección facultativa
CLASS

Class B · management. The output of this process is a decision — file or rework — so the effect is measured in avoided subsanaciones and the técnico's search time. The time maths is deceptive: half an hour of searching is small change; an extra month on the permit is not.

Today — by hand

A code question means opening six PDFs, recalling which edition is in force, leafing through the commentary and finding the clause half an hour later. Or not finding it and asking a colleague. Borderline solutions go into the project unchecked — and come back as a requerimiento.

With the system

The question is asked as is — «does this solution pass DB-SI?» — and the answer arrives with a quote from the edition in force and a clause reference. Across the whole project, a discrepancy report: what to bring to the técnico before filing.

Input → AI → output. And where the person is

03 · How it works

An example: the architect narrows the escape stair and asks what minimum width his occupancy allows. The system finds the relevant DB-SI table and quotes it with its edition and date — so the técnico checks one reference, not fifteen hundred pages.

Input

Source material

  • The design solution: memoria, drawings, construction details, estado de mediciones — as PDFs
  • The code corpus: official CTE texts (Parte I + DBs) and the LOE from codigotecnico.org and the BOE, consolidated editions with dates
  • Your work profile: which DBs are critical (SI, SUA, HE…); municipal ordinances — on request, «to confirm»
AI

What the AI does

  • Finds the applicable clauses: search over the corpus with caching — frequent queries get much cheaper
  • Answers only with a quote: the fragment is extracted from the norm's own text (Citations) — DB, clause, edition, date
  • Builds the screening report: likely conflicts and borderline items — flagged «review»
Output

What you get

  • The answer to the question — with the quote and the norm's edition
  • The project screening report: a list of clauses for the técnico's attention
  • A change trail: when the CTE updates, the corpus updates and you see which clauses moved
Human

What the person does

  • The técnico / dirección facultativa reads the quote and issues the opinion — the signature and the liability are his (LOE)
  • Municipal criteria and their reading are confirmed by your técnico locally
  • The graphic part — drawings and details — is reviewed by a person: the text is quoted, not the drawing
RULE 01

No answer goes out without a reference. Every quote carries the DB, clause, edition and date — it can be checked in a minute.

RULE 02

Quotes are extracted from the supplied documents programmatically: the pointer always leads to a real fragment, no reciting the norm «from memory».

RULE 03

Code retrieval improves relevance and traceability but does not guarantee compliance (2025–2026 studies) — which is why this is a screening before the técnico, not a visado and not an opinion.

RULE 04

Scans without a text layer go through OCR or are flagged «not checked» — no silently skipped pages.

What is included — and what is not

04 · What is included
Included
  • The corpus of official texts: CTE Parte I + DB-SE/SI/SUA/HS/HE/HR and the LOE, consolidated editions with dates
  • Setup for your work profile: the critical DBs and chapters
  • Answers with a quote (DB · clause · edition) — in Telegram or a web interface
  • A project screening report (PDF of the memoria and details)
  • Corpus updates as the CTE changes — the new DB-HSA and a DB-SI/SUA revision are coming (draft RD, 11.2025) — with a note on what changed
  • A «does not replace the técnico or the visado» notice in every answer
  • A guide + recorded walkthrough + short consultation
Not included
  • A compliance opinion or legal guarantee — the técnico / dirección facultativa only
  • The visado and dealings with the college or the town hall — not our terrain
  • Drawing and graphics review — the norm's text is quoted; details are read by a person
  • Calculations (structural, energy HULC) — those are the técnico's calculation tools
  • Municipal ordinances in the base delivery — added on request; every town hall has its own criteria («to confirm»)
Integrations & data
codigotecnico.org · BOE — official PDF corpusTelegram — question — answer · nativeWeb interface — A medida planYour project archive — custom · to confirmMunicipal ordinances — on request · to confirm

No machine-readable open corpus of the CTE exists — the official distribution is PDF only (codigotecnico.org, BOE). Turning those PDFs into a structured base with pinned editions and every reference verified is the bulk of the setup. That is why this service costs more than the bots.

Five steps — launch in 2–3 weeks

05 · Implementation
01

Audit

1–2 days · Your work profile: which DBs are critical, typical questions, who will use it.

02

Setup

1.5–2 weeks · Collecting and structuring the BOE/CTE corpus, pinning editions, search + quotes + cache.

03

Test

3–5 days · Real questions from your técnico; every reference checked down to zero false ones.

04

Launch

~2–3 weeks from start · Training on how to phrase queries; guide + recorded walkthrough.

05

Support

by subscription · Corpus updates as the CTE changes, profile tuning, SLA-backed support.

SLA: System answers — seconds; litcore support — reply ≤ 1 business day · If it does not fit the window, the corpus is too wide: we cut the scope, not the quality.

The economics, counted conservatively

06 · Economic effect

An ROI canvas for a company with four projects underway. We count only the técnico's code-search time; avoided subsanaciones stay in reserve — though that is where the real money is.

ParameterValueSource / assumption
Process and classcompliance screening of design solutions — class Blitcore framework, block 2 · lever: risk/errors + time
Volume4 projects underway, ~10 code questions per project per month[estimate] — refined during the audit
Search «before»~30 min per question: PDFs, editions, commentary[estimate] — measured during the audit
Search «after»minutes: an answer with the quote and edition[estimate] — fixed in the pilot
Time lever40 questions × 0.5 h × €40/h ≈ €800/month[estimate]; the técnico's rate — your real one
Avoided subsanacionesweeks and months of permit time — reservepermits run 12–24 months (ASPRIMA [I]); not monetised
CostsPro from €2,490 + €149/mo«from» price — approved by the owner
PAYBACK

≈ 5 months. Pro at €2,490 with 40 questions a month and a €40/h técnico rate, on a 40/70/100% adoption curve over 3 months [estimate] — inside half a year. A single avoided requerimiento saves months of permit time and pays the setup back on its own, but that is reserve and stays out of the maths.

Adoption: code questions go into the system instead of being shelved as «I'll ask later»Time: minutes instead of half an hour per code questionQuality: discrepancies caught before filing; every reference verifiable in a minuteConvenience: the técnico gets specific references, not a «look through the whole project»

Not financial advice: the calculation is a proposal built on market reference points; final figures are fixed after the audit and a pilot on your projects.

Want this calculated on your numbers? Request a proposal →

Price — from €2,490

07 · Price

Model: one-off setup + a subscription for the corpus and its updates. Pro — the CTE/LOE base for your work profile; A medida — an extended DB base, integrations, multi-client. The final price is fixed after the profile audit.

A medida
from 4,900 €

+ €290/mo — extended DB corpus

  • extended Documentos Básicos corpus
  • integration
  • multi-client
Request a proposal →

Indicative "from" prices, VAT (IVA) not included. Model: one-off setup + support subscription. The final price is approved by the owner after the audit.

THIS SERVICE IS PART OF A SYSTEM

The CTE/LOE check is module #5 of the management loop (service #15, project management): it works in the permanent risk layer — regulatory doubts are screened before they reach the técnico. View the management loop → View the bundles →

A screening, not an opinion — stated plainly

08 · Risks & control
Professional boundary

The tool issues no opinions and does not replace the visado: the signature and the liability rest with the arquitecto técnico / dirección facultativa (LOE). Code retrieval improves relevance, but compliance is confirmed by a person — and every answer says so.

Editions and dates

The CTE is alive: RD 732/2019, RD 450/2022, and the DB-HSA plus a DB-SI/SUA revision are coming (draft RD, 11.2025). Every quote carries an edition and a date; when the corpus updates, we flag which clauses changed.

Project data

Memorias and drawings are the designer's intellectual property: only what's needed is transferred, a DPA before upload, EU/US transfer disclosed (DPF + SCC). The code corpus is public BOE text.

AI Act, art. 50 and limits

The use of AI is disclosed in the interface. Municipal criteria — «to confirm» with your técnico locally; graphics — a person only.

AI-assisted — human-supervised · AI Act art. 50

09 · Custom

Need a corpus wider than the CTE?

RITE, REBT, regional regulations, municipal ordinances, your company's internal standards? Describe your work profile — we'll build the corpus around it and calculate the payback.

Other solutions in this sector

#1 · #4 · #3
#1

AI estimate generator (presupuestos)

A by-chapter estimate with correct VAT and PEM/PEC in minutes — in your own Excel template.

from €690 · Details & price →
#4

Photo-based site control

The foreman sends photos — AI sorts them by phase, keeps a timeline, and flags obvious visible issues.

from €590 · Details & price →
#3

AI schedule (cronograma) and project control

From scope to a phased schedule with deadlines, plus a weekly “done / at risk” summary.

from €690 · Details & price →

We'll demo it on your data — 15 minutes, no obligation.

Free demo · A person validates the result · ES / EN / RU · GDPR