Independent Contractor Agreements in Oregon: The Contract That Proves the Relationship
A good independent contractor agreement does two jobs. The obvious one is commercial — scope, payment, ownership, exits. The one almost nobody drafts for is legal: under Oregon law, the agreement is evidence of whether the person is a contractor at all. Here's how to draft for both, and why a template can't.
This is Part 2 of the Contracts That Actually Protect You series. Part 1 covered service agreements — scope creep and payment disputes; Part 3 covers partnership and co-owner agreements — the contracts between owners themselves.
Hiring a contractor is how most Oregon small businesses first get help — a designer, a bookkeeper, a marketer, a subcontractor, a virtual assistant. And most of those relationships run on something thin: an email thread, a rate, and goodwill. That works until it doesn't, and when it doesn't, the business discovers it never answered the questions that now decide everything. Who owns the work? Who has the passwords? What was actually promised? And — the expensive one — was this person ever legally a contractor to begin with?
Start with that last question, because everything else depends on it. As covered in the contractor versus employee post, Oregon classifies workers by the substance of the relationship, not the label, under tests with real teeth and agencies that coordinate enforcement. No agreement can make an employee into a contractor — paper never overrides facts. What a well-drafted agreement can do is document a genuinely independent relationship so thoroughly that the facts are easy to prove. That's the standard this post drafts to.
The Agreement as Classification Evidence
Here's the drafting insight that separates a real independent contractor agreement from a downloaded one: Oregon's classification test has specific elements, and the agreement can be built to document each of them.
Scope written as results, not methods. The statute lets you specify the result you're paying for — that's expressly not direction and control. So the scope section should define deliverables, outcomes, and acceptance standards, and stay silent on how the work gets done: no required hours, no mandated procedures, no supervision language. Every method you dictate in the contract is control you reserved on paper, and Oregon counts reserved rights whether or not you use them.
Independence stated and meant. The agreement should say plainly that the contractor determines the means, manner, methods, and schedule of the work; furnishes their own tools and equipment; and is free to provide services to other clients. That last clause does double duty — Oregon's independent-business test can be satisfied partly by serving multiple clients, and an agreement that prohibits other clients undercuts the classification by its own terms.
The contractor's business, visible in the terms. Oregon asks whether a genuinely independent business exists, and looks for markers like bearing risk of loss and the authority to use helpers. The agreement can reflect both: fixed-price or per-deliverable terms, an obligation to correct defective work, insurance requirements, and an express right to engage assistants (with confidentiality flowing down to them). Each of those is a commercial term worth having and a statutory factor documented.
Their taxes, their licenses, their responsibility. The agreement should state that the contractor is responsible for their own taxes, insurance, and any licenses or certificates the work requires — which is both true as a matter of law and one more element of the definition put in writing.
A template can't do this, because doing it requires knowing what Oregon's test asks and which of your facts satisfy it. The agreement that helps you in an audit is the one drafted with the audit in mind.
The Commercial Core: What the Agreement Has to Settle
With the classification foundation laid, the working provisions carry the day-to-day weight.
Scope and acceptance. Most contractor disputes are scope disputes: they thought general support, you thought specific deliverables. Define the deliverables or cadence, the inputs you owe them — access, content, approvals — and what triggers completion and payment. For ongoing arrangements, define what's included and what isn't; if you expect availability or response times, the agreement has to purchase them explicitly, or you've bought output, not priority.
Payment. Rate structure, invoicing mechanics, due dates, reimbursable expenses, and what happens when a project pauses or dies mid-stream. Vague payment terms are how businesses end up trapped paying for nonperformance and how good contractors quietly disappear.
Ownership of the work product — the clause people learn about too late. If the contractor creates anything — designs, code, copy, photography, documentation, client deliverables — ownership needs express treatment, and the drafting is more technical than most templates handle. Under copyright law, a contractor's work is not automatically yours, and the "work made for hire" label only captures certain categories of commissioned work even when the contract recites it. The reliable mechanism is a present assignment of rights to the business, paired with terms addressing the contractor's pre-existing materials and whether they can reuse components elsewhere. The practical failure mode is blunt: the contractor leaves, and your website code, your brand files, and your ad accounts sit in their possession with nothing assigned and no obligation to hand anything over.
Confidentiality and data. Contractors touch client lists, pricing, credentials, and systems — access that becomes leverage the day the relationship sours. Real confidentiality language defines what's protected and for how long, excludes what should be excluded, and — the part templates skip — dictates what happens to data, credentials, and accounts at the end: returned, transferred, deleted, on a stated timeline.
Non-solicitation. If the contractor works with your clients directly, a non-solicitation clause — no poaching your clients during the engagement and for a defined period after — is often the right protection. Note what it isn't: a noncompete. As covered in the Oregon non-compete post, noncompetes carry heavy statutory restrictions in the employment context; non-solicitation is the narrower, cleaner tool for protecting client relationships without trying to control where someone works.
Termination and offboarding. A clean exit process — notice, final invoicing, return of work product and access, transition support if you want it — is the difference between a calm handoff and a scramble for your own passwords. The offboarding section is the most underrated clause in the entire agreement.
Where Contractor Relationships Actually Fail
The pattern is consistent: the relationship starts informal, grows load-bearing, and stays undocumented. The contractor accumulates system access, client contact, and irreplaceable knowledge; the business accumulates exposure. Then something shifts — performance drops, a dispute flares, the contractor gets a better offer — and every unanswered question comes due at once, with the files and passwords on the other side of the table.
The other failure is quieter: the agreement exists, but it's a template that recites "independent contractor" while the drafted terms — required hours, mandated methods, exclusivity — read like an employment manual. That document doesn't just fail to help in a classification dispute. It's the other side's Exhibit A.
Bottom Line
An independent contractor agreement done right is two protections in one document: commercial terms that make expectations enforceable, ownership real, and exits clean — and classification evidence that documents a genuinely independent relationship element by element under Oregon's tests. A template delivers neither, because both depend on your actual facts and Oregon's actual law.
If you're engaging contractors on emails and goodwill, or your current agreement came from a download, this is inexpensive work to do right and expensive work to skip. At Track Town Law, I draft and review contractor agreements for Oregon and Idaho businesses — billed hourly and scoped with you before any work begins. Book a free consultation here.
This post is for general informational purposes only and does not constitute legal advice. Contractor relationships and classification are fact-specific. Contact a licensed Oregon business attorney to review your agreements and working relationships.
