Employee Invention Assignment in Utah

Can a Utah employer require assignment of every invention?

Section 34-39-3(1) states the carve-out as a limit on enforceability, and it is written conjunctively: both conditions must hold before a clause becomes unenforceable A.1.

“An employment agreement between an employee and employer is not enforceable against the employee to the extent that the agreement requires the employee to assign or license, or to offer to assign or license, to the employer any right or intellectual property in or to an invention that is: (a) created by the employee entirely on the employee's own time; and (b) not an employment invention.”

Note the breadth of the operative verb. Unlike a statute that speaks only of assignment, section 34-39-3(1) reaches an agreement that requires the employee to assign or license — so a Utah drafter cannot escape the carve-out by demanding a license instead of an outright transfer of a protected own-time invention.

The narrowness lives in condition (b). Everything turns on whether the invention is an employment invention, and section 34-39-2(1) defines that term disjunctively — the list is joined by or, so satisfying any single prong makes the invention assignable A.2.

“the result of any work, services, or duties performed by an employee for the employer; (c) related to the industry or trade of the employer; or (d) related to the current or demonstrably anticipated business, research, or development of the employer”

This is the point a California-trained drafter will miss. California Labor Code section 2870 protects an own-time, own-resource invention unless it relates to the employer's business or actual or demonstrably anticipated research, or results from the employee's work. Utah adds a further disjunct — prong (c), related to the industry or trade of the employer — that has no California analogue and no requirement of any connection to the employer's own business. An engineer at a Utah medical-device company who builds an unrelated-to-the-company but still medical-device gadget on a weekend, using nothing of the employer's, may find that invention is nonetheless an employment invention because it is related to the industry or trade of the employer. Utah's carve-out is real, but its protected zone is a sliver of California's.

Must a Utah employer notify the employee?

The Act's own machinery confirms the absence of a notice step. Rather than conditioning a clause on written disclosure, section 34-39-3 draws the line at what an employer may demand: it may require an employee to sign a compliant assignment agreement as a condition of employment, but it may not require the employee to agree to anything the Act renders unenforceable B.1.

“An employer may require employees to agree to an agreement within the scope of Subsection (2) as a condition of employment or the continuation of employment. (7) An employer may not require employees to agree to anything unenforceable under Subsection (1) as a condition of employment or the continuation of employment.”

That structure matters for a multistate employer. A form built around the California section 2872 or Washington RCW 49.44.140(3) notice will carry disclosure language that Utah simply does not demand — harmless surplusage, but a signal that the drafter has not thought about Utah's much narrower carve-out. The reverse point is the important one: because the Act gives the employer no notice-based safe harbor, an employer cannot cure an overbroad clause by disclosing the carve-out. Compliance in Utah is achieved by writing the assignment scope to the Act's boundaries, not by papering the employee with a notice.

Who owns an invention by default in Utah?

Stanford v. Roche anchors the default. The Court held that even the Bayh-Dole Act did not displace the long-standing premise that an invention belongs to its inventor, treating that rule as the baseline against which any assignment is measured C.1.

“Since 1790, the patent law has operated on the premise that rights in an invention belong to the 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, and any third-party interest must trace back to that inventor-grantor C.3.

“Thus, although others may acquire an interest in an invention, any such interest — as a general rule — must trace back to the inventor.”

The classic exception, recognized in United States v. Dubilier Condenser Corp., is the employee hired to invent. Where the employee's very task was to produce the invention, the resulting patent belongs to the employer as a matter of the employment bargain C.2.

“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.”

But the hired-to-invent doctrine is fact-intensive and narrow, and it is no substitute for a written clause. The dependable path for a Utah employer is a written present-assignment (hereby assigns) clause — present-tense language that transfers legal title automatically on conception, rather than a mere promise to assign later — operating within the boundaries the Employment Inventions Act imposes.

Are trailing-assignment (holdover) clauses enforceable in Utah?

Start with what the Act does not do. Sections 34-39-2 and 34-39-3 define which inventions an assignment or license clause may reach, but they say nothing about how long after employment a trailing clause may operate, and nothing about inventions conceived only after the relationship ends. Utah has no statutory durational cap comparable to a fixed post-employment ceiling.

Because no Utah case has ruled directly on invention holdover clauses, the most reliable prediction is that a Utah court would borrow its restrictive-covenant reasonableness analysis. Robbins v. Finlay states that framework: a post-employment restraint is enforceable only if carefully drawn to protect the employer's legitimate interests, judged against factors of scope, duration, and the interest protected D.1.

“Covenants not to compete are enforceable if carefully drawn to protect only the legitimate interests of the employer. The reasonableness of a covenant depends upon several factors, including its geographical extent; the duration of the limitation; the nature of the employee’s duties; and the nature of the interest which the employer seeks to protect such as trade secrets, the goodwill of his business, or an extraordinary investment in the training or education of the employee.”

System Concepts, Inc. v. Dixon confirms that this reasonableness inquiry is fact-bound rather than mechanical, which is why an overbroad trailing clause carries real risk D.2.

“The reasonableness of the restraints in a restrictive covenant is determined on a case-by-case basis, taking into account the particular facts and circumstances surrounding the case and the subject covenant.”

Two further wrinkles bear on the prediction. First, a holdover clause that sweeps in an ex-employee's genuinely independent post-employment inventions begins to look like a disguised covenant not to compete, which is exactly what the Robbins factors are built to police. Second, Utah's Post-Employment Restrictions Act (Utah Code chapter 34-51) caps noncompetition agreements at one year, and how far that cap reaches a trailing invention-assignment clause is unsettled in our review — so a Utah drafter should treat an aggressive holdover tail as exposed on both the common-law reasonableness front and the statutory-noncompete front, without overclaiming that either doctrine has resolved the question. The safe course is a holdover clause narrowly tied to inventions conceived during employment or derived from the employer's confidential information, over a short and defined trailing window.