This is the Counsel's Desk, on Terms.Law Radio. Ninety two point five. This is the Washington to Contract report. Tonight's subject needs a careful frame, so let me set it in the first breath: this is not an episode about immigration law, and nothing tonight tells anyone how to handle a visa, a petition, or a status question. Those belong with an experienced immigration lawyer, full stop. Tonight is the business continuity episode: what happens to a company when a founder's or a key employee's ability to work, travel, or remain in the country changes, and what the corporate documents, the contracts, and the operating plan should already say before that day. Because immigration status is, among the many other things it is to a human being, a single point of failure in a business, and single points of failure are exactly what continuity planning exists for.

Segment one, the dependency map. Start with an inventory, and be more honest than is comfortable. Which people in the company have work authorization that depends on a current status, a pending application, or an employer sponsorship? For each of them, three follow up questions. First, what functions stop if this person cannot work for sixty days? Not their title. Their functions: signing payroll, holding the customer relationships, being the only human who can deploy the codebase. Second, what breaks if they cannot travel internationally? That is a different and often earlier failure mode than losing authorization altogether. A person can be fully authorized and still stuck on the wrong side of a border during a renewal. Third, what depends on their physical presence in a particular state or country? Lab access, licensed activities, in person client work. Founders deserve special scrutiny in this inventory, because founder dependency is usually the deepest and the least documented. If the answer to what stops is everything, the rest of tonight is for you.

Segment two, the mechanics that reduce the dependency. Six of them, all boring, all buildable this quarter. One, signing authority. If only one person can sign contracts, approve payments, or access the bank, the company has a continuity problem that has nothing to do with why that person might be unavailable. Fix it generally: a second authorized signer, bank access for a trusted officer, board resolutions that name a delegation order. Two, powers of attorney and standing delegations, drafted with counsel and reviewed annually, so that routine corporate acts never require one specific human to be reachable. Three, remote work architecture. Whether a particular person may lawfully work from a particular place is a legal question I am not touching tonight. Whether the company could operate with that person remote is an operations question, and the honest answer should be tested before it is needed: documentation, handoff runbooks, a second person shadowing every critical function. Four, employer of record arrangements. If a key person may at some point need to work from another country lawfully, companies use international employer of record services to employ people compliantly abroad. Setting one up takes time and diligence, so investigate the option calmly, in advance. And take real care with worker classification, because bolting a contractor label onto an employment relationship to solve a mobility problem creates a second legal problem without solving the first. Five, key person provisions in your own documents. Investor agreements, major customer contracts, and insurance policies sometimes contain key person clauses that trigger on a founder's extended unavailability. Read them now, know what they trigger, and negotiate cure periods, so a temporary absence is not an instant default. Six, knowledge transfer, the least glamorous and the most valuable: if the company's critical knowledge lives in one head, no legal instrument fixes that. Runbooks, credentials in a proper vault, and cross training are continuity planning in its purest form.

You're listening to the Washington to Contract report, on the Counsel's Desk, Terms.Law Radio.

Segment three, the conversations, because continuity is also about what you say and to whom. With investors: sophisticated investors ask about key person risk in diligence anyway, and a company that raises the topic itself, with a written continuity plan attached, reads as well managed rather than fragile. The plan does not need to be elaborate. Who covers what, on what timeline, with what authority, reviewed twice a year. With customers: larger customers increasingly ask about business continuity during vendor onboarding, and the honest, boring answer, named backups, documented processes, tested access, is fully responsive without disclosing anyone's personal circumstances. Which, to be clear, you should not be disclosing. A person's immigration situation is sensitive personal information. The continuity plan speaks of roles and coverage, never of anyone's case. And with the key person themselves: the humane version of this planning is done with the person, not about them. Budget for the immigration counsel they need, build the coverage plan together, and separate cleanly the questions the company can plan for, operations, authority, documentation, from the questions that belong to their own lawyer.

Three closing notes, calibrated to company size. If you are a solo founder, tonight's episode is really about your operating agreement, your bank, and your runbook: could anyone lawfully act for the company for ninety days if you could not? If the answer is no, start there, this month. If you run a small team, the dependency map plus a second signer plus documentation covers most of the exposure for the price of a few careful afternoons. And if you are at the size where customers send continuity questionnaires, treat the immigration dependent scenario as one row in a larger resilience table that also includes illness, departure, and plain bad luck, because a plan that only works for one kind of absence is not a plan. It is a patch.

The practical question is whether your contract gives you an exit if the policy environment changes. The Terms.Law analyst and the related contract checklists are at terms dot law.

The fine print, and tonight it matters doubly. This broadcast is commentary and general information, based on public reporting and government documents as of July tenth. It is not legal advice, it is not immigration advice, and it is not investment advice, and listening does not create an attorney client relationship. Immigration questions belong with a qualified immigration attorney, and policy moves fast, so verify before acting. I'm the AI voice of Terms.Law Radio. The analysis belongs to Sergei Tokmakov, California attorney. Stay tuned, stay skeptical, and build the runbook before you need it. Good night.