The SOW gets attention; the boilerplate gets you later. IP ownership, non-solicit and non-compete language decide whether you keep the value you paid for — or rent it temporarily.
Mid-market Canadian companies sign consulting agreements every week for strategy, technology, operations and finance support. Legal review often focuses on liability caps and payment terms. Intellectual property and restrictive covenants deserve equal scrutiny. This article translates common clauses into operator language so you know what to accept, redline or reject — and when to escalate to counsel.
This is not legal advice. Provincial employment and competition context varies; use it as a briefing note before your lawyer’s review.
Why IP clauses matter in advisory work
Consultants bring methods, templates and prior know-how. You bring data, processes and confidential strategy. The work product — models, playbooks, code snippets, training decks — sits in the middle. If the contract is silent or one-sided, you may discover after exit that you have a licence to use materials you thought you owned, or that the firm can reuse a thinly anonymized version of your operating model with a competitor.
Background IP vs foreground IP
Clean contracts distinguish:
- Background IP — tools, frameworks and materials the consultant owned before the engagement. They keep ownership; you get a licence to use what was embedded in deliverables for your internal business purposes.
- Foreground IP — materials created specifically for you in the engagement. Prefer assignment to the client on payment, or an irrevocable, perpetual, royalty-free licence that is exclusive for your competitive use.
- Third-party IP — software, stock content, licensed data. Consultant should warrant they have rights to include it and disclose restrictions.
Push for a schedule listing background tools that will appear in deliverables. Ambiguity here fuels disputes when you want to share a playbook with a new plant manager two years later.
Work product, raw files and derivatives
Specify delivery format: editable source files (Excel, PowerPoint, process maps), not PDF-only. Require return or certified destruction of confidential data at exit. If AI tools are used in delivery, state whether your confidential inputs may be used to train models — default answer for most mid-market buyers should be no without explicit consent.
Non-solicitation of employees
Mutual non-solicit is common and usually reasonable for a defined period (6–12 months) covering active solicitation of employees who worked closely on the project. One-sided clauses that only protect the consultant are a red flag. Carve out general job postings and candidates who apply without solicitation. Poaching your scarce engineer mid-ERP is a real risk — so is a firm blocking you from hiring someone who wants to join your operating team after a successful project.
Non-compete language — handle with care
Broad non-competes that stop a consulting firm from working with any competitor nationally are often impractical and may be resisted hard. Narrower protections work better: non-use of your confidential information; cooling-off on named direct competitors for a short period if truly sensitive; and strong confidentiality with injunctive relief language.
Separately, consultants sometimes ask clients not to hire their people. That is a non-solicit of the firm’s employees — negotiate duration and scope, and consider a conversion fee as an alternative to a hard ban if you might want to hire a contractor who proved essential.
| Clause | Client-friendly position | Watch-outs |
|---|---|---|
| Foreground IP | Assign to client on payment | “All IP remains with consultant” |
| Background IP | Licence for internal use | Licence that expires with MSA |
| Employee non-solicit | Mutual, 6–12 months, active solicit only | One-way, overly broad definitions |
| Competitor non-serve | Narrow, time-limited, named if needed | Industry-wide bans |
| Confidentiality | Survives termination; PIPEDA-aware | Weak return/destruction duties |
Confidentiality and data
Require PIPEDA-aware handling, access on a need-to-know basis, subprocessor disclosure, and breach notice timelines. For Quebec, consider Law 25 obligations in the same breath. Ban onward sharing of your data room with offshore teams unless disclosed and approved. If the firm uses subcontractors, flow down the same IP and confidentiality terms.
Liability, disclaimers and reliance
Consultants will disclaim that advice is not a guarantee of results and will cap liability — often at fees paid in the prior 12 months. Negotiate carve-outs for IP infringement, confidentiality breaches, and wilful misconduct. If lenders or boards will rely on a report, clarify whether reliance letters are available and at what cost — especially in diligence contexts.
Termination and wind-down
Termination for convenience (14–30 days) with payment for work performed protects you when fit is wrong. On exit: deliver work-in-progress, return data, confirm licence survival for paid foreground IP, and complete knowledge-transfer sessions already paid for. Do not let IP assignment be conditional on disputes unrelated to ownership.
Negotiation sequence that saves time
- Agree commercial model and scope first.
- Redline IP, confidentiality and non-solicit before debating every liability comma.
- Align MSA and SOW — SOW should not silently override IP in the MSA.
- Have business owners initial the IP schedule so nobody is surprised at exit.
Practical examples
A Prairie manufacturer paid for a maintenance playbook, received PDFs only, and later learned the editable templates were background IP licensed only during the MSA term. A one-line fix — perpetual internal-use licence plus source files — would have preserved value. A Toronto scale-up discovered their pricing model had been reused in a competitor pitch deck with light anonymization; stronger foreground assignment and confidentiality remedies would have changed leverage.
Open-source and prior-art grey zones
Consultants sometimes embed open-source scripts, publicly known frameworks, or lightly customized industry benchmarks. Your contract should require disclosure of open-source components and licence obligations. You do not want a surprise copyleft issue in a tool that touches customer data. For benchmarks, insist on documentation of sources so you can defend numbers to a board or buyer later.
If the firm uses proprietary accelerators (pricing engines, diagnostic survey instruments), negotiate a continued internal-use licence after termination at no extra fee for artifacts already paid for. Subscription traps — “the dashboard dies when the MSA dies” — should be priced and accepted deliberately, not discovered at exit.
Multi-province and cross-border wrinkles
When advisors or subcontractors sit outside Canada, update confidentiality and data-transfer language accordingly. Name permitted geographies for data processing. For engagements spanning U.S. affiliates, clarify which entity owns foreground IP and whether licences are group-wide. Related-party confusion between Holdco and Opco is a common mid-market mess — specify the client entity carefully.
Non-solicits that purport to cover “any affiliate worldwide” may be broader than you intend. Align geography and entity lists with how your corporate chart actually works.
Playbook for your counsel kickoff
Send counsel a one-pager: deal value, strategic sensitivity of the IP, whether you might hire their people, whether competitors are obvious, and your must-have positions on assignment vs licence. Counsel then redlines faster. Business owners who dump a 40-page MSA with “please review” and no priorities pay for hours of abstract caution.
After signature, store the IP schedule and final MSA where future leaders can find them. Acquisition diligence two years later will ask who owns the playbooks — be ready.
Bottom line
Pay attention to who owns what you are buying, who can hire whom, and how confidential know-how is fenced. Canadian mid-market buyers do not need aggressive overreach — they need clarity. Get IP and restrictive covenants right at signature, and the engagement can end with assets you still control rather than memories of a great workshop.
If the contract says you own the insights but only licenses the files, you bought a story — not an asset.
