Consider an illustrative software company, North Harbor Systems. The company hires Maya, an independent data specialist, for a three-month migration project. The contract identifies a defined deliverable, Maya sets her own work sequence, negotiates a project fee, uses her own specialist tools, and continues serving two other clients.

Nothing about that opening arrangement automatically determines legal status. But it gives the company a set of facts it can later compare with reality.

Over the next ten months, the relationship changes. The lesson is not that “long contractors become employees.” The lesson is that classification should be reassessed when facts move.

Month 1: the paper and the operation broadly match

Maya receives access credentials and security instructions. The company defines the migration outcome and data-protection requirements but does not prescribe her daily schedule. She decides when to perform most work, subject to agreed meetings and system windows.

She submits invoices by milestone. If a task takes longer than expected because of her own planning, she absorbs some of that time. She still has two other customers.

At this stage the company creates a short classification record. It lists the relevant jurisdiction, the purpose of the classification review, the contract, the payment model and the facts that support independence. It also records facts pointing the other way, including access to internal systems and recurring collaboration with employees.

That balanced file matters later.

Month 3: scope expands before the original project closes

The migration reveals data-quality problems. Instead of finishing, Maya is asked to stay for another three months and help build a permanent reporting process.

This is the first review trigger.

A weak process would simply extend the purchase order. A stronger process asks whether the engagement still has a defined business-to-business outcome or is becoming a continuing internal function.

The company updates the statement of work and records the new deliverables. Maya negotiates a higher fee because the work now includes architecture decisions. She still controls methods and serves outside clients.

The classification conclusion may remain unchanged, but the review is documented.

Month 5: the manager introduces daily availability hours

A new manager wants faster responses and asks Maya to be online from 9:30 a.m. to 5:30 p.m. every weekday. The manager also asks her to notify him before taking a weekday off.

This does not automatically decide status. Businesses can impose real operational and security constraints on contractors. But the change is significant because it increases day-to-day control.

For U.S. federal tax purposes, IRS common-law guidance considers behavioral control among the relevant categories of evidence. Wage-and-hour rules use a separate legal framework. The company therefore records the new control facts instead of pretending the original contract still tells the whole story.

Month 6: commercial pricing starts to look like salary administration

The project-fee model is replaced with a fixed monthly amount. Maya no longer negotiates separate pricing for expanded tasks. Travel and ordinary work expenses are reimbursed automatically.

At the same time, one of her outside clients ends its engagement. The remaining internal workload makes it difficult to replace that client.

Now two facts have changed together: commercial pricing has weakened and economic dependence has increased.

The company should not wait for a complaint. It should run a fresh review and ask whether the current arrangement is still the operating model it actually wants.

Month 7: integration becomes visible

Maya is added to the team’s internal planning board. Her manager assigns her weekly priorities alongside employees. She receives a company job-title signature and is invited to a quarterly performance conversation.

Again, no single item is conclusive. The significance comes from accumulation.

The company now compares three snapshots: month 1, month 3 and month 7. The direction is obvious even before anyone reaches a legal conclusion: the relationship has moved from a defined outside project toward an integrated continuing role.

Month 8: the worker raises the first rights question

Maya asks whether she should receive paid holiday because the company now controls her schedule. She does not threaten a claim. She asks for clarification.

This is the moment when tone matters.

A bad response would be: “Your contract says contractor, so you have no rights.” A better response is to acknowledge the question, preserve the record, avoid retaliation, and separate the applicable legal regimes.

If the relationship is in the United States, federal tax classification, FLSA status and state law may require different analysis. If it is in the UK, government guidance expressly recognizes that tax status and employment-law status may differ.

The company should obtain local advice before making promises or categorical denials.

Month 9: the business chooses a future model

After review, the company decides it wants the role to be permanent and internally managed. It offers Maya employment from a future date.

That future design does not answer every historical question. The company therefore creates two workstreams.

Future-state workstream: salary, benefits, leave, payroll, equipment, confidentiality, IP terms, reporting line and start date.

Historical workstream: whether prior pay, tax, leave, notice or other rights need local legal or tax analysis.

Keeping those workstreams separate reduces the risk of accidental admissions or inconsistent records.

Month 10: negotiation replaces argument

Maya accepts the employment role but asks about the prior period. The company and Maya exchange factual summaries and identify the points that remain disputed.

Because both sides want to continue the relationship, they first explore a negotiated resolution rather than immediate litigation. They confirm that any settlement mechanism must comply with the applicable law and that negotiation should not be allowed to expire important deadlines.

The outcome of this illustrative scenario is intentionally not specified. Real cases depend on law and evidence, and inventing a neat result would be misleading.

What the company should have recorded at each turning point

Turning point Record to preserve Question to ask
Initial engagement contract, pricing, other clients, scope What legal test is being applied and why?
Scope extension new deliverables, fee negotiation Is this still a defined independent project?
Fixed hours manager instructions, schedule rules Has behavioral control materially increased?
Fixed monthly payment invoices, pricing changes, expenses Has commercial independence reduced?
Team integration reporting line, performance systems Is the worker now functioning like internal staff?
Rights question complaint, response, deadlines Which legal regimes and time limits apply?
Reclassification future terms and historical review What changes prospectively, and what remains unresolved?

The practical lesson

Classification risk often develops through ordinary management decisions rather than deliberate evasion. That makes event-triggered review more useful than a policy that says “review contractors annually.”

A strong trigger list includes: substantial scope expansion, relationship duration becoming indefinite, fixed scheduling, exclusivity, material increase in supervision, staff-style performance management, change from project pricing to recurring fixed payment, loss of outside clients, a complaint, and a change in relevant law.

The U.S. regulatory environment in 2026 is a useful reminder to date every analysis. The Department of Labor proposed a new independent-contractor framework in February 2026, while IRS federal tax analysis continues to use common-law categories. Other jurisdictions have their own rules.

This is a fictional operational scenario for general education, not a statement about any real person or company and not legal or tax advice. A real classification decision should be reviewed under the law of the relevant jurisdiction by qualified professionals.

The reassessment trigger is a management control, not an admission

A scheduled reclassification review does not mean the original arrangement was necessarily wrong. It is a control for detecting change. Useful triggers include a project extending beyond its planned end date, a large increase in required availability, movement from deliverable-based work to routine operational duties, removal of the worker’s ability to use substitutes or staff, or a manager beginning to supervise the person like an internal team member.

Record the trigger and the facts at that date. If the relationship remains properly structured, the record explains why. If it has changed, the business can correct payroll, contracting or operating practices before the mismatch grows. In either case, the review should focus on actual conduct, not merely refreshing the same contract label.

The most useful reassessment record is short and comparative: what the person was engaged to do, what the person actually does now, which control or economic facts changed, and which legal question those changes affect. That format gives payroll, HR, procurement and counsel the same factual baseline instead of four different versions of the relationship.

Sources

Related Reading