Seaver v. Ransom

Seaver v. Ransom is a Contracts case about third-party beneficiaries. It holds that a nonparty can enforce a contract when the original parties clearly intended to benefit that person directly.

What is Seaver v. Ransom?

Seaver v. Ransom is a contract-law case that shows when a third party can sue on an agreement even though that person did not sign it. The basic rule is that if the contract was made to directly benefit the third person, that person may have enforceable rights.

That matters because contract law usually binds the people who actually made the deal. Seaver v. Ransom is one of the classic cases that carves out an exception for intended beneficiaries. The court looked at the parties' purpose, not just the fact that someone outside the contract would receive a benefit later.

The big distinction is between an intended beneficiary and an incidental beneficiary. An intended beneficiary is the person the contract was designed to protect or reward. An incidental beneficiary may gain something from the deal, but that benefit is only a side effect, so there is no direct right to enforce.

In Seaver v. Ransom, the court found enough evidence that the contract was meant to benefit the plaintiff directly, so she could enforce it. The case is often used to show that courts read the contract and surrounding circumstances to figure out intent. The words in the agreement matter, but so does the real purpose behind them.

A common way this shows up in class is through a will, family arrangement, or property-related promise where one person promises another that a third person will receive something. If the promise was made for the third person's direct benefit, Seaver v. Ransom supports enforcement. If the benefit is accidental, the third party usually has no claim.

Why Seaver v. Ransom matters in CONTRACTS

Seaver v. Ransom gives you the core rule for third-party beneficiary analysis in Contracts: not every outsider can sue, only the ones the contract was meant to help. That makes it a clean case for spotting the difference between a real legal right and a mere practical benefit.

This case also teaches how lawyers and professors want you to read contract facts. You are not just asking, "Did a third person get something out of the deal?" You are asking, "Did the parties intend to create an enforceable benefit for that person?" That question shows up in issue-spotting, short answers, and case discussion.

It also connects to broader contract themes like intent, enforcement, and who counts as a protected party. Once you see Seaver v. Ransom, it becomes easier to explain why some nonparties can sue while others cannot, even when both seem affected by the same agreement.

In practice, the case helps you argue from facts. Words that name the third person, direct promises to pay or transfer property, and clear purpose language all point toward enforceability. Loose or indirect benefit language usually points the other way.

How Seaver v. Ransom connects across the course

Third-Party Beneficiary

This is the broader doctrine that Seaver v. Ransom illustrates. The case is a classic example of when a nonparty gets rights under a contract because the promise was made for that person’s direct benefit. If a question asks whether someone outside the contract can sue, this is the main concept you reach for.

Intent to Benefit

Seaver v. Ransom turns on intent. The court looked for a clear purpose to benefit the third person, not just a lucky side effect. When you analyze a fact pattern, this is the evidence you hunt for, like direct language in the agreement or facts showing the promise was made for that person.

Contractual Rights

The case shows that contractual rights are not always limited to the signers. If the contract creates enforceable rights for an intended beneficiary, that person can sometimes demand performance or sue for breach. This helps separate ordinary contract parties from outsiders who still have legal standing under the agreement.

Release

A release can affect whether a beneficiary’s rights survive or get cut off, depending on the type of beneficiary and the contract structure. After you identify a third-party beneficiary, the next question may be whether the original parties still had power to change or cancel the promise. That makes release a useful follow-up issue.

Is Seaver v. Ransom on the CONTRACTS exam?

A case ID question may give you a fact pattern about a promise made for someone who was not at the table, and you have to decide whether that person can enforce it. The move is to name Seaver v. Ransom, then explain that the right turns on clear intent to benefit the third party. If the facts show a direct promise for that person’s benefit, you argue intended beneficiary. If the person only gets an accidental benefit, you reject enforcement. In a cold-call or essay response, use the case to support standing, breach, or remedy analysis when a nonparty tries to sue.

Seaver v. Ransom vs Third-Party Beneficiary

Students sometimes treat Seaver v. Ransom and third-party beneficiary as the same thing. Third-party beneficiary is the doctrine, while Seaver v. Ransom is a leading case that helps explain the doctrine and its intent requirement. If you need the rule, use the concept. If you need support for the rule, use the case.

Key things to remember about Seaver v. Ransom

• Seaver v. Ransom is a Contracts case about when a nonparty can enforce an agreement.

• The central rule is that the third person must be an intended beneficiary, not just someone who happens to benefit.

• Courts look for clear intent to benefit the third party, often from the contract language and surrounding facts.

• The case is a standard way to separate enforceable third-party rights from incidental benefits.

• If a fact pattern gives you a promise made for someone else's direct benefit, Seaver v. Ransom is the case to cite.

Frequently asked questions about Seaver v. Ransom

What is Seaver v. Ransom in Contracts?

Seaver v. Ransom is a contract case about third-party beneficiaries. It stands for the idea that a person who was not a signer can still enforce the contract if the original parties clearly meant to benefit that person directly.

What does Seaver v. Ransom say about third-party beneficiaries?

It says a third party can have enforceable rights when the contract was made for that person's benefit. The important part is intent, not just whether the person received some advantage from the deal.

How is an intended beneficiary different from an incidental beneficiary?

An intended beneficiary is the person the contract was designed to benefit, so they may be able to sue. An incidental beneficiary only gets a side benefit from the deal, and that usually does not give them enforcement rights.

How do I spot Seaver v. Ransom in a fact pattern?

Look for a promise made to secure something for a specific third person, especially when the agreement shows the person was the point of the contract. If the benefit is direct and deliberate, Seaver v. Ransom supports enforcement by that third person.