Employee Invention Assignment in Maryland

Can a Maryland employer require assignment of every invention?

Because there is no statute on point, the limits come from general principles rather than a legislative carve-out. A full-text review of the Maryland Code's Labor and Employment article surfaces no employee-invention-, patent-, or intellectual-property-assignment provision. The employment-adjacent statutes Maryland does have run in other directions: Md. Code Ann., Lab. & Empl. § 3-716 voids noncompete and conflict-of-interest provisions as against Maryland public policy for lower-paid employees (the threshold is keyed to 150 percent of the State minimum wage), and the Maryland Uniform Trade Secrets Act, Md. Code Ann., Com. Law § 11-1201 et seq., governs the trade-secret overlay of a confidentiality-and-invention-assignment agreement. Neither addresses what an invention-assignment clause may capture.

The gap is a legislative choice, not an oversight. In 2020, House Bill 1466 would have voided assignment clauses reaching intellectual property an employee developed entirely on the employee's own time without employer equipment, supplies, facilities, or trade secrets — a California-style carve-out. The bill died in the House Economic Matters Committee after its March 10, 2020 hearing, and the Labor and Employment article section it would have created, § 3-717, is now occupied by an unrelated provision on facial recognition in job interviews. A Maryland employer therefore starts from contract law, not a § 2870-style statutory ceiling on what an assignment promise may reach.

The closest Maryland-forum authority treats the contract as doing exactly that work. In Crown Cork & Seal Co. v. Fankhanel, the U.S. District Court for the District of Maryland enforced a written invention-assignment agreement against a former employee, restating the settled framework under which the agreement — not any statute — determines who ends up owning an employment-related invention A.1.

“an invention made incidentally by an employee in the course of his regular or general employment, and at his employer’s expense, is the property of the employee, unless he has agreed, either expressly or impliedly by virtue of some special terms of his employment, to transfer ownership to his employer”

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

“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 Maryland 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 to the extent it operates as a restraint on the former employee it runs into Maryland's restrictive-covenant reasonableness limits discussed below. There is simply no statutory own-time/own-resource safe harbor for the employee to invoke and no statutory ceiling for the drafter to code around.

Must a Maryland employer notify the employee?

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; Maryland has enacted no such carve-out — the General Assembly declined the opportunity when 2020 House Bill 1466 died in committee — 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 Maryland does not have.

Where a Maryland employee owes invention-ownership obligations, they come from the contract, not a statute. In Crown Cork & Seal Co. v. Fankhanel, the federal district court in Maryland enforced a written assignment agreement on exactly that footing, restating the framework under which the employee keeps an incidental invention unless the agreement says otherwise B.1.

“an invention made incidentally by an employee in the course of his regular or general employment, and at his employer’s expense, is the property of the employee, unless he has agreed, either expressly or impliedly by virtue of some special terms of his employment, to transfer ownership to his employer”

For a multistate employer the takeaway is the inverse of the notice states: a Maryland 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 Maryland?

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 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. 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 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 C.4.

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

Maryland's forum courts have applied that exception in its strong form. In Houghton v. United States, the Fourth Circuit — affirming the District of Maryland and adopting the trial court's statement as the correct rule — held that the hired-to-invent duty is not limited to employees whose contract named invention as the job: an employee directed to solve a specific problem within the scope of a general employment is treated the same way C.5.

“An employee, who undertakes upon the direction of his employer to solve a specific problem within the scope of his general employment, is as truly employed and paid for the particular project as if it had been described at the outset in the contract of employment.”

The court's own formulation makes the consequence explicit: for as long as the employee is engaged on the assigned problem, the results of the work at invention belong to the employer C.2.

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

One caveat on the Maryland picture deserves emphasis: the ownership authorities here are federal. Houghton is a Fourth Circuit decision affirming the District of Maryland and applying the general common law of the pre-Erie era, and our review found no decision of Maryland's highest court addressing private employee-invention ownership. The answer above is therefore the shared federal baseline as applied in a Maryland forum, not a holding of Maryland's state appellate courts.

Short of hired-to-invent, where the employee is neither engaged 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 gets only a shop right — a non-exclusive license to use the invention, not ownership of it C.6.

“Recognition of the nature of the act of invention also defines the limits of the so-called shop-right, which shortly stated, is that where a servant, during his hours of employment, working with his master's materials and appliances, conceives and perfects an invention for which he obtains a patent, he must accord his master a non-exclusive right to practice the invention.”

Because ownership starts with the inventor and Maryland has no statute filling the gap, the dependable path for a Maryland 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 Maryland?

Two gaps define the Maryland picture. First, there is no statute on invention assignments: nothing caps the duration of a post-employment trailing assignment or otherwise limits what such a clause may reach. Second, our review found no Maryland decision applying the state's restraint-of-trade limits to an invention-holdover clause — or even deciding whether such a clause is analyzed as an ownership provision, a restrictive covenant, or both — so the invention-specific application of those limits is genuinely open rather than settled.

The framework a Maryland court would bring to that analysis is well established. In MacIntosh v. Brunswick Corp., the Court of Appeals of Maryland (now the Supreme Court of Maryland) stated the general rule for restrictive covenants in employment contracts, in a formulation it drew from its earlier decision in Silver v. Goldberger D.1.

“The general rule in Maryland is that restrictive covenants in a contract of employment, by which an employee as a part of his agreement undertakes not to engage in a competing business or vocation with that of his employer on leaving the employment, will be sustained ‘if the restraint is confined within limits which are no wider as to area and duration than are reasonably necessary for the protection of the business of the employer and do not impose undue hardship on the employee or disregard the interests of the public.’”

Extending that rule to holdover assignments is a prediction, not a holding. A Maryland court asked to enforce a clause that sweeps in inventions an ex-employee conceives after leaving would most likely ask the MacIntosh questions — whether the reach is no wider than reasonably necessary to protect the employer's business, and whether it imposes undue hardship on the former employee or disregards the public interest — rather than apply any invention-specific rule. Out-of-state authority that has voided open-ended post-employment invention assignments applies other states' law and is at most analogous; it is not Maryland law and should not be treated as controlling here.

One adjacent statute is worth flagging. Md. Code Ann., Lab. & Empl. § 3-716 voids noncompete and conflict-of-interest provisions as against Maryland public policy for employees earning at or below 150 percent of the State minimum wage. No authority found in our review applies § 3-716 to an invention-assignment clause, but a trailing assignment broad enough to function as a practical restraint on a covered employee's ability to take new work would raise the open question whether it falls within the section's reach.

The safe reading is that an overbroad trailer clause is at meaningful risk in Maryland: the reasonableness framework is the only identified limit, its application to trailing assignments has not been decided, and no Maryland authority found in our review establishes that a court would trim an overbroad clause rather than refuse to enforce it — so the drafter should not count on judicial rescue.