TL;DR: Intellectual Property (IP) Assignment: Why Your Company Must Own the Code. Avoiding legal headaches by locking down IP from day one.3
Intellectual Property (IP) Assignment: Why Your Company Must Own the Code. Avoiding legal headaches by locking down IP from day one.3 means your startup needs signed written transfers so the company , not founders, freelancers, or agencies , legally owns its code, designs, data, and other product assets from the start.
• If you skip IP assignment, you risk weak fundraising, messy due diligence, founder disputes, contractor claims, and even blocked exits. Paying for work does not always mean you own it, especially with freelancers and agencies. See this short guide on code ownership.
• You should lock down ownership with founder assignment agreements, employee invention and confidentiality terms, contractor and agency contracts with present-tense assignment language, plus company control over repos, domains, cloud accounts, and admin access. The wording matters, as this article on assignment language explains.
• Cross-border hiring, open-source code, and AI-assisted work make ownership harder. You need a clean chain of title, clear records for every contributor, and regular checks so you can prove who created what and who owns it.
If your startup has grown fast and paperwork fell behind, audit every contributor and asset this week, fix missing assignments now, and get legal review before your next investor or buyer asks.
Check out startup news that you might like:
You’re Not Scaling Content. You’re Scaling Disappointment
Intellectual Property (IP) Assignment: Why Your Company Must Own the Code. Avoiding legal headaches by locking down IP from day one.3 starts with a blunt truth: if your company does not clearly own its code, product assets, and invention rights, you may be building on borrowed ground. For startups, IP assignment means written agreements that transfer rights in software, designs, documentation, inventions, data assets, and other work product from founders, employees, contractors, and agencies to the company itself.
I have built companies across Europe and beyond, and I have seen founders obsess over pitch decks, growth loops, and product sprints while leaving ownership of the actual asset dangerously vague. That is upside-down startup behavior. If the company does not own the thing it sells, your valuation, fundraising story, acquisition path, and legal defensibility all get weaker fast.
Why this matters for startups: investors back assets, not chaos. Buyers acquire clean ownership, not founder folklore. Unlike a casual handshake or a Slack promise, a proper IP assignment creates a legal chain of title that can survive due diligence, founder conflict, contractor disputes, and cross-border hiring issues.
Key takeaway
- How IP assignment affects startup growth, fundraising, hiring, and exits
- What documents founders need from day one
- How employees, freelancers, agencies, and co-founders create different ownership risks
- What to fix immediately if your startup has messy code ownership already
Why does IP assignment matter so much for startups now?
The challenge is simple. Startups move fast, hire messy, and build with mixed teams. A founder writes the first backend. A friend designs the logo. A freelancer in another country ships the mobile app. An agency creates the website. A machine learning specialist fine-tunes a model. Months later, everyone assumes the company owns everything.
That assumption is often false.
Recent legal commentary on cross-border software deals from Law.com on cross-border software due diligence highlights a problem many founders ignore: in many jurisdictions, the employer does not automatically receive full ownership of employee-created IP in the way founders casually expect, and contractor gaps can be even worse. That means a startup with code written across borders may discover during fundraising or acquisition that the chain of title is broken.
Here is why this hits startups hard:
- Limited money means you cannot afford a major IP clean-up when a deal is live.
- Fast hiring creates documentation gaps.
- Remote teams raise jurisdiction questions.
- Founder informality creates evidence problems.
- AI-assisted coding adds license and provenance questions.
From my European founder perspective, this is where startup romanticism becomes expensive. Founders love talking about ownership until they need to document it. Then suddenly everyone gets “busy.” Busy is not a legal defense.
If you are hiring across borders, pair this article with a startup legal checklist by country because local rules shape what your contracts must say and how enforceable they are.
What is IP assignment in plain English?
IP assignment is a written transfer of ownership. It says that the person or entity creating the work gives the company the legal rights to that work. In startup context, this usually covers:
- Source code and object code
- Architecture and technical documentation
- Wireframes, designs, and brand assets
- Databases and data structures
- Inventions and patentable ideas
- Copyright in text, visuals, videos, and marketing materials
- Domain names, repositories, and admin access
- Trade secrets, know-how, and internal methods
Many founders confuse use rights with ownership. If a contractor built your product and your contract only says you can use the work, that does not always mean you own it. You may have a license, not title. That difference becomes brutal in a dispute.
Core concept #1: Chain of title
Definition: Chain of title is the documented ownership history of an asset from creator to current owner.
Why it matters for startups: during due diligence, investors and buyers want proof that every meaningful asset moved legally into the company.
Real-world example: A startup claims its platform is proprietary, but two senior developers were contractors and never signed assignment language. The code may be commercially useful, but legally contaminated.
Related terms: ownership transfer, assignment deed, copyright transfer, invention assignment.
Core concept #2: Work made for hire versus assignment
Definition: In some legal systems, work created within employment may belong to the employer automatically in limited circumstances. In many cases, and especially across jurisdictions or with contractors, you still need express assignment language.
Why it matters for startups: founders often copy United States assumptions into international teams. That is risky and sometimes flatly wrong.
Real-world example: A startup in the Netherlands hires a developer in Portugal through a loose services agreement. The founder assumes company ownership is automatic. It may not be.
Related terms: employee IP, contractor IP, moral rights, local labor law.
Core concept #3: Present assignment versus future promise
Definition: Some clauses say the creator “will assign” IP later. Better drafting often says the creator “hereby assigns” rights now.
Why it matters for startups: a future promise can create room for delay, refusal, or litigation later.
Real-world example: A departing co-founder agrees in principle to transfer code later, then disappears or demands more equity. The startup loses months.
Related terms: assignment clause, present transfer, further assurances, IP vesting.
Which startup assets should the company own from day one?
Founders often think only about code. That is too narrow. Your company should secure ownership or properly documented rights around the full product and operating stack.
- Product code: frontend, backend, scripts, APIs, integrations, deployment files
- Product design: UX flows, UI kits, illustrations, design systems
- Brand assets: logo, name options, slogans, social handles
- Content: website copy, sales decks, onboarding materials, training content
- Technical assets: repositories, cloud accounts, domains, admin credentials
- Data assets: schemas, annotations, prompt libraries, internal datasets
- Patentable inventions: technical methods, hardware ideas, proprietary processes
- Trade secrets: internal formulas, workflows, ranking methods, customer intelligence
Broaden your view of ownership. If your startup depends on it, the company should either own it or have a written right that is commercially safe, transferable, and durable.
If you want a broader map of how patents, trademarks, and copyright fit together, review this startup IP strategy guide.
How do founders lock down IP assignment step by step?
Let’s break it down. You do not need a giant legal department to get the basics right, but you do need discipline.
Phase 1: Assessment and planning
Step 1.1: Audit your current state
- List every person who has created code, content, design, invention, or data for the startup
- Check whether each person signed an employment agreement, contractor agreement, founder agreement, or assignment deed
- Map each asset to a creator and a document
- Check where each creator was based when the work was created
- Flag open-source components and third-party licenses
Step 1.2: Define your ownership strategy
- Decide which entity should own the IP
- Set one template for employees
- Set one template for contractors and agencies
- Set a founder assignment document for pre-incorporation work
- Choose where signed documents will be stored and tracked
Step 1.3: Get internal buy-in
- Explain to co-founders that IP hygiene is not “paperwork,” it is asset control
- Make one person responsible for contract completeness
- Require signed agreements before access to repositories or shared drives
- Add IP review to hiring and procurement flows
Tools for this phase: contract management software, cap table records, Git history, HR folders, and a simple asset register in a spreadsheet if you are still early.
Phase 2: Foundation building
Step 2.1: Choose your documentation stack
- Founder IP assignment
- Employee invention and confidentiality agreement
- Contractor services agreement with IP assignment
- Agency agreement with assignment and subcontractor pass-through clauses
- Open-source use policy
- Repository access and admin control policy
Step 2.2: Set up infrastructure
- Place repositories under company-owned accounts
- Move domains to company registrar accounts
- Move cloud billing and deployment tools under company control
- Store signed contracts in one searchable place
- Document who can approve third-party code or content use
Step 2.3: Build your foundation elements
- Create an IP inventory
- Create a contributor register
- Set a signature rule before work starts
- Set an exit checklist for leavers
Implementation checklist
- Documented ownership framework
- Signed founder, employee, and contractor agreements
- Company-controlled technical accounts
- Confidentiality obligations in place
- Backup copies of all signed documents
Phase 3: Review and scale
Step 3.1: Early testing
- Run a mock due diligence review on your own startup
- Ask: can we prove ownership of our top 20 assets in 30 minutes?
- Fix missing signatures and missing account transfers
- Review whether any contractor used subcontractors without approval
Step 3.2: Gradual rollout
- Apply the same rules to every new hire and freelancer
- Train managers not to bypass contract steps
- Review templates when entering a new country
- Update your asset register every month
Step 3.3: Build review loops
- Quarterly IP audit
- Monthly review of repos and admin rights
- Legal review before fundraising
- Special review before M&A conversations
What documents does every startup need for clean code ownership?
At minimum, most startups should have the following documents reviewed for their jurisdiction and facts:
- Founder assignment agreement for all pre-company work and ideas contributed to the business
- Founders’ agreement covering ownership expectations, role boundaries, and what happens if someone leaves
- Employment agreement with confidentiality, invention assignment, and post-termination cooperation clauses
- Contractor agreement with present assignment language, waiver or treatment of moral rights where lawful, and subcontractor restrictions
- Agency agreement with pass-through ownership from every agency staffer and subcontractor
- NDA to support trade secret protection
- Open-source policy to control inbound code risk
- Exit certificate confirming return of materials, credential handover, and continuing obligations
If co-founder rights and asset ownership are still fuzzy, read this piece on a founders’ agreement. It connects equity, roles, and IP before friendship turns into litigation.
Why are contractors and agencies the biggest IP trap?
Because founders trust output more than paperwork. A freelancer shipped the feature, so the founder feels the company owns it. Feeling is not ownership.
Contractors create a sharper risk than employees in many cases because default rules are often less founder-friendly. Agencies create another layer because the person signing your contract may not be the person creating the work. If the agency does not have proper pass-through rights from its team, your company may still lack clean title.
Here is the contractor trap in one sentence: you paid for the work, but you did not pay for the rights unless the contract says so clearly.
- A cheap freelance build can become expensive rework
- An outsourced prototype can block fundraising
- A vague statement of work can create ownership ambiguity
- A subcontractor you never met can later assert rights
For hiring structure and worker status, see contractor vs employee classification. Misclassification and IP confusion often arrive together.
How does cross-border hiring make IP assignment harder?
Cross-border teams are normal now. Your law assumptions should not be.
When developers, designers, and researchers are spread across countries, ownership questions become tied to local employment law, copyright rules, moral rights, contractor status, and enforceability. The Law.com analysis of cross-border M&A and IP ownership makes the point clearly: global software companies may look simple from the outside, yet the actual ownership chain can fail under local law if agreements are missing or weak.
European founders should be especially sober about this. Europe is not one legal system. A contract that feels “standard” in one country may be incomplete or weak in another. And when startups scale with remote talent, that gap widens.
- Check governing law and local mandatory rules
- Review employee-created work rules country by country
- Address moral rights where local law allows waiver or consent
- Make sure assignment language matches local legal drafting standards
- Review tax and worker status facts because legal labels alone do not save you
If you are hiring in Europe, study employment law basics by European country before you assume one employment template will cover your whole team.
What are the best practices that work in 2026?
Practice #1: Make assignment happen before access
What it is: nobody starts work, gets repo access, or touches files before signing the right agreement.
Why it works: founders are terrible at chasing documents after value has already been created.
How to do it:
- Put signature collection into hiring and procurement.
- Block technical access until paperwork is complete.
- Store the signed copy in a searchable archive.
Common pitfall: “We know this person well.”
How to avoid it: build rules for systems, not moods.
Metrics to track: percentage of contributors with signed agreements, time from offer to signature, number of unsigned contributors with active access.
Practice #2: Use present-tense assignment language
What it is: draft ownership transfer as a current transfer where lawful and suitable, not a vague future intention.
Why it works: future promises create openings for disputes.
How to do it:
- Review templates with qualified counsel.
- Use present assignment wording where appropriate.
- Add further-assistance obligations for filings and signatures later.
Common pitfall: copying random internet templates.
How to avoid it: get documents checked for your countries and worker types.
Metrics to track: number of legacy contracts needing replacement, number of disputed asset creators, percentage of templates reviewed this year.
Practice #3: Treat open source as an ownership issue too
What it is: manage inbound code licenses, attribution duties, and copyleft risk.
Why it works: you can “own” your code and still have commercial restrictions if you ignored license terms.
How to do it:
- Create an approved open-source use policy.
- Scan dependencies regularly.
- Review high-risk licenses before shipping.
Common pitfall: developers pull code fast and legal reviews it later, if ever.
How to avoid it: set rules inside development workflow, not just inside a forgotten PDF.
Metrics to track: number of unreviewed dependencies, license exceptions, remediation time.
Practice #4: Run pre-due-diligence before investors ask
What it is: perform your own ownership review before fundraising or acquisition discussions.
Why it works: deals slow down when the seller discovers its own mess in the data room.
How to do it:
- Build an IP schedule of major assets.
- Match each asset to a contract and creator.
- Fix missing links before outreach intensifies.
Common pitfall: waiting until term sheet stage to organize records.
How to avoid it: review quarterly and after any major product release.
Metrics to track: missing contract count, unresolved creator issues, percentage of major assets documented.
What common mistakes do founders make with code ownership?
Mistake #1: Assuming founders automatically own what they build together
Why founders make this mistake: early startup work feels informal and collective.
The impact: once the company is formed, pre-incorporation work may still sit with individuals unless assigned.
How to avoid it:
- Sign founder assignment documents at incorporation
- List prior code, designs, and inventions clearly
- Address side projects and excluded IP openly
If you already made this mistake:
- Prepare a retroactive founder assignment
- Get signatures now, not “later”
- Record the transfer in your company files and board approvals if needed
Mistake #2: Paying an invoice and assuming ownership follows
Why founders make this mistake: payment feels like purchase.
The impact: the startup may receive only limited use rights.
How to avoid it:
- Use contractor and agency contracts with assignment language
- Confirm subcontractor pass-through rights
- Tie payment to signed paperwork if needed
If you already made this mistake:
- Seek a confirmatory assignment now
- Check if the creator used third-party materials
- Assess whether any parts must be rewritten
Mistake #3: Ignoring account ownership
Why founders make this mistake: legal ownership gets attention, operational control does not.
The impact: a former freelancer still controls the GitHub org, cloud billing, app store account, or domain registrar.
How to avoid it:
- Create company-owned admin accounts
- Use role-based access
- Review credentials during exits
If you already made this mistake:
- Transfer ownership immediately
- Reset credentials and tokens
- Document who has admin authority
Mistake #4: Treating AI-generated output as ownership-safe by default
Why founders make this mistake: they think “generated” means clean.
The impact: unclear copyright position, source material concerns, and contract gaps with vendors or internal users.
The legal debate around AI and copyright is still moving, and commentary highlighted by Law.com on everyday copyright pitfalls and AI governance points to a smarter founder response: tighten internal copyright rules now instead of waiting for courts to answer every edge case.
How to avoid it:
- Set a written AI content and code policy
- Review vendor terms on training, output rights, and indemnities
- Track where AI-assisted assets enter product or marketing
If you already made this mistake:
- Audit high-value assets created with AI systems
- Check terms of use and source restrictions
- Replace risky material where ownership is unclear
How should startups measure IP assignment health?
Founders measure traffic, burn, and conversion obsessively. They should also measure ownership hygiene. Not because it is glamorous, but because bad ownership can wipe out value faster than a weak landing page ever will.
Foundational metrics to track first
- Percentage of contributors with signed IP assignment documents
- Percentage of top assets mapped to creators and contracts
- Number of repos under company ownership
- Number of domains and cloud accounts under company ownership
- Number of unresolved founder pre-incorporation assets
Advanced metrics to add after 3 months
- Time needed to produce IP documentation for due diligence
- Open-source review coverage
- Percentage of contractor templates updated for current jurisdictions
- Number of assets created with AI tools that have documented provenance review
- Quarterly remediation rate for identified ownership gaps
What should your internal dashboard include?
- A live contributor-to-contract register
- An asset-to-owner map
- Status of contract gaps by team or country
- Admin account ownership status
- Alert flags for unsigned contributors with technical access
Even an early-stage startup can track this in a spreadsheet. Fancy tooling is optional. Clarity is not.
What does IP assignment look like at different startup stages?
Pre-seed and seed stage
Your reality: tiny team, low cash, informal workflows, high speed.
Approach:
- Get founder assignments done immediately
- Use simple but proper contractor templates
- Move repos, domains, and cloud accounts into company control
What to prioritize: chain of title for the product and brand.
What can wait: highly detailed internal policy libraries.
Resource requirement: a few focused legal reviews and founder discipline.
Success looks like: you can prove ownership of what you demo to investors.
Series A stage
Your reality: team expansion, more contractors, more pressure from investors.
Approach:
- Standardize employee and contractor agreements
- Run a formal IP audit
- Introduce open-source and AI use rules
What to prioritize: cross-border enforceability and due diligence readiness.
What can wait: edge-case patent filing for every small idea unless central to value.
Resource requirement: outside counsel plus internal operations discipline.
Success looks like: no investor concern around ownership risk.
Series B and later
Your reality: more countries, more teams, more acquisitions, more scrutiny.
Approach:
- Centralize IP records and contributor records
- Review local law assumptions country by country
- Run recurring due diligence simulations and vendor reviews
What to prioritize: auditability, transferability, and clean data room prep.
What can wait: almost nothing if M&A is on the horizon.
Resource requirement: legal ops plus specialized counsel where needed.
Success looks like: a buyer can review your ownership chain without discovering nasty surprises.
What should founders do this week to fix or prevent ownership chaos?
Next steps. Keep them practical.
Week 1: Audit and alignment
- List every person who contributed to code, design, content, or invention
- Match each person to a signed agreement
- Identify missing founder, employee, and contractor paperwork
- Review technical account ownership
Week 2: Repair the obvious gaps
- Send confirmatory assignments where documents are missing
- Transfer repos, domains, cloud tools, and app accounts
- Update templates for future hires and freelancers
- Set one storage location for signed records
Week 3: Add process controls
- Require signed agreements before work starts
- Require approval for subcontracting
- Set an open-source review rule
- Set a simple AI content and code usage rule
Week 4 and beyond: Keep it alive
- Run a monthly contract completeness review
- Run a quarterly IP audit
- Review cross-border hiring before expansion
- Prepare an investor-ready IP folder before you need one
Glossary of terms founders should actually understand
IP assignment: a written transfer of ownership rights in intellectual property from creator to company.
Chain of title: the documented ownership history proving how an asset moved from original creator to current owner.
Copyright: legal protection for original creative works such as software code, text, graphics, and videos.
Trade secret: confidential business information that gains value because it is not public, such as formulas, methods, or internal data.
Moral rights: creator rights recognized in some countries that may limit how a work is altered or attributed, even when economic rights are transferred.
Open-source license: a license governing how software can be used, modified, and distributed.
Confirmatory assignment: a later document signed to confirm or repair an earlier ownership transfer.
What are the big takeaways?
- Your company must own the code and related assets clearly, not emotionally. If ownership is vague, startup value is weaker than it looks.
- Implementation follows a simple path: audit contributors, fix documents, secure accounts, then review regularly.
- Stage matters. Seed startups should focus on founder and contractor assignments first, while later-stage companies need due diligence-grade records.
- Success depends on documentation, account control, and repeatable hiring process.
- The cost of delay is ugly. Ownership gaps often surface at the worst possible moment: fundraising, founder breakup, or acquisition.
My blunt founder view is this: startup education should be slightly uncomfortable because reality is. IP assignment feels boring right until the day it becomes the most expensive file you forgot to sign. Build your company like a real asset from day one, and make ownership invisible inside the workflow. That is how small teams protect what they are actually creating.
People Also Ask:
What is intellectual property?
Intellectual property is a legal term for creations of the mind, such as software code, inventions, brand names, logos, written content, designs, and trade secrets. It gives the owner certain legal rights over how that work is used, copied, sold, or licensed.
What are the 4 types of intellectual property?
The four main types of intellectual property are copyrights, trademarks, patents, and trade secrets. Copyrights protect original creative works like code and written content, trademarks protect brand identifiers like names and logos, patents protect inventions, and trade secrets protect confidential business information.
What is the assignment of intellectual property rights?
An assignment of intellectual property rights is a legal transfer of ownership from one party to another. In a company setting, it usually means a founder, employee, or contractor signs a document giving the business ownership of the code, designs, inventions, or other work they created.
Why must a company own the code from day one?
If the company does not clearly own the code from the start, the person who wrote it may still hold the legal rights. That can create disputes during fundraising, acquisitions, licensing deals, or even daily business operations. Early ownership paperwork helps avoid later fights over who controls the product.
Does paying a developer mean the company automatically owns the code?
No. Payment alone does not always transfer ownership. Without a written IP assignment or work-made-for-hire language where allowed, the developer may still own the code even if they were paid to create it.
Why is it necessary to protect intellectual property?
Protecting intellectual property helps a business keep control over its products, brand, confidential know-how, and market position. It also makes it easier to enforce rights against copying, attract investors, and show clear ownership during due diligence.
Who should sign an IP assignment agreement?
Founders, employees, contractors, freelancers, consultants, and anyone else creating work tied to the business should usually sign an IP assignment agreement. This helps make sure all company-related work is legally owned by the company, not by the individual creator.
What does an IP assignment agreement usually cover?
An IP assignment agreement usually covers software code, inventions, product designs, documents, trademarks, trade secrets, and other work created for the company. It often also includes confidentiality terms and promises to help the company confirm ownership later if needed.
What happens if there is no IP assignment agreement?
Without an IP assignment agreement, ownership may stay with the individual creator instead of the company. That can cause legal disputes, delay deals, weaken the company’s value, and create problems if a founder or contractor leaves.
Can unclear IP ownership hurt fundraising or an acquisition?
Yes. Investors and buyers usually want proof that the company owns its code and other intellectual property. If ownership is unclear, they may reduce the deal value, delay the transaction, or walk away entirely.
FAQ
What happens if a startup incorporated after the product was already being built?
That is a classic chain-of-title gap. Code, designs, and product ideas may still belong to individual founders unless they were formally transferred into the company. Use founder assignment documents, list pre-incorporation assets clearly, and approve the transfer in company records before fundraising starts.
Can investors walk away over messy software IP ownership?
Yes. Investors may still proceed, but unclear ownership often leads to delays, lower valuation, extra warranties, or mandatory cleanup before closing. Treat IP diligence like finance diligence: if you cannot prove who owns core code, your startup’s main asset may look legally unstable.
Does copyright registration matter if the company already has assignment agreements?
Usually, assignment is the first priority, but registration can still strengthen enforcement in some jurisdictions. For startups with valuable proprietary software, key brand assets, or recurring infringement risk, ask counsel whether copyright registration, trademark filing, or patent strategy should complement ownership paperwork.
How should startups handle reusable code libraries created by contractors or agencies?
Separate new work from pre-existing materials. Your contract should state what the vendor owned before the project, what is being licensed, and what is being assigned to the startup. This avoids hidden reuse disputes and reduces vendor lock-in around critical software components.
What should be in an IP due diligence folder before a fundraise or acquisition?
Prepare signed founder, employee, contractor, and agency agreements; an asset register; open-source reviews; domain and repo ownership records; and evidence of account control. If your team builds quickly with AI, this Vibe Coding for Startups article helps frame governance alongside speed.
Are Git commits, invoices, or Slack messages enough to prove code ownership?
No. They may help show who created something, but they rarely replace a proper legal transfer. Ownership of startup software IP should come from signed agreements with clear assignment language, not from informal evidence that only becomes relevant once a dispute already exists.
How can startups protect trade secrets while still collaborating with external developers?
Use confidentiality clauses, least-privilege access, private repos, logging, and structured offboarding. Only share what external contributors need. If a workflow, model tuning method, or customer dataset creates competitive advantage, protect it as confidential know-how in addition to assigning copyright and invention rights.
What extra checks are needed when using open source inside proprietary startup code?
You need more than a dependency list. Review license terms, attribution duties, copyleft triggers, and whether any package could affect distribution rights. A practical open-source IP traps overview is useful when product teams move faster than legal review.
Can a startup fully own AI-assisted code or content created by its team?
Sometimes, but not automatically in every scenario. You need internal rules on approved tools, input handling, output review, and vendor terms. Track where AI-generated or AI-assisted assets enter the product so you can assess provenance, restrictions, and replacement risk later.
What is the fastest way to clean up old IP assignment mistakes without freezing product work?
Start with the assets that matter most to revenue, fundraising, or defensibility. Get confirmatory assignments signed, transfer technical accounts, map creators to contracts, and flag anything that may need a rewrite. Do not aim for perfection first; fix material ownership gaps in priority order.
