By Daniel Okafor

A Virginia court has issued a ruling that further interprets the state's statutory ban on noncompete agreements for low-wage workers, according to an analysis from the employment-law firm Ogletree. The decision supplies fresh interpretive guidance on a statute that already limits when employers can bind lower-earning staff to post-employment restraints.

Ogletree's employment-law practice dissected the court's reasoning in a recent client alert. The ruling examines how Virginia courts evaluate the enforceability of covenants not to compete (contractual clauses barring former employees from joining rivals or launching competing ventures) when the worker falls below the statutory wage threshold — the income level at which state law treats a worker as "low-wage" and therefore outside the permissible scope of a noncompete.

What did the court actually decide?

Ogletree frames the case as a clarification, not a new prohibition. The Virginia statute already bars noncompetes for low-wage employees; the court has now added interpretive scaffolding. The decision scrutinizes how the wage threshold operates in practice, particularly when an employee's compensation shifts during employment.

The court's reasoning, as summarized by Ogletree, also addresses how the statute treats workers whose roles straddle the wage line — hourly staff who receive bonuses, equity grants, or commissions that push annual earnings above the threshold.

The operative fact for employers is this: the ruling narrows the room for maneuvering rather than expanding it. Companies that treated the statute as narrow now have a sharper picture of its reach.

How does this change employer obligations?

HR leaders with Virginia workforces should treat the decision as a compliance prompt rather than a wholesale reset. Three immediate actions stand out:

• Audit noncompete templates for any worker earning below the statutory wage floor.
• Confirm that severance, equity, or commission arrangements do not inadvertently elevate a low-wage role into a higher-earner classification outside the ban.
• Document compensation history at hire, at each promotion, and at separation to defend against later challenge.

The Ogletree analysis treats the ruling as a clarification of scope, not a loosening of the prohibition. Noncompetes for protected workers remain unenforceable; the decision explains why certain workarounds fail.

Why does the ruling matter beyond Virginia?

Noncompete restrictions face simultaneous pressure at the federal and state levels. The Federal Trade Commission's proposed nationwide rule remains in litigation, and state legislatures continue to tighten the terms under which employers can deploy these clauses. For multistate HR teams, each state-level ruling adds a tile to a moving compliance map.

For HR teams operating across multiple states, compliance functions increasingly share noncompete templates via shared drives and HRIS systems (human-resources information platforms that centralize policy and employee data). A Virginia ruling exposes any gap in that shared infrastructure.

One useful comparison: the ruling functions less like a sweeping ban and more like a compliance speed bump — consequential for drivers who refuse to slow down.

What should HR do next?

Review, don't react. Ogletree's team recommends a measured response: confirm that noncompete templates exclude low-wage workers as the statute defines them, then reassess any in-flight offer letters that include such clauses. Companies with Virginia operations should also tighten tracking of compensation changes, since the wage threshold is the trigger for the statutory protection.

Legal counsel should sign off on revised templates, and any policy updates should be communicated to hiring managers who routinely extend offer letters.

For HR leaders outside Virginia, the case is a useful reminder. Noncompete policy is now a state-by-state exercise. Templates that worked in 2019 often fail in 2024, and a worker reclassified mid-year can move in or out of protected status without warning.

The ruling reads less like a headline and more like a footnote. Quiet, technical, consequential only to employers who ignored the underlying statute in the first place.