No Company Email, No Desk: How a Seasonal Worker Reports Harassment
An employment relationship that runs May to October has its own kind of silence
Workplace harassment reporting almost never happens in a seasonal hotel. That does not mean harassment is absent. It means the report never forms — and those are two different findings.
Someone working in a year-round property finds a way to raise a complaint. They have a corporate email account, a desk, an HR office in the same building, and an open-ended contract. In a relationship that starts in May and ends in October, none of that is a given. A seasonal housekeeping and F&B team can work an entire season without touching most of the company's internal communications infrastructure.
The argument here is straightforward: in a seasonal workforce, the reason harassment reports do not surface is mostly operational, not cultural. The causes can be counted, named and designed out. Six of them are set out below.
The academic literature on organisational wrongdoing reporting begins with Near and Miceli in 1985. This piece looks one step earlier than the decision that literature studies: what actually stands in the way of a worker who has already decided to report. We have written about the particular load seasonal employment carries in what the literature says about burnout in a seasonal operation; this is a different consequence of the same structural constraint.
Two definitions first, then two statutory provisions, then six break points, then a checklist.
Definitions: psychological harassment, sexual harassment, and the difference that matters
Türkiye has a published administrative definition of psychological harassment. Prime Ministry Circular 2011/2, published in the Official Gazette of 19 March 2011, issue 27879, is titled İşyerlerinde Psikolojik Tacizin (Mobbing) Önlenmesi and describes the behaviour as follows:
"Kasıtlı ve sistematik olarak belirli bir süre çalışanın aşağılanması, küçümsenmesi, dışlanması, kişiliğinin ve saygınlığının zedelenmesi, kötü muameleye tabi tutulması, yıldırılması ve benzeri şekillerde ortaya çıkan psikolojik taciz…"
In our own rendering: psychological harassment appearing in the form of deliberately and systematically, over a defined period, humiliating, belittling, excluding, damaging the personality and dignity of, mistreating or intimidating a worker, and similar conduct.
Be clear about what this document is: it is a circular, not a statute. An administrative instruction. It does not stand in for a court judgment or an article of law. What it does give you is the only officially written description of the behaviour Turkish practice calls "mobbing" — and it expressly reaches private-sector workplaces, not only public bodies.
Three elements of the definition do operational work: intent, systematic conduct, and a defined period. A single sharp exchange does not automatically fall inside that description; a repeated, targeted, continuing pattern does. The job of the person receiving a report is not to reach a verdict on those three elements but to ask the right questions with them: how often, since when, by whom.
Sexual harassment is a separate category and Turkish law treats it separately. The Turkish Code of Obligations art. 417 names both side by side; the Labour Act art. 24/II attaches a specific consequence to only one of them. That distinction is the single classification the recipient of a report has to make in the first half hour, because the legal consequence and the process that follows differ.
Where the employer's duty comes from: TBK 417
This is the provision that genuinely binds a Turkish hotel group. Article 417 of the Turkish Code of Obligations, under the marginal heading on protection of the worker's personality, says in its first paragraph:
"İşveren, hizmet ilişkisinde işçinin kişiliğini korumak ve saygı göstermek ve işyerinde dürüstlük ilkelerine uygun bir düzeni sağlamakla, özellikle işçilerin psikolojik ve cinsel tacize uğramamaları ve bu tür tacizlere uğramış olanların daha fazla zarar görmemeleri için gerekli önlemleri almakla yükümlüdür."
In our own rendering: the employer is obliged to protect and respect the worker's personality in the employment relationship, to maintain an order at the workplace consistent with the principles of good faith, and in particular to take the necessary measures so that workers are not subjected to psychological and sexual harassment and so that those who have been subjected to such harassment suffer no further harm.
There are two distinct duties in that sentence and most discussions skip the second. The first is to take measures so harassment does not occur. The second is to take measures so that a person who has been harassed suffers no further harm. The second duty begins once a report arrives, and it is precisely the subject of this article.
The third paragraph sets out the consequence:
"İşverenin yukarıdaki hükümler dâhil, kanuna ve sözleşmeye aykırı davranışı nedeniyle işçinin ölümü, vücut bütünlüğünün zedelenmesi veya kişilik haklarının ihlaline bağlı zararların tazmini, sözleşmeye aykırılıktan doğan sorumluluk hükümlerine tabidir."
That is: compensation for harm arising from the worker's death, injury to bodily integrity, or violation of personality rights caused by the employer's conduct contrary to the law or the contract — including the provisions above — is subject to the rules on liability for breach of contract.
One point deserves emphasis. The article says "gerekli önlemleri" — the necessary measures — and stops there. Hotline, software, form, channel, committee: none of these words appears in the text. Article 417 names no mechanism at all. Any presentation that reads this article as imposing a duty to build a system is saying something the text does not say. What the text says is that you are obliged to take measures, and that what those measures are is a design decision belonging to you.
Being a design decision makes it harder, not easier. Whether the measure you chose was sufficient gets assessed after the fact, once there is a dispute.
What the law attaches to a report that went nowhere: Labour Act 24/II(d)
This is the most concrete provision in the piece. Article 24 of the Labour Act no. 4857 governs the worker's right to terminate immediately for just cause. Subparagraph (d) of the second paragraph reads:
"İşçinin diğer bir işçi veya üçüncü kişiler tarafından işyerinde cinsel tacize uğraması ve bu durumu işverene bildirmesine rağmen gerekli önlemler alınmazsa."
In our own rendering: where the worker is subjected to sexual harassment at the workplace by another worker or by third parties and, despite reporting the situation to the employer, the necessary measures are not taken.
The weight of that sentence sits at the end: despite reporting it, the necessary measures are not taken. What triggers the right to terminate is not the harassment standing alone — it is the employer's inaction after the report. Subparagraph (b) of the same paragraph separately covers harassment coming from the employer:
"İşveren işçinin veya ailesi üyelerinden birinin şeref ve namusuna dokunacak şekilde sözler söyler, davranışlarda bulunursa veya işçiye cinsel tacizde bulunursa."
The operational reading of (d) is blunt. A channel that loses a report manufactures a just-cause termination ground against its own employer. A message left unread in a shared mailbox; a complaint nobody picks up at the end of the season; an incident told verbally to a supervisor and never carried upward. All three have the same shape: a report was made, and no measure followed.
The boundaries have to be stated in the same breath, because this article gets stretched:
- 24/II(d) is specific to sexual harassment. It does not cover psychological harassment, discrimination, fraud reports or health-and-safety reports. Reading it as "any report" is wrong.
- It is a worker's right, not an employer obligation to build anything.
- It says nothing about how a report has to be received, logged or acknowledged.
So the law does not make you build a channel. It defines what it costs when the channel does not work. The design decision is still yours.
Six places the channel breaks in a seasonal team
The two provisions above apply to every employer. What follows is specific to a seasonal operation.
These six are the obstacles standing in front of a worker who has already decided to report. None of them requires bad intent; each is a natural consequence of how the operation is set up. It is a textbook case of the difference between a process built for a seasonal team and one designed for the year-round team and later adapted.
First: there is no company email address
In most hotel groups, corporate email accounts go to management and back-office roles. Housekeeping, stewarding, laundry, the waiting staff and the pool team are not on that list. This is not an oversight — it is a deliberate licensing and administration decision.
The consequence: if your reporting channel is an address of the ethics@ form, the population most likely to have something to report has no account from which to write to it. Writing from a personal email account identifies the worker completely, from the first line.
What to do: the channel needs an entry point that does not require authentication against a corporate identity. Every route that requires a company account excludes everyone who does not have one.
Second: no desk, no fixed shift, nowhere private to speak
Making a report takes time and privacy. A seasonal operation is short on both.
Shifts rotate, break areas are shared, and in most properties the HR office sits off the service corridor where everyone sees who goes in. "Come to HR, let's talk" is an invitation that thirty colleagues witness. Even when the channel itself is confidential, the act of reaching it is visible.
What to do: it has to be possible to report from a personal device, outside working hours, from outside the property. Any channel that depends on a workstation, an office or an appointment is effectively closed.
Third: the contract ends in October — retaliation arrives as a non-renewal
In a seasonal team, retaliation does not look like dismissal. Nobody is fired. The person is simply not called back the following May.
This is the hardest form to detect, because there is no action to point at. There is an absence, and the reason for the absence is written down nowhere. A worker thinking about reporting knows this before they report. They decide accordingly.
The reference standard names this shape. Directive (EU) 2019/1937 is a reference standard; it does not bind a hotel group established in Türkiye. Its value here is diagnostic rather than legal: a text that has thought about the problem before us lists, in article 19, among the prohibited forms of retaliation:
"(j) failure to renew, or early termination of, a temporary employment contract"
"(c) transfer of duties, change of location of place of work, reduction in wages, change in working hours"
Point (j) is exactly the non-renewal of a seasonal contract. Point (c) is the quieter version of the same operation: the person is not let go, their station and their shift simply change. In Turkish law, declining to renew a contract is not in itself unlawful retaliation; what is described here is a framework for recognising a pattern, not a legal consequence.
On the management side there is something measurable in this. The composition of the group that does not get called back is data, and most groups never look at it. We have covered the same hidden cost in the part of turnover cost that never shows on the balance sheet; this is a different cause feeding the same line item.
What to do: record the reason a seasonal contract was not renewed, and record it separately for workers who made a report. A record does not prevent retaliation. It makes it reviewable afterwards.
Fourth: language. A worker with limited Turkish cannot complete the form
Seasonal teams get more multilingual every year. A worker may speak operational Turkish perfectly well — take an order, name the equipment, read a shift plan — and still be unable to set out in writing, in a document with legal consequences, what happened to them.
These are different language competencies. Operational fluency and narrative competence are not the same thing, and the second arrives much later. A Turkish-only reporting form is not merely difficult for part of the workforce; it is unusable.
What to do: the form has to exist in the languages the workforce actually speaks, and the free-text field has to be completable in the worker's own language. Translation is the receiving side's job. It cannot be the reporter's.
Fifth: living in staff accommodation means living in the same building as the person you named
Where staff live on site, the working relationship does not end when the shift does. Same corridor, same canteen, same shuttle.
That multiplies the cost of the decision to report compared with a year-round property. If the person named is a supervisor, that person also influences room allocation, the shift roster and often meal times. A worker who reports is risking not their job but the whole of their daily living arrangement.
What to do: how separation will be handled the moment a report arrives — who moves, where, and for how long — has to be written down in advance. Left to the moment, that decision gets taken in a hurry and usually to the reporter's disadvantage. Written in advance, it does not.
Sixth: the season ends and no record survives it
The property closes in October. The seasonal HR lead leaves. The note on their laptop, the WhatsApp thread and the diary leave with them. The team arriving next May knows nothing about last season's reports.
Two things follow. A repeating pattern never becomes visible as a pattern; every season is the first season. And the record showing that a report was made and no measure followed — precisely the record that would matter in a 24/II(d) argument — does not exist.
People say most of it on the way out, which is why the questions asked at departure are worth asking. But in a seasonal operation, departure happens for thirty people at once and nobody is listening.
What to do: the report record has to live somewhere independent of any individual and any device, and the season handover has to become a checklist. What gets handed over is not only the open files but the record of the closed ones.
The external route: ALO 170 and what Circular 2011/2 actually says
If your internal channel does not work, the worker has an external route, and that route is defined in a published text. Article 4 of Circular 2011/2:
"Psikolojik tacizle mücadeleyi güçlendirmek üzere Çalışma ve Sosyal Güvenlik İletişim Merkezi, ALO 170 üzerinden psikologlar vasıtasıyla çalışanlara yardım ve destek sağlanacaktır."
That is: to strengthen the fight against psychological harassment, the Labour and Social Security Communications Centre will provide assistance and support to workers through psychologists via ALO 170.
Article 1 of the same circular is explicit about where it places responsibility:
"İşyerinde psikolojik tacizle mücadele öncelikle işverenin sorumluluğunda olup işverenler çalışanların tacize maruz kalmamaları için gerekli bütün önlemleri alacaktır."
That is: combating psychological harassment at the workplace is primarily the employer's responsibility, and employers will take all necessary measures so that workers are not subjected to harassment.
Article 7 sets an expectation about how allegations are handled:
"Psikolojik taciz iddialarıyla ilgili yürütülen iş ve işlemlerde kişilerin özel yaşamlarının korunmasına azami özen gösterilecektir."
That is: in the work and procedures conducted in relation to psychological harassment allegations, the utmost care will be taken to protect individuals' private lives.
The picture that emerges is worth sitting with. An external route exists, it is free, and it is independent of the company. That is what your internal channel competes with. If a worker chooses to report internally, they choose it because they trust you. If internal reports are not arriving, the safer reading is not that the external route is unused — it is that yours was not preferred.
Once more: this is a circular, not a statute, and nothing in it requires a channel or a system. It assigns responsibility to the employer; it does not prescribe the form the measure takes.
A checklist for building the internal channel around a seasonal team
Each of the six break points converts into a design requirement. The list is short and no item on it describes a product:
- An entry point that does not require a corporate account. The people without company email are the people most likely to have something to report.
- Reachable from a personal device, off the property, outside working hours. The act of reaching the channel must not itself be visible.
- A form in the languages the workforce actually speaks. Free text has to be writable in the worker's own language.
- A structural separation between who receives the report and who it concerns. Routing a complaint about a supervisor to that supervisor is not a channel.
- A written separation protocol that triggers on receipt. In a property with staff accommodation especially, that decision cannot be taken after the report arrives.
- A record independent of any person or device, tied into the season handover checklist.
- The sexual-harassment / psychological-harassment distinction made at the point of logging. The legal consequence and the process differ, and the distinction cannot be made retroactively.
- A recorded reason for every seasonal contract not renewed. It does not prevent retaliation; it makes it visible.
Four items on that list are really the seasonal form of conditions any reporting channel has to satisfy. We set those out separately: the four conditions a channel has to meet are access, record, timing and impartiality, and a shared mailbox fails all four.
The difference between designing around the constraint and designing in spite of it shows up here. Opening a channel built for the year-round team to the seasonal workforce in May does not put the channel in that workforce's hands. By contrast, a channel built around a seasonal team works in the worker's hands from day one.
If you are designing a reporting channel for a seasonal operation, or you do not know how many of these eight items your current channel satisfies, let's talk. We can go through what you have against this checklist together and work out concretely which item is actually missing — get in touch.


