Fallbeispiele / Qualität & Sicherheit
Qualität & Sicherheit

Den Bauantrag im ÉTDR einreichen und die hiánypótlás erledigen

Entscheiden Sie, ob die Arbeiten eine engedély, eine bejelentés oder nichts davon brauchen, prüfen Sie die Planung gegen die Anforderungen, die sie binden, stellen Sie die in der Verordnung aufgezählten Unterlagen zusammen, reichen Sie über das ÉTDR ein und beantworten Sie die hiánypótlás innerhalb ihrer Frist.

7 Schritte12 Min.Planungs- / IngenieurbüroProjektentwickler / BauherrProjekt- / BaumanagementbüroGeneralunternehmer

So funktioniert es, Schritt für Schritt

7 Schritte über die Plattform hinweg - was Sie bei jedem tun und warum es zählt.

1

Decide the route before anything is drawn

Routenklassifikator

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.

Warum: 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.

EingangScope of the worksSite and its constraintsErgebnisAuthority route decidedReason recorded
2

Test the design against what actually binds it

Validierung

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.

Warum: 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.

EingangDesign at permit stageLocal settlement planErgebnisCompliance reportNon-compliances to resolve
3

Assemble the documentation against the list

Gemeinsame Datenumgebung

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.

Warum: 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.

EingangPermit drawingsDesigner statements and studiesErgebnisComplete documentation setIndex against the decree list
4

Submit through ETDR and keep the identifier

Behördeneinreichungen

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.

Warum: 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.

EingangComplete documentation setApplicant detailsErgebnisETDR case openedCase identifier on record
5

Answer the hianypotlas as one tracked item

Korrespondenz

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.

Warum: 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.

EingangRequest to complete the fileSubmitted documentationErgebnisAnswer filed on the caseDated correspondence thread
6

Track the decision and what it expires against

Fristen

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.

Warum: 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.

EingangOpen ETDR caseAnswer filedErgebnisPermit decisionValidity date tracked
7

Hand the permit and its conditions to the site

Dokumente

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.

Warum: 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.

EingangPermit decision and conditionsPermitted drawingsErgebnisPermit set filed on the projectConditions passed to the site
Module

Module in diesem Playbook

7 / 190 Plattform-Modulen

Der Markt, für den dieses Fallbeispiel geschrieben ist

Ungarn

Alles in diesem Fallbeispiel folgt der Art, wie Bauleistungen in diesem Markt aufgemessen, kalkuliert und abgerechnet werden. Die Formulare, die Kostengliederung und die Zahlungsregeln sind die, die dort gelten, und keine allgemeine Fassung davon.

Standards, denen es folgt

  • Kbt.
  • TSZSZ

Das müssen Sie nicht von Hand einrichten. Beim ersten Start fragt die Plattform, in welchem Markt Sie arbeiten. Wählen Sie diesen aus, und sie stellt die Oberflächensprache ein, lädt die passende Kostendatenbank, hinterlegt die Kostengliederung und legt ein Beispielprojekt an, das Sie sofort öffnen können.

Die Prüfregeln für diesen Markt sind ebenfalls dabei. Einmal eingeschaltet, fällt eine Kalkulation, der etwas Marktübliches fehlt, schon während der Arbeit auf und nicht erst nach der Abgabe.

Mehr aus Qualität & Sicherheit