Contractor agreement in Canada: the label is the least important part of it

Contractor vs. employee: the question that decides everything

The distinction matters because it switches entire legal regimes on or off. An employee in Ontario is covered by the Employment Standards Act, 2000: minimum wage, overtime after 44 hours a week, vacation pay, public holiday pay, job-protected leaves, and termination and severance pay — plus CPP and EI contributions split with the employer, and workers' compensation coverage. A genuine independent contractor gets none of those protections by default; their rights are whatever their contract says, they pay both portions of CPP themselves, they arrange their own insurance, and they handle their own taxes. The contractor model is cheaper and more flexible for the client — which is exactly why it is abused, and why regulators police it.

Outside Quebec, the CRA and the courts apply a holistic test. The CRA's guide (RC4110) works through six factors, and the courts ask the same question in one sentence: is the worker performing the services as a person in business on their own account?

• Control — who decides how, when, and where the work is done? The CRA is explicit: it is the right to exercise control that matters, not whether the payer actually exercises it. A client who could dictate hours and methods looks like an employer even if they usually leave the worker alone.
• Tools and equipment — who supplies, maintains, and insures the significant tools? A designer on their own laptop and software points to contractor; a worker on the client's machines, in the client's office, on the client's schedule points to employee.
• Subcontracting — can the worker hire helpers, send a substitute, or subcontract part of the job? The freedom to do so is a strong contractor indicator; a requirement to do the work personally is an employee indicator.
• Financial risk — can the worker lose money? Unreimbursed expenses, liability for defective work, bad debts, and overhead all point to contractor. A guaranteed wage with all expenses reimbursed points to employee.
• Investment and management — who bears responsibility for the business side: finding clients, setting prices, managing cash flow, and making business decisions? A worker who runs their own business answers yes; a worker integrated into the client's operation answers no.
• Opportunity for profit — can the worker increase profit through their own decisions (negotiating rates, controlling costs, taking on more clients), or is their pay fixed regardless of performance? Real profit opportunity points to contractor.

Quebec applies a different three-step approach: first the parties' intent, then whether the relationship fits the Civil Code's description of work, pay, and subordination, and finally a comparison of that intent with the real working conditions. And in Ontario, the ESA adds a statutory backstop: section 5.1 expressly prohibits an employer from treating an employee as an independent contractor (or as any other category of worker not covered by the ESA). Misclassification is not just a tax problem — it is an ESA violation in its own right, and a worker found to be an employee can claim the minimum entitlements they should have received all along. The practical lesson: draft the agreement to match a genuinely independent relationship, and then run the relationship that way — set deliverables, not hours; pay for results, not attendance; let the contractor serve other clients.

Services and deliverables: define the work, not the worker's day

The services clause is where contractor status is won or lost in practice. Describe the deliverables (what will be produced, to what standard, by when), not the worker's schedule. A clause that says 'the contractor will work Monday to Friday, 9 to 5, at our Toronto office, reporting to the VP of Product' describes an employee with a different title. A clause that says 'the contractor will deliver a redesigned checkout flow, tested and documented, by November 30' describes a contractor.

Include: a scope statement with acceptance criteria (how the client judges the work complete), a change-order process (extra work requires a written variation and a price), milestones and deadlines, the client's obligations (materials, access, feedback deadlines — with a remedy if feedback is late), and the contractor's right to serve other clients and to use subcontractors (with notice, and with the contractor remaining responsible for their work). If the engagement is ongoing rather than project-based, define it by retainer deliverables — a monthly output, not a monthly attendance requirement.

Payment terms: price, timing, expenses, and tax

Contractor payment disputes are the most common reason these agreements end up in Small Claims Court, and almost all of them trace back to vague payment clauses. Be specific on every element:

• Fee structure — fixed project price, hourly or daily rate, or monthly retainer, and whether the rate is all-inclusive or plus applicable taxes.
• Payment triggers — milestones, deliverables, or calendar dates; what counts as acceptance, and how long the client has to object to an invoice.
• Invoicing and deadline — invoice contents, submission method, and payment terms (net 15, net 30), plus interest on late payment.
• Expenses — which expenses are reimbursable, whether they need pre-approval, and what receipts are required. Unreimbursed expenses are also a contractor-status indicator, so the expenses clause does double duty.
• Tax treatment — the contractor invoices without payroll deductions and is responsible for their own income tax and both portions of CPP. GST/HST: a contractor is a 'small supplier' and need not register until taxable supplies exceed $30,000 in a single calendar quarter or over four consecutive quarters; once that threshold is crossed, registration is mandatory (13% HST in Ontario), and voluntary registration before the threshold allows input tax credit claims on business purchases.

Two traps to avoid. First, paying a contractor a fixed monthly amount that never varies, with no milestones and no other clients, looks like salary — and salary is what employees get. Second, withholding amounts 'for taxes' from a contractor's invoice: contractors are not employees, and payroll-style deductions muddy the very status the agreement is trying to establish. If you are worried about a contractor's tax compliance, that worry is a sign the relationship may not be a contractor relationship at all.

IP ownership: payment does not transfer copyright

This is the clause clients most often assume they do not need — and the one that costs them the most when it is missing. Under section 13(1) of Canada's Copyright Act, the author of a work is its first owner. The employment exception in section 13(3) transfers first ownership to the employer only for works created in the course of employment under a contract of service. An independent contractor is not under a contract of service, so the exception does not apply: the code, designs, copy, photographs, or reports the contractor created belong to the contractor even though the client paid for them. Payment alone never transfers copyright.

Your agreement must therefore contain an express assignment: the contractor assigns to the client all intellectual property in the deliverables — copyright, and where relevant patents, trademarks, and trade secrets — present and future, with a promise to sign further documents to perfect the assignment. No assignment is valid unless it is in writing and signed by the owner (section 13(4)), so the signed agreement itself is the transfer document. Add a moral rights waiver (moral rights cannot be assigned under Canadian law, only waived in writing), a licence-back if the contractor needs to reuse generic tools or know-how in other work, and a warranty that the work is original and does not infringe third-party rights. If the contractor will use open-source components or subcontractors, require disclosure — and chase written assignments from every subcontractor too, since their work carries the same default.

Confidentiality: protect the business, not just the document

Define confidential information broadly (business plans, customer lists, pricing, source code, trade secrets, and anything marked confidential or reasonably understood to be confidential), then carve out the standard exceptions: information already public, already known to the contractor, independently developed, or disclosed by law or court order. State the obligations (use only for the engagement, do not disclose, protect with reasonable care), the survival period (commonly two to five years after termination; trade secrets often indefinitely while they remain secret), and the return-or-destroy obligation on termination. Note the interaction with Ontario's non-compete landscape: a strong confidentiality clause plus a narrow non-solicitation clause is usually more enforceable — and more useful — than a sweeping non-compete, and it survives even if the rest of the restraint fails.

Termination: contractors have no statutory notice — the contract is everything

An employee's termination is governed by statute and common law; a contractor's termination is governed by the contract alone. If the contract says nothing, ending the engagement means negotiating an exit with a party who has no incentive to agree — or arguing about implied terms in court. Cover all three exits:

• Termination for convenience — either party may end the engagement on written notice (14 or 30 days is common), with payment for work completed and accepted to the termination date, plus any non-cancellable costs the contractor reasonably incurred.
• Termination for cause — defined breaches (failure to deliver, confidentiality breach, insolvency, loss of a required licence) allow immediate or short-notice termination, with a cure period (e.g. 10 business days) for breaches capable of being cured.
• Automatic triggers — bankruptcy, insolvency, or loss of professional standing ends the agreement without further notice.

Then settle the wind-down: handover of work in progress and materials, return or certified destruction of confidential information, final invoice timing and payment, whether any licence to partially completed work survives termination (and on what terms), and survival of the clauses that must outlive the agreement — confidentiality, IP, indemnity, and limitation of liability. For long engagements, consider a termination fee or minimum term: it gives the contractor income security and gives the client a clean, priced exit instead of a dispute.

Liability, indemnity, and insurance: who pays when it goes wrong

A contractor agreement without a liability section leaves both sides exposed to uncapped, unallocated risk. The standard structure: each party indemnifies the other against third-party claims arising from its own fault — the contractor for IP infringement, negligent performance, and breach of confidentiality; the client for claims arising from materials, data, or instructions the client supplied. Cap the contractor's aggregate liability (commonly at the fees paid under the agreement in the preceding 12 months), with carve-outs where a cap would be inappropriate: wilful misconduct, fraud, IP infringement, and confidentiality breaches. Require insurance proportionate to the work — commercial general liability as a baseline, professional liability / errors-and-omissions for advisory or technical work — and, for site-based trades work in Ontario, confirm WSIB coverage and clearance certificates before work starts. State expressly that the contractor is not an employee for any purpose, is not entitled to employee benefits, and is responsible for their own taxes and insurance — and then make sure the working relationship actually matches that statement.

Ontario specifics: what changes when the work is in Ontario

Canada-wide principles carry most of the weight, but Ontario adds four points worth naming in the agreement. First, the ESA section 5.1 misclassification prohibition: if the worker is really an employee, the ESA applies regardless of the contract, and the employer faces both ESA claims and CRA reassessment. Second, the non-compete position: Ontario's Bill 27 ban applies to employment contracts and agreements with employees (executive and sale-of-business exceptions only), so a genuine contractor agreement sits outside the ban — but any restraint is still tested for common-law reasonableness, and reclassification would bring the ESA analysis back into play. Third, tax and rates: 13% HST applies to taxable supplies in Ontario, and the $30,000 small-supplier threshold governs when GST/HST registration becomes mandatory. Fourth, dispute forum: Ontario Small Claims Court handles claims up to $50,000, so many contractor payment disputes never need a lawyer — but only if the contract's payment terms are clear enough for a deputy judge to apply without interpretation.

Mistakes that turn contractors into employees (or lawsuits)

Almost every contractor dispute traces back to one of these avoidable failures:

• Labelling an employee a contractor and running the relationship as employment — fixed hours, fixed location, direct supervision, no other clients
• No written IP assignment — the client paid for work it does not own, because Copyright Act section 13(1) gives the contractor first ownership
• Vague payment terms — no milestones, no acceptance criteria, no late-payment interest, and no tax treatment stated
• No termination clause — ending the engagement becomes a negotiation with no anchor and no notice period
• No confidentiality survival — the contractor walks away with the client list the day the contract ends
• No indemnity or liability cap — one defective deliverable becomes an uncapped claim
• A sweeping non-compete that a court refuses to enforce, while a narrow non-solicitation was never drafted
• Treating the contractor like staff for benefits, training, and performance reviews — each one is evidence of employment status
• Ignoring the $30,000 GST/HST threshold — the contractor fails to register, and the client faces invoices that never charged tax that should have been charged
• No subcontractor or assignment chain — the contractor's subcontractors never assigned their IP, so the client owns a deliverable with holes in it