An EOR is the legal employer for your people in countries where you have no entity. The contract sits with them. Payroll sits with them. Statutory compliance sits with them. Your employee, though, works for you every day.
That structure holds together well enough for routine HR. When a grievance lands, it breaks down fast.
The EOR has the legal obligation to run a compliant process. You have the context, the witnesses, and the ability to actually fix things. Neither party can do it alone, and most EOR contracts say almost nothing specific about how the two sides should coordinate. That gap is where complaints stall, escalate, or produce outcomes that neither party intended.
This is not a hypothetical problem. A complaint raised in Germany may require works council notification before any investigation begins. One raised in India under the POSH Act requires a formally constituted Internal Committee with an external member. One raised in the UK triggers the ACAS Code of Practice, and a failure to follow it can move tribunal awards by up to 25%. The EOR arrangement does not pause any of those obligations.
This guide covers the complete picture: how grievance categories map across jurisdictions, how responsibility should be divided between EOR and client, what your contract must actually say, how investigations run in practice, and where companies consistently get burned.
It also addresses termination-linked grievances, whistleblowing frameworks, platform capabilities, and a working operational model you can implement without rebuilding your HR infrastructure.
What Counts as a Grievance in an EOR Context
A grievance is a formal complaint raised by an employee about something they believe is unfair, unlawful, or in breach of their employment terms. The formal label matters because it activates specific procedural rights and obligations in most jurisdictions that apply to the EOR as legal employer, regardless of how day-to-day work is managed.
The category is broader than most companies expect. Pay errors, denied leave, bullying, harassment, discrimination, safety failures, manager conduct, role disputes, all of these qualify. Some, like sexual harassment, operate under standalone legal regimes with their own timelines, committee requirements, and reporting rules that sit entirely outside the general grievance process.
Cross-border complexity adds a layer that many companies underestimate. The same behavior can carry different legal weight depending on local law. “Bullying” under UK employment law and “hostile work environment” under U.S. Title VII describe overlapping but legally distinct concepts.
An EOR that applies the wrong frame to a complaint creates procedural problems before the investigation has even started.
There is also a category distinction that matters operationally: the difference between a formal grievance and an informal complaint. Informal complaints, a conversation with a manager, a comment to HR have not yet triggered statutory rights or timelines.
Treating every informal complaint as a formal grievance creates its own procedural complications. The intake process needs to distinguish between the two, and the EOR and client company need to agree on that distinction before any complaint arrives.
The Three-Party Problem Nobody Talks About
Every EOR arrangement involves three parties: the employee, the EOR, and the client company. Payroll and compliance work well in that structure. Grievances do not, because a grievance requires someone to take ownership, and ownership in a tripartite arrangement is almost never clearly defined in advance.
The employee feels the confusion first. They work for you. Their manager is yours. Their performance reviews are yours. When something goes wrong, their instinct is to come to you. But the legal employer, the entity with the formal procedural obligation, is the EOR. That mismatch is where complaints get misrouted before anyone realizes it has happened.
The EOR’s position is structurally constrained. They carry the statutory obligation to run a compliant process, but they are not present in your workplace. They cannot see your team dynamics, interview your witnesses, or fix your management relationship. They can ensure the documentation is legally defensible. They cannot remedy the underlying problem.
The client company faces the reverse constraint. You have the context and the authority to take real remedial action. But you are not the legal employer. Acting unilaterally, reassigning the employee, offering a resolution, changing their working arrangements, without EOR coordination creates a procedural gap that can undermine the entire process.
The sharpest risk is disagreement between the two parties on how to handle a case. The EOR may assess a complaint as requiring full formal process; the client may see it as a minor interpersonal matter.
Neither assessment is automatically wrong. Without a pre-agreed escalation protocol, the dispute about process becomes a second problem layered on top of the original complaint, and the employee is waiting through all of it.
The solution is not to wait for a grievance to find the gap. It is to map the accountability split before any complaint arrives, embed it contractually, and test it at least once a year. See how to structure that in the EOR compliance framework guide on EmployerRecords.
What Your EOR Contract Should Actually Say About Grievances
Most EOR contracts handle payroll cycles, statutory benefit administration, and termination notice periods in precise detail. Grievance handling gets a line, sometimes two. The standard language, “EOR will provide HR support as required,” tells you nothing about who does what when a formal complaint arrives.
That ambiguity becomes a liability the moment a complaint lands. Both parties assume the other is handling it. The process stalls. The employee waits. By the time roles are clarified, the statutory acknowledgment window may have already passed.
The first clause to look for is a defined intake protocol. The contract should name who receives formal complaints, specify a maximum acknowledgment timeframe, 24 hours is a reasonable standard in most jurisdictions, and confirm that both the EOR and the client company are jointly notified the moment a complaint is logged.
Investigation responsibility must be explicitly divided, not left to inference. The contract should state that the EOR leads on procedural compliance, local law alignment, and documentation, and that the client company leads on fact-finding, witness interviews, and substantive remediation. Without that split in writing, both parties either duplicate effort or leave gaps that neither fills.
Escalation terms are as important as the primary process. When the EOR and client company disagree on how to handle a case, and they will, the contract should name a senior contact on each side, set a resolution timeframe, and clarify which party’s assessment prevails on legal compliance matters versus workplace remediation decisions.
Indemnification clauses deserve specific scrutiny in the context of grievances. If a complaint escalates to a tribunal or labor authority, which party bears the cost? Standard EOR agreements typically allocate liability based on whose instructions caused the failure. Make sure that the assignment is explicit for grievance-specific procedural failures — it will determine your exposure in any claim.
Finally, check the data handling terms as they apply to investigation files. Grievance records contain sensitive personal data: allegations, witness statements, and sometimes medical information.
The contract should specify who holds the case file, retention periods, and who has access under what conditions. In Europe, this intersects directly with GDPR obligations on special category data. The data protection guidance on EmployerRecords covers how leading EOR platforms handle this in practice.
The Investigation — Step-by-Step in an EOR Model
A fair investigation has the same bones everywhere: plan, gather facts, decide, allow appeal. What changes across jurisdictions is the texture, timelines, accompaniment rights, committee requirements, letter formats.
In an EOR model, the structure runs across two organisations at once. The EOR owns the procedural layer. The client company owns the factual layer. Both must move in parallel, not in sequence.
Case scoping — days one and two. The EOR confirms which local rules apply and whether any prerequisites exist before investigation begins. In Germany, that may mean notifying the works council. In India, it means convening the Internal Committee for POSH complaints. In the UK, the ACAS Code requires considering informal resolution before escalating to a formal hearing.
Investigation planning — by day three. Both parties agree in writing: the allegation summary, who interviews whom, what records will be pulled, and when the outcome meeting happens. That written plan is the procedural baseline if the case is later reviewed by a tribunal or labour authority.
Interviews and evidence. The client company’s HR team conducts witness interviews; they have the access and context the EOR does not.
The EOR advises on scripts, accompaniment rights, and note-taking standards. In the UK, accompaniment by a colleague or trade union representative is a statutory right under the Employment Relations Act 1999, not a discretionary choice.
The outcome. The EOR reviews the proposed decision for legal defensibility before any letter goes to the employee. Tone can reflect the client’s voice. Legally required content is the EOR’s responsibility and cannot be edited out.
The appeal. The reviewer must be someone not previously involved, a standard expectation in UK and European employment systems. Pre-agree this person before any appeal is filed. Leaving it unnamed until an appeal arrives creates avoidable delays that eat into statutory timeframes.
Post-resolution debrief. Once the case closes, both parties should review what the complaint revealed. Recurring grievances about the same manager or the same policy gap are data, not coincidence. Most companies treat closed grievance files as archives. The better ones treat them as diagnostics.
Jurisdiction Snapshots — Six Countries
Local law sets the floor. The EOR must meet it. You must understand it. Here is what actually changes across the six most common EOR destinations.
United Kingdom
The GOV.UK grievance guidance requires a written procedure, a named contact, and an appeals route. The ACAS Code sets the minimum process standard, informal resolution where appropriate, fair investigation, hearing, decision, appeal.
Tribunals can adjust awards by up to 25% for non-compliance. The EOR anchors the formalities. You supply the facts and the remedy.
India
The POSH Act 2013 governs sexual harassment complaints and operates entirely separately from the general grievance process. Key requirements:
- Internal Committee (IC) mandatory for any workplace with 10 or more employees
- IC must include an external member from an NGO or similar body
- Inquiry must be completed within 60 days of receiving the complaint
- Annual IC reporting is mandatory — and a common compliance gap in EOR-managed workplaces
For general grievances, the Industrial Employment (Standing Orders) Act 1946 and applicable state-level labour laws set the applicable process. The EOR, as legal employer, is responsible for IC constitution and reporting even though day-to-day remediation sits with you.
United States
The EEOC’s 2024 harassment guidance was rescinded in January 2026, but the underlying federal statutes — Title VII, ADA, and ADEA, remain fully in force. State law frequently goes further.
California, New York, and Illinois each carry standalone harassment and retaliation statutes that apply regardless of federal position. If you employ through an EOR in a state where you have no entity, the EOR must align its process with that state’s specific rules, not just federal minimums.
Germany
Germany’s Works Constitution Act (Betriebsverfassungsgesetz) gives works councils the right to be informed and consulted on matters affecting employees.
In workplaces with a works council, both the EOR and client need to identify notification or consultation obligations before an investigation concludes. Skipping this step does not just create risk — it can invalidate the process entirely.
Local German legal counsel is not optional on complex cases. See the Germany EOR guide for hiring context.
Australia
The Fair Work Act 2009 governs unfair dismissal and general protections claims. Two numbers matter most:
- 21 days — the window within which an employee can apply to the Fair Work Commission after dismissal
- The burden of proof in general protections claims shifts to the employer once adverse action is alleged
Any change to an employee’s role, hours, or team after a complaint must be documented and justified independently of that complaint. See the Australia EOR guide for further detail.
United Arab Emirates
The UAE Labour Law (Federal Decree Law No. 33 of 2021) governs mainland employment. The Ministry of Human Resources and Emiratisation (MoHRE) is the first escalation point for unresolved complaints before cases proceed to court.
Free zone employees, including those in DIFC and ADGM, are governed by entirely separate regulations. The EOR must confirm mainland versus free zone status at the contract stage, because the applicable grievance authority differs between the two. See the UAE EOR guide for specifics.
Termination-Linked Grievances — The Highest-Stakes Scenario
Termination is where grievances get expensive. A complaint raised by someone who has just been dismissed, or is about to be, carries a different risk profile entirely. Three scenarios create the most exposure in an EOR context.
Constructive Dismissal
This occurs when an employee resigns due to a fundamental breach of contract, unreasonable working conditions, a unilateral role change, or sustained management misconduct the employer failed to address after being notified. The EOR is the legal employer.
But if the conduct happened in your workplace, under your managers, both parties may share liability. A prior grievance that was mishandled or ignored becomes central evidence in any tribunal review.
Retaliatory Termination
Dismissing or materially disadvantaging an employee shortly after they raised a grievance is among the highest-risk acts in employment law. Key points:
- Most jurisdictions treat close timing between a complaint and an adverse action as evidence of retaliation
- In Australia, the burden of proof shifts to the employer under Fair Work Act general protections provisions
- In the UK, dismissal for raising a protected disclosure is automatically unfair under the Employment Rights Act 1996
The EOR must review any proposed termination of a recent complainant before it proceeds. The stated reasoning must be legally independent of the complaint, and that independence must be documented, not just assumed.
Grievance During Redundancy
Employees facing redundancy sometimes raise grievances to pause the process, or because the redundancy itself feels retaliatory. The law in most jurisdictions requires both processes to run concurrently, each following its own separate procedure. Mismanaging the sequencing creates procedural grounds for a claim:
- Pausing redundancy pending grievance resolution is an error
- Dismissing the grievance because redundancy is pending is equally an error
Both the EOR and client company need a designated lead for each parallel track before this scenario arises. Planning it mid-process is too late.
The common thread across all three scenarios is documentation. Every decision made in the period surrounding a termination must carry its own written reasoning, reasoning that does not reference, even obliquely, the employee’s prior complaint.
For broader context on termination exposure in cross-border hiring, see the legal risks of hiring without an EOR on EmployerRecords.
Whistleblowing and Anonymous Reporting in an EOR Setup
Whistleblowing and grievances are not the same thing, and treating them as interchangeable is a compliance mistake. A grievance is a personal complaint about something that affects the employee directly.
A whistleblowing report, or protected disclosure, concerns a matter of broader public interest: fraud, safety violations, legal breaches, financial misconduct. The lane the complaint sits in determines which legal protections apply and which process must follow.
In an EOR arrangement, this distinction matters more than most companies realise. The EOR is the legal employer. If a protected disclosure is mishandled, or if the employee suffers retaliation after making one, the legal exposure lands on the legal employer first.
The EU Framework
EU Directive 2019/1937, transposed into national law across all 27 member states, requires private companies with 50 or more employees to establish internal reporting channels for whistleblowers. Key obligations under the Directive:
- Acknowledge receipt of a report within seven days
- Provide feedback on action taken within three months
- Ensure confidentiality of the reporter’s identity
- Prohibit retaliation explicitly and provide remedies where it occurs
- Allow reporters to choose between internal and external reporting channels
For EOR-managed employees in EU countries, the EOR as legal employer carries these obligations. The client company’s culture and management behaviour are where most whistleblowing triggers originate. Both parties need a shared, functioning channel, not two separate ones that create confusion about where to report.
The UK
The Public Interest Disclosure Act 1998 (PIDA) protects employees who make qualifying disclosures about criminal activity, health and safety risks, environmental damage, miscarriages of justice, or deliberate concealment of any of the above.
An employee dismissed or subjected to detriment after making a protected disclosure can bring a claim, with no qualifying service period required, unlike standard unfair dismissal.
The EOR must ensure its UK employment contracts reference the protected disclosure framework and that its intake process can correctly identify and route a PIDA-qualifying complaint separately from a standard grievance.
India
India’s Whistle Blowers Protection Act 2014 covers disclosures of corruption or wilful misuse of power by public servants. For private sector EOR arrangements, the more relevant mechanism is the Companies Act 2013, which mandates a Vigil Mechanism for listed companies and those meeting certain thresholds.
If the client company is listed or above the threshold, the EOR needs to confirm whether the Vigil Mechanism obligation extends to employees engaged through an EOR structure.
The Practical Design Problem
The structural challenge in an EOR setup is this: the employee identifies with the client company but is legally employed by the EOR. A whistleblowing channel branded by the client company may not be legally sufficient if the EOR is the entity with the statutory obligation to maintain it.
Conversely, an EOR-branded channel may feel remote and untrusted to an employee who has never interacted with the EOR outside of a payslip.
The workable solution is a single intake channel, jointly maintained, that:
- Routes employment-law complaints to the EOR for procedural handling
- Routes ethics and conduct concerns to the client company’s compliance function
- Preserves confidentiality for both streams
- Is clearly communicated to all employees at onboarding, not buried in a handbook
Anonymous reporting adds another layer. Anonymous reports cannot be investigated to the same standard as named ones, but refusing to act on them creates its own risk. The EOR and client company should agree in advance on a threshold: what level of specificity in an anonymous report triggers a formal review, and who leads it.
How EOR Platforms Handle Grievance Case Management
Most EOR platforms are designed around payroll processing, onboarding workflows, and statutory compliance. Grievance handling is a very different operational requirement.
It depends on structured intake procedures, investigation tracking, documentation controls, escalation management, and country-specific compliance decisions. That is where the gap between EOR marketing claims and actual operational capability often becomes obvious.
When evaluating an EOR’s grievance handling capabilities, the important questions are practical rather than promotional:
- Is there a structured case management workflow, or are complaints handled through a general support ticket system?
- Can the platform generate jurisdiction-specific documentation and outcome letters when required?
- Are investigation records stored in a searchable, auditable system, or scattered across emails and chat threads?
- Will your company work with a dedicated HR or employee relations contact, or rotate through a general support queue?
- What response timelines apply when a complaint is marked urgent or legally sensitive?
These details matter far more than most companies realise during vendor selection. A grievance process may appear manageable internally until a complaint escalates to a labour authority, regulator, or tribunal.
At that point, the quality of the documentation trail becomes critical. Either the investigation history is organised, timestamped, and defensible, or it is not.
Some larger EOR providers have invested more heavily in HR advisory infrastructure than others. Deel, for example, supports operations across a large number of jurisdictions and provides access to in-country compliance and legal resources when a case requires local interpretation beyond standard HR guidance.
Remote similarly emphasises country-specific HR support and formal documentation practices as part of its compliance model. Multiplier places more emphasis on dedicated account management, which can become important when a grievance requires coordination between the EOR, the client company, legal counsel, and local HR stakeholders.
The more important point, however, is that no major EOR platform currently offers grievance case management at the same depth as a specialised employee relations or HR investigations system.
Most platforms provide a combination of HR support, compliance guidance, and document management tools rather than a fully developed investigation environment.
In practice, the client company still needs its own internal process discipline. The EOR can support compliance, documentation, and local procedural requirements, but it does not replace the need for clear internal ownership, escalation protocols, and investigation management on the client side.
Where Companies Get Burned — Grievance-Specific Failures
Most grievance failures are not dramatic. They are quiet, a delayed acknowledgment, an undocumented interview, a manager who was never told to step back. By the time the damage is visible, the procedural window has usually closed.
Six patterns repeat most consistently in EOR-managed cases.
No defined intake path. The complaint arrives. HR assumes the EOR was notified. The EOR assumes HR is handling it. Nobody acknowledges the employee. That silence is a procedural failure in most jurisdictions, and it happens entirely because no one pre-agreed who picks up first.
Weak investigation notes. Notes written after the fact, summaries instead of records, files in personal email. A tribunal does not accept “we conducted a thorough investigation” without contemporaneous evidence.
The manager who kept managing. An employee complains about their manager. The manager continues making decisions affecting that employee during the investigation. Each decision may be individually defensible. Collectively, they look like retaliation, and the EOR must prove they were not.
Outcome letters that miss statutory requirements. In the UK, an outcome letter without a clear appeal right breaches the ACAS Code directly. EOR localised templates exist to prevent this. They only help if someone actually uses them.
POSH compliance gaps in India. No functioning Internal Committee, missing external member, annual report never filed. Each is a standalone compliance failure under the POSH Act 2013, regardless of whether any complaint was ever raised.
No pre-agreed appeal reviewer. The employee appeals. Two weeks are spent deciding who conducts it. The tribunal clock keeps running. A pre-agreed reviewer costs nothing to arrange in advance and everything to arrange in a hurry.
The Working Playbook
Good grievance handling in an EOR model does not require a new HR infrastructure. It requires clear agreements, pre-built templates, and a small number of habits that run every time a complaint arrives.
Step 1 — One front door. Create a single intake channel, one email address or HRIS case type, that notifies both your HR lead and the EOR case manager simultaneously. Set an auto-reply that confirms receipt, states the next steps, and includes an anti-retaliation statement. This goes out within 24 hours, every time, without exception.
Step 2 — A written investigation plan within 48 hours. By day two, both parties agree in writing: the allegation summary, who interviews whom, what records will be pulled, and when the outcome meeting happens. Written. Not discussed on a call and forgotten.
Step 3 — Manager step-back protocol. The moment a complaint is logged against a manager, that manager stops making unilateral decisions affecting the complainant. Role changes, project moves, schedule adjustments, all require a second sign-off until the case closes. Document the protocol. Do not rely on the manager’s judgment to self-regulate.
Step 4 — EOR templates, client voice. Use the EOR’s localised letter templates for every formal communication — invitation to hearing, outcome letter, appeal outcome. Adjust the tone to sound like your company. Do not adjust the legally required content.
Step 5 — Retaliation monitoring for 90 days post-close. Flag the complainant and key witnesses in your HRIS. Any material change to their role, compensation, or reporting line during that window requires written justification from the manager making the change. One line. Just enough to create a documented record.
Step 6 — Pre-agreed appeal reviewer. Name this person now, before any case arrives. Typically an EOR HR lead paired with a senior HRBP from the client company who was not involved in the original case. Put the name in the EOR contract or the shared operating protocol.
Step 7 — Post-case debrief within two weeks. One short meeting. What did the complaint reveal? Has the same issue appeared before? Does anything need to change in policy, management, or team structure? Grievances are the most reliable early warning system most HR teams never use as data.
What Good Grievance Handling Looks Like
Most companies know when a grievance process has failed. Few measure it before it does.
Tracking a small number of metrics across your EOR-managed workforce gives you two things: early warning of a pattern before it becomes a claim, and evidence of a functioning process if a case is ever reviewed externally.
These are the metrics that matter:
Time to acknowledgment. The clock starts when the complaint is received. Target: 24 hours. Anything beyond 48 hours in a jurisdiction with statutory acknowledgment requirements is a procedural risk, not just a service gap.
Time to resolution. Measured from receipt to outcome letter. A useful internal benchmark is 30 days for standard cases, 60 days for complex ones. Cases that drag beyond 60 days without a documented reason become harder to defend, and harder for the employee to trust.
Escalation rate. The percentage of complaints that move from informal to formal process. A rising escalation rate signals that informal resolution is failing, often because managers are not equipped to handle complaints at the earliest stage.
Appeal overturn rate. If a significant proportion of appealed outcomes are overturned, the original investigation process has a quality problem. One or two overturns is normal. A consistent pattern is not.
Repeat complaint rate. The same employee, the same manager, or the same team appearing in multiple cases within 12 months is a signal that the root cause was not addressed. Grievances treated as closed files rather than diagnostic data produce this pattern reliably.
Retaliation complaint rate post-close. Any complaint raised within 90 days of a prior case closing, by the same employee or a named witness, should be flagged automatically. This metric is the clearest indicator of whether your post-close monitoring protocol is working.
None of these require a dedicated analytics platform. A shared spreadsheet updated after each case closes is sufficient. The discipline is reviewing it quarterly, with both the EOR and your HR lead in the room.
Checklist — Sanity-Check Your EOR This Week
Most of the gaps covered in this article are not discovered during a crisis. They are discovered because someone asked the right questions before one arrived.
Run through this checklist with your EOR contact. If any answer is unclear or missing, that is where to start.
Conclusion
Grievance handling in an EOR arrangement is a coordination problem before it is a legal one. The legal obligations exist and are well-defined in most jurisdictions. What trips companies up is the gap between who carries those obligations on paper and who has the practical ability to meet them.
The EOR cannot investigate your workplace. You cannot sign the outcome letter on their letterhead. That division is not a problem, it is just how the model works. The companies that handle it well are the ones that mapped the accountability split before a complaint arrived, put it in the contract, and built a small number of repeatable habits around intake, documentation, and post-case review.
The goal is not a perfect grievance process. It is a defensible one, one where the employee knows someone is listening, the paperwork holds up under scrutiny, and the same problem does not appear again six months later.
