How can a company document its rights to work created by employees and contractors?

Q: How can a company document its rights to work created by employees and contractors?

Document who created the work, which duties or contract covered it, and whether the company owns the rights or has permission to use it. Resolve missing transfers or unclear terms before relying on ownership. Preserve signed agreements alongside successive versions and delivery records, timestamping them as the work progresses to reinforce their chronology.

Link the work to the agreement that covers it

For each project, keep a short list of contributors and deliverables. Identify the person who wrote the code, prepared the drawings or developed the invention, the company they worked for, and the period of their involvement. Link each contribution to the relevant files and to the employment terms or contractor agreement in force at the time.

Use the company’s legal name, particularly where several companies in a group are involved. If one company employs the creator but another is intended to own or use the results, document the transfer or permission between them.

Record whether the company claims ownership or relies on a licence, and identify the contract clause or legal rule supporting that position. Mark unresolved points explicitly rather than treating every delivered file as company-owned.

For employees, preserve evidence of their duties

Keep the signed employment terms and amendments, the job description, project assignments and dated records of the work performed. These help establish whether the work fell within the employee’s duties and which terms applied when it was created.

Ownership rules differ by country and type of IP. Rights may belong to the employer under law, require a transfer from the employee, or remain with the employee in particular circumstances. Even within Europe, employee ownership rules are not fully harmonised, as the European IP Helpdesk explains.

For an invention, keep the employee’s written description of what they developed and the instructions defining their research or development task. Check whether local law requires notification to the employer, a claim to the invention, an assignment or compensation, and preserve evidence of any required steps.

For example, an engineer’s project brief and development notes can connect a new mechanism to their assigned duties. A job title or a clause saying “all IP belongs to the company” may not establish that connection or satisfy the required legal steps.

For contractors, document exactly what rights the company receives

Keep the signed contract and statement of work, including amendments. Check that they identify the deliverables and specify whether rights are transferred to the company or licensed for particular uses. Record any conditions, such as a transfer taking effect on payment, and retain evidence that those conditions were met.

Do not assume payment transfers ownership. WIPO’s guidance on expanding a team recommends making clear what the company owns and what the contractor keeps. If the company receives a licence, specify the permitted uses, duration and territory, including whether it can modify the work or allow customers to use it.

Where ownership is transferred, check the formalities for the relevant rights and countries, such as required signatures or registration of the transfer. The European IP Helpdesk’s assignment guidance explains why one contract format cannot be assumed sufficient everywhere.

If an agency or contractor uses other people to produce the work, ask for copies of the relevant assignments or licences, or written confirmation identifying the contributions covered and the rights it obtained. Check that those rights allow the transfer or licence promised to your company.

Separate new work from material brought into the project

Ask contributors to identify existing code, templates, images, designs or methods they include. Keep a list of those items, their owners and the permissions covering the company’s intended use. Preserve the applicable licence terms and any restrictions on modification, distribution or sublicensing.

For example, a developer may create a new application using a library they already owned and third-party open-source components. The company’s documents should distinguish rights in the new code from permission to use the existing components. Paying for the application does not explain those different rights. For confidential know-how, WIPO’s guidance on collaborative innovation similarly distinguishes what each party brings from what they develop together, and recommends agreeing how both may be used.

Keep the documents with the delivered versions

At each handover, preserve the delivered files, contributor names, acceptance messages and the agreements covering that delivery. Where payment triggers a rights transfer, link the payment record too. Keep signed originals and, for electronically signed documents, the accompanying signature-validation records.

Preserving and timestamping successive deliveries and agreements builds a dated history of what the company received and which terms were documented at each stage. Different timestamping methods can support this history; see what a digital timestamp establishes. A timestamp supports when a document existed, but cannot supply a missing signature or transfer rights that the agreement does not grant.

Before a contributor leaves, check for missing signatures, unidentified third-party material and deliverables absent from the contract. Arrange any necessary clarification, licence or assignment with the appropriate parties, using the actual signing date. Keep unresolved gaps visible for legal review, and store the completed records where the company can retrieve them after the person leaves.