Cases / Quality & safety
Quality & safety

File the building permit in ETDR and clear the hianypotlas

Decide whether the work needs an engedely, a bejelentes or neither, test the design against the requirements that bind it, assemble the documentation the decree lists, file it through ETDR and answer the hianypotlas inside its deadline.

7 steps12 minDesign / engineering practiceDeveloper / clientProject / construction management firmGeneral contractor

How it works, step by step

7 steps across the platform - what you do at each one, and why it matters.

1

Decide the route before anything is drawn

Route Classifier

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.

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

InScope of the worksSite and its constraintsOutAuthority route decidedReason recorded
2

Test the design against what actually binds it

Validation

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.

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

InDesign at permit stageLocal settlement planOutCompliance reportNon-compliances to resolve
3

Assemble the documentation against the list

Common Data Environment

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.

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

InPermit drawingsDesigner statements and studiesOutComplete documentation setIndex against the decree list
4

Submit through ETDR and keep the identifier

Authority Submissions

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.

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

InComplete documentation setApplicant detailsOutETDR case openedCase identifier on record
5

Answer the hianypotlas as one tracked item

Correspondence

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.

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

InRequest to complete the fileSubmitted documentationOutAnswer filed on the caseDated correspondence thread
6

Track the decision and what it expires against

Deadlines

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.

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

InOpen ETDR caseAnswer filedOutPermit decisionValidity date tracked
7

Hand the permit and its conditions to the site

Documents

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.

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

InPermit decision and conditionsPermitted drawingsOutPermit set filed on the projectConditions passed to the site
Modules

Modules in this playbook

7 / 190 platform modules

The market this case is written for

Hungary

Everything in this case follows how construction work is measured, priced and paid for in this market. The forms, the cost breakdown and the payment rules are the ones used there, not a generic version of them.

Standards it follows

  • Kbt.
  • TSZSZ

You do not have to set any of that up by hand. The first time you open the platform it asks which market you work in. Choose this one and it sets the interface language, loads the matching cost database and records the cost classification, and it adds an example project you can open straight away.

The rule checks for this market come with the platform too. Switch them on once and an estimate that misses something the market expects is flagged while you are still working on it, not after the tender has gone out.

More in Quality & safety

Quality & safety

Toolbox talk and safety check

Brief the crew on the hazards this shift actually carries, capture who was there, then prov…

2 steps8 minOpen