Remote work removed an old visual shortcut
When nearly all employees worked at an employer’s premises, location sometimes felt like an obvious clue. Remote work weakened that intuition. An employee can work entirely from home under detailed company control, and an independent technician can perform services at a client site because the job must be done there. The IRS common-law analysis therefore does not turn on the address where a laptop sits.
For remote roles, the better evidence is digital: calendar rules, collaboration platforms, device controls, task assignment, approvals, monitoring, and customer ownership. These systems can reveal how much discretion the worker actually has.
A home office can support independence without proving it
A consultant who maintains a dedicated business office, pays for commercial software, advertises services, and serves multiple clients may have meaningful financial independence. Those facts can support contractor status. But simply working from a spare bedroom on a personal laptop is not enough. Many employees supply minor home-office items and still work under an employer’s direction.
Document investment relative to the occupation. A cybersecurity consultant’s paid lab environment, insurance, certifications, and market activity may matter more than furniture. A writer’s business investment may be lighter, making pricing, client mix, and control over method more informative.
Digital availability requirements can function like a schedule
Requiring a remote contractor to respond during a customer support window can be tied to the service purchased. Requiring broad presence on chat all day, tracking keyboard activity, and treating short absences as attendance violations can look more like employee management. The distinction depends on whether the company is defining a deliverable or controlling the worker’s time and manner of performance.
Write down the reason for each availability rule. If it is necessary for a scheduled incident-response shift, say so. If it exists because managers want to know where the person is every minute, that is a different fact. Compliance reviews improve when business reasons are recorded instead of after-the-fact labels.
Company equipment is contextual, not conclusive
Security-sensitive companies may require even outside vendors to use managed devices. That requirement can be commercially reasonable and does not automatically create employment. Still, equipment is part of the financial and behavioral picture. A company-issued laptop combined with fixed hours, internal training, continuous supervision, and an indefinite core role looks different from a secured device used only to access one client environment for a defined project.
Note whether the worker maintains the equipment needed to run the broader business, whether client equipment is limited to security or interoperability, and who bears other business costs. The explanation matters.
Remote onboarding can accidentally mimic employee onboarding
Startups often place contractors into the same onboarding flow as employees for convenience. That can include policy acknowledgments, manager introductions, staff handbooks, performance systems, mandatory culture sessions, and employee benefit materials. Some shared security and conduct rules may be necessary, but wholesale reuse can blur the relationship and create practices inconsistent with the contract.
Create a vendor-specific onboarding path. Give outside providers the information needed to deliver safely and lawfully, while avoiding employee-only procedures that are not relevant. The goal is operational clarity, not cosmetic separation.
Cross-state remote work creates a second classification map
A remote worker can perform services in a state with a classification rule different from the IRS common-law test. California’s ABC framework, New York’s unemployment standards, and other state rules can change the analysis. A federal tax memo should therefore record where services are actually performed and flag the state review.
This is one reason a “remote contractor policy” cannot be a national yes-or-no document. It should instead route the business to the right state and legal-purpose tests. Federal employment tax, FLSA, state unemployment, and workers’ compensation may not use identical standards.
Remote work also changes which state-law file you need to open
A remote relationship can cross state lines even when the company thinks of the worker as part of one national contractor program. The IRS common-law analysis remains a federal employment-tax question, but state unemployment and wage-and-hour systems can use their own tests. Capture where the services are actually performed and route the role to the relevant state review rather than assuming the company’s headquarters controls every classification question.
This is a recordkeeping point, not a shortcut to a legal conclusion. A remote address by itself neither proves contractor status nor tells the business which state obligations ultimately apply. It tells the reviewer that the federal memo should not be the only memo in the file.
Review collaboration practices, not just the contract
For a remote-role audit, sample one month of calendars, task boards, chat instructions, access rules, time tracking, expense reimbursement, and client assignments. Interview the direct manager. Ask whether the worker can change methods, decline work, serve other clients, and decide when the work is done. This creates a more reliable record than relying on a statement of work alone.
If the team’s practices changed during the engagement, identify when. A remote consultant may begin with broad autonomy and later become the de facto internal lead. Classification can require a new review even though the person never changed physical location.
The remote-work question should end with “what is the business relationship?”
Location can help explain costs and logistics, but it does not answer the IRS categories. Keep the analysis centered on rights of control, financial independence, and the type of relationship. If the company needs continuous employee-like coordination, moving the person to payroll may align better with the desired management model.
When the facts support an independent business, document them plainly: client base, pricing, business costs, scope, autonomy, and duration. A remote label is unnecessary when the substance is already clear.
REMOTE CONTROL CHECK
Audit the digital operating model, not the home address
Remote relationships leave a different evidence trail. Review the systems that shape the work before treating location as evidence of independence.
| Remote practice | Evidence to pull | Question for the file |
|---|---|---|
| Availability | Calendar rules, chat expectations, response-time policies | Is the company buying coverage or controlling broad working time? |
| Task method | Project tickets, SOPs, approval loops, QA comments | Do systems define the result or dictate how the worker performs it? |
| Equipment | Device policy, software licenses, reimbursement records | Which tools reflect security needs, and which show operational dependence? |
| Market activity | Other-client calendar, portfolio, proposals, business website | Does the provider operate a business between company assignments? |
WORKED EXAMPLE
Example: two remote designers, two different relationships
Designer A runs a studio, quotes each project, uses her own tools, can send another designer, serves four clients, and joins meetings only for milestones. Designer B works from home but is scheduled 9-to-5, receives tasks from a creative director, uses a managed company laptop, needs approval for time away, and has worked only for the company for two years.
Both are remote. That shared fact tells almost nothing about whether their broader relationships look like independent businesses or employment.