What Should I Negotiate in My Employment Contract to Protect My Ideas?

You've just received a job offer. The salary is good, the role is solid, and you're ready to accept. But buried in section 12 of the employment agreement is a single paragraph that could cost you everything you build for the next five years — including that app idea you've been sketching out on weekends.

The IP assignment clause is the most underestimated, under-negotiated part of any employment contract. It's also the single most important clause for anyone who plans to build, create, or launch anything outside of their day job.

This guide walks through exactly what to negotiate, how to frame the conversation, and what specific language to push for — so you can accept the offer without surrendering your future.

• The IP assignment clause determines whether your employer owns your side projects — not your job title, not your working hours.
• Standard tech contracts claim all IP "during the term of employment" — including weekends and personal projects.
• Three non-negotiables: carve-out for pre-existing projects, carve-out for unrelated future projects, definition of "scope of employment."
• California Labor Code 2870 protections can be explicitly preserved in your contract. Several other US states have similar statutes you can reference.
• Frame negotiations around transparency and risk reduction for both parties — not personal ambition or startup plans.
• The right time to negotiate is after the offer but before you sign. Retroactive amendments are possible but harder.

The Standard IP Assignment Clause (And Why It's a Problem)

A typical tech or creative employment contract includes language that looks something like this:

"Employee hereby assigns to Company all right, title, and interest in any and all inventions, works of authorship, and intellectual property conceived, developed, or reduced to practice by Employee during the term of employment, whether or not during business hours or using Company resources."

Read that clause again. It doesn't say "work-related projects." It doesn't say "during office hours." It says during the term of employment — meaning anything you create while you work there, including the SaaS app you're building at 11pm on Sunday, technically belongs to your employer the moment you commit the first line of code.

Most people assume this is unenforceable overreach. In the UK, it often is — courts have pushed back on overbroad clauses that extend far beyond the employer's legitimate business interests. But the fact that a clause might be challenged successfully in court is not a strategy. Court is expensive, slow, and uncertain. The far better move is to negotiate clear boundaries before you sign.

In the US, several states provide statutory protection. California Labor Code Section 2870 is the strongest — it voids any clause that attempts to claim IP developed entirely on your own time, without company resources, that doesn't relate to the employer's business or anticipated research. Colorado, Delaware, Illinois, Kansas, Minnesota, North Carolina, Utah, and Washington have similar laws. But even in these states, the default contract language often contradicts the statute — and most employees never realize they have protection until it's too late.

The Three Contract Changes Every Side-Project Builder Needs

If you're building anything independently — or plan to — these three amendments to the standard contract are non-negotiable. They turn a legal grey area into a clean boundary.

1. Carve-Out for Pre-Existing Projects (Exhibit A / Schedule 1)

Most employment agreements include a blank page at the back labelled "Exhibit A: Prior Inventions" or "Schedule 1: Pre-Existing IP." This is where you list any projects, companies, or intellectual property you created before joining. If you leave it blank, you may be implicitly representing that you had nothing — which creates a legal problem if your pre-existing project later becomes valuable.

If you have a side project, a dormant LLC, a GitHub repo, a registered domain with any development activity, or even detailed notes on a concept — list it. Be specific: include the project name, a one-line description, and when you started it.

Example entry:
"TaskFlow — a personal productivity web app for freelancers. Initial development began in July 2025. Code repository and domain registered in my personal capacity prior to this employment."

Most employers will accept this without question. The ones who push back are signalling something important: they may try to claim your pre-existing work even if their contract says they won't.

2. Carve-Out for Unrelated Future Projects

This is the big one. You want explicit language that excludes personal projects developed on your own time, using your own resources, that don't compete with or relate to the employer's business.

Proposed amendment language:
"Notwithstanding the foregoing, the assignment in this Section does not apply to any invention, work, or intellectual property that Employee develops entirely on their own time without using the Company's equipment, supplies, facilities, or trade secret information, and that does not relate to the Company's business or actual or demonstrably anticipated research or development."

This language is based directly on California Labor Code 2870. If you're in California, you can reference the statute explicitly and ask for this carve-out to be added. If you're in another jurisdiction with similar protections, reference your state's statute. If you're in the UK or a US state without a statute, you can still request this language as a reasonable clarification of scope.

The critical piece here is "does not relate to the Company's business." This creates a clear test: if your employer makes project management software and you build a video game, the video game is carved out. If you build competing project management software, it's not.

3. Clear Definition of "Scope of Employment"

Even with carve-outs, the phrase "scope of employment" or "course of employment" creates ambiguity. You want the contract to define what that actually means.

Proposed language:
"For purposes of this Agreement, 'scope of employment' means work performed (i) during Employee's regular working hours, (ii) at Company premises or using Company equipment, or (iii) at the Company's express direction for the Company's benefit."

This turns a vague multi-factor legal test into a clear three-part definition. If you're not on the clock, not on company property, not using company equipment, and not acting on company instructions — it's outside scope. This definition protects you from arguments that anything a software engineer writes is automatically within scope because "you're always thinking about code."

The Moonlighting Policy: What It Means and What to Negotiate

Many UK and US employers include a moonlighting policy or outside employment clause, often buried in the employee handbook rather than the main contract. These clauses typically require you to disclose any outside business activities and obtain company approval before starting a second job or side business.

The most restrictive versions prohibit all outside employment or business activity without exception. The more reasonable versions allow outside work as long as it doesn't interfere with your job performance, use company resources, or compete with the company.

What to negotiate here:

• Explicit permission for non-competing side projects: Get written confirmation that you're allowed to operate a side business or freelance, as long as it doesn't conflict with your role or use company time/resources.
• No approval requirement for unrelated projects: Push back on any clause that requires pre-approval for activities completely unrelated to the company's business. Asking your employer's permission to launch a coffee blog when you work at a fintech company is unreasonable.
• Confidentiality carve-out: Make sure the moonlighting disclosure requirement doesn't force you to disclose confidential details about your project that could give your employer insight into your business model or customer base.

Practical framing: "I want to make sure I'm compliant with the moonlighting policy. I occasionally do small freelance projects unrelated to [Company's business area]. I'd like to add a note in the agreement confirming that non-competing outside work is permitted as long as it doesn't interfere with my responsibilities here."

Most reasonable employers will agree. The ones who refuse are telling you something about their culture.

California and State-Specific Protections: Lock Them Into Your Contract

If you're in California, your employment contract cannot override Labor Code Section 2870 — but many try. You want explicit confirmation in your contract that Section 2870 applies and that the IP assignment clause is subject to it.

Proposed language for California employees:
"This Agreement is subject to California Labor Code Section 2870, and nothing in this Agreement shall be construed to require assignment of any invention for which Employee cannot be required to assign rights under Section 2870."

This forces the employer to acknowledge the statute and prevents them from later arguing that the contract superseded it.

If you're in Colorado, Delaware, Illinois, Kansas, Minnesota, North Carolina, Utah, or Washington, check whether your state has a similar statute and request equivalent language referencing your state's code.

In the UK, there's no equivalent protection statute — which makes negotiated carve-outs even more critical. Without a clear contractual boundary, you're relying entirely on the common-law scope-of-employment test, which is a terrible position to be in if your side project takes off.

How to Raise Contract Changes Without Killing Your Offer

The number one fear people have about negotiating employment contracts is that they'll look difficult, distracted, or like they're planning to leave before they even start. This fear is legitimate — but avoidable with the right framing.

The conversation works when positioned as risk reduction and transparency, not personal ambition. Here's the structure that works:

Timing: Raise it after you receive the written offer but before you sign. This is standard negotiation timing. Don't wait until your first day.

Framing: Position it as mutual clarity, not a red flag.
"I've reviewed the offer and I'm excited to accept. I have a couple of small clarifications on the IP assignment section — I want to make sure we're both clear on scope so there's no ambiguity down the line. I have some pre-existing personal projects that are completely unrelated to [Company's business], and I'd like to list those on Exhibit A so they're explicitly excluded."

Tone: Professional, matter-of-fact, no defensiveness. You're not asking for permission to build a competing business. You're asking for documentation of a reasonable boundary.

Fallback if they push back: If the employer refuses any carve-out for unrelated personal projects, that refusal is meaningful information. It suggests they intend to enforce the broad language — which means you need to decide whether the job is worth giving up your ability to build independently for the duration of your employment.

In practice, most professional employers — especially at companies with mature legal teams — will accommodate reasonable carve-out requests. The standard contract language is often overbroad by default, and they know it. A candidate who asks for clarification is demonstrating legal literacy, not disloyalty.

What If You Already Signed? Retroactive Amendments

If you're currently employed and realize you signed a problematic IP clause without negotiating, it's not necessarily too late. Retroactive amendments are possible — but they require a different approach.

The challenge with retroactive amendments is that you're asking your employer to give up rights they currently have under the existing contract. Legally, this requires fresh consideration — you need to give them something in exchange. That "something" can be as simple as continuing your employment (courts have found this sufficient in some jurisdictions) or agreeing to additional confidentiality or non-compete terms.

The conversation is harder to initiate retroactively because it can look like you're preparing to leave or launch something. The framing needs to emphasize ongoing compliance and transparency:

"I want to make sure I'm fully compliant with our IP agreement. I have a personal project I've been working on in my own time that's completely unrelated to our work here — [brief one-line description, e.g., a mobile game, a photography portfolio site]. I'd like to document this explicitly with a carve-out amendment so there's no ambiguity. Would you be open to reviewing a proposed amendment?"

If your employer agrees, get it in writing as a formal contract amendment signed by both parties. An email acknowledgment is better than nothing, but it's not the same as a binding amendment.

If they refuse, you have three options: stop working on the personal project, accept the legal risk and continue anyway, or find a new job that will grant the carve-out. None of these are ideal — which is why negotiating before you sign is so much more effective.

Non-Compete and Non-Solicit Clauses: The Other Constraints to Watch

IP assignment clauses aren't the only restrictive terms in employment contracts. Non-compete and non-solicit clauses can block you from launching in your industry even if you own the IP.

Non-compete clauses prevent you from working for a competitor or starting a competing business for a set period after leaving. In the UK, these are enforceable only if they're reasonable in scope, duration, and geography. In the US, enforceability varies by state — California bans them almost entirely (except in narrow circumstances like sale of a business), while other states enforce them if reasonable.

What to negotiate:

• Narrow the definition of "competing business": Push for language that limits the restriction to the specific product line or service you worked on, not the entire industry.
• Reduce the duration: 12 months is more defensible than 24 months. Six months is better still.
• Limit geographic scope: If your role is UK-based, push back on worldwide non-competes.

Non-solicit clauses prevent you from recruiting your current colleagues or clients if you leave. These are generally more enforceable than non-competes because they protect legitimate business interests without blocking your ability to work.

What to negotiate:

• Limit to direct reports or close collaborators: Push back on company-wide non-solicit clauses that prevent you from ever working with anyone you met at the company.
• Exclude inbound approaches: Make sure the clause only covers active solicitation, not situations where a former colleague applies to your new company unprompted.

Both clauses should be reviewed by a solicitor if they're aggressive. The cost of a one-hour legal consultation is far less than the cost of discovering a clause is enforceable after you've already launched.

Documentation and Evidence: Build Your Paper Trail from Day One

Even with a perfect contract, you need evidence that your personal project was actually developed on your own time and resources. Corporate IP disputes often come down to forensic analysis of when and where work occurred.

Build this paper trail from day one:

• Separate devices: Buy a personal laptop for your side project. Keep the receipt. Never use your work laptop for any part of the project — not even once to check something.
• Separate accounts: Personal GitHub, personal domain registrar, personal cloud accounts. No SSO, no company email, no company credit card.
• Timestamped creation logs: Keep a dated journal or document describing your working sessions. Ideally stored in a personal cloud account with file creation timestamps visible.
• Separate network: Work on your project from home on your personal internet connection, never through a corporate VPN.
• Local file metadata: Don't rely only on Git commits. Courts and investigators look at local file creation timestamps, IDE session logs, and file modification history.

If you ever need to defend your ownership, this evidence is what makes your case defensible. Without it, you're asking a court to trust your memory over your employer's forensic IT audit.

Practical Takeaway

The best time to negotiate IP protections is before you sign the contract. The second-best time is now. The three changes that matter most are a carve-out for pre-existing projects, a carve-out for unrelated future projects, and a clear definition of scope of employment. Most professional employers will agree to reasonable carve-outs if you frame the conversation as transparency and risk reduction rather than ambition or distraction. If you're already employed and didn't negotiate, a retroactive amendment is possible but harder. If your employer refuses any carve-out for clearly unrelated personal work, that refusal tells you something important about whether the contract would be enforced. Build your evidence trail regardless — separate devices, separate accounts, separate networks, and a timestamped creation log. These protections turn a legally grey situation into a defensible one when your side project becomes your main project.

This article is for general informational purposes only and does not constitute legal advice. Employment contract negotiation involves jurisdiction-specific law and individual circumstances. Consult a qualified employment solicitor or attorney for advice on your specific situation.

FAQ

Can I negotiate my employment contract after receiving an offer?
Yes. The period between receiving a written offer and signing the contract is standard negotiation timing. Employers expect candidates to review terms and request clarifications or changes. Raising contract concerns at this stage is professional and normal — far easier than requesting retroactive amendments after you've started.

What is Exhibit A in an employment contract?
Exhibit A (or Schedule 1 in UK contracts) is a section where you list pre-existing intellectual property or projects you want excluded from the company's IP assignment clause. Leaving it blank may imply you represented that you had no prior inventions. Always list any side projects, companies, or intellectual property you created before joining.

Will asking for IP carve-outs make me look like I'm planning to leave?
Not if you frame it correctly. Position carve-outs as transparency and risk reduction for both parties: "I want to make sure we're both clear on scope so there's no ambiguity down the line. I have some personal projects completely unrelated to [Company's business], and I'd like to document that explicitly." Professional employers understand this request and accommodate it routinely.

What is California Labor Code Section 2870?
California Labor Code 2870 is a statute that protects employees from overbroad IP assignment clauses. It voids any contract provision attempting to claim IP that an employee developed entirely on their own time, without using company resources, and that doesn't relate to the employer's business or anticipated research. Several other US states have similar protections.

Can I add a carve-out to my contract after I've already started working?
Yes, through a retroactive contract amendment — but it's harder than negotiating before you sign. Retroactive amendments require fresh consideration (you giving the employer something in exchange for the change). The conversation must be framed around ongoing compliance and transparency rather than preparation to leave. Get any agreed amendment in writing as a formal signed document.

What counts as using company resources?
Company resources include: company-issued devices (laptops, phones), company network or VPN access, company-licensed software accounts (enterprise IDE licenses, AWS accounts), company office space or equipment, and company trade secrets or confidential information. Even one instance of accessing your personal project from a company device or network creates a documented connection your employer can use to assert a claim.