Are You an Employee or a Contractor? A Self-Assessment Checklist

You don't need a magic label-you need an employee vs contractor checklist you can defend#

Forget the label. Classification turns on the relationship you actually run, not the title you typed into the contract. It is also much easier to fix before you sign.

Worker classification (employee vs. independent contractor) turns on the real relationship between the worker and the business. In practice, you do not win because a heading says "Contractor." You win by making the day-to-day setup match independent work and keeping records that show that is how the work actually happened.

The IRS puts it plainly: you have to consider all information that shows the degree of control and independence. Agencies and courts often look at the totality of the circumstances, weighing factors across the whole relationship instead of relying on any one line in a contract.

Keep this comparison in view from the first call through the final invoice:

Use this checklist as a decision tool, not as a guarantee:

• Triage: If the setup already looks employee-like, stop and redesign the engagement before you sign.
• Fix the SOW: Frame the work as a business delivering outcomes, not a person filling a seat.
• Lock the clauses: Align the contract with the relationship you intend to run instead of expecting the label to carry the weight. For clause patterns, see Independent Contractor Status: The Most Important Clause for Avoiding Misclassification.
• Keep the evidence pack: Save the SOW, change requests, approvals, invoices, and communications that show independence over time.

One calibration point: even "20-point" style checklists can help you think clearly, but they do not guarantee the answer. The goal is not certainty. The goal is a defensible, consistent story you can stand behind because it matches the work as it really happened.

That matters because, in the DOL's framing, misclassification means treating someone who is an employee under the FLSA as an independent contractor.

If you want the deeper cleanup path after the fact, read What to Do If You've Been Misclassified as an Independent Contractor. If you are still at the front end of the deal, start with a fast triage.

Run the 10-minute triage (Stop / Yellow / Green) before you sign#

Before you negotiate price, clauses, or kickoff details, decide whether the deal should pause, be reshaped, or be signed. Start with one question: does this relationship operate like an outside business engagement, or like a job with a different label?

Two grounding truths help keep this clear:

• Behavioral control focuses on whether there is a right to direct or control how you do the work.
• Labels do not decide status. The substance of the relationship does.

Stop (red)#

Stop and redesign the engagement if the client is trying to buy a seat instead of a service.

• Operating model looks like employment: a manager assigns tasks day to day, you follow their methods, and they expect you to work like internal staff. That is a strong behavioral-control signal.
• No delivery frame: if you cannot point to a Statement of Work (SOW) that defines the work and acceptance criteria that say what makes a deliverable satisfactory, you are negotiating vibes instead of outcomes.

Yellow (caution)#

Yellow means the deal may still work, but only if you clean up the structure now.

• Exclusivity pressure: push for non-exclusive language and a defined project term. A definite-duration, non-exclusive, project-based relationship weighs in favor of contractor status in the factor language cited across these tests.
• Restriction creep: if the client wants to control your schedule and also limit your ability to work for others, treat that as a renegotiation trigger.

Green (go)#

Move forward when the setup already looks like a project, not a role.

• Project term + milestones: define what ships, when it ships, and what "done" means.
• Written acceptance flow: make acceptance explicit so you can invoice cleanly and keep approval from turning into manager-style supervision.
• Evidence discipline: keep the SOW, approvals, and invoices in one deal folder so the paper trail stays consistent later.

Verdict: Any red item is a redesign signal. Do not paper over it with contractor language and hope the rest sorts itself out.

Know the tests (IRS vs U.S. Department of Labor vs ABC vs cross-border)#

Once you know whether the setup is workable at all, make sure you are using the right legal lens. Classification is not one universal test. The question changes by agency and jurisdiction, and passing one standard does not automatically clear the others.

Use this step to decide which set of rules you actually need to satisfy before you tighten the paperwork.

What this means in practice#

A common mistake is optimizing for one standard and assuming the others take care of themselves. They do not. Identify the right lens first, then shape the deal to fit it from the start.

• IRS vs DOL: The IRS applies common law rules for federal employment tax purposes. The DOL framing focuses on economic realities, specifically whether you are economically dependent or truly in business for yourself. Treat them as separate risk surfaces.
• Facts-and-circumstances beats factor-chasing: You will hear about "20 factors" because the IRS developed a 20-factor approach in guidance, often referenced through Revenue Ruling 87-41, but do not treat it like a scorecard. Collect the facts, align the relationship, and keep documents that match how the work actually runs.
• ABC regimes: In California's described ABC framework, the default assumption treats the worker as an employee unless the hiring entity satisfies the listed conditions. If you are selling into a stricter state, arguing semantics is usually a poor use of time. Change the engagement structure.
• Cross-border reality check: In the United Kingdom, IR35 and off-payroll rules can apply when services run through an intermediary and you would have been an employee if you provided services directly. In Canada, the CRA emphasizes that the facts of the whole working relationship decide status. In the European Union framing, a core "worker" characteristic includes performing services under another's direction for remuneration.

Verdict: Pick the governing lens first. Then make the facts fit that lens instead of hoping one contract label will satisfy every test.

Fix employee-like signals fast (Control, Integration, Dependence, Money)#

Most classification problems show up in the operating details long before anyone argues about legal language. If the work looks directed, integrated, exclusive, or financially open-ended, clean it up before kickoff.

A useful IRS anchor is that an employee relationship often shows up when the business can control what will be done and how it will be done. The DOL framing looks at the economic realities of the whole relationship and asks whether you are economically dependent or truly in business for yourself.

No single tweak saves a bad setup. What helps is stacking cleaner signals across the relationship.

A few deserve extra attention in practice.

Control is often where the drift starts. A client asks for a daily standup, then a response-time requirement, then a preferred method, then core hours. None of those details alone decides the outcome. Taken together, they start to look like supervision. The clean fix is to define what you owe, by when, and how acceptance works, then keep routine communication tied to delivery rather than attendance.

Integration matters because the more you are absorbed into the client's internal structure, the harder it is to maintain the posture of an outside business. If you are given an internal title, routed through staff processes, or asked to manage employees as if you are part of the org chart, the relationship starts reading like employment. Limit what needs to be limited, but do it in contract terms rather than people-management terms.

Dependence is where many otherwise clean engagements get shaky. One major client is not automatically fatal. But if the deal also comes with exclusivity, indefinite duration, and restrictions on outside work, the picture changes fast. If you cannot reduce those pressures, at least be honest that the risk is rising and price or structure the deal accordingly.

Money is the quiet signal people overlook. Undefined hourly work with no clear scope, no acceptance standard, and no change process tends to invite direct control. By contrast, milestone billing or a rules-based retainer makes it easier to operate like a vendor delivering a service, not an employee being managed through a shift.

Verdict: If the relationship still looks directed, exclusive, and indefinite after these fixes, do not argue one factor at a time. Redesign the deal so the overall facts read like a project-based service you can document.

Build a contractor-grade SOW (deliverables, acceptance, change control)#

Once the working relationship looks cleaner, put it in writing. Your SOW is where independence turns into operating instructions.

A contractor-grade SOW makes the relationship about measurable results, not supervision. When the project gets messy, this is the document that keeps the deal from sliding back into day-to-day management.

A Statement of Work (SOW) is the part of the contract that describes the services or products you will deliver, including the specs, deadlines, and deliverables that keep everyone aligned.

The reason this matters is simple: if the project shifts and the documents do not say how changes get approved, clients usually fall back to managing the person. A clean SOW gives both sides another path. Instead of "just do it this way," the conversation becomes "is this in scope, and if not, what does the change order say?"

A practical default you can reuse:

• List deliverables and milestone dates.
• Write acceptance criteria for each deliverable.
• Require changes to be documented in a written change order approved by both parties.
• Send one weekly status update and maintain a decision log.

Tools boundary: use your own stack by default where you can. Many worker-classification guides note that independent contractors often invest in their own facilities and tools, but tools alone do not decide classification. What matters is that access stays tied to delivery needs rather than becoming a sign of staff integration. Limit client-system access to what you actually need, and handle that access under the right confidentiality terms, such as an NDA, and if you touch personal data, the right data-processing terms, such as a DPA.

That supports a cleaner posture without pretending it solves the classification question by itself.

If you want language that reinforces independence without adding fluff, see Independent Contractor Status: The Most Important Clause for Avoiding Misclassification.

If you need a deliverables-first draft you can actually point to later, the SOW generator is a practical starting point for outcomes, acceptance criteria, and change control.

Lock the deal-protection clauses (Termination, Liability, Indemnity, Venue)#

With the operating model set, protect the downside in the contract. These clauses do not decide classification, but they do decide how expensive a bad deal becomes.

Think of them as the seatbelts.

During redlines, use three simple questions:

• If a clause makes you responsible for outcomes you do not control, narrow it.
• If a clause makes your downside unlimited, cap it.
• If a clause makes disputes practically impossible to pursue, change the forum.

This is also where you separate relationship risk from business risk. A deal can be structured cleanly for classification and still be commercially dangerous if liability is uncapped, indemnity is too broad, or the venue is unusable. Do not confuse those issues. Fix both.

Verdict: If the client will not move on unlimited liability, broad indemnity, and an unusable venue, treat that as a pricing and risk signal. Adjust scope or fees, or walk.

Set pay like a business (retainer, milestones, suspension rights)#

The payment structure should match the project structure. If the money flows like wages and the scope stays vague, the relationship starts drifting in the wrong direction.

Set payments around deliverables and clear terms so you keep leverage and avoid employee-like patterns. Money mechanics either reinforce independence or quietly erode it.

Milestone billing splits work into phases or deliverables, each tied to a predefined payment. That fits a contractor posture because it frames pay around project outputs, not a regular wage cadence.

When you submit a milestone, keep the review step simple: compare the deliverable against the acceptance criteria, log any gaps, then accept it or route a revision. That keeps the conversation tied to the work product rather than to personal performance management.

A retainer can still stay clean if you treat it like a defined commercial arrangement, not a disguised salary. That means the scope is spelled out, response expectations are clear, and extra work gets documented instead of absorbed.

Retainer rules that keep you sane:

• Clearly define what the retainer covers and what it does not.
• When scope expands, send a written change order with revised fees and dates.
• Keep the cadence professional: you deliver updates, and the client makes decisions.

You also need basic collection terms:

• Up-front payment at the start, before work begins.
• A late charge fee once the invoice passes its due date.
• A suspension for non-payment clause so you can pause obligations until payment lands.

Avoid the worst combination: long payment terms, open scope, and indefinite hourly work. It strips your leverage and turns every invoice into a negotiation.

Verdict: Use milestones for project work and a rules-based retainer for ongoing work. Back either structure with a deposit, late fees, and suspension rights in the SOW and the master agreement.

Use pushback scripts that keep you independent (and keep the sale)#

Even with a clean contract, client habits can pull the relationship back toward employee treatment. This is where calm, practical pushback matters.

Use factual pushback that protects your control over time and method, then redirect to deadlines, deliverables, and the SOW. You are not trying to win a debate about classification law. You are protecting an operating model that keeps the deal clean.

The underlying principle is straightforward: contractors control the manner and means of delivering results. They choose their own hours within project deadlines. Many checklist frameworks also treat set hours as a control signal, so when a client asks for core hours or daily attendance, it is worth handling that carefully.

Do not debate labels. Reframe the work.

A useful negotiation move is to offer two workable options instead of arguing in the abstract.

• Option A: milestone plan with review checkpoints.
• Option B: tighter response windows and fewer meetings, with the same delivery dates.

That keeps the conversation commercial and practical. You are not saying "no" to the client's concerns. You are offering a structure that meets those concerns without turning the relationship into day-to-day supervision.

Verdict: If they insist on set hours, client-controlled methods, and zero delegation, treat that as misclassification risk moving in. Hold the boundary or change the deal structure before week one.

Cross-border checklist (paperwork, payments, and forum planning)#

If either side is in a different country, add one more pass before kickoff. Cross-border work is much easier to defend when the tax forms, payment trail, and dispute clauses all tell the same story.

Treat cross-border work like an audit file: the right tax form, clean receipts, and clear dispute forums. Once the boundaries are set, lock down the operational details that keep your record consistent.

1) Paperwork gate: get the right IRS form on day zero#

Form W-9 is the form U.S. taxpayers use to provide a correct taxpayer identification number (TIN) to payers who file information returns with the IRS. If you are not a U.S. taxpayer, a payer may request Form W-8BEN or a different W-8 variant when needed to document status for withholding purposes.

Operator rule:

• Request the form in onboarding, not after the first invoice.
• Store the signed PDF with the client's contract and SOW.
• If you collected a W-9, keep it on file for four years.

2) Payment traceability: one folder per client, one story per payment#

You do not need fancy tooling. You need consistent artifacts that show gross receipts and tie payments back to work.

At minimum, keep:

• Invoices showing what you billed and when.
• Bank statements and deposit slips showing what you actually received.

3) Don't blur identity (without getting cute)#

Classification does not turn on one checkbox. Factors get weighed, and there is no magic number that decides it. You do not need theatrics. You need clean separation that reads naturally if someone reviews the file later.

• Use contractor language in writing: deliverables, milestones, acceptance.
• Keep communications scoped to project outcomes, not management routines.

4) Forum planning: decide jurisdiction and choice of law on purpose#

When parties sit in different jurisdictions, jurisdiction and choice-of-law clauses can get complicated. Decide this while everyone is still cooperative, not after a payment problem or a scope fight.

If you want a clean classification backbone to pair with these cross-border mechanics, use Independent Contractor Status: The Most Important Clause for Avoiding Misclassification.

Build your audit-ready evidence pack (support independence on demand)#

Once the deal is live, keep the file as you go. Do not wait until tax season, a payment dispute, or a classification question forces you to reconstruct the relationship from memory.

Build a simple evidence pack that makes your independent-business story easy to verify. The best version is boring and complete. Someone should be able to follow the scope, the changes, the money, and the business posture without a long explanation from you.

Core docs (scope + changes)#

Your Statement of Work (SOW) is the foundation document because it defines scope, deliverables, timelines, and responsibilities. Pair it with every written change order, meaning any written update to the original deal when the project terms change.

Keep, for each client:

• Proposal or scope email thread showing the original intent.
• Signed SOW.
• Every change order, even a short signed addendum.
• The independent contractor clause from the agreement as useful context, not as a magic shield.

Money trail (what you billed, what you received)#

For tax purposes, keep records as long as needed to prove income or deductions. In practice, your gross-receipts proof starts with invoices, plus deposit information that ties payments back to those invoices.

Make it easy to trace:

• Invoice -> payment record -> milestone acceptance note, all in one place.

That sequence matters because it connects the business side of the deal to the delivery side. It also makes it much easier to explain why a payment was made and what deliverable it related to.

Compliance + security exhibits (only when they apply)#

Store the tax form the payer asked for:

• Form W-9 for providing a correct taxpayer identification number to payers who file information returns.
• Form W-8BEN for foreign-status certification a payer may rely on when it is properly completed.

Then add only what the engagement actually requires:

• NDA for confidentiality terms.
• DPA when you process personal data under GDPR-style roles.
• VAT ID when applicable, because some invoicing contexts include it on invoices.

Independence proof (business posture)#

Do not over-lawyer this part. Save lightweight artifacts that help show you operate like a business: marketing presence, other proposals in flight, and, if it is useful, a calendar snapshot that reflects non-exclusivity. Just do not treat these as universally accepted proof. What a reviewer values can vary, and these items help most when they support a broader, consistent record.

If someone can follow scope -> delivery -> acceptance -> payment -> compliance from one folder, you are in much better shape. That still does not guarantee independent-contractor status by itself, but it makes your posture much easier to verify. For more classification framework context, see Independent contractor classification framework overview.

Conclusion#

The defensible path is simple, even if the analysis is not: make the work look like a business delivering defined results, then keep records that prove it.

Here is the conservative sequence:

• Triage first: run your own Stop/Yellow/Green screen on the real working setup. It is a practical tool, not an official IRS or DOL standard. Pay special attention to anything that creates economic dependence or otherwise makes the relationship look like employment.
• Turn role-filling into a project: use a Statement of Work (SOW) that defines deliverables, timelines, and responsibilities. Add acceptance criteria so "done" has a clear standard, and use a written change order when scope shifts.
• Protect the downside with enforceable terms: choose terms you can live with for how the work ends and how disputes get handled, including Termination, Governing Law, Jurisdiction, and Dispute Resolution. Those clauses manage risk. They do not prove status by themselves.

If you want one clean mental model, keep it here:

Your final check is practical: can someone trace SOW -> acceptance -> invoice -> supporting documents without calling you to explain it? If yes, you have reduced risk the right way by making your operations match your contract and your records match your operations.

Before you send the final PDF, make sure the contract language matches how you will actually work, especially scope, termination, and payment mechanics. Draft a clean baseline with the freelance contract generator.