Employment
Worker classification is a question that needs revisiting
Classification decisions are made once, early, and then inherited. The work changes; the label does not. A periodic review is inexpensive relative to what it prevents.
- Author
- Mara Ellison
- Published
- Reading time
- 3 min read
- Category
- General information
Most classification problems do not begin with a bad decision. They begin with a reasonable decision that was never revisited. A company engages a contractor for a defined project on defined terms. Two years later the same person works standard hours, uses company systems, reports to a manager and is treated as part of the team — but the paperwork still says contractor, because nobody had a reason to revisit it.
The same pattern applies to exempt and non-exempt status. A role is classified as exempt at the point of hire. The role evolves. The classification does not.
Two separate questions
Classification involves two distinct determinations, and confusing them is common. The first is whether someone is an employee or an independent contractor. The second, for employees, is whether they are exempt from overtime requirements. A worker can be correctly treated as an employee and incorrectly treated as exempt.
Both are determined by the substance of the working relationship rather than by what the parties call it or what an agreement states. A signed contractor agreement is evidence, not an answer.
The tests vary, and that matters
Different legal frameworks apply different tests to the same relationship. Tax authorities, wage and hour regimes, unemployment insurance systems and workers' compensation schemes may each use their own standard, and state law can differ substantially from federal law and from other states.
The practical consequence is that a worker may be properly classified for one purpose and improperly classified for another, and that a company operating across several states may face different answers for identical roles. For any company with a distributed or remote workforce, this is worth mapping explicitly rather than assuming uniformity. Specific tests change over time, so a review should look at current requirements in each relevant jurisdiction rather than relying on a prior analysis.
Signals worth examining
Without reciting any particular test, certain features of a relationship tend to attract attention in most frameworks:
- Control over how, when and where the work is performed, rather than over the result.
- Integration into the company's core operations rather than a discrete, bounded deliverable.
- Duration and exclusivity — long, full-time engagement resembling employment.
- Who supplies equipment, systems and tools.
- Whether the worker has genuine opportunity for profit or loss and serves other clients.
- Whether the worker is managed, reviewed and scheduled like an employee.
For exempt status, the analysis usually turns on actual duties and compensation rather than job title. A title containing the word "manager" carries no weight if the role does not involve the responsibilities the exemption requires.
Why the exposure compounds
Misclassification is expensive because the consequences accumulate across categories: unpaid overtime, payroll taxes, benefits eligibility, penalties and interest, and the cost of defending the position. Because a single classification decision often applies to a group of similarly situated workers, an issue identified for one person tends to apply to all of them, across the full period the arrangement has been in place.
A periodic review
A classification review is a contained piece of work and worth doing on a schedule rather than in response to a problem. A workable version:
- List every worker, their classification, their location, and the date the classification was set.
- For contractors engaged more than roughly six months, compare the current working relationship to the original agreement.
- For exempt employees, compare actual duties to the requirements of the claimed exemption.
- Flag any state where the company now has workers but has not reviewed local requirements.
- Address what the review finds, and record the reasoning behind each determination.
That last step matters. A documented, reasoned determination made in good faith is a considerably better position than a classification nobody can account for.
Because the applicable tests differ by jurisdiction and by purpose, a review should be conducted against current requirements in the places the company actually operates.