A pending work permit renewal does not shut the courthouse door.

If your co-founder is copying source code, draining customer lists, or moving the product roadmap into a new LLC while your EAD renewal sits in limbo, the immediate move in Seattle is usually a temporary restraining order in King County Superior Court, not waiting around for USCIS to get its act together.

That distinction matters.

A lot of people say "protective order" when what they really need is an emergency civil restraining order. In a startup fight, you are usually asking the court to block use or disclosure of trade secrets, stop access to company accounts, preserve devices, and freeze further transfer of IP. In Washington, that typically runs through a TRO followed by a preliminary injunction under state civil procedure and trade secret law.

Your expired work permit is a problem, but not this problem

If the renewal was filed on time, some categories get an automatic extension of employment authorization while USCIS processes the renewal. Some do not. The ugly part is that founders often assume a pending receipt notice fixes everything. It doesn't.

USCIS backlogs are all over the map. Nebraska, Texas, California, and Vermont service centers can each have very different delays, even for the same form type. So "still pending" could mean routine delay or a serious issue depending on the category and filing history.

But a pending or expired EAD does not normally prevent you from being a plaintiff in a Washington civil case. You can still sue. You can still verify a complaint. You can still ask for emergency relief. The court is deciding whether your co-founder is taking property, breaching duties, or misusing trade secrets. It is not deciding whether USCIS is moving fast enough.

Where this can get messy is if your immigration situation affects your role inside the company. If you were drawing wages after work authorization lapsed, or if the company's formation and ownership records are sloppy, the other side will absolutely use that to muddy the water. Not because it defeats the TRO automatically, but because chaos helps thieves.

In Seattle, speed beats perfection

King County's civil calendar gets jammed. Anyone who has tried to get in front of a judge downtown knows it. If you wait for a regular noticed motion on the standard timetable, your co-founder may have enough time to clone repos, lock you out of Slack, redirect AWS billing, and call investors with a new story.

That is why emergency filings exist.

If the risk is immediate, the usual path is filing in King County Superior Court and asking for ex parte or emergency consideration of a TRO, then setting a fast follow-up hearing for a preliminary injunction. You are asking the judge to act before the ordinary schedule grinds through the backlog.

The court is not going to grant that just because you sound panicked. It wants proof that the harm is happening now and money later will not fix it.

What usually matters most is boring, unglamorous evidence:

• GitHub logs, AWS access history, email forwarding rules, signed IP assignment agreements, cap table records, investor communications, and any message where the co-founder admits taking code, customer data, or deal documents

If you have that, the calendar problem becomes manageable. If you do not, the backup becomes deadly.

The Seattle-specific mess nobody plans for

Startup fights here often involve half the company living in Slack, Google Workspace, and cloud tools billed to a founder's personal card. Maybe the Delaware C-corp paperwork exists, maybe it doesn't. Maybe the IP assignment agreement got "circulated" but never signed after a meeting in South Lake Union. Maybe the contractor in Fremont wrote the core codebase. Maybe the co-founder is in Bellevue and the servers are somewhere else entirely.

That sloppiness is exactly why judges focus on control, ownership documents, and imminent harm.

If your co-founder is using company IP to pitch a spinout, launching a copycat product, or pulling data from a shared drive, ask for specific relief. Not vague moral outrage. Specific relief. Return of devices. No deletion. No disclosure. No customer contact using disputed assets. No transfer of domain names, repos, or funds. Preservation of evidence.

Seattle judges see plenty of overcooked startup drama. What cuts through is precision.

Don't mix up immigration court with the court you need

If your status is tangled up with removal proceedings or an old filing problem, remember that immigration courts are part of the Department of Justice, not the federal judiciary. Different rules. Different deadlines. Different appeal path. That system will not save your codebase this week.

Your business emergency belongs in civil court.

And if your co-founder tries to spin this as an employment discrimination issue because they were removed from payroll or access, that is another lane too. The EEOC handles federal employment discrimination claims like Title VII, ADA, and ADEA. That does not give someone a free pass to walk off with trade secrets.

The real trap

The biggest trap is waiting for your immigration paperwork to clear before acting on the theft.

That feels safer. It usually is not.

If the renewal is pending and your evidence shows active misuse of IP, the better path is to file for emergency relief now, explain the company structure cleanly, and keep the immigration issue from becoming the whole story. Judges in King County care a lot more about whether you can prove immediate business harm than whether USCIS has finally opened a file sitting in Nebraska or Vermont.

If you spend two more weeks refreshing a case-status page while your co-founder ports the product and poaches the customers, that backlog on Third Avenue stops being a court problem and starts being your problem.