Welcome to Legal Support
Plain-language guides on the contract terms consulting professionals actually negotiate. Browse by topic, or jump to the consultant toolkit for checklists, myths, sample clauses, glossary, and a stage-by-stage journey map.
Practical legal guides for consultants
Plain-language walkthroughs of the contract terms and concepts that come up most often in consulting work. Each topic links to a deeper guide below.
Confidentiality & NDAs
01.1What confidentiality actually covers›
A confidentiality obligation only protects information that is non-public, identifiable, and disclosed under the agreement. The clause usually defines “Confidential Information” broadly — business plans, customer data, pricing, methodologies — then adds standard exclusions for information that is public, independently developed, lawfully received from third parties, or compelled by law.
Practical takeaway: when you exchange a deck or a model, drop a small footer marker (“Confidential — subject to NDA”). It makes enforcement easier later.
01.2How long obligations last›
Most consulting NDAs run 2–5 years after termination. Trade secrets are typically protected for as long as they remain trade secrets (no fixed sunset). If a counterparty wants a 7-year or perpetual term on regular confidential info, push back — that’s outside market norms for most engagements.
01.3Mutual vs. one-way NDAs›
A mutual NDA protects both parties equally. A one-way NDA protects only the disclosing party. For consulting, mutual is almost always the right answer — your methodologies, references, and rate cards deserve the same protection as the client’s business data.
Watch for one-way NDAs that look mutual but exclude consultant-provided information from the definition of Confidential Information. Read the definitions carefully.
Intellectual property
02.1Pre-existing vs. project-specific IP›
The cleanest framing: each party retains its pre-existing IP, including methodologies, templates, and general know-how. Project-specific deliverables — the actual report, code, or analysis built for the client — are typically assigned to the client upon full payment.
Without that carve-out, an aggressive “work-for-hire” clause can sweep up your generic frameworks too. Always preserve your right to reuse general approaches across clients.
02.2License-back for portfolio use›
If you want to reference an engagement in case studies or sales materials, build the right in upfront. Two common approaches:
- A general license to reference the engagement at a high level (no confidential data, no logos without separate approval).
- An explicit logo-and-name approval workflow (typically with marketing or PR sign-off).
Add this to the SOW, not buried in MSA boilerplate — it’s easier to negotiate at the project level.
02.3Code, data, and third-party tools›
If your work involves code or data:
- Identify any open-source dependencies in the deliverable and confirm license compatibility (MIT/Apache vs. GPL matters).
- Carve out tools and libraries that exist independently of the engagement — you keep the rights.
- Be explicit about data ownership: client data stays client data; your derived models or insights may be project-specific deliverables.
Scope & change orders
03.1Make scope concrete, not aspirational›
Vague SOW language — “advise on go-to-market strategy” — invites unbounded scope creep. Tighten with:
- Specific deliverables: “30-page diagnostic report,” “3 workshop sessions of 4 hours each,” “final readout to executive committee.”
- Explicit exclusions: “Does not include implementation support, vendor selection, or post-launch monitoring.”
- Assumptions: “Client will provide access to sales data within five business days of kickoff.”
03.2How a clean change order works›
When the client asks for “just one more thing,” you need a frictionless mechanism to capture it. The pattern:
- The MSA includes a short Change Control clause requiring written agreement for scope changes.
- You email a one-page change order — what’s added, how it shifts the timeline, what the additional fee is.
- Client signs (or replies with explicit approval). Work proceeds.
The friction of putting it in writing surfaces tradeoffs early. That’s the whole point.
Payment & collections
04.1Invoicing rhythm›
Three common patterns, in order of consultant-friendly to client-friendly:
- Retainer / advance: monthly fee invoiced at the start of the month. Standard for advisory work.
- Milestone-based: invoices tied to specific deliverables. Good alignment, but cash flow lumps up.
- Net-30 arrears: work performed, then billed. Easiest for the client, hardest for you — you’re funding their working capital.
04.2Late fees that actually help›
1.5% per month (or the max allowed in your jurisdiction) is market-standard for late payment interest. The real power isn’t the revenue — it’s the conversation starter when an invoice goes 60+ days. You can wave the fee away as a goodwill gesture in exchange for prompt payment.
Also helpful: a clause that lets you suspend services if an invoice is more than 30 days overdue. This needs to be in the contract; you can’t add it after the fact.
04.3When to escalate›
Reminder → account contact reach-out → formal demand letter → suspend services → collections or small-claims. Move through the steps cleanly. Most non-payment situations resolve at the “account contact reach-out” stage if you’re paying attention.
Liability & insurance
05.1Cap your aggregate liability›
Standard market practice: cap aggregate liability at fees paid in the previous 6–12 months. Without a cap, your downside on a single engagement is unlimited — a deal-killer for many consultants and a real risk for small firms.
Carve-outs that legitimately bypass the cap: confidentiality breach, IP infringement, gross negligence, willful misconduct. Be cautious about agreeing to broader carve-outs — especially anything involving “data” or “privacy” unless you understand the scope.
05.2Exclude consequential damages›
You don’t want to be on the hook for “lost profits” or “business interruption” flowing from your work product. Standard exclusion language:
05.3Professional liability insurance›
Many enterprise clients require evidence of E&O (errors and omissions) insurance — typically $1M–$5M per claim. If you’re solo or small, this is usually a few hundred to a few thousand dollars per year and dramatically de-risks your downside. Don’t skip it.
Termination & exits
06.1Termination for convenience›
Either party should be able to walk away with reasonable notice — typically 15 to 30 days. Shorter notice (7 days) is fine for advisory retainers; longer (60 days) for capital-project engagements where ramp-down has real costs.
For your protection, fees for the current period (current month, current sprint, current milestone) should be non-refundable. You did the work; you get paid for it.
06.2Termination for cause›
Material breach — uncured after a reasonable notice period (10–30 days is standard) — should trigger an immediate right to terminate. Insolvency events (bankruptcy filing, dissolution, prolonged inability to pay) typically allow immediate termination without notice.
06.3What survives termination›
Always confirm these survive:
- Confidentiality (for the agreed term post-termination)
- Payment obligations for work already performed
- IP assignments for paid-up deliverables
- Indemnification, liability caps, and dispute resolution
If a survival clause is missing or narrowly drafted, ask for the standard list.
Consultant legal toolkit
From your readiness checklist to common legal myths, sample clauses, plain-English vocabulary, and a stage-by-stage journey map.
Legal readiness checklist
Run this list before you start any new engagement.
- Written contract signed by both parties.
- Clear payment terms (amount, schedule, late fees).
- Defined IP ownership for deliverables.
- Specific scope of work and boundaries.
- Termination clause with reasonable notice.
- Verified client entity and signatory authority.
- Named jurisdiction and governing law.
- Signed copy stored securely (cloud + offline).
- Criteria for when to seek legal review.
Common legal myths
Five beliefs that get consultants in trouble — and what's actually true.
M1“If it’s in an email, it’s legally binding.”›
Not always — it depends on intent, jurisdiction, and the clarity of terms. Some jurisdictions are stricter than others about what counts as offer, acceptance, and consideration. For anything material, get a signature.
M2“NDAs cover everything.”›
They only cover what is explicitly defined as Confidential Information. The definition is the most-negotiated paragraph for a reason. Read it carefully.
M3“Clients can’t reuse my work.”›
Only true if IP ownership and license terms are clearly defined in writing. Default rules vary by jurisdiction and engagement type. Put it in writing.
M4“All contracts must be notarized.”›
Most consulting contracts don’t require notarization. Mutual signatures and witnesses are usually sufficient. Exceptions exist for certain real estate, IP assignment, or international filings — check the specific requirements.
M5“Verbal agreements are enough.”›
They’re risky and hard to enforce — the “he said / she said” problem is real. Always capture key terms in writing, even if it’s just a confirmation email summarizing what was discussed.
Sample clause library
Five reference clauses to adapt for your own agreements. Edit the bracketed placeholders for your specifics — and have counsel review before signature.
Legal vocabulary simplified
Six terms that come up constantly in consulting contracts — explained in plain English.
Indemnification
One party agrees to cover the other’s losses or legal costs arising from specified events. Watch the scope — broad indemnities can be expensive.
Force majeure
Unexpected events (natural disasters, war, government action) that excuse a party’s obligations temporarily. Post-COVID, pandemics are often explicitly included.
Governing law
The state or country whose laws apply if there’s a dispute. Different jurisdictions interpret contracts differently — this choice matters more than it looks.
Work-for-hire
A clause that gives the client default ownership of work product. Be careful — without carve-outs, it can sweep up your general methodologies and tools.
Waiver
When a party chooses not to enforce a right in a specific instance. A well-written waiver clause confirms this doesn’t mean the right is permanently lost.
Liability cap
A maximum limit on damages one party must pay. Standard practice is to cap at fees paid in the prior 6–12 months, with carve-outs for confidentiality, IP, and gross negligence.
Independent consultant legal journey map
Plan your legal steps at each stage to reduce risk and stay protected.
J1Before engagement›
- NDA in place for sensitive information.
- Clarify IP ownership in writing before any work product is created.
- Confirm agreement structure (SOW under existing MSA, or new MSA + SOW).
- Verify signatory authority on both sides.
J2During engagement›
- Track milestones and deadlines.
- Document scope clarifications via written change orders.
- Invoice per schedule and monitor payment age.
- Keep version-stamped deliverables in a secure archive.
J3At completion›
- Secure formal sign-off and acceptance from the client.
- Transfer deliverables and access cleanly — record what was handed over.
- Confirm final payment, then close outstanding obligations.
- File the signed contract and engagement records for your future records.
Need hands-on support?
Our advisory team helps consultants and small firms with engagement structuring, document review, and consulting workflows. Reach out when you need a real human to weigh in.
› advisory@velorstrategy.com