Independent Contractor Agreement Template

In plain language: Identifies the client and contractor as legal entities and explicitly states that the contractor is an independent contractor — not an employee, agent, or partner.

Common mistake: Using a trade name instead of the registered legal entity for either party. If the client entity name doesn't match the one that actually pays invoices, enforcing IP assignment or indemnification claims against the correct entity becomes difficult.

In plain language: Defines precisely what the contractor will deliver, the timeline, and any acceptance criteria — typically via a Statement of Work attached as an exhibit.

Common mistake: Leaving scope vague — 'marketing support' or 'development work' — with no attached deliverables list. Disputes about what was promised are the single most common cause of contractor payment withheld or litigation.

In plain language: States the fee structure (fixed project fee, hourly rate, or milestone payments), the payment schedule, invoicing process, and any late-payment consequences.

Common mistake: No late-payment clause and no milestone schedule. Without both, clients delay payment indefinitely and contractors have no contractual lever to enforce timely payment.

In plain language: Confirms that the contractor is responsible for all self-employment taxes, is not entitled to employee benefits, provides their own equipment, and sets their own hours — the factual record that supports non-employee classification.

Common mistake: Including this clause while simultaneously giving the contractor a company email address, set working hours, and a desk at the office. Tax authorities look at conduct, not contract language — behavioral controls override written status designations.

In plain language: Assigns all work product, deliverables, inventions, and IP created during the engagement to the client, and requires the contractor to execute any additional documents needed to perfect that transfer.

Common mistake: Omitting a dual mechanism — both 'work for hire' designation and an assignment clause. In jurisdictions where the work-for-hire doctrine is narrow or unavailable (e.g., the UK, Canada, the EU), the assignment clause is the only reliable transfer mechanism.

In plain language: Prohibits the contractor from disclosing or using the client's confidential information — business plans, source code, customer data, pricing — during and after the engagement.

Common mistake: No carve-out for information that becomes publicly known through no fault of the contractor. An overbroad definition with no standard exceptions exposes the clause to challenge and may make it unenforceable in full.

In plain language: Prevents the contractor from recruiting the client's employees or soliciting the client's customers for a defined period after the engagement ends, and optionally prevents the client from hiring the contractor's team members.

Common mistake: Using a mutual non-solicitation without distinguishing between the contractor as an individual and their broader firm. A solo freelancer needs different protections than a staffing firm with 50 contractors.

In plain language: Sets the start and end date of the engagement, states each party's right to terminate early with notice or for cause, and defines what happens to deliverables and payment upon termination.

Common mistake: No provision for what happens to in-progress work product upon termination. Without it, a contractor can withhold partially complete deliverables as leverage, and the client has no clear right to the work they have already paid for.

In plain language: Allocates responsibility for third-party claims — typically requiring the contractor to indemnify the client for IP infringement or negligence — and caps each party's maximum financial exposure.

Common mistake: No liability cap at all, leaving the contractor exposed to claims that dwarf the project fee, or a cap set so low it offers no real protection to the client in the event of a data breach or IP dispute.

In plain language: Specifies which jurisdiction's law governs the agreement and how disputes are resolved — litigation, mediation, or binding arbitration — and in which venue.

Common mistake: Choosing a governing law with no connection to where either party operates or where the work is performed. Several jurisdictions apply local employment and labor law regardless of the chosen governing law when the engagement resembles employment.

An independent contractor agreement is a binding contract between a hiring party and a self-employed worker that defines the terms of a project-based or ongoing service engagement. It establishes that the worker is not an employee, specifies deliverables and payment terms, assigns intellectual property to the client, and sets confidentiality and termination obligations. It is the primary document protecting both parties in any contractor engagement.

An employment contract creates an employer-employee relationship, entitling the worker to benefits, overtime protection, workers' compensation, and employer-side tax contributions. An independent contractor agreement establishes a commercial services relationship with no employment entitlements — the contractor pays their own taxes, provides their own equipment, and is free to work for other clients. Misusing a contractor agreement to cover what is functionally an employment relationship exposes the hiring party to significant tax and labor law penalties.

Yes. A signed agreement is the only reliable way to establish IP ownership, confidentiality obligations, and payment terms from day one. Work performed before signing may be subject to default copyright ownership rules — meaning the contractor retains rights to everything they created. In practice, the agreement should be signed before any kickoff call, system access, or sharing of confidential information.

Without a written agreement, the contractor typically owns the IP they create. The work-for-hire doctrine in the US can transfer ownership automatically for certain commissioned works, but only when a written agreement explicitly designates them as such and the work falls within a narrow statutory category. In Canada, the UK, and the EU, no automatic work-for-hire transfer exists for contractors. A well-drafted agreement includes both a work-for-hire designation and a fallback IP assignment clause to cover all jurisdictions.

A statement of work should include a description of each deliverable, the format and specifications it must meet, the deadline for each milestone, the acceptance criteria the client will use to evaluate completion, the revision process, and any dependencies the contractor requires from the client to proceed. The more specific the statement of work, the fewer disputes arise about what was agreed.

Courts and tax authorities look at the substance of the working relationship, not the label in the contract. If the hiring party controls how, when, and where the work is performed, provides equipment, and restricts the worker from taking other clients, a contractor agreement will not prevent a reclassification finding. The agreement is enforceable as to its commercial terms — payment, confidentiality — but the contractor would also become entitled to employee-side rights, including back benefits, tax contributions, and potential reinstatement.

Non-compete clauses in contractor agreements are treated differently from those in employment contracts and vary widely by jurisdiction. In the US, they are generally more enforceable against contractors than employees because the contractor bargaining position is presumed equal, but enforceability still depends on reasonableness of scope and duration. California bans most non-competes regardless of worker classification. In the UK and EU, post-engagement restrictions for contractors are enforceable if reasonable but may require financial compensation in some member states.

Net 30 from invoice receipt is the most common standard for project-based contractor engagements. Freelancers and small contractors often negotiate Net 15 or milestone-based payments with a deposit — typically 25–50% upfront — to protect cash flow. For engagements longer than 90 days, monthly billing on a fixed retainer or time-and-materials basis with Net 15 terms is typical. Always include a late-payment interest rate — 1.5% per month is standard in most jurisdictions — to create a financial incentive for timely payment.

For standard domestic engagements involving straightforward services and a single jurisdiction, a high-quality template is typically sufficient. Engage a lawyer when the contractor will have access to core IP or trade secrets, when the engagement crosses international borders with different IP ownership rules, when the project fee exceeds $50,000, or when misclassification risk is elevated. A legal review of a template typically costs $300–$600 and is worthwhile for any high-value or high-sensitivity engagement.