Classification is easiest before the person starts
Once a contractor begins working, practical habits form quickly. Managers add meetings, deadlines become schedules, temporary projects become recurring duties, and the person may turn down other clients based on expected workload. A pre-hire review gives the business a chance to decide whether it wants an independent vendor relationship or an employee role before those expectations harden.
The review does not need to be a long legal memorandum. For many small businesses, one disciplined page of factual questions can expose whether the proposed arrangement is coherent.
Define the result the business is buying
Start with scope. What outcome, deliverable, or service is the business purchasing? A clear project or service boundary makes it easier to discuss independent methods, acceptance criteria, pricing, and completion. If the answer is “whatever the department needs each week,” the role may be designed more like ongoing staffing and deserves extra scrutiny.
Ask the manager to describe the work without using the words contractor or employee. That simple constraint often reveals whether the business expects a vendor to deliver a result or expects a person to fill a seat in an internal workflow.
Sketch the management model before writing the agreement
List the controls the business believes it needs: schedule, location, tools, training, approval, customer contact, reporting, security, and staffing. Mark which controls come from law, safety, customer requirements, or system access and which are simply management preferences. This separates legitimate commercial constraints from employee-style supervision.
If the role cannot operate successfully without extensive direction over day-to-day method, do not assume a stronger independent-contractor clause will solve the mismatch. Consider whether payroll employment is the cleaner design.
Ask whether the provider is really in business for themselves
Financial questions should be concrete. Who sets the price? What expenses will the provider bear? Do they have business insurance or meaningful tools for the trade? Can they serve other customers? Can efficient management increase profit? Can poor estimating or rework cause a loss? The answers help populate the IRS financial-control category.
An LLC, W-9, and invoice process can be collected later, but they should not substitute for this business-independence inquiry.
Put a date on the expected end or next review
If the engagement is project-based, identify the expected completion condition. If it is an ongoing professional service, set a classification review date. Permanence is one relationship factor, and even a sound initial contractor arrangement can drift as the business changes.
For startups, a ninety-day or six-month review can be more useful than an annual reminder because roles evolve quickly. The review should compare current facts with the original assumptions, not simply ask the manager to certify that nothing is wrong.
Record where the work will be performed
The IRS common-law framework is not the only rule that may matter. State unemployment, wage-and-hour, workers’ compensation, and other systems can use different standards. The pre-hire form should capture the worker’s service location and route the engagement to any required state analysis.
California is the clearest reminder: many relationships are evaluated under an ABC test for state purposes, subject to exceptions. A federal tax conclusion should not be silently reused as a California conclusion.
Create a before-start snapshot that operations can actually follow
Once the business chooses a relationship, save a dated snapshot of the assumptions that made the classification make sense: proposed scope, pricing method, expected duration, schedule rules, major tools, substitution rights if real, outside-market activity, and the manager’s planned approval process. This is more useful than a generic “approved as contractor” checkbox because it gives a later reviewer something concrete to compare with practice.
Hand a short operating summary to the manager and accounts-payable owner. If the classification depends on the provider choosing methods and negotiating scope changes, the manager should not later impose an employee handbook’s attendance process by habit. If invoices are supposed to correspond to milestones, finance should know when a recurring payroll-like amount would be a change worth escalating.
Keep the snapshot readable enough that a manager will use it. A two-page memo with named evidence is usually more operational than a dense legal memo copied into a vendor folder. The classification analysis can still link to deeper advice when needed, but the manager-facing record should make the practical boundaries visible: what the provider controls, what the company controls, which changes trigger review, and who gets called when the role no longer matches the original design.
- Save the initial scope and pricing record.
- Name the manager who owns day-to-day practices.
- Record the state where services will be performed.
- Set the first review trigger before the engagement becomes routine.
Choose the relationship first, then draft consistent paperwork
Once the facts support the intended structure, draft the agreement to match it. Define scope, commercial terms, security requirements, ownership, acceptance, expenses, and termination honestly. Do not promise independence that managers will not honor. Give accounts payable and the manager the same operating instructions so the contract and practice remain aligned.
If the business chooses employment, complete payroll and onboarding as employment from the start instead of paying “temporarily” on invoices while payroll catches up. Temporary shortcuts can create confusing records.
Escalate uncertainty instead of converting it into a checkbox
A pre-hire form should have an “unclear” outcome. Mixed facts are normal. The business may want tax or legal advice, a more careful state analysis, or, for federal employment-tax status, an SS-8 determination. Treating every review as forced pass/fail encourages people to manipulate answers until they get the desired classification.
A mature process makes uncertainty visible. That is more useful than a green check mark produced by a scoring formula the IRS does not use.
PRE-HIRE GATE
Four decisions to make before the first invoice
A pre-hire review is valuable because managers can still change the operating design. Capture these decisions before the contract language hardens around an inconsistent model.
| Decision | Record to create | Stop-and-review trigger |
|---|---|---|
| What is being purchased? | One-sentence deliverable or ongoing-function description | The answer sounds like “help wherever needed” rather than a defined service |
| How will work be managed? | Schedule, approval, supervision, and customer-contact map | The manager expects employee-style attendance or day-to-day instruction |
| What business exists outside this engagement? | Pricing, client, insurance, tools, and substitution facts | The provider has no meaningful business facts beyond this engagement |
| Where is the work performed? | State/location record for the expected service period | Another state’s classification rule may govern a separate question |
WORKED EXAMPLE
Example: a founder wanted “a contractor who works like the team”
A founder planned to hire a growth marketer on a 1099 because the budget was not ready for benefits. The proposed role had fixed full-time hours, exclusive service, company-set priorities, daily supervision, and no defined project. The pre-hire review showed that the staffing design—not the paperwork—was the real issue.
The company could either redesign a genuinely independent consulting scope or hire the person as an employee. Discovering that before the start date was far easier than trying to unwind months of inconsistent treatment.