Some clients send you their contract; plenty of smaller businesses have never hired a freelancer and expect you to bring one. An independent contractor agreement is the general-purpose answer. It works for almost any professional service and can be used from either side: by a freelancer who wants a clean set of terms, or by a business engaging a freelancer for the first time.
It also does one more job that a project contract doesn't emphasize: it describes the relationship as a business-to-business one, with the contractor in control of how the work gets done. That description doesn't decide classification on its own, but a contract that contradicts it makes things worse.
TL;DR
The independent contractor agreement template covers services via work orders, fees and invoicing, the contractor's control over methods, hours and tools, freedom to work for others, IP assignment on payment, confidentiality, taxes and insurance, and termination on notice. Use it as a master agreement for ongoing freelance relationships. Keep the actual working arrangement consistent with the contract, because authorities judge classification by practice, not labels.
What's inside
- Parties and relationship — a business-to-business engagement, not employment.
- Services and work orders — a master agreement with a short order for each piece of work.
- Fees, invoicing and expenses — rate or fixed fee per order, payment terms.
- Contractor control — methods, schedule, location, tools and the right to use helpers.
- Non-exclusivity — the contractor may work for other clients.
- Intellectual property — assignment of deliverables on payment, background IP retained.
- Confidentiality — a short clause covering both sides.
- Taxes, benefits and insurance — the contractor's own responsibility.
- Term and termination — notice period and payment for work done.
When to use it
Use it when you'll do repeated or varied work for the same client and don't want a new contract each time: a VA supporting a founder across many tasks, a developer called in for different features, a writer producing a monthly mix of content. Sign the master once, then issue a one-page work order for each job.
For a single, well-defined project, a service contract is simpler. If you're the one hiring and the person will work under your client's terms, use the subcontractor agreement so the client obligations flow down.
Worker classification: the risk the contract can't remove
Every country has its own tests, and they change. Rather than rely on any single rule, look at the factors that most tests share. The more of these that describe your relationship, the more it looks like employment:
- Control. The client tells you how to do the work, not just what result they want.
- Schedule. You must work set hours or be online at fixed times.
- Tools and place. You use the client's laptop, email address and office.
- Exclusivity. You can't take other clients, or in practice you have none.
- Integration. You appear on the team page, manage staff, or do the same job as employees.
- Duration. The engagement is open-ended rather than project-based.
- Financial risk. You're paid for time regardless of results and carry no business costs.
What the contract can do is reflect a genuine business relationship. What it can't do is fix a relationship that works like a job. If several of those factors apply, both sides should get local advice. Businesses face the bigger exposure (back taxes, contributions, penalties), but contractors can lose out too, for example on employment rights they were entitled to.
For the freelancer's side of tax and registration, the freelance taxes and finance guide covers the basics.
Customize it in your COLO workspace
Save the master agreement as a contract template in COLO Contracts, and use contract renewal if you set a fixed term. The client signs in the client portal. For each work order, create a project with tasks and a per-task rate, track time if you bill hourly, and send invoices with line items and tax from COLO invoicing.
Common mistakes
- Copying employee-style terms. Fixed hours, mandatory meetings at set times, and a requirement to use the client's devices all push toward employment.
- No work orders. An open-ended "do whatever is needed" engagement is both a scope problem and a classification problem.
- Assigning background IP. Keep your own tools and templates.
- Assuming the contract settles tax status. It's evidence, not a verdict.
FAQ
Q: What is an independent contractor agreement?
It is a contract between a business and a self-employed person who provides services without becoming an employee. It sets out the work, the fee, who owns the results, and confirms that the contractor runs their own business.
Q: Does signing an independent contractor agreement make someone a contractor?
No. Tax and labor authorities look at how the relationship works in practice, not what the contract calls it. If the business controls hours, methods and tools and the person works only for them, they may be treated as an employee regardless of the paperwork.
Q: What makes a contractor relationship look like employment?
Common warning signs include set working hours, being supervised day to day, using the client's equipment, working for one client only, open-ended engagements with no defined project, and being integrated into the client's team like staff.
Q: Can an independent contractor agreement be used for ongoing work?
Yes, as a master agreement with separate work orders for each project. Long open-ended engagements with one client increase classification risk, so define projects and deliverables where you can.
Q: Who pays taxes under an independent contractor agreement?
The contractor is normally responsible for their own income tax, social contributions and business registration. The agreement should say so, and the business should check what reporting it must do for contractor payments where it operates.