A detailed legal guide to redundancy, restructuring, and collective dismissal rules in Turkey, covering operational dismissals, collective layoff thresholds, notification duties, consultation, mediation, reinstatement risk, and HR compliance.
Redundancy and restructuring are never purely commercial decisions. In Turkey, they are also legal processes shaped by Labour Act No. 4857 and the Labour Courts Act No. 7036. Employers may genuinely need to reduce headcount because of economic contraction, technological change, reorganization, closure of a business line, or a broader restructuring plan. But once those business reasons translate into dismissals, the employer enters a legally regulated field. At that point, the issue is no longer only whether the restructuring makes commercial sense. The issue is whether the dismissals are classified correctly, whether the employer is using the right statutory route, whether collective-dismissal thresholds are triggered, whether mandatory notices and consultations are completed, and whether individual employees retain the right to challenge the termination as invalid. That is why redundancy, restructuring, and collective dismissal rules should be treated as a core HR compliance subject rather than a final administrative step. (Natlex)
The Turkish system does not use one single legal label for every workforce reduction. Instead, the law separates ordinary notice termination, valid-reason dismissal for employees protected by the job-security rules, summary termination for just cause, dismissal after refusal of a proposed change in working conditions, and collective dismissal. Article 17 regulates notice termination of indefinite-term contracts. Article 18 requires a valid reason for dismissal in covered job-security cases and recognizes “operational requirements of the establishment or service” as one of those grounds. Article 22 governs dismissal after refusal of a material change in working conditions. Article 29 adds a special procedure where redundancies reach a collective scale. Article 3 of the Labour Courts Act then requires mediation as a precondition for lawsuits involving employee or employer receivables, compensation claims, and reinstatement claims. (Natlex)
What redundancy and restructuring mean under Turkish labour law
Turkish labour legislation does not define “redundancy” as a standalone concept in the way some common-law systems do, but it clearly recognizes business-driven dismissals. Article 18 states that, in workplaces with thirty or more employees, an employer terminating an employee engaged for an indefinite period and having at least six months of seniority must rely on a valid reason connected with the employee’s capacity or conduct, or based on the operational requirements of the establishment or service. In practice, that operational-requirements language is the legal foundation for restructuring dismissals, reorganization dismissals, downsizing, and redundancy-based terminations. It is the employer’s main statutory route when the dismissal is not based on misconduct or personal performance, but on business needs. (Natlex)
This distinction is critical. A redundancy dismissal is not the same as a disciplinary dismissal. If the real reason is a business reorganization, loss of work volume, consolidation of teams, technological replacement of a role, or permanent elimination of a function, the employer should normally proceed on an operational-requirements theory rather than trying to force the facts into a misconduct narrative. Turkish law allows summary dismissal without notice only in narrower circumstances listed in Article 25, such as serious dishonesty, repeated unauthorized absence, refusal to perform duties after warning, sexual harassment of another employee, or comparable grave conduct. Ordinary redundancy is not one of those cases. (Natlex)
For HR teams, the first legal question in a restructuring therefore is not “How many people do we need to dismiss?” but “What kind of dismissal are we making?” If the answer is that the roles themselves are being reduced or reorganized for economic, technological, structural, or similar reasons, the legal pathway is usually Article 18, and if the scale reaches the statutory thresholds, Article 29 must also be added. If the employer confuses these routes, the business rationale may still exist, but the dismissal may become vulnerable because the wrong procedure was used. (Natlex)
When job-security rules apply to redundancy dismissals
Not every employee benefits from the same dismissal protection. Article 18 applies where the employee works under an indefinite-term contract, has at least six months of seniority, and is employed in an establishment with thirty or more workers. The same article also states that six-month seniority is calculated by combining periods worked in one or different establishments of the same employer, and that where the employer has more than one establishment in the same line of business, the employee threshold is calculated across those establishments. This matters in restructuring because employers sometimes look only at one office or one branch when the statute requires a broader calculation. (Natlex)
Article 18 also excludes a narrow category of top-level employer representatives and certain assistants authorized to manage the entire enterprise or to recruit and terminate employees. Outside that narrow exception, however, employees meeting the statutory threshold conditions may challenge a restructuring dismissal if they believe no valid operational reason existed or if the process was used unlawfully. For HR, this means a redundancy program should never assume that “business decision” alone automatically defeats job-security rights. Turkish law expressly allows litigation over whether the operational ground was validly used. (Natlex)
Notice periods still matter in redundancy programs
Even where a redundancy is commercially justified, Article 17 still regulates notice. For indefinite-term employment contracts, the employer must either respect the statutory notice period or pay wages in lieu of notice. The minimum periods are two weeks for service under six months, four weeks for service between six months and under one and a half years, six weeks for service between one and a half and under three years, and eight weeks for service over three years. The law also states that these are minimum periods and may be increased by contract. (Natlex)
But Article 17 also contains a point that employers sometimes overlook: payment in lieu of notice does not eliminate the application of Articles 18, 19, 20, and 21. In other words, an employer can pay notice correctly and still lose a reinstatement case if the dismissal lacked a valid reason or was procedurally defective. In a restructuring context, this means notice pay is a necessary compliance step, but not a substitute for a lawful redundancy rationale. HR should treat notice compliance and dismissal validity as related but separate issues. (Natlex)
Written reasons and procedural discipline
Where an employer proceeds with an individual redundancy dismissal, the written-notice requirement remains central. Article 19 states that the notice of termination must be given in writing and the reason for termination must be stated in clear and precise terms. The same article expressly requires an opportunity for defense where the dismissal is based on the employee’s conduct or performance. Because that defense rule is written specifically for conduct- and performance-based dismissals, the text does not impose the same defense requirement on a purely operational redundancy in the same way. Even so, the written reason remains mandatory, and the clearer the employer’s business explanation is, the stronger the dismissal file will usually be. (Natlex)
That distinction is important in practice. A redundancy dismissal letter should not use vague wording such as “management decision” or “organizational incompatibility.” Article 19 requires clarity and precision. In a restructuring case, the safer approach is to explain the operational basis in concrete terms, such as departmental consolidation, cessation of an activity line, elimination of duplicated roles, or a technology-driven reduction of a function. The goal is not to over-explain commercial strategy, but to make the statutory ground identifiable and reviewable if challenged. (Natlex)
Collective dismissal: when the restructuring reaches statutory scale
Article 29 creates a separate regime once dismissals reach a certain scale. It provides that when the employer contemplates collective terminations for reasons of an economic, technological, structural, or similar nature necessitated by the requirements of the enterprise, establishment, or activity, the employer must provide written information at least thirty days before the intended layoff to union shop stewards, the relevant regional directorate of labour, and the Public Employment Office. The same article then defines when a collective dismissal occurs. It is collective when, within one month and pursuant to Article 17, the employer terminates at least 10 employees in establishments employing 20 to 100 workers, at least 10 percent of employees in establishments employing 101 to 300 workers, or at least 30 employees in establishments employing 301 or more workers. (Natlex)
This definition contains several practical lessons. First, the collective-dismissal thresholds are linked to Article 17 terminations, meaning notice-based dismissals are the core statutory trigger. Second, the calculation period is one month, whether the terminations happen on the same date or on different dates. Third, the thresholds vary with total workforce size. Employers therefore cannot safely assess collective-dismissal risk by looking only at one dismissal day in isolation. A rolling one-month review is necessary whenever a restructuring is underway. (Natlex)
The required written notification must also contain specific information. Article 29 states that the written communication must include the reason for the contemplated layoff, the number and groups of workers likely to be affected, and the time period over which the termination procedure is expected to occur. That means a compliant Article 29 notification is not a generic announcement that “the company may reduce staff.” It must contain structured information on rationale, scope, affected categories, and timing. In HR terms, this requires planning before letters go out, not after. (Natlex)
Consultation duties in collective dismissals
Article 29 does not stop at notification. It also requires consultations with union shop stewards after the notification. According to the statute, those consultations must address measures to avert or reduce the terminations and measures to mitigate or minimize their adverse effects on the workers concerned. The law further requires that a document showing the consultations took place be drawn up at the end of the meeting. This means collective dismissal in Turkey is not only a reporting exercise. It also carries a consultation dimension, at least where workplace union representatives exist. (Natlex)
For HR departments, this part of Article 29 is especially important because it changes the sequencing of a restructuring project. Once the collective-dismissal thresholds are reached, the employer should not jump straight from internal board approval to final termination notices. The statute expects a prior written notification, then consultations on ways to avoid, reduce, or soften the impact of the dismissals, and only afterward do termination notices take legal effect. This procedural standstill is part of the law’s design. (Natlex)
The 30-day standstill and when notices take effect
Article 29 expressly states that notices of termination take effect 30 days after the notification of the regional directorate of labour concerning the intended layoffs. This is one of the most important timing rules in collective redundancy practice. It means that the legal effectiveness of dismissal notices is not immediate once Article 29 is triggered. There is a statutory waiting period tied to the notification. For HR planning, that affects payroll timing, internal communications, access management, transition planning, and the date on which the employee’s termination legally starts to produce effects. (Natlex)
A practical consequence follows from this. If the employer sends letters too early, or treats the employee as terminated before the 30-day Article 29 period has run, the employer risks procedural irregularity. Collective redundancy should therefore be managed from a single legal timeline, not through disconnected actions by HR, finance, line management, and IT. The legal clock under Article 29 is part of the dismissal itself. (Natlex)
Full closure, seasonal work, and re-hiring preference
The law also distinguishes a full and permanent closure from an ordinary collective dismissal. Article 29 states that if the entire establishment is closed with a definite and permanent stoppage of activities, the employer must notify the regional labour directorate and the Public Employment Office at least thirty days in advance and must post the relevant announcement at the establishment. In that special situation, the statute uses a different procedural formulation than the ordinary collective-dismissal process. (Natlex)
Article 29 also excludes layoffs in seasonal and campaign work where the layoffs are carried out in connection with the nature of such work. In addition, the official Turkish text of Article 29 provides that once the collective dismissal becomes final, if the employer wishes within six months to hire again for work of the same nature, workers whose qualifications are suitable should be called back with priority. This is a significant point for restructuring strategy: a company that rapidly refills the same roles after a collective redundancy may create serious credibility problems, and the statute itself recognizes a preferential re-hiring expectation in the official text. (Natlex)
Collective dismissal does not cancel individual job-security rights
One of the most important safeguards in Article 29 appears at the end of the provision. The statute expressly says the employer may not apply the collective-dismissal rules in order to evade or prevent the application of Articles 18, 19, 20, and 21; otherwise, the employee may file suit under those articles. This means that collective dismissal is not a legal shortcut around individual protection. Even in a large-scale restructuring, employees may still argue that their particular dismissal lacked a valid reason, that the written-reason requirement was not satisfied, or that the dismissal was part of an unlawful attempt to bypass the reinstatement regime. (Natlex)
This is the point where many employers make a strategic mistake. They assume that once Article 29 is triggered, the collective character of the layoff automatically shields the employer from individual challenges. The statute says the opposite. Collective procedure must be respected, but individual employees may still rely on Articles 18 to 21 where applicable. In practice, that means a lawful restructuring needs both a compliant collective process and defensible individual termination files. (Natlex)
Restructuring through contractual change before dismissal
Not every restructuring leads directly to redundancy. Sometimes the employer wants to relocate staff, merge roles, alter schedules, or change reporting structures before deciding whether dismissal is necessary. In that situation, Article 22 becomes important. It provides that any change in working conditions based on the employment contract, annexed work rules, similar sources, or workplace practice may be made only through written notice. If the employee does not accept the proposed change in writing within six working days, the change does not bind the employee. The employer may then terminate the contract by respecting the notice period, provided the proposed change was based on a valid reason or another valid reason for termination. (Natlex)
For restructuring projects, Article 22 matters because some employers try to use informal managerial directions to impose substantial changes and then dismiss the employee when resistance follows. Turkish law provides a more disciplined route. If the employer’s business plan requires a material contractual change, that change should be proposed in writing and handled under Article 22 rather than disguised as ordinary managerial control. This is especially relevant where restructuring involves relocation, function change, or different work organization rather than immediate role elimination. (Natlex)
Mediation and litigation risk after redundancy dismissals
If an employee wants to challenge the dismissal, Labour Courts Act No. 7036 adds a mandatory precondition. Article 3 states that for claims involving employee or employer receivables and compensation based on law, individual or collective labour agreements, and for reinstatement claims, applying to a mediator is a condition of action. If a lawsuit is filed without prior mediation in those matters, the case is dismissed procedurally. That means redundancy disputes usually do not begin in court. They begin in mediation. (Adalet Bakanlığı)
Article 20 of Labour Act No. 4857 then gives the employee the right to challenge the dismissal within one month of receiving the notice and places the burden of proving a valid reason on the employer. Article 21 states that if the dismissal is found invalid, the employer must re-engage the employee within one month, and if it does not, compensation of between four and eight months’ wages may be awarded, together with up to four months’ wages and other entitlements for the period not worked. For HR, this means a redundancy file should always be prepared as if it may later be reviewed in mediation and then in reinstatement litigation. (Natlex)
Common employer mistakes in redundancy projects
The first common mistake is assuming that a business decision proves itself. Turkish law allows business-based dismissals, but Article 20 still places the burden of proof on the employer in valid-reason litigation. The second mistake is ignoring Article 29 thresholds because dismissals are staggered over several dates, even though the statute counts dismissals within one month on the same or different dates. The third mistake is using collective dismissal as a shield against individual claims, despite Article 29’s express prohibition on evading Articles 18 to 21. The fourth mistake is sending vague termination letters without a clear operational explanation, contrary to Article 19’s requirement of a written and precise reason. The fifth mistake is overlooking Article 22 where the real issue is refusal of a proposed material change rather than immediate redundancy. (Natlex)
A further risk lies in how employees are selected for redundancy. The statute does not set out a detailed selection matrix, but because Article 18 requires a valid reason and also lists motives that do not constitute valid reasons, it is a strong inference that selection should not be based on protected or prohibited grounds such as union activity, pregnancy, family responsibilities, or similar factors. Where a restructuring appears to target employees for reasons excluded by Article 18, the employer’s operational explanation becomes much harder to defend. That is why objective and consistently applied selection logic is not merely an HR best practice; it is a litigation-risk measure derived from the statutory framework. (Natlex)
Best-practice approach for HR and legal teams
A legally robust restructuring process in Turkey usually requires six steps. First, identify whether the measure is a true redundancy, a contractual-change project under Article 22, or a conduct/performance issue that should not be mislabeled as restructuring. Second, determine whether the employees affected fall within Article 18 job-security protection. Third, calculate whether Article 29 collective-dismissal thresholds will be met within the one-month period. Fourth, prepare the written notices and, if Article 29 applies, the required written notification containing reasons, affected groups, and timeline. Fifth, run the consultation stage properly and document it. Sixth, prepare for mediation and possible reinstatement claims by preserving the business rationale, the selection logic, and the individual termination records. (Natlex)
The deeper point is that redundancy is not unlawful in itself. Turkish law accepts that employers may dismiss for economic, technological, structural, or similar business reasons. What the law does not accept is procedural disorder, vague reasoning, misuse of collective-dismissal rules, or attempts to bypass individual protections embedded in Articles 18 to 21. In that sense, lawful restructuring depends less on the vocabulary used by management and more on the employer’s ability to align commercial decisions with the specific dismissal route chosen by the statute. (Natlex)
Conclusion
In Turkey, redundancy, restructuring, and collective dismissal rules operate on two levels at once. At the individual level, business-driven dismissals generally rest on Article 18’s “operational requirements” ground, together with Article 17 notice rules, Article 19 written-reason requirements, Article 20 burden-of-proof rules, and Article 21 reinstatement consequences. At the collective level, Article 29 adds thresholds, advance written notification, consultation duties, a 30-day waiting period, special rules for full closure, an exclusion for certain seasonal and campaign layoffs, and an express prohibition on using collective dismissal to avoid Articles 18 to 21. On top of that, Labour Courts Act No. 7036 requires mediation before reinstatement and compensation lawsuits can be filed. (Natlex)
For employers and HR teams, the safest conclusion is clear: a restructuring plan should be built like a legal project, not only a finance project. Workforce reduction can be commercially necessary, but it must be documented, classified, timed, and communicated through the correct statutory mechanism. When that discipline is missing, the employer may find that a genuine business decision has turned into avoidable dismissal litigation. (Natlex)
Yanıt yok