IP Ownership Clauses for Remote Contractors

A remote contractor can write your next core patent before lunch. Without the right cross-border assignment language and local formalities, they may still own it.

Under U.S. law, inventors presumptively own their inventions. The Supreme Court confirmed this in Stanford v. Roche, 563 U.S. 776 (2011). Even the Bayh-Dole Act does not automatically vest title in the hiring party. For independent contractors, there is no employer default. No written, present-tense assignment means your client likely does not own what it paid for.

Cross-border work makes it worse. In most countries, the person who creates the work owns it unless a signed agreement says otherwise. Civil law jurisdictions layer on mandatory compensation, notification periods, and moral rights that a standard U.S.-style clause will not satisfy. This page is a drafting checklist for patent attorneys handling these assignments.

Last updated: March 2026. This page is informational only and not legal advice. Consult qualified counsel in each relevant jurisdiction for your specific situation.

2011

Stanford v. Roche confirmed inventors own by default. No assignment, no transfer.

10–30%

Estimated share of international workers misclassified, creating ownership gaps

4 mo.

Window to claim employee inventions under Germany's ArbnErfG before rights lapse

3 mo.

USPTO recordation window for constructive notice to subsequent purchasers

Step 1: Classify the Worker Before You Draft

The enforceability of your IP assignment clause turns first on worker classification, not clause wording. Employee, independent contractor, consultant, and offshore service provider are treated differently under IP and labor law in nearly every jurisdiction.

In the United States, a contractor retains IP rights unless there is an explicit written assignment. An employee's inventions may vest in the employer under state-specific "hired to invent" doctrines or written agreements. But the categories are not portable. A worker you classify as a contractor under U.S. tax law may be deemed an employee under German, French, or Brazilian labor law. When that happens, local employee-invention statutes override your contract terms.

Industry surveys estimate 10 to 30 percent of employers misclassify workers internationally. Misclassification does not just create tax liability. It creates ownership gaps. If a local tribunal reclassifies your contractor as an employee, the IP assignment clause drafted for a contractor relationship may be unenforceable, and mandatory employee-invention rules apply instead.

Confirm worker classification in every jurisdiction where the contractor will perform work, not just where your client is incorporated.

Evaluate Employer of Record (EOR) structure when classification risk is high. An EOR formally employs the worker under local law, activating employer-friendly IP defaults in many countries.

Understand the tradeoff. EOR structures provide a cleaner title chain but require accepting local employment obligations: benefits, termination rules, tax withholding.

Classification first, clauses second. A perfectly worded assignment clause is unenforceable if a local tribunal reclassifies your contractor as an employee. Before drafting, confirm classification in every country where work will be performed.

Step 2: Triage Jurisdictions by Legal Risk

Not all countries break your U.S.-style assignment clause the same way. A jurisdiction-risk framework helps you decide where boilerplate is adequate and where local counsel review is mandatory.

🟢 Low-Risk Jurisdictions

Generally recognize freedom of contract for IP assignment between companies and independent contractors. The U.S., UK, and several common law countries fall here. A well-drafted present-tense assignment clause is usually sufficient, provided worker classification is correct.

🟡 Medium-Risk Jurisdictions

Impose specific formalities. Germany requires employers to claim employee inventions within four months (ArbnErfG). Japan's Patent Act Article 35 requires reasonable compensation. China requires written agreements and may impose compensation obligations. Missing formalities can make an assignment voidable.

🔴 High-Risk Jurisdictions

Have mandatory rules that cannot be contracted around. France, Italy, and parts of Latin America impose strong moral rights that cannot be fully waived. Others limit assignment of future inventions or require government registration. Your clause alone is not sufficient. Local counsel review and possibly an EOR structure are required.

⚠️ Defect Taxonomy Matters

A flawed assignment may be void (no transfer occurred), voidable (can be challenged), or unperfected (valid between parties but not against third parties). Knowing which category applies determines whether you re-draft, ratify, or simply record.

Jurisdiction triage determines your drafting strategy. Boilerplate works for low-risk common law countries. For Germany, Japan, China, France, and similar civil law jurisdictions, local counsel review is not optional. It is the minimum. See the USPTO guidance and case law on AI-assisted inventions for how these standards are evolving in practice.

Step 3: Get the Assignment Language Right

Stanford v. Roche drew a bright line between present-tense assignments and future promises. The researcher's agreement stating he "will assign" future inventions lost to a second agreement stating he "does hereby assign" rights. Under U.S. law, "hereby assigns" transfers title immediately upon creation. "Agrees to assign" creates only a contractual obligation to transfer later. That obligation can be defeated by an intervening present assignment to a third party.

Language	U.S. Effect	Civil Law Risk	Recommendation
"Hereby assigns"	Immediate title transfer on creation	May be void in jurisdictions prohibiting future-invention assignments	Use for U.S.
"Agrees to assign"	Contractual promise only — defeatable	Same enforceability risk, less U.S. protection	Avoid
Work made for hire	U.S. copyright only, specific categories	Does not exist in most civil law countries; never applies to patents	Not for patents
Moral rights waiver	Not applicable (U.S. has limited moral rights)	Required in France, Italy — but may be inalienable	Country-specific

Separate your IP categories. Patent ownership, copyright ownership, trade secret rights, and moral rights are governed by different legal regimes in many countries. Your clause needs distinct treatment for each: invention assignment for patents, copyright assignment (or work-for-hire where available) for code and documentation, confidentiality obligations for trade secrets, and moral rights waivers where permitted.

"Hereby assigns" is the floor, not the ceiling. It works for U.S. patent rights but must be paired with jurisdiction-specific formalities, separate copyright assignment language, and moral rights waivers in applicable countries. One clause cannot do all of this.

Step 4: Address Inventorship Separately from Ownership

A perfect assignment clause does not fix a bad inventorship analysis. Under 35 U.S.C. § 116, each person who contributed to the conception of a claimed invention must be named as an inventor on the U.S. patent application. Inventorship is a legal determination based on contribution to conception. It is not a business decision based on who paid for the work.

If your client's remote contractor contributed to the conception of a claimed invention, that contractor must be named as an inventor. The assignment clause transfers ownership rights from the inventor to your client, but it does not eliminate the inventorship requirement. An incorrect inventorship determination can invalidate the patent under 35 U.S.C. § 256, and the error is only correctable if made without deceptive intent.

Require regular invention disclosure forms. Build contractor disclosure obligations into the engagement workflow, not just at the end of the project. A structured three-level patent disclosure framework gives contractors a practical template for capturing inventions as they happen.

Include a cooperation clause obligating the contractor to execute declarations, assignments, and other documents necessary for patent prosecution.

Make cooperation obligations survive termination. A contractor who leaves the engagement must remain obligated to assist with prosecution of inventions created during the engagement.

Direction does not equal inventorship. Conception does. If the contractor independently conceived a novel solution to the problem your client defined, that contractor is likely a co-inventor, regardless of who directed the project or what the contract says.

Step 5: Record, Perfect, and Maintain the Chain of Title

Under 35 U.S.C. § 261, patent assignments must be in writing and can be recorded at the USPTO. Recordation within three months of execution gives constructive notice to subsequent purchasers. But recordation does not create title. If the underlying assignment is defective — wrong language, missing formalities, incorrect party — recording it at the USPTO does not cure the defect.

Confirm validity under local law first. Verify the assignment is enforceable under the law governing the contractor's location before filing anything at the USPTO.

Record promptly at the USPTO within three months of execution to achieve constructive notice against subsequent purchasers.

Complete local registration steps where required — for example, China's CNIPA for patent assignments involving Chinese entities.

Require pre-existing IP disclosure before work begins. License pre-existing IP under terms allowing freedom to operate. Do not attempt to assign IP created before the engagement.

Include survival and disclosure clauses. Cooperation, assignment, and confidentiality obligations must survive termination. Disclosure of inventions during the engagement is the trigger for your client's rights.

Recordation at the USPTO is not a cure for a defective assignment. It is constructive notice of whatever transfer, valid or not, happened underneath. Fix the underlying defect first, then record.

Step 6: Clean Up Title Defects After the Fact

Sometimes you inherit the problem. A remote contractor already created patentable subject matter before the assignment was signed. The original agreement used "agrees to assign" instead of "hereby assigns." Local formalities were not followed. Here is how to work through it.

Diagnose the defect category first. Determine whether the assignment is void, voidable, or merely unperfected. The remediation path is different for each.

If the contractor is cooperative, execute a confirmatory assignment using present-tense language that complies with formalities in the contractor's jurisdiction. Back-date the effective date if the governing law permits. Record promptly at the USPTO.

If the contractor is uncooperative, enforce the contractual obligation to assign through litigation or arbitration. In the U.S., courts can order assignment under equity. Internationally, enforceability depends on the dispute resolution clause and local jurisdiction.

Scan contractor-written code during the engagement, not after. Tools that run locally on the developer's machine can identify patentable discoveries while the contractor is still available and cooperative. That gives you time to address inventorship and assignment before the relationship ends. Understanding why local-first processing matters for pre-filing invention discovery explains the trade secret risks that make this approach essential.

The best time to fix a title defect is before it exists. Scan for inventions during active contractor engagements, not during due diligence. Cooperative inventors execute documents. Former contractors hire lawyers.

Frequently Asked Questions

Which jurisdictions most often break a standard U.S.-style invention assignment clause?

Germany, Japan, China, France, and several other civil law countries impose mandatory rules that override contract terms. Germany's Employee Inventions Act requires a formal claiming process within four months. Japan's Patent Act, Article 35, requires reasonable compensation. France imposes inalienable moral rights. China requires written agreements and may mandate compensation. In these jurisdictions, a U.S.-style "hereby assigns" clause may be interpreted as a promise rather than a present transfer, or may be void for failing to follow local formalities. Local counsel review is necessary for any contractor performing work in these countries.

What is the difference between "hereby assigns" and "agrees to assign" in a contractor agreement?

Under U.S. law, "hereby assigns" operates as an immediate transfer of rights upon creation of the invention. "Agrees to assign" creates only a contractual promise to transfer in the future. The Supreme Court drew this distinction in Stanford v. Roche, 563 U.S. 776 (2011), where a present assignment defeated a prior promise to assign. For U.S. patent purposes, always use present-tense language. Note that this distinction may not be recognized or enforced the same way in civil law jurisdictions, where local statutory requirements may control regardless of the clause language.

When is an EOR structure better than a contractor agreement for IP ownership?

An Employer of Record structure is worth considering when the contractor performs work in a jurisdiction with strong employee-invention statutes (Germany, Japan, France), when misclassification risk is high, or when the IP being created is core to your client's patent portfolio. The EOR formally employs the worker under local law, which activates employer-friendly IP defaults in many countries. The tradeoff: your client accepts local employment obligations, including benefits, termination protections, tax withholding, and potentially higher costs. For low-value or short-term engagements in low-risk jurisdictions, a well-drafted contractor agreement is usually sufficient.

How do we clean up title if a contractor created patentable subject matter before the assignment was signed?

Start by determining whether the defect is void, voidable, or unperfected. If the contractor is cooperative, execute a confirmatory assignment using present-tense language ("hereby assigns") that complies with the formalities required in the contractor's jurisdiction. Record the confirmatory assignment at the USPTO under 35 U.S.C. § 261. If the contractor is uncooperative, you may need to enforce the contractual promise to assign through litigation or arbitration. In the U.S., courts can order assignment under equity. Internationally, enforcement depends on the dispute resolution clause and whether the local jurisdiction will compel IP transfer.

Does "work made for hire" apply to inventions created by foreign contractors?

No. "Work made for hire" is a U.S. copyright doctrine under 17 U.S.C. § 101. It applies only to certain categories of copyrightable works and does not apply to patent rights. Most civil law countries do not recognize the work-for-hire concept at all. For patent ownership, you need an explicit invention assignment clause. For copyright ownership in code and documentation created by foreign contractors, you need a separate copyright assignment — the work-for-hire doctrine will not be available in most non-U.S. jurisdictions.

Does recording an assignment at the USPTO fix a defective assignment?

No. Recordation under 35 U.S.C. § 261 provides constructive notice to subsequent purchasers and creates a public record. It does not create or validate title. If the underlying assignment is defective — wrong language, missing local formalities, incorrect party — the recorded document is just a record of a defective transfer. You still need to cure the underlying defect through a confirmatory assignment or other corrective action.

The inventions hiding in your codebase are not going to find themselves.

Remote contractors write patentable code every day. ObviouslyNot runs locally on the developer's machine — no code leaves the device — and surfaces inventions before the engagement ends and the window for cooperative assignment closes.

No code leaves your device.

Discover your inventions