UK IP Lawyer’s Guide For International Consultants & Founders
Founders, Consultants, Employees: What UK Law Means for Your Off-Hours Innovations
What Are the UK IP Risks for Innovators and Founders?
This article is for the senior researcher, founder, engineer or consultant who is relocating to the UK to take up a role at a serious technology business while also intending to build something of their own. That profile is common in artificial intelligence, advanced software, media technology, biotech, life sciences, quantitative research and drug discovery. A US founder moving to UK employment often assumes that work developed privately, on personal time, using personal devices, remains personal property. Under UK law, that assumption is often wrong.
The point matters most before signature. Once a UK employment contract has been signed, broad invention assignment language, disclosure obligations, confidentiality provisions, garden leave terms and restrictive covenants may already be in place. At that stage, the discussion is no longer about preserving freedom of action in principle. It becomes a dispute about what has already been assigned, what must be disclosed, and whether future business plans are too close to the employer's field. For researchers and founder-consultant-employees working at the frontier of technology, the legal risk is not abstract. It goes directly to ownership of the most valuable asset a future company may have: its core intellectual property.
This article explains how UK employment IP rules actually work for international consultants, employees and founders across AI, biotech, software, drug discovery and other research-intensive sectors — why weekend inventions may already belong to an employer, what can be done about it before signing, and how a structured founder IP strategy can preserve the value of the business a founder intends to build.
UK IP Essentials for International Consultants & Founders
Your Next Big Idea in the UK? Why It May Be Your Employer's, Not Yours
At serious technology companies in the UK, invention assignment clauses are routine. They are designed to ensure that intellectual property created by employees is owned by the employer, either automatically by statute or by express contractual assignment. The statutory starting point is already employer-friendly.
Section 11 of the Copyright, Designs and Patents Act 1988 provides that where a work is made by an employee in the course of employment, the employer is the first owner of copyright, subject to any agreement to the contrary. The copyright vests in the employer from the moment of creation — without any further act, agreement or payment required. For patents, section 39 of the Patents Act 1977 provides that an invention made by an employee belongs to the employer if it was made in the course of the employee's normal duties, or duties specifically assigned to them, where an invention might reasonably be expected to result, or where the employee had a special obligation to further the employer's interests. Section 42 of the same Act is also relevant: it reflects duties imposed on employee inventors in certain contracted roles, reinforcing that invention-related obligations can sit squarely inside the employment relationship, not merely alongside it.
That is only the baseline. Employment IP assignment UK drafting in deep-tech companies usually goes much further. Contracts commonly purport to assign all rights in inventions, software, code, models, documentation, research outputs, databases, methodologies, designs, know-how and related materials created during employment — whether created during working hours or otherwise, whether on employer systems or personal equipment, and often during any period of notice or garden leave. Some clauses extend to anything connected with the employer's business, anticipated research programmes, or future commercial direction.
A realistic paraphrased clause in a deep-tech contract might read as follows. First, it may state that the employee assigns to the employer, with full title guarantee, all intellectual property rights in any invention, work product, software, data compilation, process, improvement or discovery created, conceived, reduced to practice or developed by the employee during employment. That sentence aims to catch both early-stage concepts and fully developed assets. It may then state that this applies whether created alone or jointly, during or outside normal working hours, and whether using the employer's equipment or the employee's own devices. That is the element many founders underestimate, because it detaches ownership from time and equipment entirely. Next, it may state that the assignment covers anything relating to the employer's business, research activities, actual or proposed products, or any matter arising from the employee's duties — a formulation that expands the field of capture far beyond the exact wording of any job title. The clause may also require the employee to disclose promptly all inventions and execute any further documents needed to vest title, support patent filing, waive moral rights where relevant, and assist both during and after employment. That combination gives the employer both ownership and documentary control.
For a research scientist, principal engineer or machine learning specialist, the scope matters more because the role is likely to generate assets sitting at the border between copyright, patent, database rights and confidential information. The relevant outputs may include algorithms, model architectures, training and evaluation pipelines, datasets, data labelling structures, research methodologies, experimental workflows, optimisation methods, patentable methods and platform design. In that environment, an intellectual property assignment clause UK provision is not an administrative afterthought. It is often the most commercially significant clause in the contract.
UK IP Risks: A Practical Guide for Global Innovators
Elite Talent in the UK: How Employment Law Claims Your Inventions—Even Outside 9 to 5
The most common mistake is to treat the issue as a time question. It is not. The fact that work was done in the evening, at the weekend, on annual leave, on a home computer or in a private notebook does not by itself answer the ownership question under UK law. The legal test is substantive.
Courts look at what the employee was engaged to do, what the employer's business and research direction actually were, whether the invention arose from the employee's normal duties or from duties specifically assigned, and whether an invention might reasonably have been expected to result. They also look at overlap: was company infrastructure used, was any employer data involved, was confidential information drawn upon, did the work emerge from the same technical problems being tackled at work, and does the independent project sit in the same research domain?
That approach is grounded in Electrolux Ltd v Hudson [1977] FSR 312, a foundational decision on employee inventions. The case is repeatedly cited for the proposition that the focus is on the employee's actual duties and whether the invention arose from them — not on simplistic labels or after-the-fact descriptions of timing. The inquiry is grounded in substance: what was this person really employed to do, and was invention a reasonable expected incident of that role?
The same practical warning emerges from Helmet Integrated Systems Ltd v Tunnard [2006] EWCA Civ 1735. Although the facts involved wider duties questions, the case is a strong reminder that developing something in one's own time does not insulate a person from challenge if it overlaps materially with the employer's field and duties. For researchers and technical founders, that is the real risk zone. A side project may feel separate because it was developed privately, but if it addresses a similar technical problem or commercial application, the employer may still argue ownership, misuse of confidential information, breach of duty, or all three.
The questions that actually matter are therefore direct. Is the invention related to the work the employee is hired to do? Was any confidential information used? Was any company equipment, computing resource, dataset, model, system or infrastructure used? Does the contract contain broad assignment language? Does it require disclosure of outside inventions? Was any work done using employer accounts, repositories, devices or development environments?
Research and invention do not happen in clean, compartmentalised blocks. Ideas arise across conversations, reflections and professional context. The knowledge a researcher brings to independent work is shaped continuously by professional experience. That is precisely why the temporal framing — "I did it on Saturday" — is legally insufficient. The correct framing is one of scope and subject matter, and protecting that scope requires careful contractual drafting before employment begins.
UK IP Risks for Cross-Border Innovators
Tech, Media & Science Professionals: The UK's Surprising Claim on Your Side Hustle IP
There is a further risk that most founders and researchers overlook entirely, and it sits alongside the assignment clause rather than within it. It is the disclosure obligation.
Many employment contracts at deep-tech companies require the employee to disclose all inventions created during employment, all side projects and outside businesses, all pre-existing inventions, and sometimes any future business ideas that may connect with the employer's area of activity. Even where ownership does not transfer automatically, a broad disclosure obligation gives the employer early visibility over independent work. Once disclosed, the employer can assess whether the work falls within the assignment wording, whether it raises confidentiality concerns, or whether it justifies a demand for restriction.
For inventors and researchers, this creates an evidential problem as well as a legal one. If a future startup later develops in an adjacent technical area, the employer may say it was notified, considered the project part of the overlap zone, and never accepted the employee's position that it sat outside employment duties. A history of feeding detailed descriptions of independent ideas into a former employer's disclosure systems can complicate investor diligence and negotiations years later, even where the law might ultimately favour the founder.
That is why any employment contract IP review UK exercise must examine disclosure wording separately from assignment wording. A carve-out that excludes independent projects from assignment is incomplete if the same projects must still be reported in full under a broad disclosure provision. Before signing, a founder needs to understand exactly what must be disclosed, when, to whom, and on what terms — and any carve-out must address both the assignment and the disclosure obligation explicitly.
UK IP Risks for Global Talent: A Practical Overview
The risk profile changes significantly when the founder's independent work and the employer's business inhabit the same broad technical domain. That is often the reality for founders who are also senior researchers: they are hired precisely because their expertise is at the frontier, and their future startup plans occupy similar intellectual terrain.
The closer the overlap in technical area, business objective, datasets, research methods or commercial application, the greater the chance of a future ownership or confidential information dispute. A researcher employed to develop AI models for drug discovery who independently plans to build AI tools for adjacent pharmaceutical or biotech applications faces a situation where the assignment clause, disclosure obligations and confidentiality provisions may all be triggered simultaneously. Without careful contractual protection, a founder may inadvertently assign the most commercially valuable parts of their future business to the employer before incorporation documents are even drafted.
There is no fixed legal rule specifying how far apart two workstreams must be. The better question is whether there is demonstrable separation. Can the founder show that the independent project has distinct aims, distinct materials, distinct development records, distinct infrastructure and no use of employer confidential information or resources? Can that separation be documented contemporaneously rather than reconstructed after the fact? Without that evidential discipline, the overlap problem may not be resolvable regardless of what the founder believed at the time.
This also matters for funding. In investor diligence, one of the earliest questions is whether any former employer could claim ownership of the company's core technology. If the answer is uncertain — no carve-outs, no pre-existing inventions schedule, a history of broad disclosure to a powerful former employer operating in the same field — that can delay investment, reduce valuation or end the process entirely. Founder IP strategy UK work needs to begin while employment terms are still being negotiated, not after the company is already pitching investors.
Cross-Border Innovators: Navigating UK IP Risks
Founders, Consultants, Employees: What UK Law Means for Your Off-Hours Innovations
Garden leave is a standard UK employment device, but many overseas founders have never encountered it in practice. It refers to a period during notice when the employee remains employed and continues to be paid, but is instructed not to attend work or not to perform their usual duties. They are still an employee. The contract is still in force. Duties of confidentiality, disclosure and intellectual property assignment generally continue unless the contract expressly provides otherwise.
This creates a trap for technical employees who assume that a quiet notice period can be used productively to build a startup. The legal problem is straightforward: if the person is still employed, the invention assignment clause may still apply. The point becomes sharper because, during garden leave, there may be no meaningful concept of ordinary working hours. A researcher who develops a substantial new methodology or advances an independent project during a six-month garden leave period may find that the resulting IP belongs to the employer if it falls within the assignment clause and no express carve-out covers that period.
Garden leave must also be distinguished from post-termination restrictive covenants. Garden leave is simply employment continuing. Restrictive covenants apply after employment ends and are governed by the restraint of trade doctrine. The classic authority is Nordenfelt v Maxim Nordenfelt Guns and Ammunition Co [1894] AC 535, which remains the foundation for reasonableness analysis in restrictive covenant UK employment disputes. Post-employment covenants must be reasonable in scope, duration and geography to be enforceable — but what is reasonable for a senior technical employee at a deep-tech company may be more extensive than an international founder expects. Covenants of up to twelve months covering the relevant technical field and major commercial territories are regularly upheld for senior research roles.
The practical point is often missed in negotiations. A carve-out for independent IP that applies only during active service is not enough. If the contract allows for lengthy garden leave, the carve-out must state clearly that it continues through any notice period and any period of garden leave, and not merely during active employment.
Mastering UK IP: A Guide for Global Innovators
From Consulting to Inventing: Navigating IP Ownership as a Skilled Migrant in the UK
The good news is that carve-outs are not unusual. In well-drafted technology employment agreements, they are a recognised way to separate the employer's legitimate claim to employment-generated IP from the employee's existing and independent work. For an IP lawyer for cross-border employees or an IP lawyer for cross-border consultants, this is standard drafting territory, particularly where the individual already has research assets, code repositories, unpublished methods or plans for a future venture.
The timing matters. The right moment to negotiate a carve-out is before signature, when the employment contract is still being agreed. After joining, the employer has much less incentive to amend the bargain, and the employee is negotiating from a weaker position. If the individual does not yet have a company, that is not a reason to delay. In fact, it makes early drafting more important, because the assets still sit personally with the founder and need to be identified clearly before employment starts.
The first mechanism is a pre-existing inventions schedule. This is an annex to the contract listing the employee's existing intellectual property and excluding it expressly from the assignment clause. For a founder or researcher, that may include software, source code, notebooks, algorithms, model architectures, datasets, data schemas, evaluation frameworks, research methodologies, patent applications, draft papers, prototypes, domain names and know-how. The schedule should be specific enough to identify the asset class and subject matter without disclosing unnecessary confidential detail to the employer. A practical paraphrased entry might read: "Pre-employment machine learning workflow and associated evaluation framework for predictive analysis in [defined field], including source code modules, model design notes, benchmark methodology, dataset curation structure and all related documentation created before the employment commencement date." That works because it identifies the asset, the field, the component parts and the timing basis for exclusion — creating a contemporaneous written record that both sets expectations and supports the company's chain-of-title story when investors and acquirers later ask hard questions.
The second mechanism is a field carve-out. This defines a technical and commercial area that sits outside the employer's business or research domain, and states that intellectual property developed in that excluded area will not fall within the assignment clause. The drafting challenge is precision. If the carve-out is too broad — for example, "all personal projects" — a serious employer will resist it. If it is too narrow, it may miss the founder's actual plans. A paraphrased field carve-out might specify that the employer's business covers "AI models and systems for [narrowly described class of problems]" and that the employee's independent work in "AI tools for [distinct but related class of problems]" is excluded, provided those activities do not relate to the employer's current or planned research programmes, do not use employer resources or confidential information, and do not interfere with employment duties. Each element matters: subject matter separation, clean-room development, and no performance conflict.
The third mechanism is an independent project clause. This is express permission to continue or develop a named project during employment, subject to defined conditions: no use of employer equipment or infrastructure, no use of confidential information or trade secrets, no conflict with employment duties. It creates a defined operational space for independent work and reduces later argument about whether the employer knew of and accepted the arrangement. For most founder-side situations, the strongest protection comes from combining all three tools: a pre-existing schedule, a field carve-out, and an independent project clause. All three must address the disclosure obligation as well as the assignment, and all three must expressly cover the garden leave period.
UK Bound: The Hidden IP Dangers for Global Elite in Tech, Media, and Science
A US founder moving to UK employment often brings assumptions shaped by their home jurisdiction, and nowhere is the contrast sharper than California. California Labor Code section 2870 limits the reach of invention assignment clauses in that state. In broad terms, an employer generally cannot require assignment of an invention developed entirely on the employee's own time, without using employer equipment, supplies, facilities or trade secret information, except where the invention relates to the employer's business or results from work performed for the employer. That is a meaningful statutory protection and many California-based founders internalise it as a general rule — that what they build on their own time is theirs — and then carry that assumption with them when accepting a UK role.
There is no UK equivalent of section 2870. UK law does not provide a statutory safe harbour stating that privately created inventions automatically remain with the employee if developed off-hours on personal equipment. Instead, the analysis turns on statutory ownership rules under sections 39 and 42 of the Patents Act 1977 and section 11 of the Copyright, Designs and Patents Act 1988, the express wording of the contract, confidentiality obligations, actual duties, and the factual question of whether the work arose in the course of employment. That can produce a materially broader result than a California-accustomed founder expects.
The non-compete environment is also different. California treats post-employment non-competes as effectively void as a matter of public policy. UK law allows restrictive covenants that are reasonable and protect legitimate business interests — and what courts regard as reasonable for a senior researcher at a deep-tech company may be more extensive than expected. The same contrast applies for senior technical professionals arriving from Germany, the Netherlands, Japan, India, China and other major research and technology markets: UK employment IP and restrictive covenant rules operate differently from most domestic legal frameworks, and assumptions formed elsewhere do not travel well.
The practical consequence is simple. A US founder who signs a UK contract without specific UK IP advice may discover that the agreement captures far more of their side work, future plans and technical freedom than they assumed. That is why this area often calls for an IP lawyer for cross-border businesses as well as an IP lawyer for cross-border employees who can explain precisely where the UK framework diverges from what the individual is used to.
UK IP Guide for Cross-Border Innovators
The legal work falls into two connected but distinct stages, and they need to happen in the right sequence.
Stage one is the employment-side review. This is a document-specific analysis of the proposed contract. The task is to identify exactly what the employer is claiming through invention assignment clauses, copyright assignment language, future inventions wording, disclosure obligations, confidentiality provisions, moral rights waivers, garden leave drafting and post-termination restrictive covenants. The aim is not simply to explain the clause. It is to decide what can be negotiated, what should be amended, and which carve-outs must be requested before signature.
Stage two is founder-side IP strategy. This is broader than contract review. It examines what the individual already owns, what they intend to build, how to document a clean chain of title for independent work, how to maintain real and demonstrable separation between employed work and independent work, how to record development boundaries contemporaneously, and how to preserve investor-ready ownership evidence. This is where founder IP strategy UK advice becomes commercially important: it connects legal drafting to the future funding and scaling of the business.
Both stages need to begin before the contract is signed. The employment review must happen then because its purpose is to shape the contract. The founder strategy must also begin then because it informs what the carve-outs need to protect. Without knowing what the founder already has and plans to develop, no adviser can draft the right exclusions. For cross-border consultants and founder-employees — whether arriving from the US, Germany, Japan, India or anywhere else — the time to involve an IP solicitor London with this focus is as soon as the offer is serious and before any binding acceptance.
The sequence matters. If a founder waits until after the offer letter becomes a binding agreement, their negotiation leverage diminishes, their ability to define clear boundaries shrinks, and their future startup may begin life with an avoidable cloud over its core intellectual property.
Frequently Asked Questions
What does a UK employment IP assignment clause actually look like, and what does it claim?
A typical clause in a serious technology or research employment contract states that the employee assigns to the employer all intellectual property rights in anything created, developed, conceived or reduced to practice during employment and relating to the employer's business or the employee's duties. It usually covers software, inventions, databases, research outputs, designs, know-how and documentation, and includes an obligation to sign further documents after employment ends. In copyright terms, section 11 of the Copyright, Designs and Patents Act 1988 already makes the employer first owner of copyright in works created in the course of employment, subject to agreement otherwise. Contracts are then drafted to go beyond that baseline, often extending to adjacent technical developments including projects partly developed outside normal working hours and on personal equipment. The combined effect is that an employment IP assignment UK clause often tries to capture not only obvious work product but any development in a technical area connected with the employer's business or anticipated research — which for a deep-tech research scientist can be very broad indeed.
Does working on my own projects at weekends protect me under UK law?
No. Weekend work is not a safe harbour under UK law. The issue is whether the work was created in the course of employment, whether it arose from the employee's normal or specifically assigned duties, whether it overlaps with the employer's field, and whether employer resources or confidential information were used. Section 39 of the Patents Act 1977 is central for inventions — it looks at duties and expectation of invention, not time. In Electrolux Ltd v Hudson [1977] FSR 312, the court focused on whether the invention arose from duties in which inventive output might reasonably be expected, and the decision has informed how legal practitioners assess technical employees' inventions ever since. What gives protection is not the calendar, but clearly defined separation, careful drafting of assignment and carve-out clauses, and disciplined practices that keep employer resources and confidential information entirely out of independent projects.
What is the "course of employment" test and how is it applied?
The phrase sounds simple but the analysis is fact-heavy. Courts examine the employee's actual role, responsibilities, level of seniority, the nature of the employer's business and whether the creation is connected to tasks the employee was engaged to perform. Section 39 of the Patents Act 1977 asks whether an invention was made in the course of normal or specifically assigned duties where an invention might reasonably be expected, or whether the employee had a special obligation to further the employer's interests. Section 42 reinforces that in certain contracted roles, inventive obligations sit squarely within the employment. For technical staff whose roles involve problem-solving, design, experimentation or product improvement, the line can be much wider than they expect. An employment contract IP review UK exercise should therefore test the clause against the real substance of the role and duties — not against the employee's assumptions about personal time.
How does garden leave affect IP ownership, and why does it matter more than most people expect?
Garden leave keeps an employee in the employment relationship while removing them from day-to-day duties. Legally, they remain employed, continue to be paid, and continue to be bound by contractual obligations including IP assignment and confidentiality clauses, unless the contract draws a different line. Because section 11 of the Copyright, Designs and Patents Act 1988 and section 39 of the Patents Act 1977 both focus on works and inventions created in the course of employment, anything developed during garden leave that falls within normal duties or the employer's field can still be argued to belong to the employer. Post-termination restrictive covenants that follow garden leave are a separate question — they are governed by the restraint of trade doctrine and the reasonableness principles associated with Nordenfelt v Maxim Nordenfelt Guns and Ammunition Co [1894] AC 535 and its successors. But while garden leave is running, the person is still inside the contract, and for a founder planning to work intensively on independent ideas during a lengthy notice period, it is essential that any carve-outs explicitly cover the garden leave period.
What is a pre-existing inventions schedule and why is it the most important protection to negotiate before signing?
A pre-existing inventions schedule is an annex to the employment contract identifying intellectual property the employee already owns before the start date and excluding it from the assignment clause. It matters because it creates a contemporaneous written record of what the founder brought into the role. In fields such as AI, advanced software and life sciences, that may include code, model structures, datasets, notebooks, methods, draft patents, unpublished frameworks and related know-how. Section 90 of the Copyright, Designs and Patents Act 1988 requires assignment of copyright to be in writing and signed — clear written exclusion in the schedule reduces later argument about whether pre-employment materials were swept into a broad contractual assignment. Without the schedule, years of independent work may be drawn into dispute if a new employer later claims that key elements were first exploited during employment. A well-drafted schedule, used together with a field carve-out and an independent project clause, creates both the evidential trail and the contractual framework that supports a future company's chain-of-title story when investors ask hard questions.
I am relocating from California — how is UK IP law different from what I am used to?
The most important difference is the absence of a California-style statutory protection for employee inventions developed entirely on personal time and resources. California Labor Code section 2870 restricts employers from enforcing assignment clauses over inventions created entirely on the employee's own time without employer resources, unless they relate to the employer's business or result from work performed for the employer. In the UK, there is no direct equivalent — ownership is governed by section 11 of the Copyright, Designs and Patents Act 1988, sections 39 and 42 of the Patents Act 1977, and the express contractual terms, without an overarching statutory carve-out for spare-time inventions. The non-compete environment is also fundamentally different. California generally bars post-employment non-competes as a matter of public policy. UK law allows restrictive covenants that satisfy the restraint of trade doctrine — as established in Nordenfelt and confirmed in Beckett Investment Management Group Ltd v Hall [2007] EWCA Civ 613 — and they may be enforceable for senior technical employees for substantial periods. For an IP lawyer for cross-border employees advising a US founder, explaining that difference clearly before signature is often the most valuable single conversation.
What happens if my independent startup operates in a similar technical field to my employer?
This is where risk becomes acute. The employer may argue that core startup IP falls within the course of employment under section 39 of the Patents Act 1977, especially where the employee's role is highly inventive and the subject matter is similar. Confidential information obligations, reinforced by the Trade Secrets (Enforcement, etc.) Regulations 2018 and the principles from Faccenda Chicken Ltd v Fowler [1987] Ch 117 and Helmet Integrated Systems Ltd v Tunnard [2006] EWCA Civ 1735, are also engaged where a former employer asserts that internal datasets, know-how or research direction informed the startup's technology. When a company later seeks investment, potential investors may identify a credible risk of ownership claims from a former employer and discount the valuation, impose intrusive warranties, or withdraw altogether. Addressing this requires early strategic work: defining and documenting the intended field, designing contractual carve-outs the employer can accept, maintaining strict operational separation, and using an IP lawyer for cross-border businesses to ensure the founder IP strategy UK remains aligned with future diligence expectations.
When is the right time to get legal advice on employment IP — before or after signing?
Before signing. After signature, the legal position is already harder. At that stage, the employer can say the employee accepted the assignment language, the disclosure obligations, the garden leave provision and any restrictive covenant. The discussion then shifts from prevention to damage control. Early advice allows a specialist IP lawyer for cross-border consultants to run the two-stage approach described throughout this article: reviewing the draft employment documents to identify and negotiate amendments, and in parallel building a founder-side strategy that maps existing and planned IP, structures pre-existing invention schedules and field carve-outs, and anticipates investment-readiness issues. This is the point at which an IP solicitor London adviser adds real value: before rights are signed away rather than after. Waiting generally means managing disputes and constraints rather than designing a structure that fits the founder's ambitions.
Why Choose PAIL Solicitors?
PAIL Solicitors approaches this issue in the way sophisticated technical clients actually experience it: as two linked legal problems that need to be handled together but not confused. The first is the employment-side review of the proposed UK contract. The second is the founder-side protection of existing and future independent IP. Treating one without the other leaves a gap. A contract can be reviewed in isolation and still fail to protect a founder's real commercial plans. A founder can think strategically about a future company and still miss the fact that the employment contract already assigns too much. The two-engagement structure addresses that reality directly.
That approach is particularly important for cross-border clients. A US-based researcher, consultant, engineer or founder entering UK employment often arrives with assumptions shaped by another legal system. The same is true of senior technical hires from Germany, the Netherlands, Japan, India, China and other major research and technology markets. The issue is not just whether a clause looks broad. It is how UK employment law, UK IP law, confidentiality duties, garden leave drafting and restrictive covenant UK employment principles work together in practice. That is where specialist analysis matters, and where generic employment or corporate advice is rarely sufficient.
The first engagement focuses on employment-side IP review: taking the draft employment contract and associated policies and analysing them for invention assignments, copyright provisions, future invention language, disclosure obligations, confidentiality and trade secret clauses, moral rights waivers, garden leave provisions and restrictive covenants. The aim is not only to identify the red flags, but to define what amendments, carve-outs and clarifications are both necessary and realistically negotiable in the context of a serious technology employer.
The second engagement focuses on founder-side IP strategy: mapping existing and anticipated assets, assessing overlap risk with the proposed employment, designing pre-existing invention schedules and field carve-outs, planning independent project development during employment, and preparing for the scrutiny of future investors, partners and acquirers. The engagement letters confirm the specific scope of each strand — employment-side review covering invention assignment clauses, copyright assignment provisions, future inventions language, disclosure obligations, confidentiality provisions, moral rights waivers, garden leave provisions and post-termination restrictive covenants; founder-side strategy covering identification of existing IP assets, documentation of pre-existing work, overlap risk assessment, and investment readiness from an IP ownership perspective.
Within those engagements, Peter Adediran's work is focused on founders, researchers, creative and technical professionals, and growth-stage businesses dealing with ownership, assignment, licensing, restrictive covenants, chain of title and cross-border commercial risk. The analysis in this article reflects practical familiarity with drafting pre-existing inventions schedules, field carve-outs and independent project clauses in a way that serious employers will engage with, and that later supports a clean chain-of-title narrative when the founder's business raises capital or enters transactions.
PAIL Solicitors Limited is based at 23 Berkeley Square, Mayfair, London, and is regulated by the Solicitors Regulation Authority under SRA number 827265. That combination of location, regulatory standing and subject-matter focus matters to international clients who want direct access to a specialist firm on issues that are commercially sensitive and often time-critical.
For a founder or researcher considering a UK move, the right question is not simply whether the employer's clause is standard. The right question is whether the contract leaves enough protected space for what the individual already owns and plans to build next. PAIL Solicitors is set up to answer that question with legal precision and commercial realism.
To discuss an employment contract IP review UK issue, founder IP strategy UK planning, or cross-border IP ownership concerns before signing, contact PAIL Solicitors directly.
peter@pailsolicitors.co.uk | 0207 305 7491 | pailsolicitors.co.uk/contact
Legal Sources and Further Reading
Part A — Primary and Secondary Legal Sources
Copyright, Designs and Patents Act 1988, s.11 — sets the default rule that where a work is made by an employee in the course of employment, the employer is the first owner of copyright, subject to agreement to the contrary; the statutory baseline from which employment IP assignment clauses in UK contracts operate. https://www.legislation.gov.uk/ukpga/1988/48/section/11
Copyright, Designs and Patents Act 1988, s.90 — confirms that assignments of copyright must be in writing and signed by or on behalf of the assignor to be effective; underpins the use of express assignment clauses in employment contracts and the importance of written exclusions in pre-existing inventions schedules. https://www.legislation.gov.uk/ukpga/1988/48/section/90
Patents Act 1977, s.39 — defines when employee inventions belong to the employer, focusing on inventions made in the course of normal or specifically assigned duties where invention is reasonably expected, or where the employee has a special obligation to further the employer's interests; the central statutory provision for employment IP ownership analysis in the UK. https://www.legislation.gov.uk/ukpga/1977/37/section/39
Patents Act 1977, s.40 — provides for compensation to employee inventors where a patent owned by the employer is of outstanding benefit and the existing arrangements do not give the employee a fair share; relevant where an employee's patented invention generates significant commercial value for the employer. https://www.legislation.gov.uk/ukpga/1977/37/section/40
Patents Act 1977, s.42 — deals with duties of employee inventors in certain contracted roles and reinforces that invention-related obligations can sit squarely inside the employment relationship, not merely alongside it; relevant for senior research and technical roles. https://www.legislation.gov.uk/ukpga/1977/37/section/42
Employment Rights Act 1996 — sets the general statutory framework governing employment contracts in the UK, including notice provisions and the basis of the employment relationship within which IP and confidentiality obligations operate. https://www.legislation.gov.uk/ukpga/1996/18/contents
Trade Secrets (Enforcement, etc.) Regulations 2018 — provides the modern statutory framework for protection of confidential business information and trade secrets, providing a legal basis for action where former employees misuse confidential technical know-how. https://www.legislation.gov.uk/uksi/2018/597/contents
California Labor Code, section 2870 — limits the scope of IP assignment clauses in California employment contracts, excluding inventions developed entirely on personal time without employer resources subject to defined exceptions; cited for comparative purposes to illustrate the key differences between California and UK employment IP law. https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB§ionNum=2870
Electrolux Ltd v Hudson [1977] FSR 312 — foundational English case on employee inventions, establishing that the inquiry focuses on the employee's actual duties and whether invention was a reasonable expected incident of those duties, not on timing or equipment; repeatedly cited in employment IP ownership analysis.
Helmet Integrated Systems Ltd v Tunnard [2006] EWCA Civ 1735 — Court of Appeal decision confirming that developing something in one's own time does not insulate a person from challenge if it overlaps materially with the employer's field and duties; a key warning for technical founders working on adjacent independent projects. https://www.bailii.org/ew/cases/EWCA/Civ/2006/1735.html
Nordenfelt v Maxim Nordenfelt Guns and Ammunition Co [1894] AC 535 — foundational House of Lords authority establishing that restrictive covenants in restraint of trade are enforceable only to the extent they are reasonable as between the parties and in the public interest; the foundation for all post-employment restrictive covenant analysis in UK employment law.
Beckett Investment Management Group Ltd v Hall [2007] EWCA Civ 613 — Court of Appeal authority on the drafting and enforceability of post-employment restrictive covenants, providing modern guidance on reasonableness of scope, duration and geographic reach. https://www.bailii.org/ew/cases/EWCA/Civ/2007/613.html
Faccenda Chicken Ltd v Fowler [1987] Ch 117 — leading authority distinguishing between confidential information that remains protected after employment ends (trade secrets) and information that forms part of the employee's general skill and knowledge; central to confidential information risk analysis in founder-employer disputes. https://www.bailii.org/ew/cases/EWCA/Civ/1986/2.html
Part B — PAIL Solicitors Internal Links
The following pages on the PAIL Solicitors website provide further guidance on the legal issues covered in this article and form part of an integrated knowledge base on IP ownership, assignment, licensing and dispute resolution for founders, consultants and international professionals.
IP Assignment Agreement Solicitors — detailed guidance on IP assignment agreements, how they operate in practice, and the critical difference between an assignment (transfer of ownership) and a licence (permission to use); directly relevant to understanding employment IP assignment and founder-side transfer structures. https://pailsolicitors.co.uk/media-solicitors/guide-to-assigning-intellectual-property-rights-by-ip-assignment-agreement-lawyers
IP Licence Agreement Solicitors — PAIL Solicitors' practice in drafting and negotiating IP licences and assignment agreements across SaaS, technology, media and creative sectors; relevant to structuring future founder licensing arrangements into a new company vehicle. https://pailsolicitors.co.uk/ip-license-agreements-solicitors
Intellectual Property Licence Agreements (Blog) — in-depth article on how IP licences operate across digital platforms and media, useful context for founders considering licensing strategies as an alternative to outright assignment when transferring IP into a company. https://pailsolicitors.co.uk/media-solicitors/intellectual-property-license-agreements-lawyers
Intellectual Property Dispute Solicitors — PAIL Solicitors' enforcement and dispute resolution practice for trade mark, copyright, patent and confidential information disputes; relevant where employment IP assignments or confidentiality obligations become contentious between employers and founder-employees. https://pailsolicitors.co.uk/intellectual-property-dispute-lawyers
Intellectual Property Registration Lawyers — PAIL Solicitors' practice covering IP registration including patents, trade marks and copyright; relevant when founder-side IP strategies evolve into formal registered IP portfolios requiring protection across multiple jurisdictions. https://pailsolicitors.co.uk/intellectual-property-lawyer
IP Legal Services — the full range of IP and commercial legal services offered by PAIL Solicitors, including employment IP review, founder IP strategy, licensing, restrictive covenants and cross-border IP matters. https://pailsolicitors.co.uk/legal-services
PAIL Solicitors Blog — Digital Media and IP Law Insights — ongoing commentary on intellectual property, digital media, commercial contracts and platform law, written and edited by Peter Adediran; further reading for founders and researchers interested in developments affecting employment and founder-side IP. https://pailsolicitors.co.uk/media-solicitors
Contact PAIL Solicitors — to arrange an employment-side IP review, founder-side IP strategy engagement, or consultation on cross-border IP ownership issues before signing. https://pailsolicitors.co.uk/contact
Moving to the UK and need to protect your IP before signing? Contact PAIL® Solicitors for an employment contract review or founder IP strategy consultation.
Call: 0207 305 7491
Email: peter@pailsolicitors.co.uk
This article is for general information only and does not constitute legal advice. If you are navigating employment IP provisions, founder-side IP strategy, or the intersection of employment obligations and independent business development, PAIL Solicitors provides specialist advice in this area.
Peter Adediran is the Founder and Principal Solicitor of PAIL Solicitors Limited, an IP, digital media and commercial law firm based at 23 Berkeley Square, Mayfair, London. He advises founders, researchers, technology businesses and creative professionals on intellectual property ownership, employment IP provisions, restrictive covenants, and founder-led IP strategy.
peter@pailsolicitors.co.uk | 0207 305 7491 | pailsolicitors.co.uk
PAIL Solicitors Limited is regulated by the Solicitors Regulation Authority (SRA number: 827265).