You’re staring at an MBE question where someone who wasn’t part of the original contract is trying to sue on it. Your gut says “third-party beneficiary,” but then you freeze—was this person an intended beneficiary with enforceable rights, or just an incidental beneficiary who gets nothing? This distinction trips up more bar examinees than almost any other Contracts issue, and it shows up repeatedly on the MBE.
Why Third-Party Beneficiary Questions Are MBE Favorites
The examiners love third-party beneficiary problems because they test multiple skills at once: contract formation, contract rights, and the nuanced line between someone who can enforce a promise and someone who just happens to benefit from it. You’ll see these questions in straightforward “Can X sue?” formats, but also embedded in longer fact patterns about construction contracts, insurance policies, and family arrangements.
The core concept is simple enough. When two parties make a contract, they can create enforceable rights in a third party who wasn’t at the bargaining table. But not every third party who benefits from a contract gets to sue on it. The law distinguishes between intended beneficiaries (who have enforceable rights) and incidental beneficiaries (who have no rights, even if they benefit).
The Intended Beneficiary: Two Types You Must Know
An intended beneficiary is a third party whom the contracting parties specifically intended to benefit when they made their agreement. The contract must be made for the purpose of benefiting that third party. If you establish intended beneficiary status, that person has the right to sue to enforce the contract.
Intended beneficiaries come in two flavors, and the MBE tests both:
Creditor beneficiaries exist when the promisee (the person receiving the promise) owes an obligation to the third party, and the contract is made to satisfy that obligation. The classic example: Alice owes Ben five thousand dollars. Alice then contracts with Carol, who promises to pay Ben the five thousand dollars. Ben is a creditor beneficiary of the Alice-Carol contract and can sue Carol directly if Carol doesn’t pay.
Donee beneficiaries exist when the promisee intends to make a gift to the third party through the contract. The promisee doesn’t owe the third party anything—they just want to benefit them. Think life insurance: A father buys a life insurance policy naming his daughter as beneficiary. The daughter is a donee beneficiary of the contract between father and insurance company. She can sue the insurer if it refuses to pay the death benefit.
The modern approach (followed by the Restatement and tested on the MBE) simplifies this by asking whether the third party is an intended beneficiary, without requiring you to label them as creditor or donee. But understanding both categories helps you spot the patterns.
The Intent Requirement: How to Spot an Intended Beneficiary
Here’s where students get stuck. How do you prove the contracting parties intended to benefit the third party? The MBE will give you clues:
Direct identification in the contract. If the contract explicitly names the third party or describes them specifically (“the promisee’s daughter,” “the City of Springfield”), that’s strong evidence of intent to benefit. When the contract says “Builder shall construct the swimming pool for Owner’s son,” the son is almost certainly an intended beneficiary.
Performance runs directly to the third party. If the promised performance goes straight to the third party rather than to the promisee, that suggests intent. In the life insurance example, the insurance company doesn’t pay the father (he’s dead)—it pays the daughter directly.
The third party’s rights vest. Once an intended beneficiary’s rights vest, they become permanent. Rights vest when the beneficiary: (1) learns of the contract and assents to it, (2) detrimentally relies on it, or (3) brings suit to enforce it. After vesting, the original parties cannot modify or rescind the contract to eliminate the beneficiary’s rights without the beneficiary’s consent.
Here’s a typical MBE setup: “Homeowner contracted with Contractor to build a garage on Homeowner’s property. The contract specified that all work must be completed ‘to the satisfaction of Homeowner and his neighbor, Neighbor, whose property adjoins the construction site.’ Contractor failed to complete the work. Can Neighbor sue Contractor for breach?”
Your analysis: Was Neighbor an intended beneficiary? The contract mentions Neighbor by description, but what was the purpose? If the language about Neighbor’s satisfaction was included merely to avoid nuisance claims or maintain good relations, Neighbor is probably incidental. But if the contract shows Homeowner specifically bargained for Neighbor’s approval as part of the performance, Neighbor might be intended. The MBE will give you more facts to make this determination—look for whether performance actually runs to the third party or whether they’re just affected by it.
The Incidental Beneficiary: Benefits Without Rights
An incidental beneficiary is someone who benefits from a contract but whom the contracting parties did not intend to benefit. Incidental beneficiaries have zero enforceable rights. They cannot sue for breach, even if the breach harms them economically.
The classic example is a government contract. City contracts with Builder to construct a new highway. Local businesses will benefit from increased traffic. Are the businesses intended beneficiaries who can sue if Builder breaches? No. They’re incidental beneficiaries. The contract was made to benefit the City and the public generally, not to create enforceable rights in every business owner who might profit from the highway.
Here’s the key distinction: If the third party would benefit only as an indirect consequence of performance, they’re incidental. If the contract was made for the purpose of directly benefiting them, they’re intended.
Consider this fact pattern: “Hospital contracted with Medical Supply Company for delivery of surgical equipment. Doctor, who practices at Hospital, would benefit from having the new equipment available. Medical Supply Company failed to deliver. Can Doctor sue Medical Supply Company?”
Doctor is an incidental beneficiary. The contract was made to benefit Hospital, not to create rights in individual doctors. Doctor benefits only as a consequence of Hospital’s contract. No enforceable rights exist.
The Government Contract Exception
Government contracts deserve special attention because they appear frequently on the MBE in third-party beneficiary questions. The general rule: Members of the public are presumed to be incidental beneficiaries of government contracts, even when those contracts are designed to benefit the public.
Why? If every citizen could sue as a third-party beneficiary whenever the government’s contractor failed to perform, the courts would be flooded with litigation. The government entity itself has adequate incentive to enforce the contract, and individual citizens have no special relationship requiring direct enforcement rights.
Exception to the exception: A member of the public may be an intended beneficiary if the contract explicitly identifies a particular person or small, defined group and manifests an intent to benefit them directly. For example, if City contracts with Security Company to provide armed guards at City Hall “to protect the Mayor,” the Mayor might be an intended beneficiary. But if the contract is “to protect City Hall and its occupants,” occupants are incidental.
Who Can Sue Whom? Sorting Out the Parties
Once you’ve identified an intended beneficiary, you need to know who has rights against whom. This gets tested in multi-part MBE questions.
The intended beneficiary can sue the promisor (the party who made the promise to perform). This is the beneficiary’s primary right. Using our earlier example, Ben (creditor beneficiary) can sue Carol (promisor) if Carol doesn’t pay.
The intended beneficiary can also sue the promisee in certain circumstances. A creditor beneficiary can sue the promisee on the original underlying obligation. Ben can sue Alice on the original debt if Carol doesn’t pay. A donee beneficiary generally cannot sue the promisee because the promisee owes them nothing—it was intended as a gift.
The promisee can sue the promisor for breach. Alice can sue Carol if Carol doesn’t perform. However, the promisee’s recovery is limited. If the beneficiary has already recovered from the promisor, the promisee cannot recover again (no double recovery). The promisee might recover nominal damages or specific performance.
The promisor can raise against the beneficiary any defense the promisor has against the promisee arising from the contract itself. If the contract between Alice and Carol is void for lack of consideration, Carol can raise that defense when Ben sues. But the promisor generally cannot raise defenses from the underlying obligation between the promisee and beneficiary—those are separate.
Common MBE Traps and How to Avoid Them
Trap #1: Assuming anyone who benefits is an intended beneficiary. Remember, the benefit must be the purpose of the contract, not just a consequence. If you benefit only because someone else is getting what they bargained for, you’re incidental.
Trap #2: Confusing third-party beneficiaries with assignments. These are different concepts. A third-party beneficiary’s rights arise at the moment the contract is made. An assignment transfers rights after the contract already exists. If the question says “A transferred his rights under the contract to C,” that’s an assignment, not a third-party beneficiary situation.
Trap #3: Forgetting about vesting. Before rights vest, the original parties can modify or rescind the contract without the beneficiary’s consent. After vesting, they cannot. The MBE loves to test whether a modification was valid based on whether the beneficiary’s rights had already vested.
Trap #4: Applying the wrong standard to government contracts. Don’t assume members of the public are intended beneficiaries just because a government contract is designed to help the public. Apply the presumption that they’re incidental unless the facts clearly indicate otherwise.
Putting It All Together: A Sample Analysis
Let’s work through a complete example:
“Father, who owed Son ten thousand dollars, contracted with Nephew, promising to pay Nephew five thousand dollars if Nephew would pay Son the ten thousand dollars Father owed him. Nephew agreed but failed to pay Son. Son sued Nephew for breach of contract. Will Son prevail?”
Step 1: Identify the parties. Father is the promisee. Nephew is the promisor. Son is the third party.
Step 2: Determine if Son is an intended beneficiary. The contract was made for the purpose of satisfying Father’s debt to Son. Performance (payment) runs directly to Son. Son is specifically identified. This makes Son an intended beneficiary—specifically, a creditor beneficiary.
Step 3: Can Son sue Nephew? Yes. An intended beneficiary can sue the promisor for breach. Nephew promised to pay Son and failed to perform.
Step 4: Consider defenses. Can Nephew raise any defenses? Nephew can raise defenses arising from the Father-Nephew contract (like lack of consideration or fraud in that contract). But Nephew cannot raise defenses from the underlying Father-Son debt.
Conclusion: Son will prevail against Nephew for breach of contract.
What You Need to Memorize for Test Day
When you see a third-party beneficiary question on the MBE, run through this checklist:
For intended beneficiary status: (1) Did the contracting parties intend to benefit this third party (not just as a side effect)? (2) Is the third party identified in the contract or clearly described? (3) Does performance run directly to the third party?
For creditor vs. donee: (1) Does the promisee owe an obligation to the third party? If yes, creditor beneficiary. (2) Is the promisee making a gift to the third party? If yes, donee beneficiary.
For vesting: Rights vest when the beneficiary (1) learns of and assents to the contract, (2) detrimentally relies, or (3) brings suit. After vesting, modification requires beneficiary consent.
For government contracts: Presume members of the public are incidental beneficiaries unless the contract explicitly identifies them and manifests intent to benefit them directly.
For incidental beneficiaries: They have no enforceable rights, period. Doesn’t matter how much they benefit or how much the breach harms them.
The distinction between intended and incidental beneficiaries is entirely about the contracting parties’ purpose. Ask yourself: Was this contract made in order to benefit this third party, or does this third party simply benefit because the contract was performed? That question unlocks most MBE third-party beneficiary problems.
If you want all the contract formation rules, third-party beneficiary elements, and assignment distinctions organized in one place for active recall, FlashTables covers this in the Contracts subject. The two-column format makes it easy to test yourself on the elements of intended beneficiary status and the vesting requirements without flipping through scattered outlines. When you’re facing down 1,800 MBE rules across seven subjects, having third-party beneficiary law consolidated into testable elements saves you time you don’t have.
Master the intent analysis, know your creditor versus donee patterns, and remember that incidental means no rights. Get these distinctions down cold, and you’ll confidently handle every third-party beneficiary question the MBE throws at you.