As hiring ramps, founders and operators need paperwork that cleanly vests ownership of inventions, code, and content, without drifting into California-incompatible overreach. A common breakdown is relying on future-tense promises instead of a present assignment, or never getting a signed transfer at all. For patent rights, legal ownership turns on a written assignment under 35 U.S.C. § 261. Law Laguna drafts and implements confidentiality and invention assignment agreements that preserve chain of title, document pre-existing materials, and stay aligned with California contractor and onboarding realities.
Prevent title gaps in employee and contractor IP
Confidentiality and invention assignment documents often sit at the intersection of federal intellectual property rules and California employment and contractor constraints. For copyright, the default owner is the author, and the employer only owns as “work made for hire” in qualifying circumstances under 17 U.S.C. § 201(a), (b). If the agreement assumes ownership without meeting those requirements, the company may only have limited implied rights to use the work. The practical effect shows up later, during financing, acquisition diligence, or a customer contract that requires proof of ownership. We focus on drafting that is operationally usable, signature-complete, and structured for clean transfer and licensing.
We align confidentiality definitions, work product definitions, and present-grant assignment language into a single chain-of-title package. We document pre-existing materials with disclosure schedules and licensing mechanics that match how engineers and creatives actually build. We also pressure-test contractor language to avoid creating unintended “statutory employee” issues while still protecting deliverables and proprietary rights.
-
Secure a present assignment that states the individual hereby assigns, not “agrees to assign”, to reduce chain-of-title disputes.
-
Define work product to capture inventions, code, content, and ideas, and connect disclosure to an invention disclosure workflow.
-
Calibrate any trailer or holdover clause to a narrow, defensible scope tied to employment efforts and confidential information.
The goal is clear ownership that withstands diligence and enforcement questions. The method is clean contracts, clean signatures, and California-aware implementation.
Counsel for operators protecting day-to-day IP creation
Based in Laguna Beach and serving Southern California businesses. Remote engagements available statewide across California.
VP of Engineering (or Head of Product Engineering)
You need code and inventions assigned with present grant language, not a promise that creates only equitable rights. You also need clarity on open source intake, third-party components, and whether a shop right or implied non-exclusive license is the only thing you actually have today.
-
Clean up “agrees to assign” language before a term sheet requires proof of ownership.
-
Align invention disclosure steps with how engineers ship features and prototypes.
-
Confirm contractor deliverables are assignable without misusing work made for hire language.
Head of People / HR Director
You need onboarding documents that protect confidential information and work product without being overbroad for California practices. You also need signature tracking, pre-existing invention disclosures, and a workable trailer or holdover clause that does not read like a non-compete substitute.
-
Implement a signature-complete proprietary rights agreement workflow for every hire.
-
Standardize pre-existing IP schedules so teams disclose outside projects at onboarding.
-
Coordinate security acknowledgments to support reasonable efforts around trade secrets.
General Counsel (or outside counsel manager at a growth company)
You need a clean chain of title for diligence, customer procurement, and collaboration agreements that require transfer or sublicensing rights. You also need contractor IP terms that are deliberate about work made for hire and the statutory employee consequences that can follow in California.
-
Support a financing or acquisition diligence request with recorded and executable assignments.
-
Paper a collaboration where ownership, license-back, and further assurances must align.
-
Remediate missing signatures and unclear work product definitions before a customer negotiation.
VP of Engineering (or Head of Product Engineering)
You need code and inventions assigned with present grant language, not a promise that creates only equitable rights. You also need clarity on open source intake, third-party components, and whether a shop right or implied non-exclusive license is the only thing you actually have today.
-
Clean up “agrees to assign” language before a term sheet requires proof of ownership.
-
Align invention disclosure steps with how engineers ship features and prototypes.
-
Confirm contractor deliverables are assignable without misusing work made for hire language.
Head of People / HR Director
You need onboarding documents that protect confidential information and work product without being overbroad for California practices. You also need signature tracking, pre-existing invention disclosures, and a workable trailer or holdover clause that does not read like a non-compete substitute.
-
Implement a signature-complete proprietary rights agreement workflow for every hire.
-
Standardize pre-existing IP schedules so teams disclose outside projects at onboarding.
-
Coordinate security acknowledgments to support reasonable efforts around trade secrets.
General Counsel (or outside counsel manager at a growth company)
You need a clean chain of title for diligence, customer procurement, and collaboration agreements that require transfer or sublicensing rights. You also need contractor IP terms that are deliberate about work made for hire and the statutory employee consequences that can follow in California.
-
Support a financing or acquisition diligence request with recorded and executable assignments.
-
Paper a collaboration where ownership, license-back, and further assurances must align.
-
Remediate missing signatures and unclear work product definitions before a customer negotiation.
Chain-of-Title Agreements for Teams That Build
We build the contract package that governs confidentiality, ownership, and cooperation for inventions and work product created during employment or engagement. The output is a usable set of documents with implementation steps that fit your onboarding and development process.
Employee confidentiality and proprietary rights foundation
-
California Employee Confidentiality & Proprietary Rights Agreement drafting. Establishes confidentiality, ownership, and security-handling rules in one operational document. Ties information handling to reasonable secrecy practices so trade secret protection remains supportable under 18 U.S.C. § 1839(3).
-
Invention assignment framework with present-grant language. Uses present assignment drafting, including “hereby assigns”, to reduce title gaps created by future-tense promises. Creates a clearer transfer record that can be used in diligence and enforcement.
-
Further assurances + power of attorney package. Requires cooperation for later execution and recordation, including USPTO and Copyright Office filings where appropriate. Reduces delays when inventors or authors are no longer easily reachable.
-
Strategic assessment for onboarding ecosystem integration. Maps how the agreement should interface with offer letters, handbook acknowledgments, and security policies at an assessment level. Flags where adjacent documents should be handled through dedicated employment and privacy workstreams.
Contractor and commissioned work architecture
-
Independent contractor IP clause design (California-specific). Evaluates whether to include work made for hire language, given California statutory employee implications for contractors under Cal. Lab. Code § 3351.5(c). Structures assignment and acceptance mechanics so deliverables still transfer cleanly without importing avoidable classification consequences.
-
Work made for hire acknowledgment mechanics. Confirms when employee work can qualify as work made for hire and when a commissioned contractor work must fit a statutory category and be documented in a signed instrument under 17 U.S.C. § 101. Adds a fallback assignment so ownership does not depend on a misfit category.
-
Work product definition and deliverable scoping. Defines work product to cover tangible and intangible outputs, including ideas, inventions, code, content, documentation, and derivative works. Reduces disputes over whether “drafts,” “prototypes,” or internal tools are included.
-
Restrictive covenants tied to IP ownership. Limits filings in an individual’s name, controls mark and attribution behavior related to assigned work, and requires non-contestation where appropriate. Keeps the restrictions connected to ownership and confidentiality, rather than acting as a general restraint.
Pre-existing materials and license-back controls
-
Pre-existing IP schedule + disclosure process. Requires listing prior inventions, code libraries, templates, or creative works that an employee or contractor may want to reuse. Creates a documented baseline that reduces later ownership ambiguity.
-
Pre-existing IP license-back drafting. Grants a present license that is transferable and sublicensable so the company can operate and comply with downstream customer requirements. Adds consent gates for incorporation of outside materials into company products.
-
Representations and warranties against conflicts. Requires disclosure of third-party obligations, prior employer restrictions, and non-infringement issues. Supports procurement and diligence responses with contract-based statements.
-
Post-engagement access and return-of-materials protocols. Defines return, deletion, and device-handling steps to control confidential information after departure. Reinforces security posture and ongoing secrecy controls.
Diligence readiness and post-employment boundaries
-
Post-employment work product trailer or holdover clause design. Narrows duration and scope, often to 6 to 12 months, and ties coverage to work conceived or substantially begun during employment or derived from confidential information. Avoids drifting into non-compete-style drafting while preserving ownership of attributable inventions.
-
Invention disclosure mechanism alignment. Adds a practical disclosure obligation so inventors report developments promptly, not only at exit. Creates a record that supports prosecution strategy and internal decision-making.
-
Moral rights waiver where applicable. Addresses moral rights concerns for certain visual works where a waiver is permitted and the work is not clearly work made for hire. Reduces later disputes about modification, attribution, or integrity expectations.
-
GenAI use policy hook and contract alignment. Connects the agreement to internal policies governing use of generative artificial intelligence tools and third-party platforms. Helps preserve patent and copyright strategy by controlling disclosures and training-data inputs.
Present assignment drafting that closes chain-of-title gaps
A present assignment is contract language that transfers rights now, rather than promising a transfer later. Operationally, present-grant verbs such as “hereby assigns” reduce the risk that the company only holds equitable rights and must chase signatures when financing, licensing, or enforcement happens. For patentable inventions, legal title requires a written assignment under 35 U.S.C. § 261, so drafting and execution discipline matter. For copyrightable works that are not work made for hire, a signed writing is required to transfer ownership under 17 U.S.C. § 204(a).
California teams often mix employees, contractors, and hybrid roles, so assignment language must be consistent across engagement types. Contractor drafting also needs a deliberate choice about work made for hire language, because certain clauses can create statutory employee consequences under Cal. Lab. Code § 3351.5(c) and parallel unemployment provisions. A clean approach typically combines work made for hire where it actually applies, with a fallback present assignment that does not depend on category fit. The goal is enforceable ownership without accidental classification spillover.
-
Use present assignment verbs for inventions, code, content, and ideas, and avoid future-tense promises that leave title pending.
-
Confirm each inventor or author signs a writing that can be used for recordation, including cooperation obligations for later filings.
-
Map whether the work qualifies as work made for hire, and if commissioned, confirm it fits a 17 U.S.C. § 101 category with a signed instrument.
-
Add a pre-existing IP schedule and a transferable, sublicensable license-back to avoid blocking customer flow-down obligations.
-
Narrow any trailer or holdover clause by time and by linkage to employment efforts or confidential information to improve enforceability.
-
Align confidentiality and security handling terms to document reasonable efforts to preserve secrecy under 18 U.S.C. § 1839(3).
We draft and implement these terms to support ownership transfer formalities, confidentiality controls, and California-aware contractor choices in a signature-complete package.
California Regulatory Compliance
Ownership and protectability often turn on formalities that are easy to miss during fast hiring. Patent rights require a written assignment to transfer legal ownership under 35 U.S.C. § 261, so an agreement that relies on a future promise can leave title incomplete when the company needs to record assignments or satisfy diligence. For copyright, ownership begins with the author under 17 U.S.C. § 201(a), and employer ownership as a work made for hire depends on satisfying the statutory framework under 17 U.S.C. § 201(b) and the definition in 17 U.S.C. § 101. When a work is not work made for hire, a signed writing is required to transfer copyright under 17 U.S.C. § 204(a).
Confidentiality obligations also need operational support, because trade secret protection under the Defend Trade Secrets Act (DTSA) and the Economic Espionage Act definition requires reasonable efforts to maintain secrecy, as reflected in 18 U.S.C. § 1839(3). For California contractors, drafting must account for statutory employee consequences that can be triggered by work made for hire clauses under Cal. Lab. Code § 3351.5(c) and parallel provisions in Cal. Unemp. Ins. Code § 621(d) and Cal. Unemp. Ins. Code § 686. We design agreements and workflows with those constraints in view.
Flexible Legal Counsel
Project-Based Drafting
-
Collect role details, deliverables, and current templates, then draft the agreement set with signature-ready exhibits and schedules.
-
Implement a lightweight execution workflow so every hire or contractor signs the right version before access is granted.
-
Deliver a redline and playbook for internal rollout, including disclosure and offboarding steps.
Ongoing Outside Counsel Support
-
Review new roles, contractor engagements, and exceptions as they arise, keeping language consistent across teams.
-
Coordinate with customer and vendor contracting so assignment and licensing terms match downstream obligations.
-
Maintain version control, signature tracking, and periodic refreshes as your product and policies evolve.
Diligence and Remediation Sprints
-
Audit existing agreements for missing signatures, future-tense assignment language, and unclear work product definitions.
-
Prepare corrective assignments, further assurances, and recordation-ready documents for key personnel and contractors.
-
Package a diligence response set that supports financing, acquisition, or enterprise procurement requests.
Engagements stay contract-first and implementation-focused, with clear deliverables and timelines. When needed, we coordinate with employment classification and privacy workstreams at the assessment and referral level.
California IP and Employment Network
Connect ownership, secrecy, and contracting into one defensible system
Confidentiality, Invention Assignment & Employee IP FAQs
Do California employee invention assignment agreements have special notice requirements?
It depends, and the agreement should clearly cover inventions, source code, documentation, designs, trade secrets, and other work product created during employment. Operationally, the document should control disclosure, define confidential information, require invention reporting, and set cooperation steps for filings and recordation. The hidden risk is relying on vague ownership statements that do not produce a signed transfer where federal law requires it, including patent assignment formalities under 35 U.S.C. § 261. Law Laguna drafts California-compatible agreements that are signature-complete and structured for onboarding, enforcement, and diligence.
Is “hereby assigns” better than “agrees to assign” in an invention assignment clause?
Yes, as a general drafting principle, because it more clearly transfers inventions, improvements, source code, specifications, prototypes, and related intellectual property rights in the present. Operationally, present assignment language reduces the need to chase signatures later and supports recordation and third-party diligence where chain of title must be clean. The hidden risk is that future-tense language can leave the company with only equitable rights, and patent ownership still turns on a written assignment under 35 U.S.C. § 261. Law Laguna uses present-grant structures with further assurances so ownership remains operationally usable over time.
Can a contractor agreement say the work is “work made for hire” in California?
It depends, and it involves deliverables such as software code, content, graphics, audiovisual works, documentation, and designs, plus the associated copyright rights. Operationally, the agreement should separate (1) a work made for hire acknowledgement only where the work fits the statutory framework and (2) a fallback signed assignment that transfers rights if it does not. The hidden risk is that work made for hire clauses in California contractor agreements can trigger statutory employee consequences under Cal. Lab. Code § 3351.5(c), with parallel treatment under Cal. Unemp. Ins. Code § 621(d) and Cal. Unemp. Ins. Code § 686. Law Laguna makes a deliberate drafting choice that preserves ownership without importing avoidable classification issues.
Are post-employment invention assignment “holdover” clauses enforceable in California?
It depends, and a holdover clause can cover inventions, improvements, code, designs, documentation, and related work product that is attributable to employment efforts or confidential information. Operationally, enforceability improves when the clause is time-limited and scoped to inventions conceived or substantially begun during employment, or derived from company confidential information. The hidden risk is drafting a broad trailer that reads like a restraint unrelated to ownership, which can invite disputes and reduce practical enforceability when you need cooperation. Law Laguna drafts narrowed holdover clauses that track operational reality and reinforce confidentiality protections.
Do we need a written IP assignment for patents and copyrights, or is an offer letter enough?
Yes, you generally need a written assignment, because the assets include patent rights in inventions and copyright rights in software code, text, images, and other creative works. Operationally, the company should collect signed agreements that contain present assignment language and cooperation obligations, not just employment terms. The hidden risk is assuming the company “automatically owns” inventions and works, even though patent ownership requires a written assignment under 35 U.S.C. § 261 and copyright transfers require a signed writing under 17 U.S.C. § 204(a) unless the work is a work made for hire. Law Laguna builds a signature-complete chain-of-title package designed for diligence and enforcement.
If something is a “work made for hire,” do we still need an assignment?
It depends, and the assets include copyrightable works such as code, written materials, graphics, audiovisual content, and documentation, along with derivative works and revisions. Operationally, you should still include a signed assignment as a fallback because work made for hire status can fail if the role or the commissioned-work category does not match 17 U.S.C. § 101 requirements. The hidden risk is that if the work is not actually work made for hire, ownership remains with the author under 17 U.S.C. § 201(a), and any transfer must satisfy 17 U.S.C. § 204(a). Law Laguna pairs work made for hire acknowledgments with present-grant assignment language to keep ownership clear.
How should we handle an employee or contractor’s pre-existing code or creative assets?
It depends, and pre-existing assets can include prior code libraries, templates, designs, written content, datasets, and other intellectual property the individual created outside the engagement. Operationally, you should require disclosure on a schedule, restrict incorporation without consent, and if incorporation is allowed, obtain a present license that is transferable and sublicensable to support customer and partner obligations. The hidden risk is that undisclosed pre-existing materials can create ownership ambiguity, limit distribution rights, or force a retrofit during diligence when assignments under 17 U.S.C. § 204(a) were never obtained. Law Laguna drafts disclosure schedules and license-back terms that keep product development and contracting aligned.
Do confidentiality agreements help with trade secrets, or do we need more than a contract?
Yes, they help, and the assets include trade secrets and confidential information such as source code, product roadmaps, customer lists, pricing, technical data, and internal processes. Operationally, the agreement should restrict use and disclosure, require security handling, define return and deletion steps, and connect to access-control practices so confidentiality is actually implemented. The hidden risk is treating secrecy as only a signature task, because trade secret status under federal law depends on reasonable efforts to maintain secrecy under 18 U.S.C. § 1839(3). Law Laguna drafts confidentiality terms that map to practical security controls and integrates them into onboarding and offboarding workflows.
Stop chain-of-title gaps before diligence
When ownership language is incomplete or unsigned, transactions slow down and enforcement becomes harder than it needs to be. Future-tense assignment language can leave the company chasing signatures at the least convenient time. California contractor drafting can also create avoidable classification consequences if work made for hire language is used without a deliberate plan.
We start with a document and workflow review, then identify the shortest path to a signature-complete, present-assignment package. You receive executable agreements, exhibits, and implementation steps designed for onboarding, contractor engagement, and diligence requests.