# Employee Invention Assignment in Arizona[^about] Arizona has no employee-invention-assignment statute — the section sometimes cited for one (A.R.S. § 44-403) is the damages provision of the state trade-secrets act, and the 2013 bill that would have created a carve-out died without enactment — so an assignment clause is bounded only by ordinary contract law, the common-law default rules, and the federal patent and copyright overlay. Absent a written assignment the inventor owns unless hired to invent, and a post-employment holdover clause's enforceability is unsettled, with Arizona's restrictive-covenant reasonableness framework the likely but untested measure. ## Can an Arizona employer require assignment of every invention? {#statutory-carve-out} **Short answer.** There is no statutory ceiling. Arizona has no employee-invention-assignment statute — no California-style own-time carve-out, no employer-ownership provision, and no notice requirement — so an assignment clause's reach is bounded only by ordinary contract law, the common-law inventor-owns default, and the federal patent and copyright overlay. The section most often miscited as an Arizona carve-out, A.R.S. § 44-403, is actually the damages provision of Arizona's trade-secrets act, and the baseline any assignment clause operates against is that rights in an invention belong to the inventor [^az-44-403-damages][^stanford-baseline]. Because there is no statute on point, the limits come from general principles rather than a legislative carve-out. Arizona has enacted no § 2870-style own-time carve-out, no employer-ownership default, and no invention-disclosure or notice statute — for employee inventions it is a pure common-law and contract state, and a drafter starts from contract law rather than a statutory ceiling on what an assignment promise may capture. One point deserves an explicit correction, because a contrary claim circulates widely. A.R.S. § 44-403 is sometimes listed as Arizona's invention-assignment carve-out. It is not. Section 44-403, whose catchline is *Damages*, is the damages section of the Arizona Uniform Trade Secrets Act — A.R.S. §§ 44-401 through 44-407 — and its subject is recovery for trade-secret misappropriation, not employee inventions [^az-44-403-damages]. Its operative text is remedial through and through; subsection (B), for example, addresses exemplary damages. "If willful and malicious misappropriation exists, the court may award exemplary damages in an amount not exceeding twice any award made under subsection A."[^az-44-403-damages] The kernel of truth behind the misattribution is a dead bill. In 2013, Arizona House Bill 2632 (51st Legislature, First Regular Session) would have created a California-style own-time carve-out, with a written-notice duty, as a new A.R.S. § 23-204 — but the bill died without enactment, and the section number it targeted was later consumed by an unrelated law. The current official text of § 23-204 is an employee-benefits preemption statute, which is conclusive proof the invention carve-out never became law [^az-23-204-current-text]. "Employee benefits; state preemption; exemption; definition"[^az-23-204-current-text] The introduced text of HB 2632 remains published on the Arizona Legislature's website, which helps explain why the dead bill is still sometimes mistaken for current law; it is legislative history showing Arizona considered and declined the carve-out model, nothing more [^az-23-204-current-text]. The substantive default that Arizona contract law operates against is the federal patent premise restated in *Stanford v. Roche*: absent an effective assignment, rights in an invention belong to the person who conceived it [^stanford-baseline]. "Since 1790, the patent law has operated on the premise that rights in an invention belong to the inventor."[^stanford-baseline] The practical consequence is that an Arizona employer can, in principle, contract for assignment more broadly than a California or Washington employer, because no statute carves out own-time inventions from the reach of the clause. But that breadth is not unlimited: an assignment clause is still an ordinary contract term, subject to general contract-law defenses and, where it functions as a restraint on the employee, to Arizona's reasonableness limits on restraints. There is simply no statutory own-time safe harbor for the employee to invoke and no statutory ceiling for the drafter to code around. ## Must an Arizona employer notify the employee? {#employee-notice} **Short answer.** Not applicable. Because Arizona has no invention-assignment statute, there is no statutory carve-out to notify the employee about and no notice requirement of the kind California imposes under Labor Code § 2872 or Washington imposes under RCW 49.44.140(3). The only written-notice duty Arizona ever drafted was in 2013 HB 2632, which died without enactment — the section it targeted now holds an unrelated employee-benefits preemption statute [^az-23-204-no-notice]. There is nothing to give notice of. A notice requirement exists in California and Washington precisely to alert the employee to a statutory own-time carve-out that limits the assignment; Arizona has enacted no such carve-out, so there is no statutory line for a notice to mark. This is why the entry is marked not applicable rather than a bare no: the question presupposes a statutory carve-out that Arizona does not have. Arizona came close exactly once. The written-notice duty in 2013 HB 2632 would have required employers to tell employees about the carve-out the bill proposed to enact as A.R.S. § 23-204 — but the bill died, and the current official text of that section confirms it [^az-23-204-no-notice]. "Employee benefits; state preemption; exemption; definition"[^az-23-204-no-notice] For a multistate employer the takeaway is the inverse of the notice states: an Arizona employer neither has to give a § 2872-style notice nor can rely on one to cure an overbroad clause. The enforceability of the assignment turns entirely on the contract language and the general limits on restraints, not on any statutory notice or disclosure formality. ## Who owns an invention by default in Arizona? {#default-ownership} **Short answer.** The inventor, unless hired to invent. Absent a written assignment, the baseline under federal patent law — which governs who holds title to a patentable invention in Arizona as elsewhere — is that rights belong to the employee who conceived it. The narrow exception is the employee hired to invent, whose resulting invention the employer may claim [^stanford-inventor][^dubilier-hired-to-invent]. *Stanford v. Roche* anchors the default. The Supreme Court held that even the Bayh-Dole Act did not displace the long-standing rule that an invention belongs to its inventor, treating that premise as the baseline against which any assignment is measured [^stanford-inventor]. "Since 1790, the patent law has operated on the premise that rights in an invention belong to the inventor."[^stanford-inventor] Because ownership starts with the inventor, an employer's title is derivative — it exists only if and to the extent the employee assigned it. Any third-party interest must trace back to that inventor-grantor [^stanford-traceback]. "Thus, although others may acquire an interest in an invention, any such interest — as a general rule — must trace back to the inventor."[^stanford-traceback] The principal exception is the employee hired to invent. Under *United States v. Dubilier Condenser Corp.*, an employee engaged to make a particular invention who succeeds during the term of service must assign the resulting patent to the employer [^dubilier-hired-to-invent]. "One employed to make an invention, who succeeds, during his term of service, in accomplishing that task, is bound to assign to his employer any patent obtained."[^dubilier-hired-to-invent] Short of that, where the employee is neither hired to invent nor bound by a written assignment but has used the employer's time, tools, and materials to reach a concrete result, the employer's remedy under *Dubilier* is only an equitable shop right — a non-exclusive license to use the invention, not ownership of it [^dubilier-hired-to-invent]. Arizona's own closest appellate decision is consistent with that inventor-first default, though it is not an ownership-doctrine holding. In *San Manuel Copper Corp. v. Redmond*, a converter shift foreman had devised a smelting process before joining the company, disclosed it to management expecting compensation, and watched the company adopt it plant-wide without ever paying him. There was no written invention agreement, and the Court of Appeals sustained his unjust-enrichment claim, remanding for damages measured as a reasonable royalty [^san-manuel-unjust-enrichment]. "We do not believe it is necessary to show fraud in order to recover for unjust enrichment in the prepatent use of an invention or idea."[^san-manuel-unjust-enrichment] In reaching that result the court invoked the common-law premise of inventor ownership, quoting 69 C.J.S. Patents § 2 [^san-manuel-inventor-right]. "An inventor has a natural right, recognized by the common law, separate from, and independent of, any constitutional or statutory provision, or any patent grant, to make, use, and sell his invention or discovery."[^san-manuel-inventor-right] Read for what it holds, *San Manuel* treats the employee as the owner of the idea and makes the employer pay for uncompensated use — color consistent with the federal default, not an independent Arizona ownership rule. Our review found no published Arizona appellate decision applying the shop-right doctrine or the hired-to-invent doctrine, so those doctrines enter Arizona practice through the shared federal baseline [^stanford-inventor][^dubilier-hired-to-invent]. Because ownership therefore starts with the inventor and Arizona has no statute filling the gap, the dependable path for an employer is a written present-assignment (*hereby assigns*) clause that transfers legal title automatically on conception, rather than a future promise to assign that leaves the employer with a mere equitable claim. ## Are trailing-assignment (holdover) clauses enforceable in Arizona? {#holdover-clause-limit} **Short answer.** Unsettled. No Arizona decision found in our review squarely decides whether a trailing clause reaching inventions first conceived after employment ends is enforceable, and there is no statutory temporal cap because there is no invention-assignment statute at all. What Arizona does supply is a well-developed restrictive-covenant reasonableness framework, so a court would most likely test an aggressive holdover clause as a restraint under that framework — but applying it to invention holdovers is a prediction, not a holding [^farber-reasonableness]. Two gaps define the Arizona picture. First, there is no statute: nothing caps the duration of a post-employment trailing assignment or otherwise limits what such a clause may reach. Second, our review found no Arizona decision applying the restraint framework — or any other framework — specifically to an invention-holdover clause, so even the threshold question of whether such a clause counts as a restraint of trade is open. What Arizona does supply is a crisp general standard. In *Valley Medical Specialists v. Farber*, the Arizona Supreme Court stated the test for when a restriction on a departing employee will not be enforced [^farber-reasonableness]. "A restriction is unreasonable and thus will not be enforced: (1) if the restraint is greater than necessary to protect the employer’s legitimate interest; or (2) if that interest is outweighed by the hardship to the employee and the likely injury to the public."[^farber-reasonableness] *Farber* itself was a physician non-compete case, and its outcome rests partly on public-policy concerns specific to the doctor-patient relationship — the transferable piece is the general reasonableness test, not the extra strictness Arizona applies to physician covenants [^farber-reasonableness]. Extending that test to a holdover assignment is analogical: a court asked to enforce a clause sweeping in inventions an ex-employee conceives after leaving would most likely ask whether the restriction is greater than necessary to protect the employer's legitimate interests, but no Arizona court has yet framed the question that way for an invention clause. If the framework does apply, Arizona raises the drafting stakes with its no-rewrite rule. Arizona courts will blue-pencil a covenant — ignore grammatically severable, unreasonable portions — but they will not redraft it [^farber-no-rewrite]. "Although we will tolerate ignoring severable portions of a covenant to make it more reasonable, we will not permit courts to add terms or rewrite provisions."[^farber-no-rewrite] The consequence, if a court treats a holdover clause as a restraint, is that an overbroad trailing assignment likely dies rather than gets trimmed: unless the offending reach can be severed grammatically, the court will not narrow the clause to save it. That makes Arizona harsher on sloppy holdover drafting than reformation states, even though no invention case has yet applied the rule. Enforcement timing is a separate, distinctly Arizona trap. A.R.S. § 12-541(3) imposes a one-year limitations period on actions for breach of an employment contract [^az-12-541-one-year][^az-12-541-employment-contracts]. "For breach of an oral or written employment contract including contract actions based on employee handbooks or policy manuals that do not specify a time period in which to bring an action."[^az-12-541-employment-contracts] An action to enforce an invention-assignment clause that sounds in breach of an employment contract therefore likely faces a one-year clock, far shorter than the period that governs ordinary written contracts — though our review found no Arizona case applying § 12-541(3) to an invention-assignment dispute, so whether every assignment theory (a declaratory title claim, for example, or specific performance to compel execution of assignment documents) falls within the subdivision is itself uncharacterized [^az-12-541-one-year]. > [!NOTE] > **Practice note.** > > Do not carry a statute-state playbook into Arizona. The section sometimes cited as an Arizona own-time carve-out is the trade-secret damages provision, the carve-out bill died in 2013, and there is no notice safe harbor — the validity of an assignment turns entirely on the contract language and the general limits on restraints [^az-23-204-current-text-practice]. Draft with present-assignment (*hereby assigns*) language so title passes automatically rather than resting on a future promise, because ownership starts with the inventor and an employer's rights are only as good as the words that transfer them [^stanford-traceback-practice]. Keep any trailing or holdover assignment narrow, short, and tied to the employer's confidential information: if an Arizona court treats it as a restraint, an overbroad clause is more likely to fall than to be fixed, because Arizona courts will sever grammatically severable provisions but will not add terms or rewrite them [^farber-no-rewrite]. And calendar enforcement early — a claim sounding in breach of an employment contract likely faces Arizona's one-year limitations period [^az-12-541-one-year]. [^about]: By Steven Obiajulu, J.D. Published by [openagreements.org](https://openagreements.org). Last reviewed 2026-07-03. License: CC BY 4.0. Steven Obiajulu, J.D. is admitted in New York, not Arizona. This article synthesizes Arizona primary law and is not legal advice from a Arizona-admitted attorney. This article is for informational purposes only and does not create an attorney-client relationship. CC BY 4.0. Cite as Steven Obiajulu, *Employee Invention Assignment in Arizona*, OpenAgreements (last updated July 3, 2026), https://openagreements.org/practice-guides/invention-assignment/us/arizona. [^az-44-403-damages]: **Ariz. Rev. Stat. § 44-403** — "If willful and malicious misappropriation exists, the court may award exemplary damages in an amount not exceeding twice any award made under subsection A." *Ariz. Rev. Stat. § 44-403 (Arizona Uniform Trade Secrets Act).* [^stanford-baseline]: **Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Systems** — "Since 1790, the patent law has operated on the premise that rights in an invention belong to the inventor." *Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Sys., Inc., 563 U.S. 776 (2011).* [^az-23-204-current-text]: **Ariz. Rev. Stat. § 23-204** — "Employee benefits; state preemption; exemption; definition" *Ariz. Rev. Stat. § 23-204.* [^az-23-204-no-notice]: **Ariz. Rev. Stat. § 23-204** — "Employee benefits; state preemption; exemption; definition" *Ariz. Rev. Stat. § 23-204.* [^stanford-inventor]: **Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Systems** — "Since 1790, the patent law has operated on the premise that rights in an invention belong to the inventor." *Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Sys., Inc., 563 U.S. 776 (2011).* [^dubilier-hired-to-invent]: **United States v. Dubilier Condenser Corp.** — "One employed to make an invention, who succeeds, during his term of service, in accomplishing that task, is bound to assign to his employer any patent obtained." *United States v. Dubilier Condenser Corp., 289 U.S. 178 (1933).* [^stanford-traceback]: **Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Systems** — "Thus, although others may acquire an interest in an invention, any such interest — as a general rule — must trace back to the inventor." *Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Sys., Inc., 563 U.S. 776 (2011).* [^san-manuel-unjust-enrichment]: **San Manuel Copper Corporation v. Redmond** — "We do not believe it is necessary to show fraud in order to recover for unjust enrichment in the prepatent use of an invention or idea." *San Manuel Copper Corp. v. Redmond, 8 Ariz. App. 214, 445 P.2d 162 (Ct. App. 1968).* [^san-manuel-inventor-right]: **San Manuel Copper Corporation v. Redmond** — "An inventor has a natural right, recognized by the common law, separate from, and independent of, any constitutional or statutory provision, or any patent grant, to make, use, and sell his invention or discovery." *San Manuel Copper Corp. v. Redmond, 8 Ariz. App. 214, 445 P.2d 162 (Ct. App. 1968) (quoting 69 C.J.S. Patents § 2).* [^farber-reasonableness]: **Valley Medical Specialists v. Farber** — "A restriction is unreasonable and thus will not be enforced: (1) if the restraint is greater than necessary to protect the employer’s legitimate interest; or (2) if that interest is outweighed by the hardship to the employee and the likely injury to the public." *Valley Medical Specialists v. Farber, 194 Ariz. 363, 982 P.2d 1277 (1999).* [^farber-no-rewrite]: **Valley Medical Specialists v. Farber** — "Although we will tolerate ignoring severable portions of a covenant to make it more reasonable, we will not permit courts to add terms or rewrite provisions." *Valley Medical Specialists v. Farber, 194 Ariz. 363, 982 P.2d 1277 (1999).* [^az-12-541-one-year]: **Ariz. Rev. Stat. § 12-541** — "There shall be commenced and prosecuted within one year after the cause of action accrues, and not afterward, the following actions:" *Ariz. Rev. Stat. § 12-541.* [^az-12-541-employment-contracts]: **Ariz. Rev. Stat. § 12-541(3)** — "For breach of an oral or written employment contract including contract actions based on employee handbooks or policy manuals that do not specify a time period in which to bring an action." *Ariz. Rev. Stat. § 12-541(3).* [^az-23-204-current-text-practice]: **Ariz. Rev. Stat. § 23-204** — "Employee benefits; state preemption; exemption; definition" *Ariz. Rev. Stat. § 23-204.* [^stanford-traceback-practice]: **Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Systems** — "Thus, although others may acquire an interest in an invention, any such interest — as a general rule — must trace back to the inventor." *Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Sys., Inc., 563 U.S. 776 (2011).*