On this pageCan the employer require assignment of every invention?
State Law Practice Guide

Employee Invention Assignment in Virginia

Virginia has no employee-invention-assignment statute — no California-style own-time carve-out and no notice requirement — so an assignment clause is bounded by ordinary contract law, the common-law inventor-owns default, and the federal patent and copyright overlay. Absent a written assignment the inventor owns unless hired to invent — the leading authorities are Virginia-forum federal decisions (Avtec, Houghton) rather than state holdings — and a post-employment holdover clause would most likely be tested under Virginia's covenant-reasonableness framework, now layered with Va. Code § 40.1-28.7:8's prohibition regime for covered employees, though no Virginia decision found in our review has addressed a holdover invention assignment.

More details about this document
Editor
, OpenAgreements editor
License
CC BY 4.0
Authorities relied on

Can a Virginia employer require assignment of every invention?

There is no statutory ceiling. Unlike California or New York, Virginia has no employee-invention-assignment statute — nothing that voids an assignment of a true own-time, own-resource invention — so an assignment clause's reach is bounded by ordinary contract law, the common-law inventor-owns default, and the federal patent and copyright overlay. The one Virginia-specific outer limit is restraint-of-trade law — where an assignment clause operates as a post-employment restraint, Va. Code § 40.1-28.7:8 prohibits covenants not to compete outright for a large covered class of employees.

Because there is no statute on point, the limits come from general principles rather than a legislative carve-out. A full-text sweep of all 76 titles of the Code of Virginia, run against the official bulk data published by the Virginia Law Library, surfaces no private-employee invention provision anywhere: the word invention appears only in a 1977 consumer-protection chapter regulating commercial invention-development services (Va. Code §§ 59.1-208 through 59.1-215), which polices paid invention promoters rather than employers, and in one unrelated tax provision. Title 40.1, Virginia's labor and employment title, contains no invention, patent, or intellectual-property-assignment language at all. There is no California Labor Code § 2870 analogue and no New York Labor Law § 203-f analogue.

The nearest thing Virginia has to an employment-invention statute is public-sector only. Va. Code § 2.2-2822 gives the Commonwealth ownership of inventions developed by state employees on state time or with state resources — a rule that by its terms does not reach private employment .

Patents, copyrights or materials that were potentially patentable or copyrightable developed by a state employee during working hours or within the scope of his employment or when using state-owned or state-controlled facilities shall be the property of the Commonwealth.

The substantive default that 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 .

Since 1790, the patent law has operated on the premise that rights in an invention belong to the inventor.

The practical consequence is that a Virginia 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 contract-law defenses, and where it restrains what a person may do after employment ends, it runs into Virginia's statutory treatment of covenants not to compete — a regime analyzed in the trailing-clause question below .

No employer shall enter into, enforce, or threaten to enforce a covenant not to compete with any low-wage employee or health care professional.

Sources for this answer

Primary law

A.3 Va. Code § 2.2-2822

Va. Code § 2.2-2822 makes inventions developed by a state employee on state time, within the scope of employment, or with state facilities the property of the Commonwealth — a public-sector ownership rule that is the closest thing Virginia has to an employment-invention statute and that does not reach private employees.

Patents, copyrights or materials that were potentially patentable or copyrightable developed by a state employee during working hours or within the scope of his employment or when using state-owned or state-controlled facilities shall be the property of the Commonwealth.

See Va. Code § 2.2-2822(A).

Case law · 2011-06-06

A.2 Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Systems

Stanford v. Roche confirms the long-standing premise of U.S. patent law that rights in an invention belong to the inventor, the baseline against which any assignment clause is measured.

Since 1790, the patent law has operated on the premise that rights in an invention belong to the inventor.

See Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Sys., Inc., 563 U.S. 776 (2011).

Primary law

A.1 Va. Code § 40.1-28.7:8

Va. Code § 40.1-28.7:8(B) prohibits employers from entering into, enforcing, or threatening to enforce a covenant not to compete with any low-wage employee or health care professional — the general restraint-of-trade bound an aggressive assignment clause would face in Virginia if it operates as a post-employment restraint.

No employer shall enter into, enforce, or threaten to enforce a covenant not to compete with any low-wage employee or health care professional.

See Va. Code § 40.1-28.7:8(B).

Must a Virginia employer notify the employee?

Not applicable. Because Virginia 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 one nearby posting duty — Va. Code § 40.1-28.7:8(G) — is a generic workplace poster about the noncompete statute itself, not an invention-assignment notice, and it does not condition the validity of any assignment clause .

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; Virginia 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 Virginia does not have.

One nearby statutory duty is worth distinguishing so it is not mistaken for an invention notice. Va. Code § 40.1-28.7:8(G) requires every employer to post a copy of that section — Virginia's covenant-not-to-compete statute — or an approved summary alongside the other workplace notices required by state and federal law, with graduated penalties for noncompliance that run from a written warning to civil penalties of up to $250 and then up to $1,000 for subsequent violations .

Every employer shall post a copy of this section or a summary approved by the Department in the same location where other employee notices required by state or federal law are posted.

That posting duty attaches to every employer regardless of what any contract says. It is not triggered by an invention-assignment clause, it says nothing about inventions, and complying with it neither validates nor cures any assignment provision. For a multistate employer the takeaway is the inverse of the notice states: a Virginia employer neither has to give a § 2872-style invention notice nor can rely on one to cure an overbroad clause — the enforceability of the assignment turns on the contract language and the general limits on restraints.

Sources for this answer

Primary law

B.1 Va. Code § 40.1-28.7:8

Va. Code § 40.1-28.7:8(G) imposes a generic workplace-posting duty — every employer must post a copy of the covenant-not-to-compete statute or an approved summary with other required employee notices — which is not an invention-assignment notice, is not triggered by any contract clause, and does not condition the validity of an assignment provision.

Every employer shall post a copy of this section or a summary approved by the Department in the same location where other employee notices required by state or federal law are posted.

See Va. Code § 40.1-28.7:8(G).

Who owns an invention by default in Virginia?

The inventor, unless hired to invent. Absent a written assignment, the baseline under federal patent law is that rights in an invention belong to the employee who conceived it; the narrow exception is the employee hired to invent, whose resulting invention the employer may claim. No decision of Virginia's state appellate courts on private employee-invention ownership was found in our review — the operative authorities are the federal baseline and the federal courts sitting in Virginia that apply it.

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 .

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. Any third-party interest must trace back to that inventor-grantor .

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

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 .

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.

The Fourth Circuit — whose decisions bind the federal courts sitting in Virginia — stated the hired-to-invent rule early and in strong form in Houghton v. United States. One caveat on provenance: Houghton came up from the District of Maryland, so it is circuit-level doctrine that Virginia's federal courts apply, not a holding of Virginia law .

During the period that he is so engaged, he is ‘employed to invent,’ and the results of his efforts at invention belong to his employer in the same way as would the product of his efforts in any other direction.

The real-world Virginia-forum fight is Avtec Systems, Inc. v. Peiffer, the canonical Virginia-sited dispute over an employee's off-hours creation — satellite-orbit software the employee developed at home, on his own equipment. Avtec is a copyright and trade-secret case rather than a patent case, so its ownership analysis runs through the work-made-for-hire doctrine, and the Fourth Circuit made the employer's claim turn on the Restatement (Second) of Agency § 228 scope-of-employment test .

conduct is within the scope of employment ‘only if: (a) it is of the kind he is employed to perform; (b) it occurs substantially within the authorized time and space limits; [and] (c) it is actuated, at least in part, by a purpose to serve the master.’

Short of ownership, an employer whose time, tools, and materials contributed to the invention holds only a shop right. In the Avtec litigation the Eastern District of Virginia stated the doctrine by adopting the Ninth Circuit's definition from California Eastern Laboratories, Inc. v. Gould — a nonexclusive right to use, not title .

A shop right is an employer’s nonexclusive right to use an employee’s patented process or invention that was developed during the employee’s hours of employment. The right is based on the employer’s presumed contribution to the invention through materials, time, and equipment.

Because ownership therefore starts with the inventor, Virginia has no statute filling the gap, and the scope-of-employment fight in Avtec shows how weak an employer's implied claim is for off-hours, own-equipment work, the dependable path for an employer is a written present-assignment (hereby assigns) clause with a defined scope of covered inventions — one that transfers legal title automatically on conception rather than resting on a future promise, an after-the-fact hired-to-invent argument about what the employee's duties actually were, or a shop right that licenses use but passes no title.

Sources for this answer

Case law · 2011-06-06

C.1 Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Systems

Stanford v. Roche confirms the long-standing premise of U.S. patent law that rights in an invention belong to the inventor.

Since 1790, the patent law has operated on the premise that rights in an invention belong to the inventor.

See Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Sys., Inc., 563 U.S. 776 (2011).

Case law · 2011-06-06

C.3 Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Systems

Stanford v. Roche holds that although others may acquire an interest in an invention, that interest as a general rule must trace back to the inventor — so an employer takes title only through an assignment from the employee-inventor.

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

See Bd. of Trustees of the Leland Stanford Junior Univ. v. Roche Molecular Sys., Inc., 563 U.S. 776 (2011).

Case law · 1933-05-08

C.2 United States v. Dubilier Condenser Corp.

United States v. Dubilier Condenser Corp. holds that an employee hired to make an invention who succeeds during the term of service is bound to assign the resulting patent to the employer.

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.

See United States v. Dubilier Condenser Corp., 289 U.S. 178 (1933).

Case law · 1928-01-10

C.4 Houghton v. United States

Houghton v. United States — a Fourth Circuit decision on appeal from the District of Maryland, so binding circuit doctrine applied by Virginia's federal courts rather than a holding of Virginia law — holds that while an employee is engaged on work directed at making an invention, he is employed to invent, and the results of his efforts at invention belong to the employer.

During the period that he is so engaged, he is “employed to invent,” and the results of his efforts at invention belong to his employer in the same way as would the product of his efforts in any other direction.

See Houghton v. United States, 23 F.2d 386 (4th Cir. 1928).

Case law · 1994-04-06

C.5 Avtec Systems, Inc. v. Peiffer

Avtec Systems, Inc. v. Peiffer — the leading Virginia-forum fight over an employee's off-hours software creation — makes the employer's work-made-for-hire claim turn on the Restatement (Second) of Agency § 228 scope-of-employment test, which the Fourth Circuit quotes as the governing standard.

conduct is within the scope of employment "only if: (a) it is of the kind he is employed to perform; (b) it occurs substantially within the authorized time and space limits; [and] (c) it is actuated, at least in part, by a purpose to serve the master."

See Avtec Sys., Inc. v. Peiffer, 21 F.3d 568 (4th Cir. 1994) (quoting Restatement (Second) of Agency § 228 (1958)).

Case law · 1992-11-04

C.6 Avtec Systems, Inc. v. Peiffer (E.D. Va.)

Avtec Systems, Inc. v. Peiffer (E.D. Va.), quoting the Ninth Circuit's definition in California Eastern Laboratories, Inc. v. Gould, states the shop-right doctrine as applied in a Virginia forum — a nonexclusive right to use an employee's invention developed on the employer's time, based on the employer's presumed contribution of materials, time, and equipment, not ownership of it.

A shop right is an employer’s nonexclusive right to use an employee’s patented process or invention that was developed during the employee’s hours of employment. The right is based on the employer’s presumed contribution to the invention through materials, time, and equipment.

See Avtec Sys., Inc. v. Peiffer, 805 F. Supp. 1312 (E.D. Va. 1992) (quoting Cal. E. Labs., Inc. v. Gould, 896 F.2d 400, 402 (9th Cir. 1990)).

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

Most likely tested for reasonableness, but the invention-specific application is undecided — and for a large statutorily covered class the risk is outright prohibition, not a trim. No Virginia decision found in our review has addressed a post-employment holdover invention-assignment clause. What Virginia has is a mature reasonableness framework for provisions that restrain post-employment competition — narrowly drawn, not unduly burdensome, not against public policy — plus Va. Code § 40.1-28.7:8, whose functional definition of a covenant not to compete could plausibly reach an aggressive trailing clause; if it does, the consequence for covered employees is statutory prohibition backed by a civil penalty, not reasonableness balancing.

Two layers define the Virginia picture: a well-settled common-law reasonableness rule for restraints on competition, and a fast-moving statute that prohibits covenants not to compete outright for a large covered class. Neither layer has been applied to a trailing invention-assignment clause by any Virginia decision found in our review.

The common-law framework comes from the Supreme Court of Virginia. Home Paramount Pest Control Cos. v. Shaffer, restating the test announced in Omniplex World Services Corp. v. US Investigations Services, Inc., gives the operative three-part standard .

It is enforceable if it ‘is narrowly drawn to protect the employer’s legitimate business interest, is not unduly burdensome on the employee’s ability to earn a living, and is not against public policy.’

The analysis is substance-over-label: the court weighs what the provision actually does, quoting Simmons v. Miller for the elements it considers .

When evaluating whether the employer has met that burden, we consider the ‘function, geographic scope, and duration’ elements of the restriction.

The employer carries the load throughout. Omniplex frames restrictive covenants as disfavored restraints, with the burden of proof on the employer and ambiguities construed against it .

Because such restrictive covenants are disfavored restraints on trade, the employer bears the burden of proof and any ambiguities in the contract will be construed in favor of the employee.

And the scrutiny has tightened over time: Home Paramount struck a functionally overbroad clause identical to one the same court had upheld in 1989, expressly overruling its earlier decision .

Therefore, to the extent that Paramount Termite conflicts with any portion of our holding today, Paramount Termite is overruled.

The statutory layer is Va. Code § 40.1-28.7:8, enacted in 2020 (cc. 948, 949, originally codified as § 40.1-28.7:7) and substantially expanded in 2025 (c. 585) and 2026 (cc. 883, 1113, 1114). Its definition of a covenant not to compete is functional rather than label-bound — it reaches any agreement that restrains, prohibits, or otherwise restricts post-termination competition .

‘Covenant not to compete’ means a covenant or agreement, including a provision of a contract of employment, between an employer and employee that restrains, prohibits, or otherwise restricts an individual's ability, following the termination of the individual's employment, to compete with his former employer.

For covered employees the statute is a prohibition, not a reasonableness test: an employer may not enter into, enforce, or even threaten to enforce a covered covenant, and subsection E backs the ban with a civil penalty of $10,000 per violation .

No employer shall enter into, enforce, or threaten to enforce a covenant not to compete with any low-wage employee or health care professional.

The covered class is large and got much larger in 2025. Low-wage employee originally meant a worker earning below the Commonwealth's average weekly wage; the 2025 amendment (c. 585) extended it to every employee entitled to overtime under the federal Fair Labor Standards Act — that is, all FLSA non-exempt employees regardless of what they earn — along with interns, students, apprentices, trainees, and certain lower-paid independent contractors, with an exclusion for workers whose earnings are predominantly commission-based .

who, regardless of his average weekly earnings, is entitled to overtime compensation under the provisions of 29 U.S.C. § 207

The 2026 amendments (cc. 883, 1113, 1114) added a separate rule that applies to all employees, not just the low-wage class: a covenant not to compete is unenforceable against an employee discharged without cause unless the employer provides severance or another monetary payment, and that severance must have been disclosed when the covenant was signed .

No covenant not to compete between an employer and an employee is enforceable if such employer discharges such employee from employment without providing severance benefits or other monetary payment to such employee, unless such employer discharges such employee for cause. Such severance benefits or other monetary payment shall be disclosed upon execution of the covenant not to compete.

The statute does carve out a safe harbor — but for nondisclosure agreements, not assignments. Subsection H.1 preserves NDAs protecting trade secrets, as defined in Virginia's Uniform Trade Secrets Act at Va. Code § 59.1-336, and proprietary or confidential information; it says nothing about invention-assignment clauses .

Nondisclosure agreements intended to prohibit the taking, misappropriating, threatening to misappropriate, or sharing of certain information to which an employee has access, including trade secrets, as defined in § 59.1-336, and proprietary or confidential information

Whether a trailing invention-assignment clause is a covenant not to compete under that functional definition is an open statutory question — no Virginia court has decided it, and no decision found in our review has even confronted it. A trailing clause does not forbid taking a job in terms; it transfers ownership of post-termination inventions. But an aggressive one — sweeping in all inventions for a fixed period after departure regardless of any connection to the employer's business — arguably otherwise restricts the former employee's ability to compete, since the ex-employee cannot exploit new inventions and becomes a riskier hire for competitors. The omission of assignment clauses from the H.1 safe harbor, which conspicuously protects trade-secret NDAs, cuts both ways in that argument. The stakes of the characterization are high: for the covered class — all FLSA non-exempt employees, sub-average-wage workers, health care professionals, and any employee discharged without cause where disclosed-at-execution severance is missing — a covered clause is prohibited and void, with a $10,000 civil penalty per violation, rather than trimmed to a reasonable scope.

Remedially, Virginia is unforgiving of overbreadth. In Roto-Die Co. v. Lesser, a federal court predicting Virginia law declined to adopt the blue-pencil rule — a court will not rewrite or trim an overbroad restraint to save it — while at the same time severing genuinely independent covenant subparts and enforcing the valid ones .

While I believe paragraphs 7(a) and 7(b) are severable from paragraphs 7(c) and 7(d), I decline to adopt the so-called ‘blue pencil’ rule.

Roto-Die is a federal prediction — no square holding of the Supreme Court of Virginia adopting or rejecting blue-penciling was found in our review — but its two-sided rule matters for drafting: an overbroad holdover clause likely falls in its entirety, yet a structurally independent present-assignment clause bundled in the same agreement may survive through severance. And however the challenge arrives, it will be fact-bound: in Assurance Data, Inc. v. Malyevac the Supreme Court of Virginia held that the enforceability of a restraint on competition cannot be resolved on a demurrer, so an employer must be prepared to prove reasonableness with evidence .

Because a demurrer cannot be used to decide on the merits whether a restraint on competition is enforceable, we will reverse the circuit court's judgment.

Applying any of this to holdover assignments is a prediction, not a holding. The uncertainty comes from missing case law rather than ambiguous doctrine: Virginia's reasonableness framework and the statute are both well documented, but neither has been applied to a trailing invention-assignment clause by any decision found in our review. The safe reading is that an overbroad trailing clause is at meaningful risk in Virginia twice over — as an unreasonable restraint under the Omniplex/Home Paramount framework, and, if characterized as a covenant not to compete, as a statutorily prohibited one for the large covered class — while a narrow holdover tied to the employer's trade secrets and confidential information, with a short tail and a genuine business nexus, remains the defensible zone.

Sources for this answer

Case law · 2011-11-04

D.1 Home Paramount Pest Control Cos. v. Shaffer

Home Paramount Pest Control Cos. v. Shaffer, restating the test from Omniplex World Services Corp. v. US Investigations Services, Inc., gives Virginia's operative three-part standard for restraints on competition — narrowly drawn to protect a legitimate business interest, not unduly burdensome on the ability to earn a living, and not against public policy — the framework a holdover assignment clause would most likely be measured against.

It is enforceable if it “is narrowly drawn to protect the employer’s legitimate business interest, is not unduly burdensome on the employee’s ability to earn a living, and is not against public policy.”

See Home Paramount Pest Control Cos. v. Shaffer, 282 Va. 412, 718 S.E.2d 762 (2011) (quoting Omniplex World Servs. Corp. v. US Investigations Servs., Inc., 270 Va. 246, 618 S.E.2d 340 (2005)).

Case law · 2011-11-04

D.3 Home Paramount Pest Control Cos. v. Shaffer

Home Paramount Pest Control Cos. v. Shaffer, quoting Simmons v. Miller, holds that Virginia courts evaluate a restraint by weighing its function, geographic scope, and duration — a substance-over-label inquiry into what the provision actually restricts.

When evaluating whether the employer has met that burden, we consider the “function, geographic scope, and duration” elements of the restriction.

See Home Paramount Pest Control Cos. v. Shaffer, 282 Va. 412, 718 S.E.2d 762 (2011) (quoting Simmons v. Miller, 261 Va. 561, 544 S.E.2d 666 (2001)).

Case law · 2005-09-16

D.4 Omniplex World Services Corp. v. US Investigations Services, Inc.

Omniplex World Services Corp. v. US Investigations Services, Inc. holds that restrictive covenants are disfavored restraints on trade in Virginia, that the employer bears the burden of proof, and that contractual ambiguities are construed in favor of the employee.

Because such restrictive covenants are disfavored restraints on trade, the employer bears the burden of proof and any ambiguities in the contract will be construed in favor of the employee.

See Omniplex World Servs. Corp. v. US Investigations Servs., Inc., 270 Va. 246, 618 S.E.2d 340 (2005).

Case law · 2011-11-04

D.5 Home Paramount Pest Control Cos. v. Shaffer

Home Paramount Pest Control Cos. v. Shaffer struck a functionally overbroad restraint identical to one the Supreme Court of Virginia had upheld in 1989 and overruled that earlier decision — the clearest marker that Virginia's scrutiny of restraints on competition has tightened over time.

Therefore, to the extent that Paramount Termite conflicts with any portion of our holding today, Paramount Termite is overruled.

See Home Paramount Pest Control Cos. v. Shaffer, 282 Va. 412, 718 S.E.2d 762 (2011).

Primary law

D.2 Va. Code § 40.1-28.7:8

Va. Code § 40.1-28.7:8(A) defines a covenant not to compete functionally — any agreement that restrains, prohibits, or otherwise restricts post-termination competition — a label-blind definition that could plausibly reach an aggressive trailing invention-assignment clause, though no Virginia court has decided that question.

"Covenant not to compete" means a covenant or agreement, including a provision of a contract of employment, between an employer and employee that restrains, prohibits, or otherwise restricts an individual's ability, following the termination of the individual's employment, to compete with his former employer.

See Va. Code § 40.1-28.7:8(A).

Primary law

D.6 Va. Code § 40.1-28.7:8

Va. Code § 40.1-28.7:8(B) prohibits entering into, enforcing, or threatening to enforce a covenant not to compete with any low-wage employee or health care professional, and subsection E backs violations of the prohibition with a civil penalty of $10,000 per violation — a voidness-plus-penalty regime, not a reasonableness test.

No employer shall enter into, enforce, or threaten to enforce a covenant not to compete with any low-wage employee or health care professional.

See Va. Code § 40.1-28.7:8(B), (E).

Primary law

D.7 Va. Code § 40.1-28.7:8

Va. Code § 40.1-28.7:8(A), as amended in 2025 by c. 585, extends the definition of low-wage employee to any employee entitled to overtime compensation under 29 U.S.C. § 207 regardless of earnings — bringing all FLSA non-exempt employees into the covered class.

who, regardless of his average weekly earnings, is entitled to overtime compensation under the provisions of 29 U.S.C. § 207

See Va. Code § 40.1-28.7:8(A) (as amended by 2025 Va. Acts c. 585).

Primary law

D.8 Va. Code § 40.1-28.7:8

Va. Code § 40.1-28.7:8(C), added by the 2026 amendments (cc. 883, 1113, 1114), makes a covenant not to compete unenforceable against any employee discharged without cause unless severance or another monetary payment is provided, and requires that severance to have been disclosed when the covenant was executed.

No covenant not to compete between an employer and an employee is enforceable if such employer discharges such employee from employment without providing severance benefits or other monetary payment to such employee, unless such employer discharges such employee for cause. Such severance benefits or other monetary payment shall be disclosed upon execution of the covenant not to compete.

See Va. Code § 40.1-28.7:8(C) (as amended by 2026 Va. Acts cc. 883, 1113, 1114).

Primary law

D.9 Va. Code § 40.1-28.7:8

Va. Code § 40.1-28.7:8(H)(1) safe-harbors nondisclosure agreements protecting trade secrets, as defined in Va. Code § 59.1-336, and proprietary or confidential information — but says nothing about invention-assignment clauses, an omission relevant to whether a trailing assignment could be characterized as a covered covenant not to compete.

Nondisclosure agreements intended to prohibit the taking, misappropriating, threatening to misappropriate, or sharing of certain information to which an employee has access, including trade secrets, as defined in § 59.1-336, and proprietary or confidential information

See Va. Code § 40.1-28.7:8(H)(1).

Case law · 1995-04-17

D.10 Roto-Die Co. v. Lesser

Roto-Die Co. v. Lesser, a federal court predicting Virginia law, declined to adopt the blue-pencil rule — refusing to rewrite an overbroad restraint to save it — while severing genuinely independent covenant subparts and enforcing the valid ones, so an overbroad clause falls entirely but a structurally independent clause in the same agreement may survive.

While I believe paragraphs 7(a) and 7(b) are severable from paragraphs 7(c) and 7(d), I decline to adopt the so-called “blue pencil” rule.

See Roto-Die Co. v. Lesser, 899 F. Supp. 1515 (W.D. Va. 1995).

Case law · 2013-09-12

D.11 Assurance Data, Inc. v. Malyevac

Assurance Data, Inc. v. Malyevac holds that whether a restraint on competition is enforceable cannot be decided on a demurrer — reasonableness is evidence-dependent, so a challenge to an assignment or holdover clause would be litigated on a factual record.

Because a demurrer cannot be used to decide on the merits whether a restraint on competition is enforceable, we will reverse the circuit court's judgment.

See Assurance Data, Inc. v. Malyevac, 286 Va. 137, 747 S.E.2d 804 (2013).

Primary law

D.12 Va. Code § 40.1-28.7:8

Va. Code § 40.1-28.7:8(A) defines a covenant not to compete functionally — any agreement that restrains, prohibits, or otherwise restricts post-termination competition — a label-blind definition that could plausibly reach an aggressive trailing invention-assignment clause, though no Virginia court has decided that question.

"Covenant not to compete" means a covenant or agreement, including a provision of a contract of employment, between an employer and employee that restrains, prohibits, or otherwise restricts an individual's ability, following the termination of the individual's employment, to compete with his former employer.

See Va. Code § 40.1-28.7:8(A).

Case law · 1995-04-17

D.13 Roto-Die Co. v. Lesser

Roto-Die Co. v. Lesser, a federal court predicting Virginia law, declined to adopt the blue-pencil rule — refusing to rewrite an overbroad restraint to save it — while severing genuinely independent covenant subparts and enforcing the valid ones, so an overbroad clause falls entirely but a structurally independent clause in the same agreement may survive.

While I believe paragraphs 7(a) and 7(b) are severable from paragraphs 7(c) and 7(d), I decline to adopt the so-called “blue pencil” rule.

See Roto-Die Co. v. Lesser, 899 F. Supp. 1515 (W.D. Va. 1995).

Case law · 2011-11-04

D.14 Home Paramount Pest Control Cos. v. Shaffer

Home Paramount Pest Control Cos. v. Shaffer, restating the test from Omniplex World Services Corp. v. US Investigations Services, Inc., gives Virginia's operative three-part standard for restraints on competition — narrowly drawn to protect a legitimate business interest, not unduly burdensome on the ability to earn a living, and not against public policy — the framework a holdover assignment clause would most likely be measured against.

It is enforceable if it “is narrowly drawn to protect the employer’s legitimate business interest, is not unduly burdensome on the employee’s ability to earn a living, and is not against public policy.”

See Home Paramount Pest Control Cos. v. Shaffer, 282 Va. 412, 718 S.E.2d 762 (2011) (quoting Omniplex World Servs. Corp. v. US Investigations Servs., Inc., 270 Va. 246, 618 S.E.2d 340 (2005)).

Practice caution

Do not assume a Virginia employee works like a California or Washington one. There is no invention-assignment statute here, so there is no statutory carve-out to rely on and no notice safe harbor — but there is a statutory trap on the restraint side: Va. Code § 40.1-28.7:8 defines a covenant not to compete by function, reaching anything that restrains, prohibits, or otherwise restricts post-termination competition, and no Virginia court has decided whether a trailing invention-assignment clause fits that definition . If it does, the clause is prohibited outright for a very large covered class — all FLSA non-exempt employees regardless of pay, sub-average-wage workers, health care professionals, and any employee discharged without cause where disclosed-at-execution severance is missing — with a $10,000 civil penalty per violation, not a reasonableness trim. Keep any trailing or holdover assignment narrow, short, and tied to identifiable trade secrets and confidential information, and remember that even outside the statute it must survive Virginia's narrowly-drawn, not-unduly-burdensome, public-policy test . Because Virginia courts will not blue-pencil an overbroad restraint — though genuinely independent provisions can be severed and enforced — house the present assignment (hereby assigns) of during-employment inventions and any holdover clause in separate, severable provisions, so an overreaching holdover does not take the core assignment down with it .

Also for Virginia

Researching a different state? This survey covers all 56 U.S. notes