Type of contracts I have been trying to understand what type of contracts a Contract Lifecycle Management platform should actually model. I am a software engineer and I do not know so much about law... Looking online, it seems to me that these platforms always talk about &quot;Buy Side&quot; and &quot;Sell Side&quot; contracts like if they were the only types. Aren't there also other contracts that do not involve buying or selling? To be honest, I haven't been able to come up with good examples, but I do not know if this is because they do not exist or because I am ignorant. Just to give some context... I am thinking to interview for a job as software engineer in a company that has a contract lifecycle management suite and I would like to know a bit more about contracts just to show that I am not completely ignorant and that I tried to be prepared for the interview.
Because a contract is simply an agreement between two parties to exchange anything of value, there are many, many more types of contracts. If the company hires you, you would have an employment contract. If you agree to pick up a shift this week for someone who will pick up a shift for you next week, you have a contract. If the company lays you off, you may end up with a severance agreement. If you sue them for race discrimination you may enter into a contract to settle the case for a million dollars. If you want to protect that money from your fiance, you might enter into a prenuptial agreement. If you get divorced anyway, you might split up custody of your children in a shared parenting agreement. All of these agreements would constitute contracts.
Jurisdiction has not been provided, so I've written a general answer: Not necessarily; often, such provisions clauses will have their own expiration dates, for example "for five years after signing, X", with X still being valid after cancellation up to 5 years(so if you cancel after 3 years, X is still valid for 2 more years), or "for two years after cancellations, Y"(especially common with non-compete clauses) where the time-limit of Y starts when the contract is cancelled. Other clauses are meant to indeed be enforced forever, such as some non-disclosure, non-disparagement, or indemnity clauses. For example, an indemnity clause in a contract that prevents a party from suing the counter-party for work done under the contract would be pointless if it could be bypassed by a party terminating the agreement. There are lots of legal limits, based on the terms of the provision, and its nature, all governed by the contract law of the jurisdiction under which the contract was drafted under and/or is governed by (this is generally obvious, except for some cross-border contracts, which generally will have a declaration as to whose laws apply). It is not inherently abusive, but can certainly be abused. What is considered abusive often varies from jurisdiction to jurisdiction (not only on this issue, but on legal issues in general). It depends on the jurisdiction, and generally on the terms of the provision itself. If the court asked to enforce the terms of the agreement feels that the provision is illegal or abusive, they won't be enforced (and possibly the entire document declared null and void, depending on the central-ness of the illegal or abusive provision; some provisions specifically state that invaliding the provision doesn't invalidate the whole contract to try to prevent this). If they don't feel the provision is illegal or abusive, they will generally enforce it.
does the individual have a legal case against the company? Unfortunately, no. Some details and terms you use are unclear (e.g., "phantom" equity, "manifest" core technology, and so forth), but your overall description reflects that the individual sabotaged himself by signing a contract that does not mention the promise of equity through which he was persuaded to engage. A written contract usually supersedes any prior agreement --regarding the subject matter of that contract-- between the parties. That superseding effect means that the contract formalizes or overrides, accordingly, said agreements or promises. Since the initial promises of equity are not reflected in the "interim" contract, the investor's subsequent silence upon individual's reproach/reminders is from a legal standpoint irrelevant. At that point only the terms of the contract matter. The individual might consider alleging mistake in the sense of Restatement (Second) of Contracts at § 151-154 such that would make the contract voidable and perhaps "make room" for other theories of law. However, that seems futile unless the interim contract contains language that (1) provides specific conditions for its expiration, or (2) reflects the company's [mis-]representations that induced the individual to sign it. Neither seems to have occurred in the situation you describe. There is always a possibility that the contract might favor the individual's position and he just has not noticed it. But the only way to ascertain that is by reading the contract itself.
Preface and Caveats The question doesn't specify where this happened. I am providing an outline of the way that most U.S. states would handle this situation, if the fats are as they are much more likely to be and not as claimed in the question probably due to a misunderstanding of the underlying transaction. I identify areas where state laws most often vary and don't describe those areas of the law in detail since that is impossible without knowing where this happens. This is a matter of state law and varies from state to state, although most U.S. states are quite similar until you get to the fine details. Atypical language in the contract between the contractor and the client could also lead to a different conclusion. I don't know how this would be resolved in a non-U.S. jurisdiction. Background: The Structure Of A Typical Construction Loan Financed Construction Project In business and contractual disputes you can only understand the answer if you understand the underlying business transaction, which the question itself doesn't spell out very fully. The fact pattern identified in the question is so unusual that I strongly suspect that there is a misunderstanding of the facts, or an inadvertent misstatement in the language used in the question due to sloppy writing that flows from not appreciating the importance of some key facts. The transaction was almost surely structures more or less as follows (for background, I'm presenting a more general very of this kind of transaction rather than the simple one with no subcontractors or material suppliers involved, because this context helps someone understand why the laws are written the way that they are written.) Usually, the client owns real property, takes out a construction loan from a bank secured by the real estate, and hires a general contractor. The client will usually make some down payment to the general contractor who will take care of paying the subcontractors and material suppliers, and will pay the balance of the amount due to the general contractor through proceeds of the construction loan disbursed by the bank which are drawn as the work is done and payment is earned. Typically, each drawn cycle, which is often monthly for a smaller project and weekly, biweekly or semimonthly in a larger project, materials suppliers and subcontractors submit invoices and lien waivers to the general contractor based upon the work done. If the work is complete, a complete lien waiver is submitted, if he work in only partially finished, a partial lien waiver is submitted. The general contractor substantively reviews the invoices based upon a physical review of the construction site and a review of the subcontract. If there are problems it is rejected and must be resubmitted by the material supplier or subcontractor. If it is approved, the general contractor attaches that invoice as a supporting document to a draw request for the draw cycle summarizing all validly submitted invoices from material suppliers, subcontractors and itself, and also attaching a partial lien waiver from the general contractor. Then, the general contractor submits that draw request to a bank officer handling the construction loan as an agent of the property owner-client, and also a client representative for approval. The bank officer and client representative make a much less probing review of the draw request, looking only for obvious irregularities or suspicious amounts, and if everything is in order, they approve the request. Then, the bank write a check in the draw amount approved to the general contractor. The general contractor then disburses the invoiced amounts to the materials materials suppliers and subcontractors and pays itself the amounts that it has earned. Sometimes, however, the general contractor gets a valid invoice from a material supplier or subcontractor, and receives funds from the client in the form of a downpayment or a loan draw, but doesn't pay the subcontractor or material supplier with those funds. Also, sometimes, the general contractor does work that it is entitled to be paid for or incurs an obligation to a material supplier or subcontractor, but the client doesn't pay or the bank doesn't disburse the funds requested even though the request is valid. When a general contractor, material supplier or subcontractor doesn't get paid for work that is actually done at a particular piece of real estate, the law gives the firm that wasn't paid for its work on that particular piece of real estate what is called a mechanic's lien encumbering that piece of real estate. The details of how a firm with a mechanic's lien gives notice to the world of its rights, the priorities of lien's vis-a-vis each other, and the way that mechanic's liens are enforced varies significantly from state to state. But typically the notice must be given very promptly and not long after notice of non-payment is given, a lawsuit to foreclose on the real estate encumbered by the lien is commenced. An unpaid material supplier or subcontractor, in addition to its lien rights, can also sue the general contractor for breach of contract, and sometimes also for misappropriation of disbursements from the client or the bank. An unpaid general contractor, in addition to its lien rights, can also sue the owner of the property for breach of contract. The Facts In The Question and Analysis The first paragraph of the question tells us what went wrong. The client paid an employee of the general contractor (probably a project manager) instead of the firm the employee worked for (basically embezzling the money by deceiving the client into thinking that the employee was authorized to receive a payment to the employee's firm on its behalf when that wasn't the case), and the firm of the employee who was paid now wants to get paid. This happens and lawsuits usually follows when it does. But exactly what happens next depends upon the facts in the next to paragraphs. The next two paragraphs of the question, however, are probably confused and incorrect. The next two paragraphs say: Two weeks later, the client received a letter from the contractor's lender asking the client for money owed to the contractor, saying that if it was not paid, the client could be double charged. Does the client owe the contractor's lender? What probably actually happened is that the finance office of the contractor submitted a draw request to the bank officer in charge of the client's construction loan with the bank, and also gave a notice of the draw request to the client. The client tells the bank officer not to approve the draw request because the client has already paid the draw request directly to the employee of the contractor (probably the project manager) without the knowledge of the firm the employee worked for. What Happens Next If The Facts Are As I Believe Them To Be? When this happens, the finance officer at the contractor firm talks to the client figures out what happens and then talks to the employee to whom the payment was made. If the employee promptly turns over the funds the the contractor firm, the finance officers at the contractor firm scolds the employee for screwing up the system and the client for making a payment to the wrong person and there is no harm, no foul, and the matter is over. But if the employee who took the client's money doesn't turn over the money which the client can prove to the contractor firm that he paid to the employee, several things are likely to happen. Non-Lawsuit Actions: The client will direct the bank not to pay the draw request. The employee who took the money from the client is fired (no big deal, he was probably long gone). The contractor firm and/or the client will often, but not always, report to the police that the employee embezzled the funds from the client, and if the police find it credible, will issue an arrest warrant. The main reason not to do so is that the facts are uncertain enough that the police and prosecutor don't want to touch it (e.g. the client paid the employee in cash and didn't get a receipt, or the employee when asked says that the payment was made but was a &quot;tip&quot; or was payment for something unrelated), or the client and/or the contractor firm don't want to harm their reputations by making public the fact that there was a theft on this job. Three lawsuits could be brought, although, in practice, these might be consolidated as claims against different parties and cross-claims between defendants, in a lawsuit brought by the contractor, or in some other configuration. The contractor firm sues the employee who took the money for converting money from a client intended for it (probably both as a tort and as a breach of fiduciary duty by an agent of the construction firm). The contractor firm sues the client for breach of contract. The question is about the liability of the client in this second lawsuit. The client might also bring a counterclaim against the contractor for negligent supervision of its employee if the employee did indeed abscond with the money and the facts support that counterclaim. If the client prevailed on that counterclaim, the judgment on the counterclaim for negligent supervision (e.g. if the contractor knew that the employee had a history of doing things like this and didn't warn the client) would be setoff against the breach of contract judgment, rather than being a defense to the breach of contract claim. The client sues the employee for fraud, conversion or theft. What Are The Rights Of The Parties In These Lawsuits? In the second lawsuit, the client has breached the contract. The contract said to pay the firm, the client paid someone else, and so the obligation under the contract was not satisfied. The disputes in the lawsuit between the contracting firm and the client will be over whether the employee had apparent authority to accept the funds as an agent of he contracting firm, over whether the payment that the client says was made to the employee was made at all, and over the purpose of the payment if a payment was made to the employee but the employee claims that it was a &quot;tip&quot; or a payment for something else (e.g. the employee also had a catering side hustle and the employee says it was for catering services). The issue of whether the client made the payment at all may be hard to prove if the payment was made in cash and the employee didn't provide a receipt and will come down to the credibility of the client and employee's testimony at trial. if the payment was made with a check or credit card, bank records will make it an open and shut case on that issue that will probably not be disputed at trial. If the facts reveal that the employee had apparent authority to accept the funds from the client for the contractor firm and that the payment was for work on the project and not something else, then the the payment made by the client to the employee satisfies the client's duty under the contract even if the employee wasn't actually authorized to receive the funds for the contractor firm. So, the client wins and the contractor firm's sole remedy is to sue its employee for misappropriating the client's funds. On the the other hand, if the employee did not have apparent authority to accept the funds from the client, or the payment was for something other than work on the project, or the client fails to prove that the payment was ever made, then the client owes the money to the contracting firm and must pay the contracting firm for the amount due (plus interest, litigation costs and possibly attorneys' fees depending on the terms of the contract). The client may pay that obligation out of separate funds of the client's own, or may authorize a the bank officer to make a draw on the construction loan to pay the amount owed. The construction loan bank of the client wouldn't sue the client or demand payment from the client for the amount that should have been paid to the contractor firm but was instead paid to the employee. It didn't pay money to someone it shouldn't have paid it to unless the client authorized the bank to do so. And, the bank won't pay the contractor without the client/borrower's say so. If the client authorized a draw payment from the construction loan to the employee rather than the contractor firm, the client still owes the bank for what it paid to the employee at the direction of the client (in addition to all other draws on the project), although the client may have a suit against the bank officer for negligence in administering the loan by failing to flag that the payee was wrong (which might lose but isn't a sure loss). The amount owed to the contractor firm proceeds under the analysis set forth above. What If The Facts Are Right? If, improbably, the facts as stating in the question are actually what happened, the client will owe or not owe the contractor money under the same analysis as above. But the client will not have liability to any company that the contractor got a loan from (which would not encumber the client's real estate), since the client has no contractual relationship with the contractor's lender. Post-Script On Double Payment Prevention Laws The question hinges on the unfairness of the client having to possibly pay twice for the same construction work. In some situations, where the general contractor firm is at fault for causing the double payment to happen, the law protects the client from double payment, even though those laws don't apply here. I explain why these laws don't apply below. Basically, the client has to eat the double payment when the double payment occurs because the client screwed up though no fault of the general contractor and the general contractor doesn't benefit from the double payment. Some states have laws designed to prevent property owners, often only residential property owners having work performed on their own residences, from having to double pay for work done in some circumstances. But these laws usually only apply when the client pays the general contractor firm as the client is supposed to, satisfying his contractual obligation, and the general contractor doesn't pay the subcontractor, causing the subcontractor to sue the general contractor for breach of contract and the owner to enforce the subcontractor's mechanic's lien. In those situations, the double payment prevention law eliminates the subcontractor's mechanic's lien rights when the client pays the general contractor in full, and the subcontractor is left only with a lawsuit against the general contractor who didn't pass on the client's or the client's bank's payment to the general contractor for the subcontractor's share of work to the subcontractor. In this case, the double payment laws usually wouldn't apply because the legal issue here is whether the client paid the contractor, or was deceived by the employee into paying someone other than the contractor in an act of conversion/embezzlement/fraud.
It should contain one of the following two clauses: A clause that explicitly lists all of the side projects you are working on at the point of employment, that will not be transferred to the employer's ownership under Section 11 of the Copyright, Designs and Patent Act 1998 (&quot;the Act&quot;) which states (1) The author of a work is the first owner of any copyright in it, subject to the following provisions. (2) Where a literary, dramatic, musical or artistic work, or a film, is made by an employee in the course of his employment, his employer is the first owner of any copyright in the work subject to any agreement to the contrary. (3) This section does not apply to Crown copyright or Parliamentary copyright (see sections 163 and 165) or to copyright which subsists by virtue of section 168 (copyright of certain international organisations). This would mean that your existing side projects are protected, but any future side projects would transfer to your employer under S11(2). This might be fine if you don't intend on doing any more side projects during your employment and simply want to protect your existing work. A clause that explicitly rejects S11(2) of the Act in relation to work undertaken outside of your employment and not on company resources, that is specifically defined as &quot;side projects&quot; (including a non-exhaustive list of examples) and the rebuttable presumption that any such work is outside S11(2) unless proven to the civil standard in a court of law. This provides balance to both sides: the employee is free to pursue their side projects outside of work, but in the event that they work on them in company time and on company resources (e.g. a laptop) the employer is free to rebut that presumption in court and have the work transferred to them. Generally, the second clause seems to be what most employees would want in a contract to protect their side projects. Whether it can successfully be inserted depends on the negotiation between both sides. Most reasonable employers would not refuse it. The leading case on the matter of S11(2) is Penhallurick v MD5 Ltd [2021] EWCA Civ 1770 (02 December 2021) which future courts of first instance are presently bound to follow, unless the Supreme Court issues a different decision. What does &quot;in the course of employment&quot; mean? Per Penhallurick mentioned above, &quot;in the course of employment&quot; is generally held to mean doing things that you are paid for as part of your employment. For example, if you are a baker and you write a novel in your free time, it is clear that has nothing to do with your employment: you are not being paid by the bakery to write novels. However, if you were to write a baking cookbook that incorporated recipes that you developed at the bakery, that could be held to be done &quot;in the course of employment&quot; because the bakery could argue that you are paid to develop new recipes for them. The development of side projects in relation to software development is fraught with peril. A lot of employers will try and advance the argument that, although you did not develop the work using company resources and time, your work is still &quot;connected&quot; to the area they operate in. Well known examples of this include Google asserting ownership of software development side projects that, on the surface of it, aren't done on company time and resources and don't appear to have been done &quot;in the course of employment&quot; as you are not being paid specifically to work on, e.g. game development when you are employed as a website backend engineer. If the employer can present enough evidence that what you are/were working on is &quot;connected&quot; to their business in some fashion, that is (at present, in England and Wales) sufficient for ownership to transfer to them under S11(2) even if the work wasn't done in company time and/or using company resources. An example of a clause that seeks to protect side projects Both Parties agree that Section 11(2) of the Copyright, Designs and Patent Act 1988 (&quot;the Act&quot;) does not apply to any and all Side Projects started prior to the commencement of employment. Both Parties also agree that S11(2) of the Act does not apply to any and all Side Projects started after the commencement of employment, specifically where said Side Projects are unrelated to the Employer's business of area of business. For the avoidance of doubt, &quot;unrelated&quot; has the ordinary meaning that a reasonable person would assign to it. For example, since the Employer operates in area of business, a Side Project regarding the development of an online video game is clearly unrelated to the Employer's business. This ex post presumption is rebuttable on the provision of clear and compelling evidence presented in a competent and validly constituted court of law in England and Wales that the Side Project was developed on company time and/or using company resources (e.g. a laptop) or that it validly infringes upon a business domain the Employer operates in. Both Parties agree that it will not be sufficient to adduce that the Employer &quot;could&quot; seek to operate in the Side Project's domain. For ownership to transfer under S11(2) of the Act, the Employer must demonstrate that they operated in that domain prior to the creation of the Side Project or that the Side Project has taken advantage of company resources that were not legitimately available outside of the company. For example, confidential company know-how that is specific to the Employer and not an industry standard or widely known thing. For the avoidance of doubt, use of open-source software (used in compliance with the licence and regardless of whether that software was created, released, or maintained by the Employer or someone else) does not constitute taking advantage of company resources. The Employer agrees to pay the Employee a sum of special damages assessed and awarded appropriately by a court of law in England and Wales for any attempt to subvert this clause or sue the Employee for a Side Project contrary to this clause. In the alternative, at the Employee's absolute discretion, a permanent injunction enforcing this clause may be awarded against the Employer.
Can anybody create their own license? That is to say, can I for example create my own license under which I can license software? Yep. It's just a contract granting rights to use a copyrighted work. You can write your own contracts, so you can write your own software license. It's just often recommended that you don't, because common licenses are more well-understood, and inexperienced drafters may make errors that could result in problems, such as unintended restrictions, failing to restrict things that were intended to be restricted, or creating provisions that aren't enforceable in some/all jurisdictions. Can you mandate how a software will be released? Yes. Many software licenses, including GPL, do. The restrictions you describe in your example sound similar to CC BY-NC-SA. Also, would the following clause even be legal? Using this software you agree that any work and intellectual property based on or created with this software will be under the [INSERT_NAME_LICENSE] license, even after any and all code from this software is removed in a future update, or even if the work is rebuilt from the ground up I'm not entirely certain, but &quot;even after any and all code from this software is removed in a future update, or even if the work is rebuilt from the ground up&quot; seems, in my opinion, unlikely to be enforceable—especially &quot;even if the work is rebuilt from the ground up.&quot; How would you differentiate a complete rebuild from a totally new piece of software? More broadly, once your copyrighted code is no longer in the product, there's nothing for them to license from you. It's hard to imagine how you'd be able to claim that you're harmed by someone releasing a new version of a product that used to contain your code under a different license. Without harm to you, there's nothing for a court to redress.
The contract between you and the company is for the supply of the goods. How they get them to you is irrelevant; they may have them in stock, or they may order them and ship them on, or they may send an order to the factory to ship them directly to you. There is nothing saying that they have to be in stock anywhere. The law you refer to says that they must ship within 30 days unless they provide a specific date. In effect "shipped within 30 days" is an implicit term in the contract. If after 30 days they have not shipped the goods then you are entitled to rescind the contract (i.e. get your money back). Where things get interesting is if they took your money knowing that they would not be able to ship within 30 days, or at least being reckless (i.e. not caring) about it. It does rather sound like this may be the case. If so then it may rise to the level of fraud, and the FTC or state authorities may take action. Try writing to the FTC. A single event won't get any action, but if they get lots of complaints then they might.
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.