Şantiye-M for Residential 2026: 50+ Unit Developer Guide

Why Is Şantiye-M Different in the Residential Sector?

Compared to other construction sub-segments, residential projects occupy a unique position in Şantiye-M compliance. The first reason is the high number of stakeholders involved: investor, contractor, subcontractors, material suppliers, and most critically — the independent unit owners. A residential developer must maintain information flow not only with the permitting authority but also with every individual buyer.

The second reason is that threshold values are most frequently triggered in residential projects. A large portion of building permits issued nationwide in Turkey are for residential purposes, and most of these projects fall within the Şantiye-M scope. Particularly in metropolitan areas, even a mid-sized apartment project easily exceeds the 5,000 m² total construction area threshold.

Third is the direct link between the occupancy permit (iskan) process and Şantiye-M reports. When you apply for occupancy, the authority requests all Şantiye-M reports covering the project's full lifecycle. A missing or flawed report can extend your occupancy process by months, leading to delays in delivery commitments stated in sales contracts and triggering penalty clause claims.

For residential developers, Şantiye-M is not just a compliance obligation — it is a tool that protects buyer trust and brand reputation. The full process framework is detailed in the Şantiye-M 2026 software compliance guide, while this article focuses specifically on the residential sector.

A fourth distinguishing feature is the continuity pressure created by project volume in the residential sector. Industrial or infrastructure projects are typically multi-year endeavours with large dedicated teams, so the Şantiye-M team can afford to focus on a single project at a time. Residential developers, however, usually run 3-5 projects simultaneously; with each in a different phase and on a different notification calendar, a centralised notification management system becomes essential rather than optional.

Which Residential Projects Fall Within the Scope?

Multiple criteria are evaluated simultaneously to determine whether a residential project falls within the Şantiye-M scope. Rather than a single threshold, several measures are applied based on the project's nature:

Criterion	Threshold	Typical Project Example
Total Construction Area	≥ 5,000 m²	Mid-sized apartment, 40-60 units
Number of Independent Units	≥ 50 units	Residential complex, 4-6 blocks
Building Height	≥ 21.50 m (high-rise)	8+ storey residential
Mixed-Use Ratio	Commercial area > 20%	Residence with retail base
Budget	Specified upper limit	Luxury residence, boutique project

Triggering any one of these criteria is sufficient to bring your project into the scope. Even if the area is below 5,000 m², if the building height exceeds 21.50 m, your Şantiye-M obligation is active. The detailed analysis of all 8 thresholds is available in the construction software selection criteria article.

Another important point concerns projects built in phases. The authority generally applies the principle of "same parcel block, same investor, same permit cluster." Two separate blocks of 30 units each — if on the same parcel under the same developer — are treated as 60 units in total and fall within the scope.

The situation is more complex for mixed-use projects. In buildings with commercial units on lower floors and residential above, if the commercial area exceeds 20% of total construction area, the project is classified as "mixed use" and Şantiye-M notification obligations are separated by use type. Different acceptance protocols, different fire safety reports, and different MEP tests are required for residential and commercial parts. If the developer does not account for this separation from the outset, the file structure becomes disorganised and error risk increases.

Building class definitions in zoning plans can also be threshold triggers. For example, projects classified as "high-specification residential" may fall directly within scope regardless of unit count or area threshold; for this reason, it is critical that the consultant clarifies the classification assessment at the permit stage.

Transition from Building Permit to Şantiye-M Registration

One of the most critical transitions in residential development is opening the Şantiye-M registration after the building permit is issued. These two processes are connected yet entail different obligations. The building permit is an authorisation; Şantiye-M registration is the starting point for all reporting and monitoring obligations during the construction phase.

Under the general regulatory framework, Şantiye-M registration must be completed within 30 days of the building permit's issue date. Within this period:

• Owner (investor) information is registered in the system.
• Contractor details and authorisation certificate numbers are recorded.
• Site manager assignment is made and professional certification is uploaded.
• Building inspection company details are added.
• Project designers (architect, structural, mechanical, electrical) and their chamber registration numbers are entered.
• Approved project drawings are uploaded in PDF format.

Exceeding this deadline triggers administrative fines and — more critically — flags subsequent notifications with a "late start" indicator. The authority is known to weigh this flag heavily when prioritising inspections.

Practical recommendation: while preparing the building permit application file, simultaneously gather the documents required for Şantiye-M registration. If registration can be opened the same day the permit arrives, you comfortably meet the legal window and your team gains full command of the process from the start.

Registration responsibility usually rests with the project manager, but it is advisable to run the process in parallel with the contractor's legal department or external consultancy support. Even a single missing document in the system (for example the site manager's social security registration certificate or one of the project designers' updated chamber dues payment) can cause the registration to be deemed incomplete. For this reason, running the "permit obtained, registration opened" workflow against a checklist is the healthiest approach. The checklist template from the main Şantiye-M software compliance guide adapts well to residential projects.

Typical 12-Month Şantiye-M Calendar for a Residential Developer

For a mid-sized residential project (50-80 units, 8,000-12,000 m² construction area), the Şantiye-M calendar over 12 months can be planned as follows. This is a reference framework; each project must adapt it to its specific conditions.

Month	Phase	Şantiye-M Notifications
Month 1	Excavation	Registration opening, start protocol, excavation disposal report
Month 2-3	Foundation, shoring	Foundation concrete sample reports, rebar inspection protocols
Month 4-6	Structural frame, floor cycles	Per-floor concrete-rebar report, monthly OHS report
Month 7-8	Walls, plaster, MEP rough-in	Shaft inspections, fire damper report
Month 9-10	Finishes, facade	Facade fire test, thermal insulation inspection
Month 11	Landscaping, final tests	Elevator periodic inspection, fire suppression test
Month 12	Occupancy preparation	Completion report, summary of all notifications

Synchronising this calendar with your project management tool is critically important. The WBS structure described in the construction project management guide can be mapped to Şantiye-M notification dates to ensure no critical milestone is missed.

Data Sharing with Independent Unit Owners (KDPR Compliant)

One of the most sensitive areas in residential project Şantiye-M processes is data sharing with independent unit owners. Buyers rightfully expect access to certain information about the construction of their units; however, this sharing is subject to specific rules from both KDPR (Turkish data protection) and trade secret management perspectives.

Key principles when building a KDPR-compliant sharing model:

• Transparency notice: A separate transparency notice must be presented to the buyer at sales contract signing, explaining the purpose and recipients of construction process data.
• Explicit consent: Certain data (e.g. name visibility in common communication panels) requires explicit consent. Anonymous or initials-only sharing is preferred for general announcements.
• Data minimisation: Buyers should only see technical information about their own unit and general information about common areas; technical details of other units are not shared.
• Retention period: Construction process data is retained throughout the contractual warranty period plus the statutory retention period; afterwards it is deleted or anonymised.
• Data controller registry: Developers above a certain turnover threshold are required to maintain VERBIS registration.

In practice, many developers open a buyer-specific portal where the buyer can view construction photos, progress percentages, and projected delivery dates for their unit. AECKraft's CRM module can be used to manage such buyer portal scenarios; however, direct integration of the portal with the Şantiye-M system is not a regulatory requirement.

Another frequently encountered issue in the data sharing process is the conflict between buyer requests and legal boundaries. For example, a buyer may request photos taken during the full concrete pour of their unit; however, if these photos also contain details of other units, direct sharing is not appropriate. In such cases, the most correct approach is to prepare buyer-specific materials (containing only their unit's footage). AECKraft document management's tagging feature can be used to control which document is visible to which unit/buyer.

Special Considerations for Housing Cooperatives

Housing cooperatives differ from classical residential development in several important ways, and the Şantiye-M process must adapt to these differences.

In the cooperative model, the "owner" is a single legal entity (the cooperative), yet funding comes from all members and decisions flow through a board of directors. This creates the following considerations in Şantiye-M notifications:

• Authorisation: The person(s) authorised to file notifications must be designated by board resolution, and this resolution must be uploaded to the system.
• Member information: Notification reports must be shared not only with the board but with all members through the general assembly information mechanism.
• In-house contracting: If the cooperative itself undertakes contracting (self-build), the authorisation certificate classification differs and site manager assignment is more strictly audited.
• Financial transparency: Şantiye-M notification data must be accessible to cooperative auditors; this is mandatory for the annual audit report.

Best practice for cooperative boards: establish a sub-committee (3-4 people) dedicated to managing the Şantiye-M process. This committee holds regular meetings with the contractor and site manager to ensure timely filings.

Integration with Site Management

Once a residential project is completed, Şantiye-M records do not close — they are retained as an information archive and become a critical reference point for site management.

Situations where site management most needs Şantiye-M data:

• If a structural issue arises in an independent unit, accessing the concrete-rebar reports of the relevant floor from the construction period.
• When a warranty claim emerges, supporting the matters that can be claimed from the contractor with documentation.
• For issues in common areas (elevator, generator, water tank), accessing inspection reports from the construction period.
• For major renovations such as facade or roof replacement, reviewing the original designs and material specifications.

A good developer hands over a "construction dossier" to site management at occupancy delivery. This dossier should contain a summary and reference map of the Şantiye-M notifications.

Role of Şantiye-M Data in the Residential Sales Process

For sales departments, Şantiye-M data is not just a legal requirement; it is also a trust-building marketing tool for buyers. Particularly after 2023, with increased buyer awareness, the message "This project is within Şantiye-M scope and all notifications are filed regularly" has become an important part of the sales conversation.

Şantiye-M-based information that can be shared with buyers during sales:

• Project permit number and Şantiye-M registration number.
• Contractor authorisation certificate class.
• Chamber registration details of the site manager and project designers.
• Name and expert team of the building inspection company.
• Regularly shared progress reports (in anonymised, summarised form).

However, the sales team must absolutely coordinate the accuracy of buyer-disclosed information with the contractor. Misleading or exaggerated information creates future legal liability.

Another important sales-stage issue is the marketing of projects that fall within Şantiye-M scope but have not yet had their registration opened. Off-plan sales is a common model, but commitments made to buyers must run in sync with the Şantiye-M registration process. Otherwise, buyers spend the waiting period questioning whether "the project is real," and mistrust takes root. The best practice is to send a formal notice to buyers once the 30-day post-permit registration is complete: "Our project has been registered in the Şantiye-M system; tracking number ..."

Synchronisation with Şantiye-M notifications is also critical for unit option modelling (for example, the buyer choosing a wall position, bathroom fixture grade, or door orientation). Each option revision, once reflected in the project, may require a permit revision or a minor revision notification. Before promising flexibility to buyers, the sales team must align with the engineering team on which changes constitute Şantiye-M triggers.

Transparent communication on satisfaction directly influences repeat-sale rates. The customer satisfaction measurement article provides a comprehensive NPS and transparency metrics framework on this topic.

7 Common Mistakes in Official Reporting

Recurring typical mistakes in Şantiye-M audits of residential projects:

1. Late notification of unit changes: When unit merging or interior modifications are requested during sales, revision permits and Şantiye-M updates are delayed.
2. Skipping site manager change notifications: Site manager changes are frequent over the 12-18 month duration of residential projects; the outgoing manager's closing protocol and new appointment notification are often missed.
3. Confusion in concrete sample reports: When multiple blocks are poured in the same period, the block to which sample reports belong is not clearly indicated, causing issues during audits.
4. Missing common area acceptance protocols: While unit-level acceptances are well tracked, common area acceptance processes (elevator, social facilities) are loosely handled.
5. Unproven building inspection fee payments: Evidence that building inspection fees are deposited into the escrow account must be added to the Şantiye-M file at every stage.
6. Skipping landscaping notifications: The construction process for elements like gardens, parking, and playgrounds is excluded from residential notifications; this delays occupancy.
7. Document confusion in partial occupancy processes: Developers wishing to deliver some blocks early do not adequately plan which notifications must be completed for partial occupancy applications.

Şantiye-M Data in the Occupancy Permit Process

The ultimate success of residential projects is measured by obtaining the occupancy permit (iskan). The occupancy process depends directly on Şantiye-M reporting quality. Key items the authority examines during the occupancy permit application:

• Completeness of notifications for all construction phases.
• Approval of concrete-rebar inspection protocols by the building inspection firm.
• Regular publication of monthly OHS reports.
• Final test reports for systems such as elevators, fire suppression, thermal insulation, and gas installation.
• Landscaping and shelter (if applicable) acceptance protocols.
• Completion compliance letter from the building inspection company.

In a well-managed residential project, the occupancy process can be completed within 3-4 weeks. For projects with missing Şantiye-M notifications, this period can extend up to 4-6 months; during this time, no deliveries can be made to buyers, penalty clauses in sales contracts begin to apply, and brand reputation is seriously damaged.

AECKraft's Support in Residential Projects

AECKraft provides the following support to residential developers in preparing for Şantiye-M audits. An important note: AECKraft is not a Ministry-accredited Şantiye-M API vendor; official notifications are always made through accredited vendors. AECKraft operates on the documentation and management side of the process.

• CRM module: Manages all buyer communication, contracts, payment plans, and notifications in the residential sales process from a single location. Provides the foundation for buyer portal scenarios.
• Document management: All documents supporting Şantiye-M notifications (concrete sample report, rebar inspection protocol, OHS report, acceptance protocols) are archived with version control.
• Project management (WBS + Gantt): The 12-month residential project calendar is planned in WBS structure, matching each work item with its Şantiye-M notification date.
• 3D editor (browser-based Pascal engine): BIM models are visualised with IFC import support; the sales team presents a concrete vision to buyers while the construction team identifies coordination problems in advance.
• Progress payment tracking module: Contractor and subcontractor progress payments are calculated within AECKraft; results can be exported in Excel/CSV for transmission to the accounting team.
• Mobile field app (iOS + Android): Site manager and field team transfer daily reports, photos, and inspection protocols to the system from the field.
• Audit trail and role-based access: All changes are traceable by user and timestamp; this record is critical in audit preparation.
• KDPR-compliant Turkey data residency: Provides legal compliance infrastructure for data sharing scenarios with independent unit owners.
• 14-day free trial: No credit card required; residential developer teams can test the system with their real projects.

For demo requests visit the contact page; for package details and pricing visit the pricing page.

Conclusion

In the residential sector, Şantiye-M compliance is far more than a simple registration obligation; it is a strategic process that directly affects project completion duration, sales success, occupancy timing, and brand reputation. For projects of 50+ units, developer success is directly proportional to the investment made in notification discipline and document management.

The 12-month calendar, KDPR-compliant data sharing model, and 7 common mistakes covered in this guide provide a starting framework for building your project on solid foundations. Proactive management of the Şantiye-M file by your team provides advantages at every stage — from occupancy processes to penalty clauses, from buyer satisfaction to repeat sales.

Frequently Asked Questions

Does a residential project with fewer than 50 units fall within the Şantiye-M scope?

Unit count is not the sole measure. If total construction area exceeds 5,000 m² or building height exceeds 21.50 m, the project falls within the scope. Each criterion is evaluated independently.

How long do I have to register for Şantiye-M after the building permit?

The general regulatory framework allows 30 days. Exceeding this period triggers administrative fines and an unfavourable flag in inspection prioritisation.

Would sharing construction photos with buyers constitute a KDPR violation?

General project photos (exterior facade, common areas) can be shared under the transparency notice. However, sharing interior photos of other buyers' units or materials containing personal data requires explicit consent.

How does partial occupancy (phased delivery) affect the Şantiye-M process?

In a partial occupancy application, all Şantiye-M notifications for the blocks to be delivered must be complete. Notifications for other blocks may remain open, but a separate completion calendar must be submitted for them.

Is it possible to change the site manager mid-project?

Yes, but both the outgoing manager's closing protocol and the new manager's appointment protocol must be uploaded to the Şantiye-M system. It is critical that no documentation gap remains during the handover.

Are Şantiye-M fees different for housing cooperatives?

Certain facilities are recognised for housing cooperatives within the general regulatory framework; however, Şantiye-M notification obligations are the same as standard residential projects. Authorisation processes differ.

Does AECKraft have an official Şantiye-M reporting API?

No. AECKraft is not a Ministry-accredited Şantiye-M vendor and does not offer an official reporting API. Official reports are submitted through accredited vendors. AECKraft supports audit readiness with document archive, CRM, project management, and 3D editor capabilities.