- Is the liquidated damages provision enforceable?
Answer: Yes, because enforceability is judged at the time of contracting, and $50,000 was a reasonable forecast of the likely harm.
This question tests the line between enforceable liquidated damages and an unenforceable penalty. The decisive timing rule: enforceability is judged at contract formation, not at breach. Apply the statute's two conditions from the signing date — (1) harm difficult to estimate and (2) amount a reasonable forecast. At signing, the clinic's historical data showed a typical replacement cost of about $45,000 plus $20,000 in lost revenue during a three-month vacancy. That made future harm genuinely hard to predict, and $50,000 was within a reasonable range of likely loss. The later actual loss of only $12,000, because the clinic efficiently filled the position before Dr. Chen left, does not retroactively make the clause a penalty.
"No, because the Clinic's actual loss was only $12,000" is the classic hindsight trap: actual loss is informative but not the standard. "No, because Dr. Chen's six months' notice let the Clinic avoid a vacancy" similarly focuses on events after breach and on mitigation; a breaching party cannot avoid an agreed liquidated sum merely because the nonbreaching party mitigated. "Yes, because the parties expressly acknowledged that the amount was reasonable, and that acknowledgment is conclusive" overstates the recital: the court independently reviews reasonableness; an acknowledgment is persuasive, not binding. The correct view is the one that measures validity at contracting: $50,000 was a reasonable forecast of likely harm, so the clause is enforceable.
Strategy: on liquidated-damages questions, immediately test "reasonable forecast at the time of contracting" and "difficult to estimate." Whenever an answer relies on actual loss being lower, it is usually the wrong penalty trap.
- Is the Company liable for breach?
Answer: No, because the CEO's approval was not obtained before Marcus performed any work on the website.
When you see a contract question like this, your first job is to identify whether the terms are conditions precedent or mere promises. Here, the contract explicitly lists three strict conditions for outside activity: (i) no competition, (ii) CEO's written approval, and (iii) approval obtained before performing any work. All three must be satisfied, and the contract states that failing any one is a material breach.
The Company is not liable because Marcus failed the timing condition. He worked on the website in January and February, but only sought approval in March. Although the CEO's email is a signed writing and the website did not compete, the contract explicitly requires approval before any work. Since Marcus worked before approval, the Company had Cause to terminate.
Now the wrong answers. The choice saying "Yes, because the website did not compete and the CEO gave written approval before the website launched" conflates "launch" with "work"—the contract requires approval before any work, not before launch. The choice saying "Yes, because after-hours work on his own computer did not violate his duty to devote full working time" ignores the specific contractual approval requirement, which applies regardless of when the work is done. Finally, the choice saying "No, because an email is not a signed writing" is a trap: under modern e-signature laws, a CEO's email can satisfy a writing requirement if it authenticates approval. The issue is timing, not form.
Strategy tip: On bar exam questions, read conditions literally. "Before X" means before X, not before Y. Watch for traps that swap timing thresholds or substitute general principles for explicit contractual conditions.
- Which issue is most significant in resolvingthe bonus dispute?
Answer: Whetherthe company's discharge of the executive excuses her failure to satisfythe continued-employment requirement for the bonus.
When you see a contract dispute where one party's own act prevented the other from satisfying a condition, think of the prevention doctrine: a promisor cannot rely on a condition's failure if that promisor caused the failure. That is exactly the issue here. The contract made continued employment through March 1 a condition of receiving the bonus, but the company discharged her without cause in November. If an employer wrongfully prevents an employee from satisfying a condition, the condition is excused and the employee may treat the bonus as due. So the most significant issue is whether the discharge excuses her failure to meet the continued-employment requirement.
The wrong answer about the bonus being unenforceable as a penalty misses the distinction between a liquidated-damages penalty and a promised employment benefit; a $500,000 bonus is compensation, not a penalty, and the company's actual loss is irrelevant. The answer about recovering the reasonable value of services is also off target: when an enforceable contract exists, the employee normally sues under the contract, not in quantum meruit, especially when the dispute is about an express condition. Likewise, reducing the claim by salary earned in a new position confuses mitigation of damages for wrongful discharge with enforcement of an agreed contractual bonus; and a claim for the bonus, if the condition is excused, is not automatically offset by later earnings.
So your study takeaway: whenever a condition becomes impossible because the other party interfered, ask whether the condition should be excused before jumping to damages, penalty, or quantum meruit theories.
- Which issue is most significant in evaluating Nina's claim?
Answer: Whetherthe contract's description of Nina's position was a binding promise thatthe reassignment breached, justifying her resignation.
When you see a contract claim involving an employment term, separate the liability question from the damages question. The bank's "only for cause" restriction makes Nina's position and duties central: if reassignment was allowed, she has no claim; if it was a breach, she may treat the contract as ended by the bank's conduct.
Here, the key issue is whether the contract's description of Nina as "Senior Vice President of Commercial Lending, responsible for managing the bank's commercial loan portfolio" was a binding promise. If so, the president's reassignment to file-retention work was a material breach, and Nina's resignation could be justified as a constructive discharge. If that language was only aspirational or descriptive, the bank likely did not breach, and Nina resigned without cause.
The bank's "business judgment" in reorganizing is not a defense unless the contract gave it discretion to change her duties. Nina's decision to resign does not automatically bar recovery; an employee may resign and claim damages when the employer's breach is material. And while damages would be reduced by income she could earn in a comparable position, mitigation matters only after liability is established, so it is not the most significant issue here.
Study tip: on employment-contract questions, first ask whether the employer's action breached an express contractual term—especially a job-description promise—before analyzing resignation, cause, or damages.
- Which issue is most significant in determining whetherthe engineer breached the agreement?
Answer: Whetherthe restriction against selling or providing technical support also covers an employee who directs and supervises others who do so.
When you see a restrictive covenant in an employment agreement, first ask what conduct the plain language actually prohibits and whether the employee's new role falls within that scope. Here, the covenant bars the engineer from personally "sell[ing] or provid[ing] technical support" to customers in the 200-mile territory. He does not do either; instead, he supervises the competitor's sales team and sets its pricing. The central interpretive question is whether directing and supervising others who sell is the functional equivalent of selling—whether the restriction covers indirect participation. That is the most significant issue in determining breach.
The former company's need to prove which specific customers stopped buying is a damages or causation question, not a liability question; a breach can occur even without identifiable lost customers. The engineer's post-employment duty of loyalty is not the source of the claim—the express 18-month covenant is, and a former employee generally owes no ongoing duty of loyalty absent such an agreement. Finally, the indemnification clause in the new employment contract may determine who pays for the engineer's defense, but it has no bearing on whether he breached the earlier agreement.
Study tip: read restrictive covenants narrowly and focus on the defined conduct. If a covenant prohibits "selling," ask whether the facts show actual selling or merely assisting, supervising, or enabling sales—courts often decide based on the precise scope of the restriction.
- Is Brianna entitled to the severance payment?
Answer: No, because Brianna's email did not identify the specific condition with particularity, so the notice requirement was not satisfied.
When a question involves a "Good Reason" resignation clause, your first move is to check procedural compliance—notice, specificity, and cure—before analyzing whether the underlying condition actually occurred. Here, the contract required written notice identifying the specific condition "with particularity" within 90 days. Brianna's March 15 email said only "recent changes to my job"—that is vague, not particular. It fails to mention the 15% salary reduction, the reporting change, or any specific trigger. Because her notice was deficient, the company never had an opportunity to cure, and her resignation cannot qualify as for Good Reason, even though the salary reduction itself was clearly material and uncured. So the correct answer is the one stating that her email did not identify the specific condition with particularity.
Why the others fail: The first wrong answer ("Yes, because the 15% reduction...") correctly notes a material reduction but ignores that the notice defect is fatal—the cure period never started. The second ("Yes, because her March 15 email was timely...") mistakes timeliness for sufficiency and invents a waiver; silence doesn't waive a contractual notice requirement. The third ("No, because reporting to a newly hired senior vice president...") reaches the right result but for the wrong reason—the salary reduction alone established a good reason condition, but the notice failure is what defeats her claim.
Strategy tip: On bar exam questions about employment contracts, always parse the notice/cure process step by step. A minor procedural slip can be dispositive, even if the substantive trigger is met.
- Will the Company likely obtain an injunction?
Answer: Yes, because the covenant expressly survives any termination, and under Weller an employer's prior breach does not defeat such a covenant.
Whenever you see a restrictive covenant question, start with the exact contractual language and then apply any controlling precedent. Here, the non-solicitation covenant expressly states it survives "any termination," including termination by the employee. The state's highest court in Weller directly answers the central issue: a covenant with such a survival clause is enforceable even if the employer's material breach caused the resignation, unless it is unconscionable or a severance provision is implicated. No severance provision exists, and the covenant is not unconscionable. Therefore, Jenna remains bound, and the injunction should issue.
The choice saying the Company's material breach excused Jenna from performing reflects a tempting general contract principle, but Weller is more specific and controls: an express survival clause defeats that excuse. The choice claiming a covenant applying after any termination is automatically an unreasonable restraint is also wrong; non-solicitation covenants are evaluated for reasonableness, and this one is not unconscionable under the stated facts. Finally, the answer asserting the car-allowance failure was not a material breach contradicts the passage, which expressly calls it material.
Your takeaway: when a precedent squarely addresses the facts, apply it even if a general rule points elsewhere. On restrictive-covenant questions, watch for "expressly survives" language—it is often the key to enforceability despite an employer's prior breach.
- Which claim is the manager most likely able to bring against the company?
Answer: A claim for breach of contract, based on the president's promise and the manager's continued employment through the closing.
When a case involves a promise conditioned on some future action, start by asking: was there a bargained-for exchange? A contract needs offer, acceptance, and consideration. Here, the president's offer was concrete—stay employed through the closing and receive $50,000—and the manager accepted by doing exactly that. His continued employment was not just a "reliance" step; it was the requested performance, and therefore valid consideration. Even in an at-will workplace, an employee can bargain to stay in exchange for a bonus, so the manager has a strong claim for breach of contract.
The promissory estoppel claim is a trap: estoppel is an equitable fallback for promises made without consideration, but here the exchange itself created an enforceable contract, so the stronger claim is breach of contract, not reliance. The implied covenant of good faith and fair dealing also misses the mark—that duty supplements an existing contract, but it cannot itself create the obligation to pay a bonus when no promise has been made. Finally, restitution would seek the reasonable value of services to avoid unjust enrichment, but it is unavailable when an express contract governs the subject matter; the manager does not need to recover in equity when he can enforce the exact promise.
On the exam, whenever a bonus is promised "if you stay" and the employee stays, treat that as an offer and acceptance supported by consideration. Do not default to promissory estoppel just because employment is at-will.
- Which issue is most significant in determining whether the CFO is entitled to severance?
Answer: Whether the CFO's conduct falls within the agreement's definition of cause and thus relieves the company of the severance obligation.
Whenever you see a question about an employment agreement with a defined term like "cause," your first move should be to look at the contract's actual language. The company's obligation to pay severance is triggered only by a termination "without cause," and the agreement expressly defines cause asthe CFO's felony conviction or intentional embezzlement. So the pivotal issue is whether the CFO's conduct falls within that contractual definition: if it does, the company has no severance obligation; if it does not, the CFO is likely entitled to the 18 months' salary.
That makes the correct answer the one about whether the CFO's conduct falls within the agreement's definition of cause and thus relieves the company of the severance obligation. The new allegation — gross negligence and undisclosed conflict of interest — matters only insofar as it fits that definition, so the key dispute is contractual interpretation.
Now look at the distractors. The choice about whether the CFO's failure to oversee the vendor relationship caused the loss is a tempting but mistaken focus: causation of the loss is not the agreement's test, and negligence is not intentional embezzlement. The choice about wrongful discharge in violation of public policy is also off point because the CFO is seeking the contractual severance benefit, not making a tort claim for wrongful discharge. Finally, the choice about reducing severance by income earned in a new position confuses damages mitigation with entitlement; mitigation would matter only after it is decided that the termination was without cause and severance is owed. The threshold question is always the contract's own definition of cause, so focus your analysis there on similar questions.
- Which legal issue is most significant in evaluating a claim by Priya against the retailer?
Answer: Whether the statements in the employee handbook became part of Priya's employment relationship and limited the retailer's right to end her employment.
When a question involves an employee handbook and an at-will employment agreement, the central issue is usually whether the handbook created a binding contractual promise that limits the employer's right to fire. At-will employment can be modified by an implied contract, and a handbook's language plus an employee's reliance can matter.
Here, Priya signed an offer stating her employment could end at any time, but the later handbook promised discharge only for just cause and required a warning and 30-day cure period. That directly conflicts with at-will employment. The most significant legal issue is whether those handbook statements became part of her employment relationship and restricted the retailer's termination rights. If the handbook is found to be an enforceable promise, her discharge without warning would breach that promise.
The wrong answers each miss that core question. The claim about a breach of the implied covenant of good faith and fair dealing fails because that covenant generally does not override at-will termination; the threshold issue is whether the handbook created a contract in the first place. The wrongful-discharge-in-violation-of-public-policy theory is irrelevant—there is no whistleblowing or refusal to commit an illegal act. And Priya's decision to decline the competitor's offer does not entitle her to recover the compensation she would have earned there; at most, reliance could support promissory estoppel, but the claim would be about enforcing the retailer's promise, not recovering lost wages from a third party.
Study strategy: when a handbook or policy manual appears, ask whether its language promises specific procedures or just describes general practices. Specific, mandatory language plus employee reliance tends to create enforceable rights; vague language does not.
- What is Lena entitled to recover?
Answer: $250,000 reduced by any income Lena actually earned or could have earned with reasonable efforts during the remaining six months.
Whenever a breach-of-contract claim involves an employee's remaining pay, the key is damages, not just liability: the employee may recover the promised balance, but must mitigate. Here the statute tells you exactly what to do: start with the remaining promised compensation, $250,000, and subtract any income Lena actually earned or could have earned with reasonable efforts during the remaining six months. Label's breach excused Lena from the exclusivity clause, so she was legally free to seek other work; because she did not, the court will impute the income she reasonably could have earned and reduce her award accordingly.
The full-$250,000 choice is tempting because the minimum payment was guaranteed, but a guaranteed payment does not eliminate the mitigation requirement. The "nothing because failure to mitigate bars recovery" choice is wrong for the opposite reason: failing to mitigate reduces damages, it does not wipe out a valid claim entirely. Finally, the impossibility choice is wrong because Label's voluntary business decision to suspend projects was not an impossibility; a party cannot escape its contractual obligation simply by choosing not to perform.
Study tip: whenever you see an employee-damages question, think "promised balance minus reasonably avoidable earnings"—and remember that a failure to mitigate is a deduction, not a forfeiture.
- Which of the following is the maximum amount Okafor is entitled to recover?
Answer: $720,000, because the purported for-cause termination did not satisfy §7 and is therefore treated as a termination without Cause; because it occurred within six months after the acquisition, §9 supplies the exclusive remedy of two times base salary.
Whenever a termination package includes both a liquidated payment and an exclusive-remedy clause, resist the instinct to fall back on common-law damages. The contract's own remedy scheme controls. Here, the new owners fired Okafor for poor performance after labeling it "Cause," but §7 expressly says failure to meet performance expectations is not Cause and requires written notice plus a 30-day cure opportunity for willful misconduct. Because neither occurred, the termination is treated as one without Cause. The firing also happened within six months of the acquisition—a Change of Control—so §9 is triggered. That provision awards two times Base Salary, or $720,000, and states it is "in lieu of any amount under §8." Section 12 then makes that the sole remedy, even for a breach-of-contract claim, so no further damages are available.
The $200,000 answer incorrectly treats this as ordinary breach damages for the remaining 18 months and applies mitigation. But the contract displaced those default damages with the exclusive §9 payment. The $90,000 and $50,000 answers both look only at the §8 90-day notice-period payment; the $50,000 version even applies §8's reduction for outside earnings. Yet §9 expressly replaces §8 once a qualifying termination occurs within six months after a Change of Control, and §9 contains no mitigation offset. So mitigation is irrelevant, and the full $720,000 liquidated amount is recoverable.
Study tip: whenever a contract defines a special payment triggered by a specific event, check whether that clause says it is "in lieu of" other payments—that signals exclusivity.
