The Emergency Powers Charter 2.3D.3-1

The Emergency Powers Charter is a living document that pre-commits the organization to restraint during the moments when restraint is hardest. It is written in normal times, when perspective is clear, rather than in crisis, when panic dominates reasoning.

This application walks through how to construct and maintain an Emergency Powers Charter.

Template and Framework

Section 1: Definitions of Emergency

Start with specificity. Define what qualifies as an emergency. Not every difficulty is an emergency. Emergency should be rare — if you declare emergency monthly, the restraints have failed.

An emergency is declared if, and only if, one of the following conditions is present:

Imminent Threat to Life or Safety

A reasonable likelihood of serious injury or death within 24 hours if immediate action is not taken qualifies as an imminent threat. Examples include an active threat (armed person on premises), natural disaster (earthquake, fire), or pandemic with exponential growth in severe cases in the region. Non-examples include possibility of threat, slowdown in service, or risk of financial loss.

The determination requires both the CEO and Board Chair to affirm that the condition exists. If they disagree, the condition is not met. The decision is documented.

Critical System Failure

Failure of a system essential to the organization's core function qualifies when normal governance would cause loss exceeding $1 million or loss of service to more than 50% of customers for more than 4 hours. Examples include data center failure with backup failure, primary payment system down with no redundancy, or cessation of a critical supplier.

Non-examples include slowdown in performance, partial failure with workarounds, or expected infrastructure maintenance.

The determination requires the CTO, CFO, and CEO to all affirm that the condition exists. Any disagreement means the condition is not met.

Existential Threat to Organization

A condition where organizational failure is probable within 7 days without immediate action qualifies as existential. Examples include loss of license, discovery of fraud threatening credibility, or insolvency with no funding available. Non-examples include difficult quarter, loss of major customer, or regulatory inquiry.

The determination requires a Board vote with a 2/3 majority required. The Emergency Oversight Committee can object within 2 hours; such objection requires supermajority override.

All other conditions are not emergencies. Response proceeds through normal governance, with acceleration where appropriate.

Be specific. Specific definitions constrain abuse. Vague definitions enable it.

Section 2: Specific Powers Activated

For each emergency condition, name exactly what powers activate. The principle is precise delegation, not unlimited authority.

Imminent Threat to Life: Activated Powers

The normal constraint is that CEO decisions exceeding $50k require board approval. Board approval requires 1-week notice and 2-day discussion period.

The emergency power is that the CEO can authorize spending up to $500k without notice or approval. The constraint on this power is that it must be directly related to the life-safety threat. The CEO provides written rationale within 4 hours. The Emergency Oversight Committee reviews all expenditures.

The normal constraint is that operational decisions require consultation with department heads.

The emergency power is that the CEO can issue direct orders to staff without consultation. The constraint is that orders must be documented. Staff may decline if they believe the order violates legal or ethical constraint; the CEO cannot retaliate.

The normal constraint is that customer data may not be shared without written consent.

The emergency power is that customer data may be shared with emergency responders (fire, police, medical) if the life-safety benefit exceeds privacy cost. The constraint is that each sharing instance must have documented rationale. Data shared is limited to what is necessary for the stated purpose. Data is retrieved and deleted within 24 hours of emergency end, unless the customer explicitly consents to continued sharing.

The normal constraint is that employee records are confidential; terminations require notice and due process.

The emergency power is immediate termination of staff for insubordination during crisis. The constraint is that termination must be documented with justification. Terminated staff have the right to appeal to the board within 7 days of emergency end. Appeal can result in severance, reinstatement, or other remedy. No retaliation.

For each power, name the constraint. Powers with no constraints are not emergency powers — they are autocracy.

Section 3: Authority to Declare Emergency

Emergency authority is not unilateral. Multiple authorities must concur.

Threat to Life or Safety

Either the CEO or Board Chair can initiate declaration. The other party must affirm or reject within 15 minutes. If rejected, the condition is not declared emergent. If affirmation is not received within 15 minutes, the declaration is not authorized.

If neither CEO nor Board Chair is available, designate a backup (named in advance in the charter appendix). The backup has the same authority as the principal.

Critical System Failure

The CTO identifies system failure and initiates. The CFO and CEO must review within 30 minutes and affirm that the impact condition is met. If any party rejects, the condition is not declared emergent.

Existential Threat

The Board requires a supermajority (2/3) vote. The process is proposal and discussion within 1 hour. Board votes. 2/3 majority required. The Emergency Oversight Committee has the right to object within 2 hours of the vote, which requires board supermajority override (3/4).

For all declarations, the Board must be notified within 30 minutes. If the board is not yet aware, the CEO and Board Chair take immediate action to assemble the board for ratification within 4 hours.

No single individual can declare emergency. This structure prevents unilateral capture of emergency authority.

Section 4: Time Limits and Renewal

Emergency authority is time-limited by architecture. All emergency authority expires 7 days after declaration, unless renewed.

Renewal Process

Days 1–7 constitute the initial emergency period. Powers are active. Light oversight occurs through weekly review by the Emergency Oversight Committee.

On Day 7, the Board must vote on renewal. Renewal requires simple majority. Renewal is for another 7 days (14 days total).

On Day 14, a second renewal vote occurs. This requires 2/3 majority.

On Day 21, a third renewal vote occurs. This requires 3/4 majority. If renewal fails, emergency authority expires regardless of whether emergency conditions still exist.

After Day 21, no further renewal is possible without a new declaration (same authority, same thresholds as original).

If emergency conditions cease before expiration, the board can vote to terminate emergency authority at any time. Once terminated, a new emergency cannot be declared for 30 days without a board vote. This prevents repeated emergencies designed to circumvent governance.

All renewal votes are documented: date, who voted, and rationale for renewal.

The increasing thresholds force reexamination. By the third week, if the board is not convinced the emergency is genuine, it expires. This prevents emergency authority from metastasizing into permanent capture.

Section 5: Oversight During Emergency

Emergency authority is not unsupervised. A standing Emergency Oversight Committee monitors use.

Committee Composition

Three members serve, all from outside the executive team. One is a board member (not board chair, not audit committee chair). One is a senior staff member (not executive team, chosen by staff vote). One is an external party (customer council representative, or pre-agreed external auditor).

The Committee reviews emergency authority use at least weekly during active emergency. Review includes spending (is expenditure genuinely related to stated emergency? is it proportionate?), data sharing (is privacy exception used only for documented life-safety purposes?), personnel actions (are terminations justified by emergency conditions?), and communication (is the organization being transparent about situation and response?).

If the Committee identifies misuse of emergency authority, it can recommend to the board that emergency authority be suspended. The recommendation requires a board vote; suspension requires simple majority.

All Committee meetings are documented. Minutes are held in confidence until the emergency ends, then released (to avoid compromising response). If emergency authority is suspended, minutes are released immediately.

Oversight is not ceremonial. The committee has teeth.

Section 6: Recovery and Return to Normal

When emergency authority expires, the organization returns to normal governance — but not all at once.

Day 1 (Emergency Ends)

Emergency authority expires. Normal governance resumes for all forward-looking decisions. Retroactive review begins.

Days 2–7: Review and Remediation

Data shared during the emergency is reviewed to determine whether it is still necessary. All unnecessary data is returned or deleted within 7 days.

All emergency spending exceeding $10k is audited. Emergency justification is documented. Expenditure is classified as permanent or temporary.

All terminations are reviewed. Terminated staff are provided severance within 30 days, with an option to appeal to the board.

Policies changed during emergency are reviewed. Permanent changes require board approval; temporary changes sunset.

Days 8–30: Normalization

Permanent expenditures are incorporated into the normal budget (next budget cycle). Emergency hires are converted to permanent positions or separated with severance. New policies are approved by the normal process or reverted. Compensation or benefits provided during emergency are normalized or phased out.

Day 31: Board Post-Mortem

The board discusses what triggered the emergency and whether conditions were correctly assessed. The board examines how well emergency governance worked and what should change in the charter. The board identifies what lasting changes will result from the emergency and how the organization should prepare for future emergencies.

Post-mortem findings are documented and used to update the Emergency Powers Charter.

Recovery is as important as response. How quickly the organization returns to normal governance is a measure of whether emergency authority was used appropriately.

Section 7: Amending the Charter

The Emergency Powers Charter is not permanent. It evolves based on what you learn.

Normal Amendment

Any board member or Emergency Oversight Committee member may propose an amendment. Approval requires a board vote; simple majority suffices. The amendment becomes effective 30 days after the vote (allowing a challenge period).

Urgent Amendment

Within 30 days of emergency end, an amendment can be proposed to respond to lessons from the recent emergency. This requires a board 2/3 vote and becomes effective immediately.

All amendments are documented with effective date. Prior versions are retained for historical reference.

The charter is reviewed annually by the board and Emergency Oversight Committee. Review includes whether the organization has declared emergencies, whether charter provisions worked, and what should change.

The full charter is available to all employees and stakeholders. Specific contact information for the Emergency Oversight Committee is published so that anyone suspecting misuse of emergency authority can report.

The charter evolves. It is not meant to be permanent — it is meant to learn from practice.

Example Application: A Real Emergency

Scenario: Malware infection in customer data system. Ransomware is spreading. Attackers demand $500k. Deadline: 12 hours.

Hour 0–1: Declaration

The CEO and CTO discover active malware. The CTO initiates emergency declaration. The CEO affirms that the critical system failure condition is met: "Primary customer database is compromised; ability to serve customers is at risk; if unresolved within 12 hours, estimated 90% customer data loss or $2M in fraudulent transactions."

Emergency is declared. The Board Chair is notified.

Hour 1–2: Response

Under emergency authority, the CEO authorizes $200k for an emergency incident response team (which would normally require board approval). The CEO authorizes rerouting of customer traffic to backup systems (which normally takes 1 week). The CEO authorizes sharing of the affected customer list with payment processors to flag fraudulent transactions (which normally requires consent). The CEO authorizes calling in staff at night (which would normally require 24-hour notice).

All actions are documented with emergency rationale.

Hour 2–12: Response Execution

The incident response team isolates infected systems. Malware is contained. Backups are restored. Affected customers are notified.

The Emergency Oversight Committee is convened (emergency requires at least weekly review, but in this case review is immediate). The Committee reviews spending ($200k for incident response, additional $50k for expedited backup recovery — both justified by emergency and approved), data sharing (customer list shared with payment processors; necessary to prevent fraud and appropriate), and personnel (emergency staff called in; documented and authorized; appropriate).

Hour 12+: Escalation or Containment?

At 12 hours, the CEO can declare the emergency ended or request renewal.

Situation: Malware is contained, but recovery is incomplete. Customer service is degraded. Full recovery will take 48–72 hours. But core systems are stable. No immediate threat to life/safety or existential threat to the organization.

The CEO proposes ending emergency authority and returning to normal governance for non-urgent decisions (budget, hiring), while maintaining some expedited authority for system recovery-related decisions.

The board votes at hour 14. The board is briefed on the situation and votes to terminate emergency authority effective at hour 14, except for critical system recovery spending (up to $100k), which remains expedited for 7 more days.

Hour 14+: Recovery and Review

Emergency authority ends. Normal governance resumes for all decisions except critical recovery spending (which is still expedited to speed system restoration).

Over the next 7 days, all spending during the emergency is documented and classified as temporary ($150k) vs. permanent ($100k). Staff called in for the emergency are paid emergency premium and given flexible scheduling for the next week. Customer data shared with payment processors is retrieved within 24 hours after the threat passes. The board holds a post-mortem: What did charter provisions do well? What failed? How should the charter be updated?

Post-mortem findings show that the charter worked: emergency was declared correctly, time limits worked, and oversight worked. An area for improvement is identified: the charter should clarify what counts as "critical system failure" — this took 30 minutes to assess initially. An amendment is proposed to add a decision tree to help the CTO quickly assess impact and initiate declaration.

The charter is updated for the next potential emergency.

The Practice

An enterprise practicing Resilient Objectivism (RO) at this level operationalizes the principle that emergency authority does not override restraint. It does this by pre-writing the charter before crisis arrives, while thinking is clear; naming authorities to declare (so dual or triple authority prevents unilateral capture); time-limiting emergency authority (so automatic expiration forces reaffirmation, preventing emergency from becoming permanent); establishing oversight during emergency (so a standing committee monitors authority use and can recommend suspension); planning recovery in advance (so the charter anticipates that emergency will have side effects and normalizes them); learning from emergencies (so post-mortems identify what charter provisions worked and what should change); and making the charter public (so all employees and stakeholders know what emergency authority is available and what limits apply).

The practice is not perfect crisis response. It is crisis response designed so that the response does not become the excuse for permanent capture.

This connects to the restraint principle (1.2.3), which establishes that restraint is a first-class moral design requirement at every level, and to answerability (2.3C.1), which translates institutional analysis into binding architecture. The Emergency Powers Charter operationalizes the principle that restraint as governance constraint intensifies under stress — the conditions when restraint matters most.

The charter also connects to the organizational institutional charter (2.3C.1), which establishes the basic governance structure the organization operates within, and to the polycentric governance charter (2.3D.1), which defines the multiple jurisdictions and exit rights that allow individuals and teams to maintain optionality even during enterprise-level crises. The staged-judgment lifecycle (2.3D.1-2) applies directly: emergency declarations themselves are a form of judgment that must earn their hardness, and the charter's multi-authority structure, renewal requirements, and time limits implement that principle architecturally.

The connection to Arc 2 sunset schedule / institutional fallibilism (2.2.5) is crucial: emergency authority that cannot be renewed at increasing thresholds is a sunset schedule — a deliberately expiring power that prevents permanent capture. This echoes the structure of institutional fallibilism, which requires that policies be periodically reaffirmed rather than calcified. Similarly, protected dissent (2.2.6) is operationalized through the Emergency Oversight Committee's independence and the requirement that emergency Oversight Committee can block emergency authority continuation, preventing silencing of contrary views precisely when power is most concentrated.