Employee

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Employee status depends on the governing source

Different laws use different definitions and purposes. A person may be an employee under the Fair Labor Standards Act, a state wage law, unemployment law, workers’ compensation law, tax rules, or another program even when a different framework reaches another result.

Run each required analysis separately. Preserve the controlling source, date, facts, reviewer, conclusion, and recheck trigger rather than storing one universal employee flag.

The FLSA looks at economic reality

The Wage and Hour Division FLSA page explains federal minimum-wage, overtime, recordkeeping, and child-labor protections for covered employees. Independent contractors do not receive FLSA employee protections through that relationship.

Courts analyze whether the worker is economically dependent on the employer for work or is in business for themself. Contract wording and tax paperwork cannot override the actual relationship.

Federal classification status needs a date stamp

The 2024 DOL rule describes six economic-reality factors. A 2026 DOL compliance page also identifies a February 2026 proposed rulemaking.

DOL Field Assistance Bulletin 2025-1 states that the 2024 rule remains effective for private litigation while the agency uses other guidance for current investigations. This split makes “follow the DOL test” too vague. Record the legal source, forum, enforcement posture, and advice used for each decision.

Tax classification uses another test

The IRS common-law employee page focuses on the business’s right to control what will be done and how, with behavioral, financial, and relationship facts considered.

Tax treatment, FLSA status, unemployment, workers’ compensation, and state wage classification should not be assumed to match. A payroll setup is a result of analysis, not the analysis itself.

ABA work models contain important facts

Relevant facts may include who assigns clients and hours, controls rates, supplies systems and materials, requires methods, provides supervision, bears business expenses, can hire helpers, markets to other customers, accepts or declines work, and bears profit or loss.

Clinical supervision and payer requirements can constrain work for legitimate reasons. Their presence still belongs in the total factual record and does not mechanically decide employment status.

Payer enrollment is a separate question

A payer may credential, enroll, roster, or authorize a person in a defined provider role. That status does not determine wage-law classification or permit the practice to ignore employment duties.

Likewise, employee status does not establish licensure, competence, clinical authority, supervision compliance, payer recognition, billing eligibility, or claim payment. Maintain separate gates.

A fictional configuration review

A fictional practice locks 12 worker configurations before a new service launch. Counsel and HR approve seven as employee configurations, identify two genuinely independent vendor relationships under the applicable tests, and hold three for missing control, investment, or state-law facts.

Classification review reach is 9 of 12, or 75%. Employee configurations are 7 of 9 completed reviews, while the original-cohort employee share is 7 of 12. The three holds remain visible and cannot be released to work.

These measures describe workflow status. They do not establish that the legal conclusions are correct.

Classify before onboarding work begins

For an employee path, activate payroll, tax withholding, unemployment, workers’ compensation, wage notices, timekeeping, leave, accommodations, required postings, policies, training, and benefit eligibility by their own triggers.

Training, orientation, documentation, meetings, travel, and after-hours messages can be compensable work. Do not use an unpaid “trial shift” or contractor agreement while classification remains unresolved.

Recheck when facts change

A new schedule, exclusivity term, rate method, supervision structure, equipment requirement, service location, management layer, payer contract, or state can change the analysis.

Set event-based review triggers and a periodic audit. Compare written agreements with schedules, messages, invoices, supervision records, and actual practice. Repair inconsistencies through counsel and payroll rather than rewriting history.

Store a dated classification packet for each governing framework. It should identify the controlling test, current rule or enforcement posture, facts considered, unresolved facts, reviewer, conclusion, system activations, and next trigger. When a source changes, open a new review instead of overwriting the prior basis.

Useful evidence fields

• worker, entity, work location, role, and service
• each governing law or program and current source
• control, investment, permanence, integration, skill, and profit-or-loss facts
• tax, wage, unemployment, workers’ compensation, benefit, and payer conclusions separately
• reviewer, decision date, effective date, exception, and recheck trigger
• payroll and timekeeping activation evidence

Access to legal analysis and personal data should be role-limited.

Questions owners should ask

• Which legal test controls this exact issue?
• What does the working relationship look like in practice?
• Which facts are missing or likely to change?
• Have federal and state tests been analyzed separately?
• Which employee systems must activate before work?
• Are payer and clinical gates stored separately?
• When will the classification be reviewed again?