A worker-classification decision should happen before payroll, tax withholding, benefits, notice rights, overtime assumptions or a contractor invoice routine harden into practice. The label on the agreement is only one piece of evidence. In the United States, different legal regimes can use different tests; in the United Kingdom, tax status and employment-law status can also diverge. That means the useful question is not “What do we want to call this person?” but “What does the real working relationship look like under the rules that apply here?”

As of 5 October 2026, the U.S. Department of Labor’s own materials still describe the 2024 Fair Labor Standards Act classification rule while also flagging a 2026 proposal to replace it and a different current enforcement position. The IRS separately applies common-law control principles for federal tax purposes. GOV.UK likewise warns that a person can have one status for tax and another for employment rights. Those moving parts are exactly why a classification file should record facts, not merely conclusions.

Use the following sequence before signing, renewing or materially changing the relationship.

1. Write down the legal questions before collecting facts

Start with the jurisdictions and consequences that actually matter. A cross-border marketing consultant working from London for a U.S. company can raise different questions from a California delivery driver or a UK software engineer supplied through an intermediary.

At minimum, identify:

  • where the individual physically performs the work;
  • where the hiring entity is established;
  • whether a staffing agency, personal service company or other intermediary sits between the parties;
  • which wage-and-hour, tax, social-insurance and employment-rights rules may apply;
  • whether state, provincial or sector-specific rules use a stricter test.

This prevents a common mistake: answering a tax question and assuming the employment-rights question is therefore settled.

Decision rule: if two legal regimes may apply, create two columns in the file and test the same facts under both. Do not force one label to answer every statute.

2. Map control in practice, not only in the contract

Ask who decides how, when and where the work is done. Look at the ordinary week rather than an exceptional busy period.

Useful facts include whether the business:

  • sets a mandatory schedule;
  • requires approval for time off;
  • assigns tasks in a detailed sequence;
  • supervises methods rather than outputs;
  • restricts work for competitors;
  • sets the price the worker may charge;
  • requires use of the business’s systems, branding or scripts beyond what is genuinely necessary.

Then test the reverse. Can the worker decide how to deliver the result, decline work, negotiate price, choose helpers where lawful, or serve multiple customers?

Control is not a single switch. Safety requirements, legal compliance, information-security controls and customer specifications may be necessary without proving employee status by themselves. The question is what the whole pattern shows.

3. Follow the money and the risk

A contractor relationship usually needs more than an invoice template. Record whether the person can make business decisions that affect profit or loss.

Check:

  1. Who sets the rate?
  2. Can the worker negotiate different rates for different projects?
  3. Does the worker invest in a business that can serve multiple customers?
  4. Can efficient management increase profit, or is income mainly the product of hours assigned?
  5. Who absorbs rework, idle time, marketing cost and ordinary operating expense?

Do not overvalue a laptop or phone. A worker buying basic tools needed to perform the job is different from making entrepreneurial investments that expand market reach or productive capacity.

4. Test permanence and dependence

A six-week engagement is not automatically independent contracting, and a long relationship is not automatically employment. Duration is useful only with context.

Look for whether:

  • the relationship is indefinite or repeatedly renewed as a continuing role;
  • the worker depends on one business for most available work;
  • the work continues as long as the business needs the function;
  • the worker markets services to others between projects;
  • the engagement is tied to a defined result, milestone or specialist assignment.

A useful internal question is: If this client disappeared tomorrow, would the person still have an operating business, or mainly lose their job? That is not a legal test by itself, but it exposes facts worth examining.

5. Ask whether the work is central to the business

In some legal tests, whether the function is integral to the hiring entity’s business matters. Avoid the simplistic version — “everyone is important, therefore everyone is an employee.”

Instead describe the function. A bakery hiring a one-off electrician is different from a bakery engaging people every day to bake and sell its core product. A software company may hire outside counsel for legal work without becoming a law firm. Write down why the function exists and how it fits the revenue-generating operation.

6. Separate specialized skill from business initiative

Expertise alone does not settle status. A highly skilled designer can still work under close direction with no independent business initiative; a less specialized service provider can operate a genuine independent business.

Record whether the worker:

  • markets a distinct service;
  • chooses projects using business judgment;
  • hires or coordinates resources;
  • develops repeatable processes for multiple clients;
  • bears responsibility for delivering a defined result.

The evidence should show what the person actually does with their skill, not merely that the skill is valuable.

7. Compare the agreement with reality

Now read the draft or existing contract. Highlight every clause that conflicts with ordinary practice.

Typical mismatches include:

Contract says Day-to-day reality suggests
“Independent contractor” manager sets daily hours and approves leave
“Free to work for others” workload and exclusivity policy make that unrealistic
“Paid by project” person is effectively paid a fixed weekly amount indefinitely
“Controls method” detailed scripts, monitoring and required methods dictate performance
“May use substitutes” substitution is never realistically permitted

A mismatch does not automatically decide the classification, but it is a warning that the paper file is describing a relationship that does not exist.

8. Check tax and payroll separately

In the U.S., the IRS groups common-law evidence around behavioral control, financial control and the type of relationship. In the UK, HMRC tax status can differ from employment-law status, and off-payroll rules may add another layer for some intermediary arrangements.

Do not let the legal team assume payroll already solved the employment question, or let payroll assume a contractor agreement solved tax classification. Record which adviser or internal owner reviewed each regime.

If a reclassification is possible, model the operational consequences before changing anything: withholding, payroll reporting, benefits, overtime exposure, leave rights, social contributions, insurance and contract termination can all require separate treatment.

9. Record facts that could change the result

Classification is not a one-time checkbox. A genuine project can drift into a managed staff role.

Set review triggers such as:

  • the worker becomes full-time for one client;
  • pricing changes from project fees to fixed recurring pay;
  • a manager begins setting daily schedules;
  • the worker loses the practical ability to serve other clients;
  • the project ends but the relationship continues indefinitely;
  • the worker is integrated into staff performance reviews or internal hierarchy.

A six-month review can be useful, but event-driven reviews are better because the legal risk changes when the facts change.

10. Make the decision traceable

The final file should be understandable by someone who was not in the original meeting. Keep:

  • the applicable-jurisdiction note;
  • the signed agreement and amendments;
  • a short factual questionnaire;
  • examples of invoices and payment structure;
  • evidence of scheduling and supervision;
  • information about other clients or marketing where relevant;
  • tax-status analysis;
  • the classification conclusion, reviewer and date;
  • the next review trigger.

Do not write “contractor because both sides agreed.” Write which facts support the conclusion, which facts cut the other way, and which legal test was considered.

What should stop the process?

Pause before onboarding or changing status if the facts are mixed and the financial consequences are material; if a local “ABC” or other statutory test may apply; if the person works through an intermediary; if the relationship crosses borders; or if reclassification could affect accrued wage, leave, pension, tax or benefit obligations.

The safest operational habit is simple: classify the relationship you actually run, not the relationship the template says you run. Because tests and enforcement positions change, this checklist is general information only. A specific classification decision should be confirmed under the current law of the relevant jurisdiction by a qualified local professional.

Sources

Related Reading