Most permit delays aren't caused by the municipality being slow, they're caused by a document package that was submitted incomplete and has to cycle back for correction.
The sequence, in practical terms
In broad terms, the path runs from zoning status verification (imar durumu) confirming what can legally be built on the parcel, through survey and site plan approval, to the architectural, structural, mechanical, and electrical project sets that together support the yapı ruhsatı (building permit) application, and finally to the iskan (occupancy permit) once construction is complete and inspected.
Each of these has its own submission requirements and its own municipal or institutional reviewer, and they are not fully independent, a change discovered during structural review, for instance, can require a revision to the architectural set that has already been submitted, restarting part of the review clock.
The practical implication for a client's timeline: permit processing time is genuinely municipality-dependent and varies by district and by current review backlog, but the variable a project actually controls is submission quality, not processing speed.
Where most delays actually come from
In our experience, the single largest source of delay is an incomplete or internally inconsistent submission, a structural drawing that doesn't match the latest architectural revision, a missing signature or stamp from a required engineer of record, or a site plan that doesn't reflect an as-built survey correction. Each of these triggers a formal rejection and resubmission cycle, not a quick fix.
The second largest source is a zoning status that was assumed rather than freshly verified. Zoning regulations and parcel-specific conditions can change, and a project designed against outdated zoning information can require rework at the design stage before a permit application even goes in.
Both of these are avoidable with the same discipline: verify zoning status directly and freshly before design starts, and run an internal cross-check between all discipline drawings before submission, rather than assuming each consultant's set is correct in isolation.
What a realistic timeline looks like
Clients often anchor their expectations to the fastest permit story they've heard from a friend's project, which is rarely a useful baseline, parcel history, district-specific requirements, and current municipal workload all vary enough that a project-specific estimate, checked with the relevant municipality early, is worth far more than a general rule of thumb.
What is reliably true across projects: building in the schedule for at least one round of clarification or minor revision requested by the reviewing authority is realistic, not pessimistic. Treating the first submission as final and unchangeable is the assumption that most often blows a client's schedule.
Occupancy permit (iskan) timing deserves its own attention, since it depends on construction actually matching the approved drawings, deviations discovered at final inspection, even minor ones, can delay occupancy well after construction itself is finished. This is one more reason mid-construction changes should go through formal documentation rather than being handled verbally on site.
The document package, treated as one system
Architectural, structural, mechanical, and electrical drawings are reviewed as a coordinated set, not independently, and a mismatch between any two of them is grounds for rejection even if each drawing is individually correct. Coordination review before submission is not a formality, it's the step that determines whether the package is accepted on the first pass.
Keeping a single, current revision log across all consultants, so everyone is working from the same version of every drawing, sounds basic but is the most common point of failure on multi-consultant projects, especially when changes happen quickly during preliminary design and aren't communicated to every discipline at the same time.
This coordination discipline is a large part of what a design office actually does beyond drawing: managing the document package as one coherent system rather than a collection of individually correct pieces is what determines whether a permit application moves smoothly or cycles back.
What a client can do to help their own timeline
Respond to reviewer clarification requests quickly and completely, a request that sits unanswered for two weeks adds two weeks to the schedule regardless of how simple the eventual answer turns out to be, since most review queues are date-stamped by response, not by request.
Avoid requesting design changes once drawings have been submitted for permit unless genuinely necessary, since any change at that point usually means withdrawing and resubmitting rather than a simple amendment, and effectively restarts part of the review.
Ask the design team for a project-specific timeline estimate early, and treat it as a range with a realistic worst case included, not a single date, a client who has budgeted for the realistic range rarely experiences a permit delay as a crisis, because it was already priced into the plan.

