Is this &quot;Works for Hire&quot; language enforceable? I am reviewing a job offer that includes this Works for Hire clause: Works for Hire During the term of your employment, you may create an idea, process, trademark, invention, technology, program, original works of authorship, patent, and/or copyright, including improvements, rights, and claims thereto, alone or in connection with others (“Works”). All such Works are within the scope of employment and, by signing below, you acknowledge you hereby assign and transfer all right, title, and interest therein to CompanyName My initial thought was that by using &quot;term of your employment&quot; and &quot;all such works are within the scope of employment&quot; that this clause would cover any pet-projects I undertake on my free time while employed by this company. Friendlier language would limit to IP crafted as a function of/related to my employment or on company time/equipment. I found this similar question but for the UK: Is this Intellectual Property clause over-reaching? Am I correct that as-written this clause would apply to things I create outside the scope of this job? Is a clause like this generally enforceable in the US (or Colorado more specifically)?
It would not be valid in California. see California Labor Code § 2870(a). This will be state-specific and complicated.
Generally, what you say you will do in a contract is what you must do - there is no "the dog ate my homework" excuse. For your examples: Employment contracts have so much government regulation that the common law contract is lost in the mists of time. It is unlikely that a court would interpret an employment contract as requiring exact timekeeping; it is also unlikely that the person would have worked exactly 38 hours on every week except the one where they worked 37.5. However, if it were proved that the employee owed 0.5 hours to the employer they could be required to provide it or refund the pay they had received, barring a law that changed this. The dog must be walked. Alice must find a substitute walker if she is unable to provide it. Falling sick is something foreseeable that Alice should have provided for either in the contract ("if I am sick I won't walk the dog") or by arranging for someone else to do it. For purely personal services, falling sick may frustrate the contract, however, dog-walking is probably not personal enough. There is a doctrine which allows termination by frustration where neither party is at fault, however, it is not clear that this would apply. The building burning down is foreseeable and could (should?) have been addressed in the contract. If the destruction of the building was without fault on the owner then the contract is frustrated. If there was some fault on the owner (smoking in bed, inoperative fire alarm etc.) and the cleaner stands willing, ready and able (that is able except for the absence of a building) to perform their obligations, the owner would probably be obliged to pay, at the least for unrecoverable costs (e.g. wages) and loss of profits - if they pay for the cleaning products the cleaner would be obliged to deliver them up. One of the main reasons for the length of contracts for non-trivial transactions is they deal with these contingencies.
Basically, "in the course of your employment" means "while you are working, or should be working, for the employer". If you're not using company resources or time to create or acquire the works in question, and the works are unrelated to company business, they're quite unlikely to become the company's property. (Particularly since the company almost certainly doesn't have an interest in controlling the distribution of your vacation photos.) When you let your personal side projects and the company's stuff get intertwined, that's where the troubles begin. Works made on company time, or using company resources, or to do company-related things, may be claimed by the company, and this agreement basically says you'll cede ownership of the works to them, patents and all, for whatever amount of money they decide it's worth paying you.
Contracts do not have to be written and signed on pieces of paper, except in a few cases specified by law. Writing style (ordinary style of talking vs. high-register formulaic language) does not affect the validity or a writing in contract law. You do have something in writing. What matters most is what he actually said (exact words, not your belief of what it must have meant), and how it relates to any existing contractual obligation. For example if the message says &quot;You're fired, turn your badge in at the desk. I'll think about giving you two weeks pay&quot;, that's not an enforceable promise. But your existing contract might say &quot;You get 2 weeks severance pay when we fire you&quot;, and that can't be walked by by saying &quot;I'll thinking about it&quot;. And it also depends on whether there are any laws mandating severance pay (but California does not have any mandatory severance pay law).
The creator of the derivative work has copyright in the derivative work. The copyright would protect only the new elements of the derivative work. Wikipedia is a good place to start. In the case of a book with updated grammar, depending on the extent of the changes, it would probably be easier to copy the original directly than to eliminate the updates from a copy of the derivative work.
Yes Written contracts do not have to be written in any particular language or character set. Purely visual contracts are used and are legally binding. If a pictorial term is ambiguous it is resolved by the court the same way as a textual term would be.
The first question is whose law you are concerned with, since in principle you might have violated copyright law in any country, and might be sued under the laws of multiple countries. The US has a concept of "fair use" which is notoriously difficult to apply. When you are sued in the US, you can defend against the allegation by arguing certain things: telegraphically, this includes purpose and character of use, nature of the work, substantiality in relation to the whole, and effect on market. Plus there is a 5th factor to be considered, transformativeness. The court then weighs these factors to decide if the use is "fair". By reading existing case law on the topic (conveniently available from the US Copyright office) you might develop a fact-based opinion of the risk: you would be vastly better off hiring an attorney who specializes in US copyright law to do an analysis for you. Do not hire a programmer to give you legal advice (do not hire an attorney to debug code). You would "fail" on the test of substantiality in that you are copying a highly substantial portion of the original work(s). You would "win" on nature of use (research especially non-profit and commentary are the underlying purposes that drive fair use law). It's not clear how you would fare w.r.t. nature of the work, which is intended to distinguish the extremes "news report" and "literature and artistic work" where copying news is at the fair use end of the spectrum. It is not clear how you would fare on "effect on market", but probably not so badly: are you avoiding some licensing fee? Coupled with the tranformativeness consideration, you are most likely having no effect on the market, since the product that you will distribute is not the original work, but a scientific conclusion about the work. Germany has different laws, and this article would be relevant if you cared about Germany. There was a change in the law that expanded the analog of fair use pertaining to research use. That law allows 15 percent of a work to be reproduced, distributed and made available to the public for the purpose of non-commercial scientific research. That, b.t.w., does not refer to what you are planning to do (unless you also publish quotes); for personal scientific research you may reproduce up to 75 percent. Since this is a new law only a year old, you could become part of the cutting edge in testing the limits of the law. So the standard disclaimer applies: ask your attorney. But note section 60d of the law which legalized data mining, and is squarely on point: (1) In order to enable the automatic analysis of large numbers of works (source material) for scientific research, it shall be permissible to reproduce the source material, including automatically and systematically, in order to create, particularly by means of normalisation, structuring and categorisation, a corpus which can be analysed and to make the corpus available to the public for a specifically limited circle of persons for their joint scientific research, as well as to individual third persons for the purpose of monitoring the quality of scientific research. In such cases, the user may only pursue non-commercial purposes. (2) If database works are used pursuant to subsection (1), this shall constitute customary use in accordance with section 55a, first sentence. If insubstantial parts of databases are used pursuant to subsection (1), this shall be deemed consistent with the normal utilisation of the database and with the legitimate interests of the producer of the database within the meaning of section 87b (1), second sentence, and section 87e. (3) Once the research work has been completed, the corpus and the reproductions of the source material shall be deleted; they may no longer be made available to the public. It shall, however, be permissible to transmit the corpus and the reproductions of the source material to the institutions referred to in sections 60e and 60f for the purpose of long-term storage.
could this mean my employer owns the idea and anything I develop --since I would use the same technology for my idea that I do at work? No, unless by &quot;technology&quot; you mean the employer's materials or resources (see condition 3 of the clause). Your remark that &quot;this is completely and utterly unrelated to [employer's] business model&quot; survives items 1 and 2. Likewise, working on your idea outside hours survives the corresponding part of item 3. Would this also mean that any open-source software I develop outside of work automatically belongs to my employer? No, unless the software you develop is &quot;based on [your] knowledge [etc.] of (COMPANY)&quot;.