Casos / Qualidade e segurança
Qualidade e segurança

Submeter o pedido de licença no ÉTDR e responder ao hiánypótlás

Decida se o trabalho precisa de engedély, de bejelentés ou de nenhum dos dois, confronte o projeto com os requisitos que o vinculam, reúna a documentação que o decreto enumera, submeta-a através do ÉTDR e responda ao hiánypótlás dentro do respetivo prazo.

7 etapas12 minGabinete de projeto / engenhariaPromotor / clienteGabinete de gestão de projetos / obrasEmpreiteiro geral

Como funciona, passo a passo

7 passos ao longo da plataforma - o que fazer em cada um e por que importa.

1

Decide the route before anything is drawn

Classificador de Rota

Classify the work against the current procedural decree: an epitesi engedely, an egyszeru bejelentes, or work that needs neither. Record the decision and what it rests on, including anything that overrides the general rule such as protected status, a heritage constraint or a site under a special regime.

Por quê: Government Decree 281/2024 (IX. 30.) replaced the decree everybody in the industry learned this from, and it absorbed the separate notification route for dwellings. A firm applying the version it remembers is not making a small error: work built on the wrong route is unlawful construction, and the fix is retrospective and expensive. Recording the reason also means the next person does not re-decide it from memory.

EntradaScope of the worksSite and its constraintsResultadoAuthority route decidedReason recorded
2

Test the design against what actually binds it

Validação

Check the design against the national requirements base and the local settlement plan on top of it: use, height, built ratio, setbacks, parking, green surface and whatever the local plan adds. Resolve the failures before submission rather than letting the authority find them.

Por quê: The national base changed: Government Decree 280/2024 (IX. 30.), the TEKA, took over from the OTEK from 1 January 2025 and became mandatory that July. A parameter checked against the old base and a parameter checked against nothing look identical in a drawing, and both come back as findings. Doing it here costs a design iteration; doing it after submission costs the iteration plus the procedure.

EntradaDesign at permit stageLocal settlement planResultadoCompliance reportNon-compliances to resolve
3

Assemble the documentation against the list

Ambiente de dados comum

Build the application set in one place with a version and an author on every document, and index it against the decree's own annex rather than against the last application your office made. Include the designer statements, the specialist studies and the consents the case needs.

Por quê: The annex to the procedural decree is a list, and an application is judged complete or incomplete against it mechanically. Indexing against the last successful application is how an office carries a missing document forward for a year: it worked before, so nobody looks, and the authority is the one who eventually notices.

EntradaPermit drawingsDesigner statements and studiesResultadoComplete documentation setIndex against the decree list
4

Submit through ETDR and keep the identifier

Submissões à Autoridade

File the application electronically through ETDR and record the case identifier on the project, together with the date of submission and the documents that actually went in that version.

Por quê: Everything that follows is addressed by that identifier: the requests, the specialist authority opinions, the decision and any later modification. A project that only records that the application went in cannot answer which version of the drawings the permit was granted on, and that is the exact question a building supervision inspection asks on site.

EntradaComplete documentation setApplicant detailsResultadoETDR case openedCase identifier on record
5

Answer the hianypotlas as one tracked item

Correspondência

Log the request as correspondence with its deadline and an owner, answer each point separately so the authority can tick them off, and keep the revised documents versioned against the ones they replace.

Por quê: A request to complete the file arrives at the designer, who is usually on the next project by then, and the deadline runs whether or not anyone has read it. Half of the delay on Hungarian permits is not the authority being slow, it is a two-week gap between a request landing and somebody noticing it, and that gap is entirely inside the applicant's own office.

EntradaRequest to complete the fileSubmitted documentationResultadoAnswer filed on the caseDated correspondence thread
6

Track the decision and what it expires against

Prazos

When the decision comes, record it with the conditions attached to it and set a deadline on the date the permit stops being usable, so an approval that has been sitting in a drawer while funding was arranged does not quietly expire.

Por quê: A permit is not permanent, and the gap between getting one and starting on site is exactly where a development stalls for reasons that have nothing to do with the permit. The date is knowable on the day the decision arrives and unknowable to whoever finds the file two years later, so it is recorded once, here.

EntradaOpen ETDR caseAnswer filedResultadoPermit decisionValidity date tracked
7

Hand the permit and its conditions to the site

Documentos

File the decision, the conditions and the permitted drawings on the project as one set, and pass the conditions to whoever will run the site as items with owners rather than as a PDF attached to an email.

Por quê: The permit is what the naplo is opened against and what the work is checked against, so the site needs it as a live document rather than as an archive. A condition that never reached the foreman is the most ordinary way a permitted building ends up not matching its permit, and it is discovered at the occupancy stage, which is the worst possible moment.

EntradaPermit decision and conditionsPermitted drawingsResultadoPermit set filed on the projectConditions passed to the site
Módulos

Módulos deste playbook

7 / 190 módulos da plataforma

O mercado para o qual este caso foi escrito

Hungria

Tudo neste caso segue a forma como a obra é medida, orçada e paga neste mercado. Os documentos, a decomposição de custos e as regras de pagamento são os que se usam lá, não uma versão genérica.

Normas que ele segue

  • Kbt.
  • TSZSZ

Você não precisa configurar nada disso na mão. Na primeira vez que abre a plataforma, ela pergunta em que mercado você trabalha. Escolha este e ela ajusta o idioma da interface, carrega a base de custos correspondente, registra a classificação de custos e adiciona um projeto de exemplo que você pode abrir na hora.

As verificações deste mercado também vêm com a plataforma. Ative uma vez e um orçamento ao qual falte algo que o mercado espera é sinalizado enquanto você trabalha nele, e não depois que a proposta já saiu.

Mais em Qualidade e segurança