Employment IP provisions should reflect the work employees are engaged to perform and the rights the business needs. Copyright in work created in the course of employment generally belongs to the employer, subject to agreement, but not every asset or activity follows the same analysis. [1]
Identify prior inventions, personal projects and external materials before they become mixed with company work. Review other rights, such as inventions, under their applicable rules rather than treating a copyright clause as a complete solution. Use clear reporting and handover arrangements alongside the contract.
Connect the clause to the employee's actual role
Describe the work the person is employed to perform and the kinds of assets they are expected to create. The copyright starting point for work made in the course of employment differs from independent contracting, subject to relevant agreements. [1] A contract should reflect the real role rather than make an unexplained claim over everything the employee creates in any context.
Keep job descriptions and material role changes documented. A person hired for one function may later develop software, training material or designs as part of another. Accurate records help explain the circumstances of creation. Do not rely only on a broad IP clause while leaving the actual employment duties and project assignments unclear.
Identify prior work before it enters company products
Ask the employee to disclose relevant background code, designs, inventions or other material they propose to use. Record what existed before employment and who owns it. The company may need a licence or a different solution if that material becomes part of a commercial product. Possession by the employee does not establish an unrestricted right to introduce it.
Distinguish the employee's own work from material licensed from a former employer, client or third party. Avoid requesting confidential files from a previous job as evidence of expertise. The onboarding process should make clear that company work must not incorporate material the employee has no right to use or disclose.
Separate copyright from other IP questions
Inventions, registered designs, trade marks and confidential information have their own legal frameworks. A copyright clause should not be treated as a complete answer to every asset created during employment. Obtain specialist advice where the role involves potentially patentable developments or complex ownership arrangements, using the actual duties and facts.
Explain how employees report potentially valuable work and who decides whether to seek protection. A timely internal process can help the company assess disclosure and filing questions before a public launch. The contract should support that process without pretending that a general assignment automatically creates every registration or settles all statutory rights.
Manage personal projects with clear boundaries
Discuss relevant outside projects and any overlap with company activities, time, equipment or information. A project completed at home is not automatically outside every employment issue, while a personal idea is not automatically company property merely because its creator is an employee. The facts and applicable rights need assessment.
Record agreed permissions or exclusions precisely enough to apply later. If the project changes or begins using company material, revisit the arrangement. Avoid leaving both sides with conflicting assumptions that remain hidden until the employee departs or the company seeks investment.
Support the clause with practical records
Keep project briefs, contributors and meaningful creation milestones. Link them to the employment agreement in force at the time. IPO guidance emphasises keeping records of creators and contractual arrangements. [1] A final file with the company logo does not explain who made it or whether external contributors were involved.
Give staff a route to request approval for third-party assets and software components. The employer may own the employee's original contribution while still needing permission for included stock material or code. Maintain those licences separately and make the conditions available to teams publishing or distributing the work.
Plan confidentiality and departure handover
Identify company files, source materials and accounts that must be returned or transferred. Preserve business records through a controlled process without collecting unrelated personal information unnecessarily. The employee's departure should not leave the company unable to access work it is entitled to use.
Review continuing confidentiality and assistance provisions under the actual contract and applicable law. Do not assume that leaving employment removes all obligations concerning company information, or that every broad restriction is enforceable. Obtain advice on the particular proposed conduct and rights rather than relying on labels.
Review the arrangements when the business develops
Growth, collaboration and new product lines can change the types of IP employees create. Update onboarding, project records and contracts where appropriate. Keep the approach understandable so employees can identify issues before valuable work becomes entangled with unclear rights.
Read Who owns software created by a contractor for the different contractor-software position. IP ownership review can help review the company's ownership evidence and identify employment or specialist IP questions requiring a focused assessment.
Illustrative scenario
A developer joins a company with an existing personal library of code. The parties record that background material and decide whether the company may use it. This avoids later uncertainty about whether a product component was created as part of employment or merely introduced from an earlier project.
Preparation checklist
- Describe the employee’s relevant duties and output.
- Record agreed background assets and permitted outside work.
- Check confidentiality and invention reporting arrangements.
- Keep project and departure handover records under company control.
Frequently asked questions
Does the employer own every personal project automatically?
No. The type of right, employment circumstances and agreements matter. Assess the actual facts rather than assuming either all personal work or none belongs to the company.
Why record pre-existing code at onboarding?
It helps distinguish background material from new work and identify permissions needed before the company incorporates it into a product or service.
Does a copyright clause settle invention ownership?
Not necessarily. Different IP rights have their own rules. Obtain specialist advice where inventions or other complex assets are part of the employee's role.
What records help establish ownership later?
Keep employment terms, duties, project briefs, contributors and dated creation evidence, with separate permissions for third-party material included in the work.
Official sources
Sources checked: 8 September 2026. Check the linked guidance for subsequent changes.
General information only. The appropriate action depends on your circumstances and the applicable jurisdiction.
Report a correction