All articles

Content moderators: employee or contractor? What actually decides it under U.S. law

9 min read

Most operators think about the review queue as a cost line, not a legal category. Someone has to look at every new ad before it goes live, decide whether the photos meet the rules, flag the ones that need a second look, and reject the ones that do not belong on the site at all. Hiring that person as a freelancer, on a per-listing rate or a flat monthly fee with a 1099 at the end of the year, feels like the same decision as hiring a freelance designer or a bookkeeper. It is not the same decision, and the gap between the two is where a surprising number of small directories end up owing years of back wages to someone they thought they had already paid in full.

The reason has nothing to do with adult content specifically. It is about what the job actually looks like once you write it down: a person who works your hours, follows your written policy, uses your dashboard, answers to your escalation process, and does the same task every single day for as long as the relationship lasts. Every test that decides whether a worker is an employee or a contractor, federal or state, asks some version of the same two questions, and a content review queue answers both of them the wrong way for the "contractor" label almost every time.

Why review work is the hardest job on the site to call freelance

The oldest and still most widely used test for employee status looks at control: who decides when the work happens, how it gets done, and what tools are used. A freelance designer picks their own hours, uses their own software, and can turn down a project. A moderator working your queue cannot. You set the shift, you write the rules for what gets approved and what gets kicked back, you provide the moderation dashboard, and you decide what counts as a violation serious enough to escalate. That is not a criticism of how moderation has to run. It is simply what control looks like on paper, and it is the first thing an investigator or a plaintiff's lawyer checks.

The second question is whether the work is part of the hiring business's own operation, or something separate and incidental to it. A graphic designer who redesigns your logo once is doing something outside your normal business. A person who reviews every listing before it can appear on your site is doing the thing your site cannot legally or practically operate without. Content review is not a side task you happen to outsource. It is the trust layer that keeps advertisers payable and keeps the site off a payment processor's watch list. A worker performing a function that is this central to the business is exactly the profile every classification test was built to catch.

None of this changes because the moderator works from home, sets their own start time within a window, or is paid per listing instead of per hour. Those details affect how strong the case is, not which direction it points. A queue that runs every day, under your written rules, using your tools, for your core function, points toward employee status under nearly every version of the test in use in the United States right now.

The two tests that apply, and why neither one is going away

At the federal level, the rule has moved twice in two years and is likely to move again before it settles. The Department of Labor's 2024 rule set out a six-factor "totality of the circumstances" test that made it harder to classify a worker as a contractor. In May 2025, the department told its own investigators, through an internal enforcement memo, to stop applying that 2024 test and go back to the narrower approach the agency used before it, built around control and the worker's opportunity for profit or loss. In February 2026, the department went further and proposed a new rule that would formally replace the 2024 standard with that narrower approach. As of this writing, that proposal has not been finalized. The public comment period closed at the end of April 2026, and the department has given no date for a final rule.

None of that back and forth changes what a court does when a moderator sues you directly. The 2025 enforcement memo only tells the department's own investigators how to prioritize their cases. It does not bind a judge, and it explicitly says so. The 2024 rule remains the standard a federal court applies in a private wage lawsuit unless and until it is formally replaced, and legal challenges to that 2024 rule are still working their way through federal appeals courts with no final outcome yet. An operator who reads "the department stopped enforcing the strict rule" as "the strict rule no longer applies" is reading a policy memo as if it were a repeal, and a moderator's lawyer will not make that same mistake.

State law sits on top of all of this and does not wait for Washington. California's AB5 law presumes every worker is an employee unless the hiring business proves all three parts of what is called the ABC test: the worker is free from the company's control, the work falls outside the company's usual business, and the worker runs an independently established business doing the same kind of work for other clients. That middle prong, work outside the company's usual business, is the one that sinks the most cases, because it asks a question a review queue cannot answer favorably: is checking every listing before it goes live part of what a listings site does, or is it something else entirely? No court has yet ruled on that exact question for a classifieds directory, but the reasoning courts have already applied to comparable core functions leaves very little room for a different answer. Other states use their own versions of a similar test, and a worker's location, not your company's, generally decides which one applies.

The bill nobody prices before day one

California backs its test with a specific number. Willfully misclassifying a worker there carries a civil penalty of five thousand to fifteen thousand dollars per violation, rising to ten thousand to twenty five thousand dollars per violation if the state finds a pattern of doing it rather than a single mistake. On top of that sits ordinary back pay: unpaid overtime and meal and rest break premiums, recoverable for three years under the wage claim alone, stretching to four years if it is paired with the state's separate unfair competition claim, which most plaintiffs' lawyers file as a matter of course. None of this requires the state to catch you first. A single former moderator with a lawyer can start all of it.

Under federal law, a worker who wins a misclassification claim can also recover liquidated damages equal to the unpaid wages, which in practice doubles the bill. An employer can avoid that doubling only by proving it acted in good faith and had objectively reasonable grounds for believing the classification was correct, and courts read that defense narrowly. Believing a lawyer or a payroll vendor told you it would be fine is not, by itself, enough; the belief has to be reasonable given what the job actually looked like, and a queue run on your schedule with your rules is a hard set of facts to explain away after the fact.

The part that catches most operators off guard has nothing to do with wages. Independent contractors are not covered by your workers' compensation policy, because that policy only covers employees. If a moderator is later found to have been misclassified, an injury claim from that person, including a psychological injury claim tied to what they had to look at, becomes your direct, uninsured liability rather than a claim your comp carrier absorbs. No reported case has yet combined a misclassified moderator with a psychological injury claim, so this is a reasoned consequence of two well established rules rather than a decided precedent, but the underlying risk in the job itself is not theoretical. Content moderators employed through staffing vendors at larger platforms have already won real settlements over psychological harm from reviewing graphic material: Facebook's vendor-employed moderators settled a claim for fifty two million dollars in 2020, and YouTube's for four point three million dollars in 2022. Those workers were employees of a vendor, not misclassified contractors, so the theory of liability was different from the one described here, but the cases prove the underlying injury is real and litigated, not hypothetical. Strip out the workers' comp coverage those vendor employees had, and the same injury becomes a claim with nowhere else to land.

What to actually put in place

The daily review queue, the one running under your written rules on a recurring schedule, should sit on payroll as a W-2 role, or should sit entirely inside a vendor company whose own business is moderation, so that the worker is that vendor's employee rather than yours. Comparing what each of those architectures actually costs before choosing one is worth doing properly rather than guessing, because the cheapest option on paper is rarely the cheapest option once a misclassification claim is added to it. What does not belong in either category is a freelancer hired through a gig marketplace to do the same daily work a payroll employee would do, just without the paperwork.

Save contractor status for work that is genuinely separate from the daily queue: an outside lawyer who reviews your moderation policy once a year, a consultant who audits your escalation process after an incident, someone paid for a single defined project rather than an ongoing function. If the person answers to your schedule and does the same task every working day, the label on the invoice will not save you.

For moderators working from outside the country, a plain contractor agreement carries the same exposure translated into local labor law, which is frequently stricter than U.S. law on this exact point. An employer of record handles the local employment relationship correctly and is worth the added cost for anyone doing recurring work, rather than treating a foreign time zone as a workaround for the classification question.

Check your insurance before you need it, not after. A standard commercial policy is written around ordinary bodily injury and will not necessarily respond to a psychological injury claim from a moderator, and figuring out what your coverage actually excludes is worth doing before the exposure described above becomes a live claim rather than a paragraph in an article. Put the classification analysis in writing before the relationship starts, not after someone asks a lawyer about it, and apply the strictest test that could plausibly reach your business rather than the one that is most convenient to cite. A dated file explaining why you classified the role the way you did is cheap insurance against a decision that, if wrong, does not get cheaper with time.

Try the DEMO

Escort directory software, ready to go