A departing founder and company intellectual property

A founder's departure can expose uncertainty about who owns the company's intellectual property. A domain login, a source-code folder and a shareholding are not proof of the same legal right. Start by identifying the assets, how they were created and the documents governing their use.

Build an asset and ownership schedule

List software, designs, branding, written materials, databases, domains, trade marks and other relevant assets. Record the creator, creation date, contracting party and any assignment or licence. Include material developed before incorporation and work supplied by freelancers.

Do not assume that paying an invoice automatically transferred copyright. Official guidance distinguishes employment-created works from commissioned work, where ownership often remains with the creator unless agreed otherwise. ^[1]

Review founder and contractor documents

Check employment, consultancy, founder and investment agreements. Identify which rights were assigned, any exclusions and whether future work was addressed. A clause referring generally to company materials may not establish ownership of every pre-existing asset.

Where the evidence is incomplete, obtain a properly drafted assignment or licence if appropriate. Do not backdate signatures or claim that a historic transfer occurred when it did not. The completion record should explain the actual position.

Separate legal ownership from practical access

The company may own an asset but lack access to the account that controls it. Conversely, holding the password does not establish ownership. Plan a controlled handover of domains, repositories, cloud services and recovery contacts through the relevant provider processes.

Keep evidence and business continuity in mind. Do not delete accounts or material that may be needed to understand ownership, customer obligations or an unresolved dispute.

Departure checklist

• Confirm ownership and licence rights for key assets.
• Complete necessary assignments and consents.
• Transfer company-controlled access and recovery arrangements.
• Identify third-party and open-source restrictions.
• Address confidentiality and permitted future use.
• Record delivery of files, documentation and outstanding work.

Review continuing obligations

A departing director should consider relevant duties and conflicts concerning company information or opportunities. Confidentiality, restrictive covenants and future competition require careful, fact-specific review; a broad prohibition is not automatically enforceable merely because it appears in a draft. ^[2]

For example, a founder may have built the original website personally before the company existed. The exit agreement should establish the company's right to continue using it and the practical transfer of access. Simply requiring the founder to sell shares may leave both the ownership and continuity questions unanswered.

Trace the assets the founder brought into the business

List pre-incorporation designs, software, content, domains and registered rights separately from work created later. Identify who created each asset and which agreement governs it. A founder's shareholding or job title does not prove that all earlier work was transferred to the company. Look for actual assignments or licences and any limits they contain.

Include contributions from contractors engaged personally by the founder. The company may depend on work produced under an agreement to which it was never a party. Payment from a company bank account does not necessarily repair that ownership gap. Obtain the relevant documents and assess what rights the business has and what further agreement may be needed.

Separate legal rights from technical control

Prepare two columns: evidence of ownership or permission, and the person controlling files or accounts. A company can own copyright while lacking the repository access needed to maintain its product. It can also hold administrator access without owning the underlying work. Both problems matter, but they require different solutions.

For an illustrative departure, the founder controls the domain account and source-code repository while an external developer retains rights in part of the code. Transferring passwords addresses access but not the contractor's rights. The exit plan should therefore combine an operational handover with review of the underlying development and licensing documents.

Agree deliverables for the handover

Identify source files, build instructions, design originals, licence records and account administration changes required. Specify the format and person responsible for confirming receipt. A zip file that nobody can open or rebuild may not provide meaningful continuity. Ask the receiving team to verify the practical materials without assuming that technical delivery settles legal ownership.

Check third-party components and restrictions before promising unrestricted use. Fonts, stock assets, open-source code and licensed tools may remain subject to their own terms. A founder cannot transfer more than they own. The settlement should identify retained material and necessary permissions rather than using a blanket ownership statement unsupported by the evidence.

Address continuing obligations accurately

Review confidentiality, permitted portfolio use and any restrictions on future activity under the actual documents. Do not assume every restriction is enforceable or that leaving the board removes all duties relating to company information and opportunities. Obtain a focused assessment of the proposed exit terms and conduct.

Use Assigning intellectual property to a company for assignments to a company. Shareholders agreement review can help review founder departure provisions, with detailed IP ownership and transfer work scoped alongside the wider shareholder arrangements.

A completed handover should allow the business to operate without relying on the departing person's personal accounts or undocumented permission.