Independent Contractor Agreement: What to Check Before Signing

This section defines exactly what the contractor will deliver — and just as importantly, what they won't. Vague scope language is the single biggest source of disputes: if the contract just says something like "marketing services" or "development support," either side can argue the work should include far more (or far less) than what was actually intended.

Good scope language lists specific deliverables, formats, and what counts as "done." It should also say what happens when the client wants something added that wasn't in the original scope — usually through a change order or amendment process with its own price and timeline.

This covers the rate, when invoices go out, when payment is due, and what happens if payment is late. Look for whether payment is tied to milestones, hours, or a flat fee, and whether there's a cap on total hours or cost.

Also check for a

kill fee

or early termination payment — if the client cancels partway through, does the contractor get paid for work already done? Without this, a contractor can do weeks of work and receive nothing if the project is cancelled the day before a milestone.

This clause states that the contractor is not an employee, and it usually limits how much control the client can exercise over how the work gets done. This matters beyond the paperwork: if the actual working relationship looks like employment (set hours, exclusive commitment, direction over daily tasks, no ability to send a substitute), the label in the contract may not hold up if a regulator or court looks at it.

For contractors, retaining real independence — how you work, when you work, and for whom else you work — protects both your tax status and your ability to argue you were never an employee if a dispute arises.

This decides who owns the work once it's finished. Many agreements state that everything created is a

work made for hire

or assigned to the client upon full payment. That's standard for most commissioned work, but the trigger matters — ownership transferring

,

,

only after payment

is very different from ownership transferring the moment work is delivered.

Watch for language that also grabs ownership of pre-existing tools, templates, code libraries, or methods the contractor brings to the project and reuses across clients. Without a carve-out for these, a contractor could technically lose the right to reuse their own toolkit.

Confidentiality clauses are standard and reasonable — they stop either side from sharing sensitive information. Non-compete and non-solicitation clauses are more aggressive: they can restrict a contractor from working with competitors or other clients in the same industry, sometimes for a period after the contract ends.

These restrictions vary widely in how enforceable they are depending on where you are, but even an unenforceable clause can scare a contractor out of taking other work, or give a client leverage in a dispute. The scope (what's restricted), duration, and geography of any restriction should be narrow and clearly tied to a real business interest.

Indemnification clauses say who pays if something goes wrong — a lawsuit, a data breach, property damage, a third-party claim. One-sided indemnification (where only the contractor indemnifies the client, not the other way around) shifts most of the risk onto the smaller party.

Some agreements also require the contractor to carry specific insurance (general liability, professional liability/errors & omissions) at their own cost. That's not unusual for higher-risk work, but it's a real cost that should factor into the rate being charged.