Updated 2026-09-30
from the news desk
Can AI be an employee? U.S. labor statutes define employees as individuals
The Fair Labor Standards Act and the ADA both define employee as an individual. A Supreme Court labor case reads employee broadly, but the worker in that case was still a person serving two masters, not software.
On the Fair Labor Standards Act, the ADA and the Supreme Court's Town & Country decision, the answer is no. The statutes say “The term “employee” means any individual employed by an employer.” and “The term “employee” means an individual employed by an employer.”, and Town & Country reads employee broadly under the National Labor Relations Act without treating software itself as the worker.
What the statutes say
The Fair Labor Standards Act, in 29 U.S.C. § 203, defines employer this way: “Employer” includes any person acting directly or indirectly in the interest of an employer in relation to an employee and includes a public agency.” The same section defines employee this way: “The term “employee” means any individual employed by an employer.” Section 203 also says employ includes to suffer or permit to work.
One straightforward reading of that structure is that the Act can cast a wide net around work relationships while still limiting the status of employee to an individual. Section 203 broadens the idea of employment by describing when a person is treated as employing someone. But the same section still uses individual when it names the employee.
The rest of § 203 points in the same direction. The statute discusses topics such as child labor, tipped employees, volunteers, parents, spouses and children working in agriculture, and elementary and secondary schools. Those are all details in the statute's own text. One reading is that Congress wrote this section around human workers and human institutions, not around software systems.
The ADA, in 42 U.S.C. § 12111, repeats the same basic definition. It says “The term “employee” means an individual employed by an employer.” The ADA section then defines a qualified individual as someone who can perform the essential functions of the position, with or without reasonable accommodation, and it lists accommodations that may include job restructuring, modified schedules, readers, interpreters, and equipment changes.
That matters because the ADA definition does not just use the word individual once. The surrounding provisions keep building a framework around human employment. Section 12111 also states that, for employment in a foreign country, employee includes a U.S. citizen. It defines covered entities as employers, employment agencies, labor organizations, and joint labor-management committees. On this text, the legal actors are people and institutions, even when the statute reads broadly.
So the narrow answer is not that software can never matter at work. The narrower and better-supported answer is that these federal definitions do not name software as the employee. They name an individual.
What the Supreme Court's broad reading still does not do
The strongest push against an overly narrow answer comes from the Supreme Court's labor cases. In NLRB v. Town & Country Electric, the Court considered whether a worker could still count as an employee under the National Labor Relations Act while also being paid by a union to help organize the company. The Court held that the answer was yes.
In explaining why, the Court quoted the NLRA's definition of employee: “The term 'employee' shall include any employee, and shall not be limited to the employees of a particular employer.” The Court said the National Labor Relations Board could lawfully read that language to include company workers who were also paid union organizers. The Court also noted that job applicants can count as employees for purposes of anti-discrimination rules under the Act.
That opinion matters here because it shows that employee can be read broadly in labor law. The Court did not confine the term to a simple one-employer, one-paycheck picture. The Court also rejected the company's argument that a paid organizer had to be only the union's servant. In the Court's common-law agency discussion, the key question was whether one person could serve two masters without abandoning service to one of them.
The Court also refused to shrink the category of employee because of practical worries about loyalty or disruption. When the company warned about those concerns, the Court answered: “The law offers alternative remedies for Town & Country's concerns, short of excluding paid or unpaid union organizers from all protection under the Act.”
Still, Town & Country does not get all the way to AI. Every worker in that case was a person: job applicants, union members, a company worker, or a union official. The Court's examples and its agency analysis were all about whether a human worker could have overlapping roles. So Town & Country is best read as a case about breadth within human employment, not as a case that detaches employee status from personhood altogether.
The strongest case for a broader reading
The best case for saying the answer could someday be yes starts from the breadth of these texts. Section 203 of the Fair Labor Standards Act says employ includes to suffer or permit to work. Town & Country says employee under the NLRA can extend beyond a narrow payroll intuition. One reading of those materials is functional: labor law can care about who is performing assigned work and who controls the work, not just about labels.
On that reading, a sufficiently autonomous AI system could look worker-like in ordinary language. If software takes assignments, carries them out, and operates under a firm's direction, an advocate could argue that the law should focus on function rather than biology or payroll form. Town & Country gives that argument some shape because the Court there resisted a formal status objection and accepted a broad reading of employee.
But the same documents also show why that argument is not the current rule. The Fair Labor Standards Act does not stop at a functional description of work; it still says employee means an individual. The ADA does the same. And the surrounding provisions keep returning to human markers: U.S. citizenship in foreign employment, parents and spouses, children, tips, readers, interpreters, and school definitions.
Town & Country points the same way. The Court's common-law discussion asked whether a worker could be the servant of two masters at once. That is a broad rule about dual service. It is not a rule that software can itself hold the legal status of employee.
So the strongest pro-AI reading available from these materials is limited. It supports the idea that labor law definitions can be broader than an employer may want, and that complicated work relationships do not automatically defeat employee status. It does not support the further step that a nonhuman system already fits the statutory word individual.
What would have to change
Nothing in § 203, § 12111, or Town & Country says that software, a model, or an AI agent is an employee. A future yes would likely need different statutory text or a different binding interpretation that expressly says an AI system counts for this purpose.
That is why this question is separate from debates about capability. Even if software performs tasks that a business assigns, the current texts discussed here place employee status on an individual and place employer or covered-entity status on persons and institutions. The ADA states: “The term “covered entity” means an employer, employment agency, labor organization, or joint labor-management committee.”
The same legal-status issue appears in other contexts on this site, including whether AI can sign a contract, whether AI can be a judge, and the broader idea of electronic personhood. On the labor materials cited here, though, the conservative reading is also the strongest one: software may be involved in doing work, but the employee is still the individual the statute recognizes.
Frequently asked questions
Does doing the work make AI the legal employee?
No on the texts cited here. The Fair Labor Standards Act says employee means an individual, and the ADA uses the same definition. Section 203 of the FLSA says employ includes to suffer or permit to work, but that expands the employment relationship without changing the statute's definition of who the employee is.
Can one employee have two employers at once?
Town & Country says yes in at least one labor-law setting. The Supreme Court held that a worker could still be a company's employee under the National Labor Relations Act even while a union also paid that worker to help organize the company.
Do job applicants count as employees in labor law?
In Town & Country, the Supreme Court noted that, under established NLRA doctrine, job applicants can count as employees for purposes of the Act's protection against discrimination in hiring. That point is specific to the NLRA context described in the opinion.
Do these materials create any separate AI worker category?
No. Section 203, § 12111, and Town & Country do not create a separate category for AI workers. The current texts discussed here use employee for an individual and place the other legal roles on employers, agencies, unions, and related entities.
Caveats: The discussion of the National Labor Relations Act is single-sourced to the Supreme Court's 28 November 1995 Town & Country opinion, which quotes the NLRA definition and describes the Board's interpretation. No separate NLRA statutory text or NLRB materials are cited here.