Lesko v. United States

Plain English (For Everyone)

Imagine you hire someone to paint your house. You can tell them what color to paint it, but you can't tell them exactly how to hold the brush or mix the paint. This case says that for someone to be considered your employee for copyright purposes, you need to have the power to control not just the final result, but also the creative process of how they do the work. Just deciding what you want done isn't enough; you have to be able to direct the 'how-to' of the creation.

For Legal Practitioners

The Federal Circuit clarified that 'control' under the work-for-hire doctrine requires more than the right to dictate the scope or specifications of the final product. The court emphasized the need for control over the 'manner and means' of the creative process itself, distinguishing it from mere supervision of the end result. This ruling reinforces that absent a specific agreement, a party's ability to define project requirements, without more, will likely not establish an employment relationship for copyright ownership purposes, impacting how attorneys advise clients on commissioning creative works.

For Law Students

This case tests the 'control' element of the work-for-hire doctrine, specifically whether specifying project requirements constitutes sufficient control over the 'manner and means' of creation. The Federal Circuit held that it does not, requiring a higher threshold of control over the creative process itself. This decision fits within the broader doctrine of copyright ownership, highlighting the importance of contractual agreements and the nuances of establishing an employer-employee relationship for copyright purposes, particularly in government contracting scenarios.

Newsroom Summary

A federal court ruled that the U.S. government did not have enough control over a software developer to be considered their employer for copyright purposes. The decision clarifies that simply dictating project specifications isn't enough; the government must control the creative process itself. This impacts how copyright ownership is determined in government contracts.

Rule Statements

"When interpreting a statute, we look to the plain meaning of the words used."

"The plain language of § 6511(a) requires that a claim for credit or refund be filed within three years from the time the return was filed or two years from the time the tax was paid, whichever of such periods expires the later."

Judges

• Richard Linn

Attorneys

• Jimmie V. Reynolds
• Michael J. Ryan

Scenario: You hire a freelance graphic designer to create a logo for your new business. You provide detailed specifications for the logo's appearance, colors, and intended use, but you don't dictate the specific software they use, their design techniques, or how they sketch out initial concepts.

Your Rights: Under this ruling, if a dispute arises over copyright ownership of the logo, you likely would not be considered the 'employer' for work-for-hire purposes. This means the designer, as the creator, would likely own the copyright unless you have a written agreement stating otherwise.

What To Do: If you want to ensure you own the copyright to work created by a freelancer, always have a clear, written contract that explicitly states the work is a 'work made for hire' and assigns copyright ownership to you, or includes a broad assignment of all rights.

Is it legal for me to claim copyright ownership of software I commissioned a freelancer to build, just because I gave them detailed requirements?

Depends. Under this ruling, it is likely not legal to automatically claim copyright ownership solely based on providing detailed requirements. The court requires proof of control over the 'manner and means' of the creative process, not just the end product's specifications, to establish a work-for-hire relationship.

This ruling applies to federal copyright law and interpretations by the U.S. Court of Appeals for the Federal Circuit, which hears appeals in patent and government contract cases, among others. Its interpretation of copyright law is influential nationwide.

For Government Contractors

This ruling clarifies that specifying the end product's requirements for government projects does not automatically create a work-for-hire situation for copyright purposes. Contractors should ensure contracts clearly define copyright ownership, as the government's ability to dictate specifications alone won't suffice to claim ownership.

For Freelance Creators (Software Developers, Artists, Writers)

The decision reinforces that creators retain copyright ownership unless there's a clear agreement or sufficient control over the 'manner and means' of their work. This strengthens freelancers' positions regarding copyright unless explicitly contracted away.

Q: What is Lesko v. United States about?

Lesko v. United States is a case decided by Federal Circuit on January 30, 2026.

Q: What court decided Lesko v. United States?

Lesko v. United States was decided by the Federal Circuit, which is part of the federal judiciary. This is a federal appellate court.

Q: When was Lesko v. United States decided?

Lesko v. United States was decided on January 30, 2026.

Q: What is the citation for Lesko v. United States?

The citation for Lesko v. United States is . Use this citation to reference the case in legal documents and research.

Q: Who were the parties involved in the Lesko v. United States case?

The parties in Lesko v. United States were the plaintiff, Lesko, who was an independent contractor or creator of software, and the defendant, the United States, which contracted for Lesko's services.

Q: What court decided the Lesko v. United States case?

The United States Court of Appeals for the Federal Circuit (CAFC) decided the Lesko v. United States case, affirming the lower court's decision.

Q: What was the nature of the dispute in Lesko v. United States?

The dispute in Lesko v. United States centered on copyright ownership. Lesko argued he was an employee for hire, meaning the United States would own the copyright, while the United States contended it had sufficient control to establish a work-for-hire relationship.

Q: What specific type of work was at issue in Lesko v. United States?

The work at issue in Lesko v. United States was software developed by Lesko for the United States government. The dispute concerned whether this software was a 'work for hire'.

Q: Is Lesko v. United States published?

Lesko v. United States is a published, precedential opinion. Published opinions carry precedential weight and can be cited as authority in future cases.

Q: What topics does Lesko v. United States cover?

Lesko v. United States covers the following legal topics: Copyright law, Work for hire doctrine, Employee status under common law agency test, Copyright ownership, Independent contractor vs. employee.

Q: What was the ruling in Lesko v. United States?

The court ruled in favor of the defendant in Lesko v. United States. Key holdings: The Federal Circuit affirmed the district court's determination that the United States did not qualify as the "employer" under the Copyright Act's work-for-hire provisions because it did not possess the right to control the "manner and means" by which the software was created.; The court clarified that the "control" prong of the work-for-hire doctrine requires more than the right to specify the end product or the general scope of the work; it demands the right to control the creative process and the specific methods of creation.; The court found that while the government could dictate the specifications, requirements, and desired outcomes of the software, this did not demonstrate control over the "manner and means" of Lesko's creative and intellectual labor in developing the software.; The court distinguished between controlling the "end result" of a work and controlling the "manner and means" of its creation, emphasizing that the latter is essential for establishing an employer-employee relationship for work-for-hire purposes.; The court rejected Lesko's argument that the government's extensive oversight and detailed specifications constituted sufficient control, holding that such actions were consistent with a client-contractor relationship rather than an employer-employee one..

Q: Why is Lesko v. United States important?

Lesko v. United States has an impact score of 40/100, indicating moderate legal relevance. This decision clarifies the "control" element of the work-for-hire doctrine, particularly in the context of government contracts for creative works like software. It emphasizes that specifying an end product is insufficient to establish an

Q: What precedent does Lesko v. United States set?

Lesko v. United States established the following key holdings: (1) The Federal Circuit affirmed the district court's determination that the United States did not qualify as the "employer" under the Copyright Act's work-for-hire provisions because it did not possess the right to control the "manner and means" by which the software was created. (2) The court clarified that the "control" prong of the work-for-hire doctrine requires more than the right to specify the end product or the general scope of the work; it demands the right to control the creative process and the specific methods of creation. (3) The court found that while the government could dictate the specifications, requirements, and desired outcomes of the software, this did not demonstrate control over the "manner and means" of Lesko's creative and intellectual labor in developing the software. (4) The court distinguished between controlling the "end result" of a work and controlling the "manner and means" of its creation, emphasizing that the latter is essential for establishing an employer-employee relationship for work-for-hire purposes. (5) The court rejected Lesko's argument that the government's extensive oversight and detailed specifications constituted sufficient control, holding that such actions were consistent with a client-contractor relationship rather than an employer-employee one.

Q: What are the key holdings in Lesko v. United States?

1. The Federal Circuit affirmed the district court's determination that the United States did not qualify as the "employer" under the Copyright Act's work-for-hire provisions because it did not possess the right to control the "manner and means" by which the software was created. 2. The court clarified that the "control" prong of the work-for-hire doctrine requires more than the right to specify the end product or the general scope of the work; it demands the right to control the creative process and the specific methods of creation. 3. The court found that while the government could dictate the specifications, requirements, and desired outcomes of the software, this did not demonstrate control over the "manner and means" of Lesko's creative and intellectual labor in developing the software. 4. The court distinguished between controlling the "end result" of a work and controlling the "manner and means" of its creation, emphasizing that the latter is essential for establishing an employer-employee relationship for work-for-hire purposes. 5. The court rejected Lesko's argument that the government's extensive oversight and detailed specifications constituted sufficient control, holding that such actions were consistent with a client-contractor relationship rather than an employer-employee one.

Q: What cases are related to Lesko v. United States?

Precedent cases cited or related to Lesko v. United States: Community for Creative Non-Violence v. Reid, 490 U.S. 730 (1989); Aldon Accessories Publishers, Inc. v. Spiegel, Inc., 737 F.2d 598 (2d Cir. 1984).

Q: What is the main legal issue in Lesko v. United States?

The central issue in Lesko v. United States was the interpretation of the 'control' prong of the 'work for hire' doctrine under the Copyright Act. Specifically, the court had to determine whether the United States exercised sufficient control over the 'manner and means' of Lesko's work to classify him as an employee for hire.

Q: What is the 'work for hire' doctrine in copyright law?

The 'work for hire' doctrine generally means that the employer or commissioning party, rather than the creator, is considered the author and owner of a copyrighted work. This doctrine has specific requirements, including the creator being an employee or the work being specially commissioned under a written agreement.

Q: What did Lesko argue about the government's control over his work?

Lesko argued that the United States exercised sufficient 'control' over the 'manner and means' of his work, which he believed qualified him as an 'employee' for the purposes of the work-for-hire doctrine under the Copyright Act.

Q: What was the Federal Circuit's holding regarding 'control' in the work-for-hire doctrine?

The Federal Circuit held that 'control' under the work-for-hire doctrine requires more than just the right to specify the end product; it necessitates the right to control the 'manner and means' by which the work is created. Simply dictating scope and specifications is insufficient.

Q: Did the court find that the government controlled the 'manner and means' of Lesko's software development?

No, the court found that the government's ability to dictate the scope and specifications of the software did not equate to control over the creative process itself, meaning they did not control the 'manner and means' of its creation.

Q: What does the 'manner and means' test refer to in copyright law?

The 'manner and means' test, as applied in Lesko v. United States, refers to the level of control a commissioning party has over how a work is created. It goes beyond dictating the subject matter or final specifications and delves into the methods, techniques, and creative choices involved in the production process.

Q: Does Lesko v. United States change the definition of 'employee' for copyright purposes?

While not directly redefining 'employee' in the general sense, Lesko v. United States refines the application of the 'employee' prong within the work-for-hire doctrine. It clarifies that for copyright purposes, demonstrating control over the 'manner and means' is crucial, even if the creator is labeled an 'employee' in a contract.

Q: What is the burden of proof in a work-for-hire dispute like Lesko v. United States?

In a work-for-hire dispute, the party asserting the work-for-hire relationship typically bears the burden of proving that the statutory requirements are met. In Lesko, the United States would have had to prove it exercised sufficient control over the 'manner and means' of Lesko's work.

Q: What is the difference between controlling the 'end product' and controlling the 'manner and means'?

Controlling the 'end product' means defining what the final work should achieve or look like (e.g., software must perform X function). Controlling the 'manner and means' means dictating how the work is created (e.g., specific programming languages, development methodologies, or creative approaches).

Q: Did the court consider Lesko's status as an independent contractor or employee?

The court considered Lesko's status in the context of the work-for-hire doctrine. While Lesko argued he was an 'employee' due to government control, the court ultimately found the government did not exercise sufficient control over the 'manner and means' to deem him an employee for hire under copyright law.

Q: What is the relevance of the Copyright Act in this case?

The case directly interprets provisions of the Copyright Act, specifically Section 101, which defines 'work made for hire.' The court's analysis hinges on the statutory language and judicial interpretations of terms like 'employee' and the control required for such a relationship.

Q: How did the specific nature of software development influence the court's decision?

The court likely considered the nature of software development, which often involves significant creative input and technical expertise from the developer. This complexity supports the idea that specifying requirements alone does not equate to controlling the intricate 'manner and means' of coding and design.

Q: What happens to copyright ownership if a work is NOT considered a 'work for hire'?

If a work is not considered a 'work for hire,' the creator (in this case, Lesko) is generally considered the author and owner of the copyright, unless there is a separate, explicit agreement transferring ownership to the commissioning party.

Q: How does Lesko v. United States affect me?

This decision clarifies the "control" element of the work-for-hire doctrine, particularly in the context of government contracts for creative works like software. It emphasizes that specifying an end product is insufficient to establish an As a decision from a federal appellate court, its reach is national. This case is moderate in legal complexity to understand.

Q: What is the practical impact of the Lesko v. United States decision on independent contractors?

The decision clarifies that for a commissioning party to be considered the 'author' under the work-for-hire doctrine based on control, they must demonstrate control over the creative process ('manner and means'), not just the final product. This makes it harder for government or corporate entities to claim copyright ownership over independent contractors' work without explicit agreements.

Q: How does the Lesko decision affect government contracts for creative work?

Government agencies must be more explicit in their contracts if they intend to secure copyright ownership of commissioned works. The Lesko ruling emphasizes that specifying project requirements is not enough; control over the creative process must be demonstrable to establish a work-for-hire relationship.

Q: What are the implications for businesses commissioning software development after Lesko v. United States?

Businesses commissioning software development should ensure their contracts clearly define copyright ownership. If they wish to claim work-for-hire status based on control, they need to document and exercise control over the development process itself, not just the project's requirements and deliverables.

Q: Could Lesko have secured copyright ownership if the government had acted differently?

Potentially. If the United States had exercised more direct control over the specific coding techniques, development tools, or creative decisions Lesko made during the software creation process, it might have met the 'manner and means' test and established a work-for-hire relationship.

Q: How does this case relate to prior interpretations of the work-for-hire doctrine?

Lesko v. United States builds upon existing case law, such as Community for Creative Non-Violence v. Reid, which also emphasized the importance of the 'manner and means' test for independent contractors. This decision reinforces that mere specification of the end product is insufficient to establish control for work-for-hire purposes.

Q: What is the historical context of the 'work for hire' doctrine and independent contractors?

Historically, the work-for-hire doctrine was primarily applied to employer-employee relationships. Landmark cases like CCNV v. Reid (1989) clarified that for independent contractors, specific statutory requirements, including a written agreement and certain categories of works, must be met, and the 'control' test is crucial.

Q: What was the docket number in Lesko v. United States?

The docket number for Lesko v. United States is 23-1823. This identifier is used to track the case through the court system.

Q: Can Lesko v. United States be appealed?

Potentially — decisions from federal appellate courts can be appealed to the Supreme Court of the United States via a petition for certiorari, though the Court accepts very few cases.

Q: What is the significance of the Federal Circuit affirming the lower court's decision?

The Federal Circuit affirming the lower court's decision means that the appellate court agreed with the trial court's legal reasoning and outcome. This strengthens the precedent set by the lower court regarding the interpretation of the 'control' element in work-for-hire cases.

Q: How did the case reach the Federal Circuit?

The case reached the Federal Circuit on appeal from a lower court's decision. Lesko appealed the lower court's ruling, which had likely found that the work was not a work for hire because the government did not exercise sufficient control.