What does the EAT signal on up-or-out performance models mean for UK professional services and tech firms?
Last updated: 29th April 2026
The Employment Appeal Tribunal has cast doubt over whether "up or elsewhere" performance management frameworks can survive legal scrutiny when applied to long-tenured staff. For UK professional services and tech firms that borrowed their career progression structures wholesale from Big 4 consultancies, this is a doctrine-level warning shot.
The EAT's signal stops short of enforcement, but it creates binding uncertainty. If you're running a performance model that ties employment continuation to promotion timelines rather than role-based capability standards, your HR and legal teams need to understand what's changed and what hasn't.
Picture the conversation that gets you in trouble: a senior associate of seven years, performing well in their current role, told they have 18 months to make partner or leave. No documented capability concerns, no support plan, just a promotion clock. That's the moment a career progression framework starts to look like a breach of mutual trust and confidence, as highlighted in Pal v Accenture (2026) where a manager employed since 2009 successfully challenged similar treatment.
What this changes in practice
The EAT has said, in effect, that if you're using a promotion deadline to move someone out, with no real capability evidence behind it, you may be breaching the implied term of mutual trust and confidence. The longer they've been with you, the riskier that conversation gets.
Ordinary unfair dismissal protection generally kicks in at two years' service. That means the people most likely to bring a claim, and most likely to win it, are precisely the long-tenured employees an up-or-out model is designed to move on.
The compensatory award is capped at the lower of a year's gross pay or the statutory cap (£123,543 from April 2026), so the financial exposure on a senior salary is real, predictable, and worth modelling before you start the exit conversation, not after.
An up-or-out model differs from a capability procedure because up-or-out ties employment continuation to promotion timelines, while capability procedures tie employment continuation to meeting the current role's objectively defined performance standards.
A PIP differs from an up-or-out "time-to-promote" review because a PIP is designed to remediate performance in-role with defined support and measurable milestones.
EAT decisions bind tribunals on points of law. First-instance tribunal findings turn on the facts of one case and don't set precedent. So when the EAT speaks, every employer's playbook should be read against it.
What did the EAT actually signal?
The Employment Appeal Tribunal questioned whether performance management models requiring employees to be ready for promotion within defined timeframes can amount to constructive dismissal when applied to push out long-tenured staff. This is a doctrine-level statement, not an enforcement-level ruling from a first-instance tribunal.
The distinction matters. EAT guidance creates binding legal principles that shape how Employment Tribunals approach future cases. When the EAT expresses doubt about a practice, tribunals will scrutinise similar arrangements more closely. But this isn't the same as a tribunal finding against a specific employer with a specific set of facts.
What the EAT has done is put professional services and tech firms on notice. The "up or elsewhere" model that works culturally in partnership-track environments may not survive Employment Rights Act scrutiny when the employee being exited has built up significant tenure and there's no genuine capability concern beyond "not ready for the next level."
What is up-or-out performance management?
Up-or-out (also called "up or elsewhere") is a performance management and career progression model that requires employees to achieve promotion within a defined period or leave the organisation. The model originated in partnership-track professional services firms where the business model depends on a pyramid structure with few partners and many associates.
The logic is straightforward. If someone isn't progressing toward partnership, they're occupying a development slot that should go to someone who will. The firm invests heavily in training and expects either a return through partnership or an exit that creates space for the next cohort.
Here's the problem. Many mid-market professional services and tech firms adopted this framework without the partnership economics that justify it. They borrowed the cultural expectation of "progress or leave" without building the legal infrastructure to support it. The result is a performance management approach that looks like capability management but functions as tenure management.
Why does this look like constructive dismissal?
Constructive dismissal occurs when an employee resigns because the employer's conduct amounts to a fundamental breach of contract. The implied term of mutual trust and confidence is the most common basis for these claims. It requires employers not to act in a manner likely to destroy or seriously damage the employment relationship without reasonable and proper cause.
The EAT's concern centres on how up-or-out frameworks interact with this implied term. When an employer tells a long-tenured employee "you must be ready for promotion by X date or we'll manage you out," and there's no genuine capability concern about their current role performance, the employer may be breaching mutual trust and confidence.
The critical question is whether the employer has reasonable and proper cause. A genuine capability concern about someone's performance in their current role is reasonable cause. A structural preference for promotion-track employees over steady performers may not be.
Most competitor content discusses this as a culture issue. But the compliance reality is more specific. The evidential burden in capability processes requires documented performance standards, support measures, and a reasonable improvement window. Up-or-out frameworks often skip this because the concern isn't capability in the current role. It's pace of progression.
How does this interact with the Employment Rights Act?
The Employment Rights Act 2025 strengthened unfair dismissal protections and increased tribunal scrutiny of performance management processes. The EAT's signal about up-or-out frameworks fits within this broader shift toward employee protection.
For constructive dismissal claims, the employee must generally have at least 2 years' continuous service to qualify for ordinary unfair dismissal protection. This makes long-tenured staff the highest-risk population for up-or-out exits. They have the qualifying service to bring claims, and they have the tenure that makes "not progressing fast enough" look less like capability management and more like forced exit.
UK "protected conversations" under section 111A of the Employment Rights Act 1996 generally do not protect discussions where there is improper behaviour. They also don't prevent evidence being used in claims such as discrimination, harassment, or whistleblowing detriment. If your up-or-out conversation touches on any protected characteristic or suggests retaliation, the protection evaporates.
Which sectors are most exposed?
Professional services firms with partnership-track structures face the most direct exposure. Law firms, accountancies, and consultancies that adopted up-or-out models from Big 4 templates need to review whether their implementation matches the legal requirements for capability management, particularly given the UK's 3.4 million professional services jobs potentially affected.
Tech firms present a different risk profile. Many adopted "up or elsewhere" language from Silicon Valley without the at-will employment framework that makes it work in the United States. In the UK, you can't simply exit someone for not progressing fast enough. You need documented capability concerns, a fair process, and evidence of support.
Mid-market companies in both sectors face particular challenges. They often lack the in-house legal expertise to distinguish between legitimate capability management and constructive dismissal risk. They've built performance frameworks that feel culturally appropriate but may not survive tribunal scrutiny.
Teamed's analysis of global employment patterns shows that UK-based mid-market firms expanding internationally often replicate their UK performance frameworks across jurisdictions. This creates compounding risk. In France, terminating an employee commonly requires a formal process with written summons, a pre-dismissal meeting, and a dismissal letter stating the reasons. Procedural defects can create separate compensation exposure even when there's a substantive reason. In Germany, works council co-determination obligations can affect the timing and validity of terminations and performance-related policies.
What about long-tenured staff specifically?
Long-tenured employees represent the highest-risk population for up-or-out exits. They have the qualifying service for unfair dismissal claims. They have documented performance history that may contradict sudden "not ready for promotion" assessments. And they have the institutional knowledge that makes "not progressing" look more like role stability than capability failure.
In the UK, statutory redundancy pay entitlement generally requires at least 2 years' continuous service. This increases termination cost sensitivity for long-tenured staff in up-or-out models. But the bigger exposure isn't redundancy pay. It's the compensatory award for unfair dismissal, which can reach the statutory cap or one year's gross pay.
Choose a role redesign and redeployment assessment before exit when business need has changed and the employee's historic performance is strong. Role mismatch cases are higher-risk for constructive dismissal arguments than true capability cases. If someone has performed well for years and suddenly "isn't progressing," the tribunal will ask what changed.
What to do before your next review cycle
The EAT's signal doesn't require immediate policy changes, but it does require immediate risk assessment. Here's what mid-market professional services and tech firms should prioritise.
First, audit your performance framework language. Does it tie employment continuation to promotion timelines, or to meeting current role standards? The distinction matters legally even if it feels similar culturally. Choose a capability-based performance process over an up-or-out pathway when the role has objective output metrics and the organisation can document support, training, and a reasonable improvement window tied to role requirements.
Second, review your long-tenured population. Who has 2+ years' service and is currently in an "up or elsewhere" conversation? These are your highest-risk exits. Choose a settlement-led exit strategy (with legal advice) when the performance concern is real but the evidential record is weak, the employee is long-tenured, or there is heightened risk of discrimination, whistleblowing, or retaliation allegations.
Third, strengthen documentation and calibration controls. Choose enhanced documentation and calibration controls when your performance model uses forced distribution, because inconsistent scoring across teams is a predictable trigger for grievances and subsequent litigation.
Fourth, consider your international footprint. If you're running the same performance framework across UK, France, Germany, and the Netherlands, you're facing different termination formality and employee protection requirements in each jurisdiction. Most HR guides ignore this cross-border operational problem, but it's where mid-market firms get caught out.
How does employment structure affect this risk?
Most guidance doesn't connect up-or-out risk to employment structure choices. But whether you're using an Employer of Record versus an owned entity affects who is the legal employer, who runs the process, and how local procedural rules change the playbook country by country.
An EOR is a third-party organisation that becomes the legal employer of a worker in a specific country, handling payroll, tax withholding, statutory benefits, and local compliance while the client controls day-to-day work. When you're using an EOR, the EOR is the legal employer. Performance management processes need to align with the EOR's policies and local legal requirements, not just your internal frameworks.
This creates both risk and opportunity. The risk is that your internal "up or elsewhere" expectations may conflict with the EOR's local employment obligations. The opportunity is that EOR providers with genuine expertise can help you navigate local termination requirements before you create exposure.
Teamed's work with over 1,000 companies on global employment strategy shows that performance management alignment is one of the most overlooked aspects of international expansion. Companies replicate their home-country frameworks without understanding how local employment law changes the rules.
Choose an EOR when you need to employ in a new European country in weeks rather than months and you don't yet have enough headcount or revenue certainty to justify creating and maintaining a local legal entity. Choose local entity formation when you expect sustained in-country hiring, need direct sponsorship of local benefits and policies at scale, or the total ongoing EOR fees would exceed the internal and external costs of running payroll and compliance in that jurisdiction.
The honest next step
The EAT's signal creates a window for proactive risk management. You don't need to abandon performance standards. You need to ensure your framework can survive tribunal scrutiny if someone with 5+ years' tenure challenges their exit.
This means separating "not progressing fast enough" from "not meeting role requirements." It means documenting support, training, and reasonable improvement windows. It means calibrating performance ratings consistently across teams so that forced distribution doesn't create arbitrary outcomes.
For mid-market firms operating across multiple jurisdictions, it also means understanding how your UK framework translates (or doesn't) into local employment law requirements. The performance conversation that's legally defensible in London may create immediate exposure in Paris or Berlin.
If you're not sure your current framework would hold up, or you're running performance management across multiple countries and the approach is drifting, talk to an expert. You'll get a named specialist who has sat with companies in exactly your position, walked through the files, and helped them quietly tighten the process before anyone had to find out the hard way.
