Contracts generally bind and benefit only the parties who signed them -- a rule known as privity of contract. Third-party beneficiary doctrine is the recognized exception: it lets someone who never signed the contract, and who may not even have known about it when it was formed, sue to enforce a promise made for that person's benefit. The doctrine solves a real problem, because contracts are routinely written with a non-party's benefit specifically in mind -- a life insurance policy naming a beneficiary, a construction contract requiring payment to a subcontractor, a settlement agreement providing for a payment to someone outside the litigation.

The entire doctrine turns on a single classification question: was this particular non-party an intended beneficiary of the promise, or merely someone who happens to benefit incidentally from the contract's performance without the parties having specifically meant to benefit them. Only an intended beneficiary gets enforceable rights. Getting this classification wrong is the most common way third-party beneficiary claims fail.

Restatement (Second) of Contracts Section 302 asks whether recognizing the beneficiary's right to performance is appropriate to effectuate the parties' intention, and whether either the performance will satisfy an obligation the promisee owed the beneficiary (a creditor beneficiary, under older terminology) or the circumstances indicate the promisee intended to give the beneficiary the benefit of the promised performance as a gift (a donee beneficiary). Modern Restatement usage collapses both into the single category of intended beneficiary.

The key evidence is usually the contract's own language -- does it name the beneficiary, direct payment or performance specifically to them, or otherwise make plain that the parties meant to confer a direct benefit on that person, as opposed to the beneficiary simply standing to gain if the contract happens to be performed well. Courts look to the contract as a whole and the circumstances of formation, not just a single clause in isolation.

An incidental beneficiary is someone who benefits from a contract's performance purely as a side effect, without the contracting parties having specifically intended to benefit them. A homeowner in a neighborhood might benefit if a city contracts with a developer to build a park nearby, raising property values -- but that homeowner is not an intended beneficiary of the city-developer contract and cannot sue to enforce it. The same is often true of a general public that benefits diffusely from a government contract's performance.

The line can be genuinely close in commercial settings -- a subcontractor on a construction project, for instance, is often an incidental beneficiary of the general contract between the owner and general contractor (even though the subcontractor's work depends on that contract existing) unless the contract's language specifically identifies the subcontractor as someone the parties meant to directly benefit, such as through an express payment-to-subcontractor provision.

Even an intended beneficiary's rights are not permanent from the moment the contract is signed. Under Restatement Section 311, the original contracting parties generally retain the power to modify or rescind the contract, cutting off the beneficiary's rights, until the beneficiary's rights vest -- which typically happens when the beneficiary manifests assent to the promise in a manner invited by the parties, brings suit to enforce it, or materially changes position in justifiable reliance on it. Before vesting, the beneficiary is at the mercy of the contracting parties' continued cooperation.

Defendants resist third-party beneficiary claims by arguing the plaintiff is merely incidental rather than intended, that the contract's language does not clearly show an intent to benefit that specific person, that the beneficiary's rights had not yet vested when the contract was modified or terminated, or that the promisor retains against the beneficiary any defense it would have had against the promisee under the original contract.

In Juricratic, third-party beneficiary status is modeled as a threshold standing gate that must clear before any of the underlying contract-breach elements matter at all -- an incidental beneficiary's claim ends at that gate regardless of how strong the breach itself would otherwise look, so it is the highest-leverage node to war-game first in any case brought by a non-signatory.

A user can sweep the dial on how clearly the contract's language and circumstances indicate an intent to benefit the plaintiff specifically, and separately on whether the plaintiff's rights had vested before any modification or termination the defendants raise, to see how the modeled strength of the claim shifts between viable intended-beneficiary status and a dead-end incidental-beneficiary classification. These are simulation inputs for stress-testing standing, not predictions of how a court will classify any particular plaintiff.