What to Look for Before Signing a Consulting Agreement

Consulting agreements are one of the most common contracts in business, and one of the most misunderstood. Whether you're the consultant being brought in for an engagement or the company hiring one, the terms of this agreement define everything — what's being delivered, how much it costs, who owns the work, and what happens when things go sideways.

Most consulting agreements look similar on the surface. They typically cover scope of work, compensation, intellectual property, confidentiality, term and termination, and a handful of general provisions. But the details within each section can vary dramatically, and those details are where risk lives.

Here's what to pay attention to.

Scope of Work

This is the foundation of the entire agreement. A well-defined scope protects both parties — the consultant knows exactly what's expected, and the company knows exactly what they're getting.

Watch for scope definitions that are vague or open-ended. "Consultant shall provide strategic advisory services as requested by Company" gives the company unlimited ability to expand what they ask of you without changing the compensation. Compare that to "Consultant shall deliver a market analysis report covering [specific topics], a 60-minute presentation to the executive team, and two rounds of revisions" — that's specific, bounded, and measurable.

If the scope is vague, everything else in the contract — payment, timeline, IP — becomes harder to evaluate because you don't have a clear baseline for what the engagement actually involves.

Compensation and Payment

Beyond the dollar amount, look at the mechanics. When are you paid — upon delivery of milestones, monthly, or upon "completion" of the project? If it's the latter, who defines when the project is complete?

For hourly engagements, is there a cap on hours? If not, is there a mechanism for approving additional hours? For fixed-fee engagements, what happens if the scope expands beyond what was originally defined?

Payment timing matters too. Net 15 is very different from Net 60. For consultants, cash flow is often tight, and a 60-day payment cycle on a 3-month engagement means you might complete half the project before receiving any payment.

Look for late payment provisions. If the company pays late, are there consequences? Interest charges? Your right to pause work? If the contract is silent on late payment, you have limited leverage if invoices go unpaid.

Intellectual Property

IP is where consulting agreements get complicated. The default assumption in most agreements is that the company owns everything the consultant produces during the engagement. That's generally reasonable for the specific deliverables — the company is paying for that work.

Where it gets problematic is when the assignment clause extends beyond the deliverables. Does the company claim ownership of your pre-existing tools, frameworks, or methodologies that you use in the engagement? If you have a proprietary process or analytical framework that you bring to every client, you need to make sure it's excluded from the IP assignment.

Look for a "pre-existing IP" or "consultant tools" carve-out. This is a provision that explicitly states that your pre-existing intellectual property remains yours, and the company receives only a license to use it within the deliverables.

Also consider work product developed for other clients. If you're doing similar work across multiple engagements, broad IP clauses could create conflicts where two different clients both claim ownership of overlapping work.

Confidentiality

Most consulting agreements include mutual confidentiality obligations, which is standard. What varies is the scope and duration.

Pay attention to how "confidential information" is defined. Broad definitions that include "any information disclosed during the engagement, whether or not marked as confidential" can be difficult to comply with in practice — especially if you're in meetings where information flows freely.

Duration matters too. A 2-year confidentiality period post-termination is standard. A 5-year or perpetual obligation is more aggressive. Consider what's realistic given the nature of the information and the industry.

Also look for whether the obligations are truly mutual. If only the consultant has confidentiality obligations but the company doesn't, that's a one-sided arrangement — especially relevant if you're sharing your own proprietary methodologies or business information during the engagement.

Term and Termination

How long does the agreement last, and how can either party end it?

The healthiest termination provisions are symmetric — both parties can terminate with reasonable notice (14 to 30 days is common) for any reason. This gives everyone an exit if the engagement isn't working.

What happens upon termination is equally important. Do you get paid for work completed up to the termination date? Is there a kill fee if the company terminates early? Do you have to return all materials, or can you retain copies of your own work product?

Watch for termination "for cause" provisions that are overly broad. If "cause" includes things like "failure to meet Company's expectations" — which is subjective — the company could terminate for cause (potentially avoiding payment obligations) based on a standard that's impossible to objectively verify.

Limitation of Liability

This determines your maximum financial exposure if something goes wrong. Without a liability cap, your exposure is theoretically unlimited — meaning a project worth $20,000 could generate liability claims far exceeding that amount.

The standard approach is to cap each party's liability at the total fees paid or payable under the agreement. This is generally considered balanced and reasonable.

Look for whether the cap applies to both parties or just one. If only the consultant's liability is capped (or worse, if neither party's liability is capped), the risk allocation is skewed.

Also look at indemnification obligations. Indemnification means one party agrees to cover the other's losses in certain situations. Broad indemnification obligations without corresponding liability caps can create significant exposure.

Non-Compete and Non-Solicitation

Not all consulting agreements include these, but many do. A non-compete restricts what kind of work you can do after the engagement ends. A non-solicitation typically prevents you from hiring the company's employees or soliciting their clients.

For consultants, non-competes can be particularly impactful. If your consulting practice serves a specific industry, a broad non-compete could effectively shut down your business for the restricted period.

Evaluate non-competes on three dimensions: duration (how long), geography (where), and scope (what activities are restricted). The narrower each dimension, the more reasonable the restriction.

Governing Law and Dispute Resolution

This determines where and how disputes are resolved. If you're a consultant based in New York working with a company in Texas, and the contract specifies Texas law and Texas courts, you'd need to litigate in Texas if there's a dispute.

Arbitration clauses are also common. Arbitration is generally faster and more private than court litigation, but it can also be more expensive upfront and limits your right to appeal.

Consider whether the governing law and venue are practical for you if you ever need to enforce the agreement or defend against a claim.

Check Your Consulting Agreement

If you're reviewing a consulting agreement right now — whether you're the consultant or the company — paste it into dott.legal and get a free risk analysis. The tool evaluates all of the areas above and gives you a risk score in 30 seconds.

If you want a licensed attorney to review the findings, provide specific contract edits, and deliver a professional legal memo, Dott offers attorney-validated review for $349 with 24-hour turnaround.