Worker Classification Can Kill a Harassment Lawsuit Before Trial

Lively's Federal Claims Dismissed on Classification Alone

Blake Lively sued the production entities behind the film It Ends with Us, alleging sexual harassment, hostile work environment, and retaliation under Title VII of the Civil Rights Act and other federal statutes. The court never reached the merits. Instead, it applied a threshold test: was Lively an employee or an independent contractor? Title VII covers only employees.

The court found her to be an independent contractor. The reasoning rested on a multifactor test examining the totality of the working relationship. Lively had significant creative control over her performance, her work required specialized skill, the role was limited and project-based, and her compensation was tied directly to the project rather than a salary structure. Because she failed the employee threshold, all ten of her federal discrimination and retaliation claims were dismissed before trial.

Other claims under state law survived and the case eventually settled, but the federal gatekeeping proved decisive: one classification decision made the entire federal statutory framework irrelevant.

Classification Risk Grows as Contractor Use Expands

The case underscores a common misstep: assuming that job centrality determines employment status. Lively was the lead actress—obviously central to the film's success. That centrality did not override the contractor factors. For HR teams, the implication is stark: the person most essential to your operation may have no federal antidiscrimination protections if the relationship is structured as a project-based engagement with direct compensation.

Three structural risks emerge. First, exercising too much control over schedules, methods, or performance can flip a contractor into an employee in the eyes of a court, even if the contract says otherwise. Second, compensation that resembles a salary or hourly wages raises the same question. Third, scope creep, ongoing engagement, or unclear expectations at the outset can undermine contractor classification retroactively.

The key tension: classification limits federal exposure but does not eliminate it. Lively's state-law retaliation claims proceeded despite the federal dismissal. So while contractor status creates a federal law firewall, state statutes, common law theories like breach of contract, and other avenues may still apply. The classification buys protection, not immunity.

Consistency Between Contract, Relationship, and Operations

The defense of independent contractor status depends entirely on alignment. If the contract says project-based but operations treat the person as a permanent team member reporting to a manager, the classification collapses. If compensation is labeled as a project fee but paid in regular installments like a salary, courts will discount the label.

For HR, the audit involves three layers. First, review the engagement contract: is the scope bounded? Is the term finite? Is compensation tied to deliverables or a fixed project fee, not hourly wages or salary? Second, observe day-to-day operations: who controls the schedule, the methods, the performance standards? Third, document the original expectations: was scope expansion discussed and approved, or did it drift? Misalignment between any two of these layers creates litigation risk.

The Lively case suggests courts will examine the full picture, not just the label on the contract. Contractors with central roles, high skill, and clear project boundaries are defensible. Contractors who begin to resemble permanent employees, subject to detailed operational control and salary-like pay, are not.