Off the Payroll: Who Can Actually Use Your Ethics Hotline
Not everyone working in your hotel is your employee
Seven in the morning at a 400-room resort. The laundry van is at the service entrance, night security is handing over, the landscaping crew is working the pool perimeter, the spa desk is opening up. Every one of these people is inside the hotel. Most of them are not on the hotel's payroll.
When a company sets up an ethics reporting channel, the first question is usually which topics are in scope. The decisive question comes earlier: who can use an ethics hotline once you have built one? That question mostly never gets asked — it gets answered by default. Whichever population HR administers is the population the channel opens to. Scope ends up defined by who the system can already see, not by who carries the information.
We have already covered why a shared inbox is not a reporting channel and what the four conditions of a real channel are. This post takes the layer underneath: once a channel meets those four conditions, who is it open to, who is it closed to, and on what basis do you decide?
The order is this. First the four groups that sit off the payroll. Then the one concrete point of contact in Turkish law — article 2 of the Labour Act. Then who the reference standard counts. You will finish with three costs of drawing scope narrowly, two of drawing it widely, and a four-question frame for writing the decision down.
Four groups off the payroll: subcontractor, agency, trainee, former employee
In hospitality, off-payroll labour is not an exception to the staffing model. It is the staffing model. The operator runs rooms, F&B and front office on its own headcount and contracts out the rest. That leaves four groups.
| Group | Where they typically sit in a hotel | Who employs them | Where they show up in your records |
|---|---|---|---|
| Subcontractor staff | Laundry, security, landscaping, technical maintenance, often spa, sometimes an F&B outlet | The subcontracting firm | Procurement and contract files — not the HR system |
| Agency and temporary supply staff | Housekeeping, banqueting and stewarding at peak | The agency or supplier | Invoices and timesheet attachments |
| Trainees and vocational placement students | Kitchen, front office, housekeeping | School protocol; paid or unpaid | Training and placement files |
| Former employees | Every department | Nobody, now | The personnel archive, not the active roster |
The last column is the important one. None of these groups appears in the list HR works from day to day. Decide scope by looking at the HR system and all four have been eliminated before the decision is made — without anyone ever saying no.
So the first practical step is to build your off-payroll population from procurement and contract files, not from HR. List the live service contracts, ask each supplier how many people they place on site, and write down which departments and which shifts they cover. That list is almost always longer than anyone expects, and it is where managing contracted staff actually begins.
The second step sits on the headcount side. The question of who the channel is open to gets a much cleaner answer alongside a scope defined role by role, because once a role is defined, so is the question of who is contracted to perform it. The obstacles specific to seasonal crews were covered separately in where the channel breaks for a seasonal team; this post is about the employment-status boundary.
What "they are not our staff" means legally: Labour Act art. 2
It is the most common sentence in any scope discussion, and administratively it is correct. A subcontractor's worker is not on your payroll, is not paid by you, and is not subject to your disciplinary process.
Legally it draws a much less tidy line than it sounds. The seventh paragraph of article 2 of Labour Act no. 4857 gives the relationship a name and attaches a liability to it:
"Bir işverenden, işyerinde yürüttüğü mal veya hizmet üretimine ilişkin yardımcı işlerinde veya asıl işin bir bölümünde işletmenin ve işin gereği ile teknolojik nedenlerle uzmanlık gerektiren işlerde iş alan ve bu iş için görevlendirdiği işçilerini sadece bu işyerinde aldığı işte çalıştıran diğer işveren ile iş aldığı işveren arasında kurulan ilişkiye asıl işveren-alt işveren ilişkisi denir. Bu ilişkide asıl işveren, alt işverenin işçilerine karşı o işyeri ile ilgili olarak bu Kanundan, iş sözleşmesinden veya alt işverenin taraf olduğu toplu iş sözleşmesinden doğan yükümlülüklerinden alt işveren ile birlikte sorumludur."
In our own rendering, not an official translation: where one employer takes on ancillary work, or a specialist portion of the principal work, at another employer's workplace and deploys its own workers solely on that job there, the relationship between the two is a principal employer–subcontractor relationship. And in that relationship the principal employer is liable jointly with the subcontractor for obligations owed to the subcontractor's workers arising from the Labour Act, the employment contract, or a collective agreement to which the subcontractor is party.
The definitional half settles laundry, security and landscaping without argument — these are ancillary work in the plain sense of the provision. The typical hospitality contracting structure is not adjacent to this relationship. It is the relationship.
The operative words are "birlikte sorumludur" — jointly liable. Subcontractor liability is shared liability, and it does not stop at the payroll boundary.
What joint liability covers, and what it does not
This is the section to read carefully, because it is easy to take article 2 one step too far, and that step is wrong.
What it covers: the text names the sources of the obligation — the Labour Act, the employment contract, or a collective agreement the subcontractor is party to. Wages, severance, notice, annual leave and overtime sit inside that set. If a subcontractor's worker has a claim arising from those, the principal employer is an addressee of it too.
What it does not cover — and this needs saying plainly: article 2 imposes no obligation on a principal employer to give a subcontractor's workers a reporting channel. No such obligation exists in Turkish law. Joint liability runs over a defined and closed set, and "therefore you must open your hotline to contractors" is not a conclusion that comes out of it.
So what is article 2 doing in this post? Two things.
- A risk argument. The payroll boundary and the liability boundary are not in the same place. When the financial and legal consequences of something happening to a subcontractor's worker on your premises can land on you, closing off the route by which you would learn about it should be a deliberate choice rather than an unexamined one.
- A practical argument. The people who see the loading bay, the back corridor, the night shift and the staff changing rooms are usually the off-payroll ones. The group most likely to witness something overlaps heavily with the group least able to report it.
Those two are the case for widening scope. It is not a compliance case and it should never be presented as one. A compliance officer who is told an obligation exists when it does not stops reading at the first paragraph.
Muvazaa: when the relationship gets re-characterised from the outset
The same article contains a sentence that shows why the boundary is not yours to fix:
"…genel olarak asıl işveren alt işveren ilişkisinin muvazaalı işleme dayandığı kabul edilerek alt işverenin işçileri başlangıçtan itibaren asıl işverenin işçisi sayılarak işlem görürler."
In our rendering: where the principal–subcontractor relationship is held to rest on a sham arrangement (muvazaa), the subcontractor's workers are treated as the principal employer's workers from the outset.
"From the outset" is the operative phrase. Not from the date of the finding — from the beginning of the relationship.
For a scope decision the consequence is this: "on the payroll / off the payroll" is not a fixed line that sits under your control. It is a line that can be re-characterised after the fact. And when it is, the re-characterisation covers the entire period during which your channel was closed to those people.
That is the least comfortable and most honest reason to draw scope widely. Making an uncertain distinction the boundary of your channel means building a system on top of something that is not settled.
Who the reference standard covers: Directive art. 4
One boundary first. Directive (EU) 2019/1937 does not bind Turkish companies. Türkiye is not an EU member state and this instrument places no obligation on a Turkish hotel group. Its use here is exactly one thing: a reference standard. It is the text an investor, a lender, a franchise partner or the other side of an acquisition process looks at when they want a benchmark. The same caveat applies to the two closest domestic instruments: the CMB's corporate governance communiqué is written for listed companies and the banking regulator's internal systems regulation for banks. A privately held hotel group is the addressee of neither. All three are comparison points, not obligations.
Article 4 of the Directive lists who counts as a reporting person. The scope opens with persons "working in the private or public sector who acquired information on breaches in a work-related context including, at least" — and for our question the decisive point is art. 4(1)(d):
"any persons working under the supervision and direction of contractors, subcontractors and suppliers"
That description is precisely where a hotel's laundry, security, landscaping and spa staff stand. The reference standard's answer to the scope question does not leave hospitality's contracting structure outside. It brings it in.
Art. 4(1)(c) additionally covers shareholders, members of the administrative, management and supervisory bodies, and — in the text's own words — "volunteers and paid or unpaid trainees". Given the volume of placements a hotel takes each season, trainees are not a token category here.
The person who left — information does not leave with them
Art. 4(2) extends scope to people whose working relationship has "since ended".
Nowhere is that paragraph more concrete than in hospitality. In a seasonal operation a large share of the workforce becomes a former employee every November. Define scope as "active employees" and from November to April most of the people who know what happened are outside the channel. And that is exactly the window in which they are most likely to speak — season over, relationship over, and the cost of talking suddenly much lower.
What a departing employee tells you is already partly captured in an exit interview. But an exit interview is scheduled, face to face and run by HR. It is not the right place for something remembered three months later, or for something that could not be said at the time. A former employee needs a separate route, because that person no longer has a company email address, intranet access, or the right to enter the building.
The decision point: does a report from a former employee enter the same triage, or a separate queue? Both are defensible. What is not defensible is never asking, and letting the channel's authentication answer "no" on your behalf.
The candidate in a recruitment process: a relationship not yet begun
Art. 4(3) goes one step further, covering people whose working relationship "is yet to begin" and expressly naming information acquired "during the recruitment process".
This is the detail most readers do not expect. A candidate asked an improper question in an interview, subjected to discrimination in a selection process, or asked for something in exchange for a job is inside the reference standard's scope.
Operationally this is the hardest of the four groups to reach. A candidate has no account, no company email, no badge, no site access. If the channel is built on authentication, that person is outside it by definition. Including them means the channel has to accept a report without authenticating the reporter — which is a design decision, not a policy one. Confuse the two and the policy is wide on paper while the implementation stays narrow in practice.
Three costs of drawing the scope narrowly
Narrow scope is a defensible choice. It is not a free one, and these are the bills.
1. You exclude the group with the best line of sight. The loading bay, the back corridor, the stores, the night shift, the outdoor areas — the places in a hotel where something gets seen and told to nobody are usually where off-payroll staff work. Limiting scope to the payroll builds the channel's blind spot around exactly the people who see the most.
2. The boundary of your risk is not the boundary of your channel. Joint liability under article 2 and the muvazaa rule both keep the distance between you and a subcontractor's worker shorter than you assume. Being the last party to learn about an event whose consequences you carry is not a position worth choosing.
3. One person turned away takes the channel's credibility with them. Somebody told "this line is not open to you" does not keep it to themselves; they tell everyone on the shift. A reporting channel's reputation spreads through the reports it refuses far faster than through the ones it resolves well. If you are going to draw scope narrowly, how that is communicated matters as much as the decision itself.
Two real costs of drawing it widely
Wide scope has a bill too, and waving it away would be as sloppy as waving away the narrow case.
1. A larger reporting population means more triage. But the real load does not come from headcount — it comes from variety. Different employers, different contracts, different working patterns and often different languages mean every report first has to answer "whose matter is this?" A hypothetical comparison: going from a 600-person payroll to a 900-person reporting population is arithmetic; in the same hypothetical picture, dealing with eight separate employers is structural.
2. You will receive reports you have no authority to investigate. This is the serious objection to widening scope, and it is a genuine one. A subcontractor's worker may bring you a pay dispute with their own employer, a management problem inside their own firm, or a conflict with their own supervisor. On those you have no investigative authority: you cannot interview that firm's staff, cannot access its records, and cannot run a disciplinary process.
That leaves two options. Refer the report to the subcontractor under the service contract — in which case you no longer control the confidentiality of that report. Or log it and tell the reporter it is out of scope — in which case, for that person, there is no channel, and they will only find that out once.
There is no right answer between those two. There is a deliberate choice. What matters is not improvising it after a report has already arrived. The third question in the frame below exists precisely to settle it in advance.
Putting the scope decision in writing: a four-question frame
A scope decision is not one sentence. It is four questions. Answer all four in writing, date them, and re-read them at every contract renewal.
| # | Question | Where the answer comes from | Written output |
|---|---|---|---|
| 1 | Who? Which groups are in scope? | Procurement and contract files — not the HR system | A group-by-group list: subcontractor, agency, trainee, former employee, candidate |
| 2 | What? Which report types are in scope for each group? | Ethics policy plus the service contracts | A group × report-type matrix; out-of-scope cells are marked, never left blank |
| 3 | Who handles it? In each cell, who receives, who investigates, and what happens where you have no authority? | The delegation decision | A referral rule: when a report goes to the subcontractor, and how confidentiality is held when it does |
| 4 | How is it announced? How does someone with no company email, no intranet and no badge learn the channel exists? | Communications plan plus contract wording | Physical notice points, the language list, and the clause added to the service contract |
Question four is the one most often skipped, and on its own it can invalidate the whole scope decision. If your policy covers a subcontractor's staff but that staff does not know the channel exists, scope is wide on paper and absent in practice. The announcement has to reach off-payroll groups through a point you control rather than through their own employer — staff entrance, changing rooms, service corridor — and it has to become a clause in the service contract.
What comes out of these four questions is not a list but a boundary definition: a map of who can reach whom about what. Operating that map takes a structure that can open scope beyond the payroll — an entry point that does not depend on authentication, routing that varies by report type, and a record layer that logs out-of-scope reports without mixing them into the rest. Widening scope on paper while leaving the system locked to the payroll is the worst version of both decisions at once.
In a hotel group the scope question almost never stops at one property: each site has a different contracting structure, a different agency arrangement and a different placement volume, while the scope decision has to be written once, at group level. If you want to map your own off-payroll population and work through these four questions together, the HRMIM team works on HR processes and measurement discipline in hotel groups — write to us from the contact page.


