Table of Contents >> Show >> Hide
- The Big Moment: Nevada Says “Registered Agent ≠ General Jurisdiction”
- General vs. Specific Jurisdiction (The 90-Second Version That Won’t Hurt)
- Where Mallory Fits (And Why Nevada Didn’t Follow It)
- So What Did the Nevada Supreme Court Actually Limit?
- Why Businesses Should Care (Even If You Don’t Have a Trust Fund… Yet)
- Concrete Examples: What This Looks Like in the Real World
- Practical Takeaways for In-House Counsel and Business Owners
- FAQ: The Questions People Ask Right After They Google “General Jurisdiction Nevada”
- Conclusion: Nevada Draws a Bright Line (And Businesses Benefit From Clarity)
- Field Notes: of Practical Experience Around Jurisdiction Fights
If you run a business that operates in multiple states, you’ve probably had this vague fear in the back of your mind: “What if I get sued anywhere just because my company paperwork exists there?” You knowlike being invited to a party you didn’t RSVP to, but still getting assigned cleanup duty.
Nevada’s highest court just delivered some comforting news for companies worried about being hauled into Nevada courts for disputes that have nothing to do with Nevada. In a decision involving a trust dispute and a nationally chartered bank, the Nevada Supreme Court emphasized a modern, due-process-friendly rule: general jurisdiction isn’t a souvenir you automatically pick up just by registering to do business or appointing a registered agent.
Translation: Nevada is not handing out “Congrats, you exist herenow you can be sued here for literally anything” trophies. And for businesses trying to manage litigation risk (and sleep), that matters.
The Big Moment: Nevada Says “Registered Agent ≠ General Jurisdiction”
The headline takeaway comes from In re: Richard H. Goldstein Irrevocable Trust, a case where a Nevada resident tried to bring a trust dispute into Nevada court even though the trust administration lived elsewhere. The trustee was Bank of America, a national bank administering the trust from Missouri.
The petitioner’s playbook had two bold moves:
- Move 1: Argue Nevada could decide the dispute through “in rem” trust jurisdiction under Nevada’s trust statute.
- Move 2: Argue the trustee bank had effectively consented to being sued in Nevada because it appointed a registered agent in the state (a standard requirement for doing business).
Nevada’s high court wasn’t buying it. The court’s reasoning (simplified) goes like this: if the trustee is a necessary and indispensable party, the court can’t sidestep personal jurisdiction requirements just by labeling the case “in rem.” And as for consent-by-registration? Nevada’s statutes cut the other way.
Why the Trustee Issue Matters (Yes, Even If You Don’t Care About Trusts)
The court emphasized that a trustee isn’t decorative. The trustee is the entity charged with administering the trust and carrying out the settlor’s intent. If the court interprets a trust’s no-contest clause (or any key administrative provision), the trustee’s rights and duties are directly impacted.
That means the trustee must be in the caseand the forum must have personal jurisdiction over the trustee. Nevada pointed to the constitutional baseline: due process still applies. Calling something “in rem” doesn’t grant a magical immunity cloak against minimum contacts analysis.
The Statutory One-Two Punch: NRS 14.020 vs. NRS 77.440
Businesses often appoint a registered agent because state law requires it. Nevada’s registered agent requirement appears in NRS 14.020. The attempted leap was: “If you must appoint an agent, that must mean you consent to jurisdiction.”
But Nevada has another statuteNRS 77.440that essentially says: appointing (or maintaining) a registered agent in Nevada does not, by itself, create a basis for personal jurisdiction. The court treated that as a clear legislative signpost.
Bottom line: Nevada’s statutory scheme does not turn routine registration compliance into automatic all-purpose jurisdiction.
General vs. Specific Jurisdiction (The 90-Second Version That Won’t Hurt)
Personal jurisdiction is the court’s authority over a defendant. For businesses, two categories dominate:
General Jurisdiction: “You’re at Home Here”
General jurisdiction means a company can be sued in a state for basically any claimeven one unrelated to that state. The U.S. Supreme Court dramatically narrowed this concept in Daimler, explaining that corporations are typically “at home” in their state of incorporation and where they have their principal place of business.
For most companies, “we sell stuff there” or “we have branches there” is not the same as “we live there.” (If it were, your favorite sandwich shop would own your mailing address.)
Specific Jurisdiction: “This Lawsuit Connects to What You Did Here”
Specific jurisdiction is case-by-case. The claim must arise out ofor at least “relate to”the defendant’s contacts with the forum. The Supreme Court’s Ford decision reinforced that the relationship can be close even if there isn’t a strict causal chain, but there must be a meaningful connection between the forum contacts and the lawsuit itself.
Nevada’s high court applied that spirit: even if a business has a substantial presence in Nevada, the dispute still needs to tie back to Nevada contacts for specific jurisdiction to work.
Where Mallory Fits (And Why Nevada Didn’t Follow It)
If you’ve been following jurisdiction nerd news (no judgmentsome people do CrossFit, others do civil procedure), you’ve heard of Mallory v. Norfolk Southern.
In Mallory, the U.S. Supreme Court addressed a Pennsylvania statute that explicitly treated corporate registration as consent to general jurisdiction. The Court allowed that scheme to survive a due process challengeunder that specific statute and set of factsreviving a controversial “consent by registration” theory.
So why didn’t Nevada copy/paste that logic? Because Nevada’s statute doesn’t do what Pennsylvania’s does. Pennsylvania’s law contained express language linking registration to general jurisdiction. Nevada’s laws do not. In fact, Nevada has NRS 77.440 telling courts not to treat registered agents as a standalone jurisdiction hook.
The Nevada Supreme Court effectively said: “Mallory involved a statute that wears its consent-to-general-jurisdiction badge on its sleeve. Ours doesn’t. Also, ours literally says the opposite.” That’s not a subtle differenceit’s a different sport.
So What Did the Nevada Supreme Court Actually Limit?
This decision is best understood as a strong boundary marker on general jurisdiction over businesses in Nevada. It reinforces three practical limits:
- Registration alone won’t do it: appointing a registered agent in Nevada doesn’t automatically create general jurisdiction.
- Presence isn’t enough when the claim is elsewhere: even significant Nevada operations won’t create specific jurisdiction if the lawsuit is about activities in another state.
- “In rem” can’t dodge due process: a statutory grant that lets courts address certain property-related matters doesn’t erase the need for personal jurisdiction over necessary parties.
In the Goldstein trust dispute, the court found the key trust administration activity was centered in Missouri, not Nevada. The bank’s Nevada footprint (branches, ATMs, general business presence) didn’t create a lawsuit-specific connection to the trust controversy.
Why Businesses Should Care (Even If You Don’t Have a Trust Fund… Yet)
This isn’t just “trust law drama.” It’s about litigation exposure for any company doing business in Nevadawhich includes a lot of companies. Nevada is a major commercial jurisdiction, and it’s also a popular state for incorporation and entity formation.
If corporate registration automatically created general jurisdiction, multistate companies could be sued in Nevada over disputes that happened anywhere: a Florida contract fight, a Midwest product claim, a New York employment disputeyou name it. That would incentivize aggressive forum shopping and raise defense costs, settlement pressure, and uncertainty.
Nevada’s decision signals a more restrained approach: companies should generally face general jurisdiction where they are truly “at home,” not wherever they have filed paperwork.
Concrete Examples: What This Looks Like in the Real World
Example 1: The “We Registered in Nevada, So See You in Court” Attempt
Imagine a Delaware corporation headquartered in Illinois. It registers to do business in Nevada, appoints a registered agent, and runs a small sales office in Las Vegas. A dispute arises from a supply contract negotiated and performed entirely in Texas.
Under the Nevada Supreme Court’s approach, a plaintiff can’t simply say, “You registered in Nevada, therefore general jurisdiction.” Unless Nevada is the company’s home base (or the contract dispute is tied to Nevada conduct), Nevada courts should not be a default landing pad.
Example 2: Specific Jurisdiction Still Has Teeth
Flip it: if that same company markets a product heavily in Nevada, sells it to Nevada consumers, and the Nevada sales or conduct relate to the claim, specific jurisdiction may be appropriate. The decision doesn’t create a corporate forcefield. It just stops plaintiffs from using registration as a universal remote control for jurisdiction.
Practical Takeaways for In-House Counsel and Business Owners
1) Keep Calm and Keep Your Registered Agent (Probably)
This decision doesn’t mean registered agents don’t matter. They matter a lot for service of process and compliance. It just means Nevada won’t treat a registered agent as a “consent to everything” button.
2) Audit Your “Where Can We Be Sued?” Map
Your general jurisdiction risk is usually concentrated where you are incorporated and headquartered. Your specific jurisdiction risk follows the trail of your forum-related activities: sales, marketing, contracts, employees, property, and targeted conduct.
3) Use Contract Tools Like an Adult
Forum selection clauses, choice-of-law provisions, arbitration agreementsthese are the seatbelts of modern commerce. They don’t prevent every crash, but they reduce chaos when something goes wrong.
4) Watch Legislative Attempts to Expand Jurisdiction
After Mallory, some states have flirted with expanding consent-by-registration rules. Nevada saw a proposed bill (AB 158 in the 2025 legislative session) that would have broadened general jurisdiction concepts, though it did not pass. The policy debate isn’t over, and businesses should monitor changes that could shift exposure quickly.
FAQ: The Questions People Ask Right After They Google “General Jurisdiction Nevada”
Does registering to do business in Nevada mean we consent to general jurisdiction?
Not automatically. Nevada’s statutes and the Nevada Supreme Court’s approach reject the idea that appointing a registered agent alone creates personal jurisdiction, much less general jurisdiction.
Can we still be sued in Nevada?
Yesespecially if the claim connects to your Nevada contacts (specific jurisdiction), or if your company is “at home” there (general jurisdiction), or if you contractually agree to Nevada as a forum.
Does this decision matter outside Nevada?
Absolutely. Courts and litigators nationwide are watching how states interpret their registration statutes after Mallory. Nevada’s decision is part of the developing map that tells businesses where “registration” is routine complianceand where it might become a jurisdictional trap.
Conclusion: Nevada Draws a Bright Line (And Businesses Benefit From Clarity)
The Nevada Supreme Court’s message is refreshingly direct: general jurisdiction over businesses has limits. Nevada isn’t going to treat routine registration steps as an open-ended invitation to sue companies for out-of-state disputes. That reduces forum-shopping incentives, aligns with modern due process principles, and gives businesses a clearer sense of litigation risk.
If you operate across state lines, this is the kind of clarity you want: predictable rules, fewer surprise venues, and a legal system that recognizes the difference between “we do business there” and “we are based there.”
Field Notes: of Practical Experience Around Jurisdiction Fights
In practice, jurisdiction battles tend to start the same way: the complaint lands, everyone pretends they’re calm, and then somebody says, “Wait… why are we being sued there?” That’s when the real sport begins. Plaintiffs often pick forums strategicallysometimes because they live there, sometimes because an event happened there, and sometimes because they’re hunting for procedural advantages (timing, jury pools, local rules, reputation, you name it).
When the forum choice feels “creative,” defendants usually respond with a motion to dismiss for lack of personal jurisdiction. The first few pages of the motion read like a geography lesson: incorporation state, headquarters, where the product was designed, where it was sold, where the injury happened, where the contract was negotiated, and where the emails were sent. Then comes the “minimum contacts” analysisbasically the legal version of asking, “Did we actually do anything meaningful in this state that relates to this lawsuit, or are we just being dragged here because it’s convenient for the plaintiff?”
Here’s where Nevada’s approach is especially useful: it reduces one of the most tempting shortcutsarguing that “registration equals consent.” From a business perspective, that matters because registration is often unavoidable. If your company operates nationally, you register in many states because you want to sell, hire, open locations, and not get fined. Turning that compliance step into blanket jurisdiction would punish normal commerce and create constant litigation roulette.
Another common experience: plaintiffs will point to a defendant’s visible local footprintstores, branches, ads, sponsorships, even a billboard with an unfortunately catchy slogan. Defendants respond by separating “presence” from “connection.” Yes, the company has activity in the state. No, the claim doesn’t arise from that activity. The difference is everything. A national bank having branches in Nevada doesn’t mean a Missouri-administered trust dispute suddenly becomes a Nevada case. Courts increasingly demand a real relationship between the forum and the controversy, not just a corporate zip code collection.
Finally, there’s the contract angle. Many businesses learn (sometimes the hard way) that forum selection clauses are underrated heroes. When the clause is well-drafted, it can stop a jurisdiction fight before it becomes a multi-month side quest. When it’s missingor sloppyyou may end up litigating jurisdiction first, then litigating the merits second, and then wondering why nobody warned you that “boilerplate” is the most expensive word in the English language.
The overall lesson businesses tend to adopt after one of these fights: map your jurisdiction risk like you map your supply chain. Know where you’re “at home,” where your activities are strongly forum-directed, and where you’re merely compliant. Nevada’s line-drawing helps keep that map readableso you can spend more time running your business and less time starring in America’s Next Top Defendant.
