Intellectual property in HR: employment guide (2026)

Four types of intellectual property HR must understand

IP type	What it covers	Registration required?	Duration
Copyright	Written works, software, training materials, marketing content	No (automatic on creation); registration strengthens enforcement	Life of author + 70 years
Patent	Inventions, processes, new product designs	Yes — USPTO application required	20 years (utility)
Trade secret	Formulas, algorithms, customer lists, pricing models, business strategies	No — protected by confidentiality and reasonable security measures	Indefinite while secret
Trademark	Brand names, logos, slogans that distinguish goods/services	Optional; registration at USPTO provides national protection	Indefinite with renewal

For most HR and talent teams, copyright and trade secrets are the highest-frequency concerns: they cover the work product employees create daily and the confidential business information they access from day one.

Summarise this post with:

IP ownership: employees vs. contractors

Ownership rules differ sharply based on whether the creator is an employee or an independent contractor. HR must apply these rules consistently at every hiring stage.

The work-for-hire doctrine

Under the U.S. Copyright Act, a work created by an employee within the scope of employment is a “work made for hire” — meaning the employer, not the individual, is the legal author and owner from the moment of creation. No assignment agreement is needed for employees; scope of employment does the work.

For independent contractors, the work-for-hire doctrine applies only to nine statutory categories (contributions to collective works, motion pictures, translations, instructional materials, tests, answer materials for tests, atlases, compilations, and supplementary works) and only when both parties sign a written agreement stating the work is a work for hire. For anything outside those nine categories — including most software — a contractor owns their own copyright unless they explicitly assign it in writing.

Patent ownership defaults

Patents follow a different default: the inventor owns the patent regardless of employment status, unless the employee was specifically hired to invent (the “hired to invent” doctrine) or a written assignment agreement transfers rights to the employer. According to the Society for Human Resource Management (SHRM), all employees — from the receptionist to the CEO — should sign a separate written IP assignment agreement at the date of hire.

Scenario	Copyright default	Patent default	What fixes it
Employee, within scope of duties	Employer owns	Employee owns (unless hired to invent)	Written invention assignment clause
Employee, outside work hours, no company resources	Employee owns	Employee owns	Broad assignment clause (check state law)
Independent contractor, inside nine categories + written WFH agreement	Employer owns	Employee owns	Separate patent assignment clause
Independent contractor, outside nine categories, no written agreement	Contractor owns	Contractor owns	Both copyright assignment + patent assignment in contract

State law adds complexity. California, Delaware, Illinois, Minnesota, North Carolina, and Washington all limit employer claims over inventions developed entirely on the employee’s own time without company resources. HR policies must reflect the applicable jurisdiction.

Key IP clauses in employment contracts

A robust individual employment agreement includes at minimum four IP-related clauses.

1. IP assignment clause

Requires the employee to assign all rights in work-related IP to the employer at the moment of creation. Should cover inventions, software, designs, written works, and any other output created with company resources or related to company business. The USPTO recommends that employers require written assignment of patent rights for every employee, not just engineers or developers.

2. Prior inventions disclosure

Requires new hires to disclose any IP they own before joining. This protects the company from inadvertently claiming rights to something the employee already owned and protects the employee from unfair assignment of pre-existing work. Document this at offer acceptance, not on day one.

3. Confidentiality and non-disclosure agreement (NDA)

A confidentiality agreement protects trade secrets and proprietary information by prohibiting employees from disclosing or using the information outside of their employment duties. It should define what counts as confidential, how long the obligation lasts post-termination, and the specific permitted uses. Under the DTSA, any NDA that covers trade secrets must include a whistleblower immunity notice (see below).

4. Non-compete and non-solicitation clauses

Non-compete clauses restrict employees from working for competitors after leaving. Their enforceability varies widely by state — California, Minnesota, and North Dakota ban them entirely. Non-solicitation clauses (restricting poaching of clients and colleagues) are more broadly enforceable. HR should work with legal counsel to calibrate scope, duration, and geographic reach for each role and jurisdiction. Note: the FTC proposed a near-total ban on non-competes in 2024; monitor regulatory status.

The Defend Trade Secrets Act (DTSA) and what HR must do

The Defend Trade Secrets Act of 2016 (18 U.S.C. § 1836) created a federal civil cause of action for trade secret misappropriation, giving employers nationwide remedies including injunctions, damages, and attorneys’ fees. Before DTSA, employers relied on a patchwork of state trade secret laws.

Three DTSA requirements HR must implement:

• Whistleblower immunity notice. Any NDA or employment agreement that covers trade secrets must include language notifying employees that they may disclose trade secrets to federal, state, or local government officials or to an attorney solely for the purpose of reporting a suspected law violation, without liability under federal or state trade secret law. Failure to include this notice bars the employer from recovering exemplary damages or attorneys’ fees in a DTSA lawsuit.
• Define “employee” broadly. DTSA’s definition of “employee” includes contractors and consultants, not just W-2 staff. The notice requirement applies to all agreements with these individuals.
• Reasonable security measures. To qualify for trade secret protection, the company must take steps reasonably calculated to keep the information secret — access controls, confidentiality agreements, need-to-know policies, and offboarding checklists.

Building an IP policy: what HR must include

An IP policy operationalises the legal framework into day-to-day HR practice. Effective enterprise IP policies cover six elements:

1. Scope of covered IP. Define exactly what types of creations the policy covers — software, documentation, internal tools, customer data models, pricing algorithms.
2. Assignment at point of creation. IP transfers automatically; no separate action needed from the employee. Make this explicit.
3. Prior inventions carve-out. List employee-owned IP at hire; update annually for long-tenured staff in R&D roles.
4. Contractor and vendor requirements. Require IP assignment and DTSA-compliant NDAs in every SOW and contractor agreement. HR and Legal should co-own this checklist.
5. Access controls and classification. Classify information by sensitivity (public, internal, confidential, restricted) and tie access to role. This feeds both trade secret protection and SOC 2 / GDPR data governance.
6. Offboarding IP checklist. Return of company devices, revocation of access credentials, confirmation of trade secret obligations, and destruction/return of any confidential materials. Document completion in the HRIS.

Use skills-based assessments to screen candidates for legal and compliance roles. Explore Testlify’s assessment library

IP considerations in hiring and skills assessment

IP risk does not start at signing — it starts at the first interview. For technical and knowledge-worker roles, HR faces two distinct IP challenges in hiring:

Preventing IP contamination from new hires

Candidates who bring proprietary code, algorithms, or confidential data from a prior employer create misappropriation liability for the new company. HR should require candidates to confirm in writing (typically in the offer letter or onboarding paperwork) that they will not use or bring any prior employer’s confidential information. Background verification for senior technical roles should include review of prior IP and non-compete obligations.

Verifying technical competence without enabling misappropriation

Take-home coding tests and whiteboard exercises sometimes inadvertently prompt candidates to reproduce proprietary solutions. Structured, role-specific skills assessments run on a standardised platform avoid this problem: they test genuine ability without asking candidates to demonstrate work belonging to a prior employer. For enterprise hiring at volume, this reduces both legal exposure and bias in technical evaluation.

Frequently asked questions

Verify technical candidates’ IP credentials with Testlify’s role-specific assessments before extending an offer. Start free trial

Frequently asked questions

Run role-specific assessments to validate IP, legal, and compliance competencies before you hire. Start free trial