Independent contractor agreement template: 7 clauses you shouldn't skip
The template saves 20 minutes — the right clauses save the project; here's what every solo freelancer needs in an independent contractor agreement.
You just landed the project. The client is excited, they want to start Monday, and you've shaken hands (or exchanged a string of enthusiastic Slack messages). Now you need a contract.
If you've ever spent 45 minutes rebuilding a freelance agreement from a Google doc you found in 2021, you know what comes next: copy-paste, fix the dates, update the payment terms, export to PDF, email it, wait two days, get back a scanned JPG of the signed page with someone's thumb over the total. That workflow doesn't protect anyone — it just checks the "we had a contract" box.
Here's a faster approach, and the 7 clauses you need to make the agreement actually work.
The fast version
- Build the template once — with the 7 clauses below, plus your payment and contact fields.
- Fill in the project specifics before you send: scope, amount, dates.
- Send for e-signature — the link opens on their phone, they sign in under a minute, it comes back to you.
- Signed copies land in both inboxes automatically. No printing, no scanning, no chasing.
- Reuse the same template on the next job with three fields changed.
Once the template exists, you should be able to go from "client said yes" to "contract sent" in under two minutes.
What the agreement actually needs to do
There's a version of a freelance contract that exists to "prove I'm a contractor and not an employee." That's payroll's problem, handled elsewhere. For solo operators — designers, writers, developers, consultants, photographers, coaches — the independent contractor agreement has four jobs:
- Define what you're delivering, specifically enough that "done" is unambiguous.
- Define what they're paying and when — including what happens if they're late.
- Establish who owns the work product.
- Limit your exposure if the project goes sideways.
Every clause in a good freelance agreement maps to one of those four jobs. If a clause doesn't map to any of them, it's probably boilerplate from a law firm's blog post and can be cut.
The 7 clauses
1. Scope of work
This is the one most agreements get wrong. "Design services for ABC Corp" is not a scope. "Design and deliver three homepage mockups and two rounds of revisions by June 15, 2026" is a scope.
Write the scope in deliverables, not effort. "40 hours of consulting" invites a fight about whether hour 37 counted. "A 30-page brand audit delivered as a PDF" closes the loop. If the work happens in phases, list the phases and what marks each one complete.
2. Payment terms
Four sub-fields, all required:
- The amount (total or monthly, depending on the engagement)
- The due date (net-15, net-30, due on delivery — pick one and state it clearly)
- The late-payment penalty, if any (1.5% per month is common; even if you'd never enforce it, it tends to speed up check-writing)
- The payment method (ACH, check, wire — be specific, especially if different methods carry different processing fees)
3. Revision limits
"Unlimited revisions" is a pricing problem disguised as a clause. Specify how many rounds, what qualifies as a round ("one consolidated set of feedback delivered in a single message"), and what happens when the client exceeds that limit — additional hourly rate, fixed revision fee, or pause-and-renegotiate.
If your work is iterative by nature — software development, ongoing copywriting — revisions may not be the right frame. Milestone sign-offs work better: the client approves each stage before you proceed to the next.
4. Intellectual property
Two questions to answer explicitly:
- Who owns the final deliverable? (Usually the client, upon full payment — if you use work-for-hire language, ownership transfers automatically at that point.)
- Who owns unused concepts, drafts, and intermediate work? (Usually the contractor, absent specific language to the contrary.)
If you want to show the work in your portfolio, add a portfolio license clause — one sentence is enough. Most clients don't object, and it doesn't conflict with work-for-hire. But if you don't ask, you don't have it.
5. Confidentiality
If the client is sharing pricing data, unreleased product plans, or other sensitive business information, a short confidentiality clause inside the main agreement covers it cleanly. You agree not to share what they share with you; they agree to the same for any non-public process or pricing you bring to the engagement. This doesn't need to be a separate NDA unless the stakes are high enough that the client's legal team needs to be involved.
6. Termination
What happens if either side ends the engagement early? The clause should answer:
- How much notice is required (10–14 business days is common for ongoing work)
- What you're owed for work completed to the termination date (pro-rated by milestone is cleaner than by calendar day)
- Whether the client can use deliverables that are complete but unpaid for (standard answer: not until the final payment clears)
This clause is invisible on jobs that go well. On jobs that go sideways, it's the one both sides will read three times.
7. Independent contractor status
One paragraph: you control your own hours, tools, and methods. You are not entitled to benefits. You may work with other clients simultaneously. Neither party intends to create an employment relationship.
This clause protects both sides — you from misclassification, them from payroll-tax exposure. Keep it plain. It doesn't need to be a treatise, and the boilerplate you find online is usually fine.
Using the template without undermining it
The template is only as good as how you fill it in. Two mistakes that quietly negate the protection:
Sending with placeholder text still inside. If the scope section still says "[DESCRIBE PROJECT HERE]" when the client opens it, the agreement doesn't have a scope. Read the whole document before you hit send.
Treating the template as "set it and forget it." Each new engagement should change at minimum three things: the scope, the payment amount, and the dates. If those three fields look identical to your last project, something's wrong. The remaining clauses — confidentiality, termination, IP — can and should stay consistent across engagements.
The goal is a template that is 85% identical project-to-project and 15% project-specific. That 85% is what you build once and trust. The 15% is what you fill in carefully each time.
How to get it signed without a printer
Emailing a PDF and waiting is the slowest part of the workflow. On a good day, the signed copy comes back in 24 hours. On a typical day, you send two follow-up nudges before the client finds 10 minutes to print, sign, photograph or scan, and email it back.
The alternative: a signing link. You send a link (by text, email, or both). The client taps it, sees the document, signs with their finger or types their name, taps submit. The signed copy lands in both inboxes in seconds. The whole exchange — from your send to their submit — takes under two minutes when the client is at their phone.
That speed matters more than it sounds. The moment between "client said yes" and "contract signed" is when second thoughts happen. Getting the agreement signed before they sleep on it removes a meaningful dropout point.
vouch.ink lets you upload any PDF, place signature and date fields, and send the link in about a minute. The free tier at vouch.ink covers five documents a month — enough for most solo operators to run an entire month of contracting without paying anything.
Where to put the signed copies
The signed PDF goes to both parties automatically. The habit that breaks most people isn't sending the contract — it's filing the signed copy somewhere retrievable. "I have a signed contract" means nothing at 9 PM when a client disputes the payment terms and you're searching your inbox for the document name.
Two places worth putting it, right after the signed copy arrives:
- A client folder in your file system, named by client name + project name + date signed
- A thread or card in your project management tool, attached to the corresponding project
Don't count on "it's somewhere in my email" as a filing system. Inboxes don't scale, and search fails exactly when the stakes are highest.
What the audit trail records
When you send through vouch.ink, the signed PDF includes a tamper-evident audit trail: a record of when the document was opened, when each field was signed, and from what device and IP address. You don't configure this — it's automatic. The full details on how it works are on the compliance page.
Most clients will never look at the audit trail. It's there for the edge case: a question about whether the client actually reviewed the agreement before signing, or when they saw the final payment terms. Having that record attached to the signed PDF is worth more than the explanation of it.
One template, seven clauses, two minutes to send. That's the whole workflow — and it fits between two client emails.