Tribal Sovereign Immunity in Business Contracts

A tribal business contract should answer three questions before anyone signs it: Which legal entity is bound? What disputes may be heard, where, and under what law? What remedy may actually be enforced against which assets? If the agreement leaves those questions to boilerplate, the parties may discover after a default that they made very different deals.

The Baseline: Immunity Reaches Commercial Contracts

In Kiowa Tribe of Oklahoma v. Manufacturing Technologies, Inc., the United States Supreme Court held that tribal sovereign immunity applied to a contract suit involving commercial conduct away from the reservation. The Court described the rule as applying to governmental and commercial activity, on and off Indian land, unless Congress authorizes the suit or the tribe waives immunity.

That baseline matters at the beginning of negotiations. A counterparty should not assume that an ordinary contract remedy is enforceable against a tribe. A tribe should not assume that calling an entity “commercial” automatically separates it from immunity. Entity status, governing documents, purpose, control, finances, and controlling law all require review.

For a broader explanation, see our tribal-immunity guide.

What C & L Enterprises Actually Decided

A tribal waiver cannot be implied; it must be unequivocally expressed. That does not mean the contract must use one talismanic sentence.

In C & L Enterprises, Inc. v. Citizen Band Potawatomi Indian Tribe of Oklahoma, the Tribe proposed a standard American Institute of Architects contract. The agreement required arbitration, selected Oklahoma law, and provided that an arbitration award could be entered in any court having jurisdiction. Read together, those provisions made the Tribe amenable to state-court enforcement of the award.

C & L does not hold that every arbitration clause, state-law clause, or forum clause independently waives immunity. It shows why the full dispute-resolution package must be read as a whole. A clause that looks routine in isolation may become an express waiver when combined with consent, enforcement, and jurisdiction language.

Step 1: Identify the Exact Contracting Party

The first page and signature block should use the entity's full legal name and legal form. Counsel should confirm:

• Whether the party is the tribal government, a federally chartered Section 17 corporation, a tribal corporation, a limited liability company, an authority, or a subsidiary
• Which charter, ordinance, operating agreement, or other organic document governs
• Whether the entity shares the tribe's immunity under controlling law
• Who has authority to approve the agreement and any waiver
• Whether a board, council, committee, or regulator must act
• Whether an authorizing resolution should be attached

Do not treat similar names as interchangeable. An operating company may hold project assets while the tribal government owns neither the contract nor the revenue stream. Conversely, an entity may share tribal immunity even though it conducts business. Our tribal-business formation guide explains why structure matters.

Step 2: Define the Waiver Instead of Saying “The Tribe Waives”

If a waiver is part of the deal, it should answer:

1. Who waives? Name only the entity with authority to grant the waiver.
2. For which claims? Limit the waiver to defined claims arising from the agreement.
3. In favor of whom? Decide whether affiliates, assignees, lenders, employees, and third-party beneficiaries are included.
4. For how long? State whether the waiver survives termination and for what period.
5. In which forum? Identify the court or arbitration process and any required tribal remedies.
6. For which remedies? Address damages, specific performance, injunctive relief, fees, interest, and remedy caps.
7. Against which assets? Identify available revenue or project assets and preserve protected governmental assets.
8. For enforcement too? Separately address confirmation, judgment, attachment, and execution.

A limited waiver is not a sign that sovereignty is unimportant. It is an exercise of sovereignty: the authorized tribal entity decides exactly how far consent extends. Our article on waiving sovereignty as sovereignty develops that point.

Step 3: Separate Forum, Governing Law, and Enforcement

These clauses solve different problems:

• Forum identifies where a dispute begins.
• Governing law identifies the substantive rules used to interpret the agreement.
• Arbitration language identifies who decides the dispute and under which procedure.
• Enforcement language identifies where and how an award or judgment may be confirmed and collected.

A tribal court can apply agreed nontribal law. A state or federal court can be asked to interpret tribal law. Choosing one does not automatically choose the other.

If tribal law governs, identify the relevant code or body of law and address whether later amendments apply. Do not leave the contract vulnerable to an argument that one party may change the bargain unilaterally after execution. If state law governs selected commercial questions, define those questions and preserve federal Indian law, immunity, and tribal law where intended.

When tribal court is selected, address service, appellate review, exhaustion, and recognition of the resulting judgment. When arbitration is selected, specify the administrator or rules, seat, arbitrator qualifications, governing law, provisional relief, confidentiality, allocation of costs, and courts authorized to confirm an award.

Step 4: Treat Remedies and Executable Assets as Their Own Negotiation

Consent to adjudication does not necessarily waive immunity from attachment or execution. The contract should say whether recovery is limited to:

• Insurance proceeds
• Project revenues
• A defined reserve account
• Assets owned by the contracting enterprise
• A stated dollar cap or contract amount

It should also identify excluded assets, such as tax revenue, trust property, restricted funds, governmental accounts, and property used for essential services, when applicable. Those exclusions must match the entity's actual structure and the governing law.

A lender or contractor needs a remedy it can understand. The tribe needs to know that a commercial default will not expose unrelated governmental assets. Precision serves both sides.

Step 5: Confirm Guarantees and Security

A guaranty by the tribe is not the same as a personal guaranty by an officer, and neither is the same as a guaranty by a parent enterprise. The document should identify the guarantor, authority, consideration, waiver scope, available assets, and enforcement process.

Security interests, revenue pledges, lockboxes, and limited-recourse structures also require coordination with tribal law, federal restrictions, existing debt, and the immunity provisions. Do not promise collateral that the contracting entity does not own or cannot legally encumber.

Step 6: Screen for Federal Approval Under 25 U.S.C. § 81

25 U.S.C. § 81 provides that an agreement with an Indian tribe that encumbers Indian lands for seven or more years is not valid unless it bears the approval of the Secretary of the Interior or the Secretary's designee, subject to the statute and implementing rules.

The implementing regulations in 25 C.F.R. Part 84 define key terms, describe exemptions, and govern the approval process. Not every long-term tribal contract encumbers Indian land. But leases, management rights, exclusive-use provisions, financing restrictions, and development agreements should be screened before execution. Approval is a validity issue, not a paperwork item to investigate after a dispute begins.

Other transactions may require separate federal, tribal, lender, or regulatory approvals. Section 81 is one checkpoint, not a complete approvals list.

A Practical Pre-Signature Checklist

• Confirm the entity's legal name, form, ownership, and immunity status.
• Review the charter, ordinance, operating agreement, and waiver authority.
• Obtain the required resolution or approval in the form the governing law requires.
• Define claims, parties, forum, law, procedure, and waiver duration.
• Separate consent to suit from consent to confirmation, attachment, and execution.
• State the remedy cap and the only assets or revenues available.
• Coordinate insurance, indemnity, defense, and additional-insured provisions.
• Define assignment, lender, affiliate, and third-party-beneficiary rights.
• Address service, notice, exhaustion, appellate review, and judgment recognition.
• Screen land-related and long-term agreements under 25 U.S.C. § 81 and 25 C.F.R. Part 84.
• Make sure sovereignty protections appear in the final signed agreement, not only in a term sheet or side letter displaced by the integration clause.

Frequently Asked Questions

Can a tribe waive sovereign immunity by contract?

Yes, if the authorized tribe or tribal entity unequivocally expresses the waiver. The scope depends on the contract language and authority. C & L shows that arbitration, governing-law, and enforcement terms can operate together as a clear waiver.

Does a waiver allowing suit expose every tribal asset?

Not automatically. Immunity from suit and immunity from attachment or execution are distinct questions. The agreement should identify remedies and executable assets expressly rather than leave them to inference.

Does selecting state law automatically waive immunity?

Not necessarily. A governing-law clause identifies substantive law; a waiver identifies consent to adjudication. But the whole contract must be read together, and combined clauses can express a waiver as C & L demonstrates.

Who may approve a waiver?

That depends on the tribe or entity's constitution, charter, code, ordinance, operating documents, and resolutions. A signature from someone without the required authority may create a serious enforceability dispute.

Must every tribal contract receive federal approval?

No. Section 81 addresses agreements with a tribe that encumber Indian lands for seven or more years, subject to statutory and regulatory definitions and exemptions. Other approval regimes may apply to other transactions.

Should every dispute stay in tribal court?

There is no universal answer. A tribal forum may best protect jurisdiction and institutional interests. Some transactions use arbitration or another forum. The decision should be deliberate and coordinated with law, waiver, remedies, and enforcement—not inherited from a nontribal template.

At Addison Law, our tribal economic-development practice and commercial-contracts counsel help tribal governments and entities structure enforceable agreements while preserving the protections they intend to keep.

This article is for general information only and is not legal advice. Tribal contracting rules vary by entity, governing law, transaction, and jurisdiction.

Primary federal authority reviewed July 13, 2026: Kiowa, C & L Enterprises, 25 U.S.C. § 81, and 25 C.F.R. Part 84.