What Chief and Council Should Do Before an Emergency Happens

Set emergency leadership priorities, decision authority, partner expectations and resource limits before a crisis, using a practical decision record.

First Nations Knowledge Centre / Emergency Management & Resilience

First Nations Management & Leadership · Arcus perspective

What Chief and Council Should Do Before an Emergency Happens

Resolve the consequential leadership choices before urgency makes them harder to examine.

Prepare the governing decisions, not just the plan

Chief and Council can make a distinctive contribution to emergency preparedness by resolving the choices that operations cannot legitimately make alone: community priorities, authority boundaries, resource commitments and acceptable partner arrangements. A plan can describe an action without establishing who may authorize it or how its continuing costs will be supported.

Arcus’s central proposition is that pre-event governance should reduce avoidable decision delays while preserving accountability. Leadership should give the emergency team a usable mandate, with explicit conditions and a review process. This does not mean pre-deciding every response or treating an approved document as proof of safety.

This article addresses decisions before an emergency. It complements the emergency management planning guide and the readiness assurance framework. It does not provide incident-command instructions. The Nation’s own laws, governing institutions, agreements and emergency specialists must determine applicable authorities; elected, hereditary and other legitimate responsibilities cannot be assumed to follow one template.

What the evidence supports—and what it does not

The Auditor General of Canada’s November 2022 audit found that Indigenous Services Canada had 112 eligible structural mitigation projects awaiting funding and lacked consistent information about whether emergency services met First Nations’ needs.[1] These are dated federal-program findings, not an assessment of an individual Council. They challenge an explanation that attributes every preparedness gap to local planning or leadership.

Conditions also change. A March 2025 joint announcement concerning British Columbia reported Phase I emergency-management negotiation results, including support for additional coordinator positions, remaining eligible mitigation projects and improvements to reimbursement processes.[2] An announcement establishes a commitment, not proof that a particular Nation has received sufficient support. Leadership should verify its actual agreements, capacity and funding position rather than carry forward either an old deficit assumption or an untested expectation of improvement.

ISC’s January 2026 interim service standards recognize that culturally relevant services must be defined by First Nations and should reflect differences in governance, geography, language and community circumstances. They describe expectations for EMAP-funded partners while preserving existing First Nations-led standards.[3] The management implication is to specify what acceptable support means before asking whether an agreement provides it.

FNESS describes preparedness and recovery support that combines local leadership, training, planning and partnerships in British Columbia.[4] Its service description identifies a specialist support route; it is not independent evidence that a training course or a signed plan produces a particular outcome. The sources together support explicit local decisions and confirmed external dependencies, not a universal preparedness score.

Distinguish three causes of an unresolved readiness gap

Suppose leaders repeatedly hear that “transport arrangements are not ready.” That statement can conceal different management problems.

  • An authority gap: qualified staff know what is needed but cannot identify who may approve a commitment. Examine the relevant delegation, an actual request and the decision route. Clarifying authority may help; buying another plan may not.
  • A capacity or funding gap: authority exists, but the required staff, vehicles, accessible facilities or financing are unavailable. Examine supplier confirmations, funded positions and the financing timeline. Escalate the unresolved requirement and develop a feasible alternative with specialists. A resolution cannot create an unavailable resource.
  • A coordination gap: both parties believe the other will deliver part of the service. Compare written responsibilities, activation contacts and evidence from an agreed exercise. Resolve the handoff and confirm what happens if the partner cannot respond.

The explanations can coexist. Use a small set of consequential dependencies to test them, including arrangements for members whose needs are poorly served by standard services. Avoid interpreting a missing document as the sole cause, or a completed document as proof that people and equipment will be available.

Set priorities and authority before making commitments

Ask service leaders to identify the functions that cannot simply stop, their minimum operating requirements and the consequences of interruption. Leadership then needs to resolve conflicting priorities and the conditions under which normal activities may be deferred. A list in which every service is equally critical provides little direction when the same employees support several functions.

Translate this direction into a bounded mandate through the Nation’s appropriate process. Identify which decisions remain with its governing authority, which an authorized administrator or emergency lead can make, how an alternate is appointed, and when escalation is required. Check these arrangements against applicable instruments with qualified advice. Do not assume that an internal decision changes another government’s obligations or creates a power the Nation’s chosen process has not authorized.

Include a practical reporting commitment. Leadership needs enough information to reassess priorities without repeatedly requesting the same update from operational staff. Decide who consolidates information, which consequential changes require immediate escalation and how decisions will be recorded when normal systems are unavailable.

Where authority is contested or a proposed delegation exceeds the current mandate, resolve that question before relying on it. Separate it from smaller improvements that can proceed under existing authority. This keeps one unresolved decision from freezing all preparedness work.

Compare local, shared and externally supported delivery

A locally led model may suit a Nation with sustained staff and specialist access. It preserves direct control but requires coverage for absences, training and routine maintenance of readiness. One capable coordinator is not the same as a resilient team.

A shared arrangement may provide expertise or coverage that would be difficult for one administration to sustain. It needs clear representation, service priorities, decision authority and a process for simultaneous demands. A shared coordinator serving several Nations should not be counted as fully available to each during the same regional event.

Contracted or partner support may address a specific technical or coordination gap. Specify the deliverable, availability conditions, information permissions, activation process and internal owner. Purchasing assistance does not transfer the Nation’s governing decisions or eliminate the need for local participation.

Compare these options using the same required service, coverage period and acceptance evidence. Include salaries, relief coverage, training, exercises, travel, communications, equipment maintenance and the time needed to manage agreements. Examine the transition effort separately from the annual commitment. Select the option whose dependencies can be made credible; the lowest quoted fee may purchase a narrower service.

Separate affordability from the ability to pay on time

A preparedness budget should show recurring operating commitments, occasional readiness work and potential response cash requirements separately. Expected reimbursement is not cash already available, and an eligible activity is not necessarily an approved claim.

Consider a fictional financing test, not a recommended reserve. Assume C$60,000 of authorized response payments must be made before reimbursement. If C$15,000 of usable cash and a confirmed C$20,000 advance are available before those payments fall due, the initial gap is C$25,000. If the advance arrives later, the gap rises to C$45,000. Restricted cash cannot be treated as available unless its use is permitted. This simplified example excludes further response costs and any financing charges.

The finance lead should map expected payments and confirmed funding dates, document uncertainties and identify who may approve commitments. Leadership must then resolve the financing plan through its proper authority or revisit the unsupported commitment with the relevant partners. This is a preparation exercise, not a reason to delay urgent protective action during an incident.

Do not reduce the economics to a claimed return on preparedness spending. Avoided losses are uncertain and vary by hazard and intervention. Compare feasible options, continuing obligations and the consequences of an unfunded dependency without inventing a universal savings ratio.

Use a Pre-Emergency Leadership Decision Record

This original Arcus framework turns broad preparedness intentions into reviewable governing choices. It is analytical synthesis, not a validated benchmark or a substitute for emergency planning. Create one record for each consequential decision rather than one large score for the whole Nation.

  1. Decision and purpose. State the service or risk decision leadership must make, the people affected and the outcome it is intended to protect.
  2. Authority and boundary. Identify the legitimate decision-maker, the operative authority, permitted scope, alternate and escalation conditions.
  3. Resource commitment. Identify staff coverage, recurring costs, transition work, usable financing and the commitments that remain conditional.
  4. External dependency. Name the partner contribution, its written acceptance, availability limits and the alternative if it cannot be provided.
  5. Evidence and acceptance. Specify the records or exercise that would demonstrate the arrangement works, who checks them and who accepts remaining limitations.
  6. Review and expiry. Set the next review and triggers such as a change of leadership, staff turnover, revised agreement or a failed exercise.

For a hypothetical shared transport arrangement, the decision is not simply “approve the agreement.” The record should establish the service requirements, who may activate support, how costs are authorized, which partner has accepted the commitment and how accessibility requirements will be checked. A contact list without confirmed availability leaves the dependency open.

Use three outcomes: accepted on current evidence, accepted within explicit limits, or unresolved and escalated. A conditional acceptance must identify the limit, owner and next decision. Never convert a red item to green merely because its owner has promised to investigate it. Acknowledging an unresolved external constraint is more useful than claiming readiness the Nation cannot demonstrate.

Implement the decisions in a manageable sequence

First, assemble the decision agenda. The administrator and emergency lead identify the few gaps most likely to obstruct essential services, using existing plans, exercises and partner records. Finance verifies the resource assumptions. Obtain community and service-user input through the Nation’s appropriate protocols, with care for confidential information.

Second, resolve and record the governing choices. The authorized leadership body decides priorities, mandates and resource boundaries. Where agreement or specialist input is missing, assign a next action and an interim arrangement rather than invent certainty.

Third, confirm dependencies and exercise the handoffs. Workstream owners obtain counterpart acceptance and use a proportionate, professionally guided exercise to examine the selected decisions. Record what actually happened, not just attendance. Correct the specific weakness and review the affected decision.

Finally, maintain the mandate. Track unresolved critical dependencies, coverage gaps, expired agreements and corrective actions demonstrated as closed. Compare decision delays and service handoff failures across exercises, while recognizing that different scenarios are not directly comparable. Maintain a leadership transition briefing so the next Council can distinguish confirmed commitments from open negotiations.

This approach can fail if it becomes an additional reporting burden without time to resolve the findings. It also has limits where external resources remain unavailable. Keep the record short, support the people maintaining it and escalate structural constraints with evidence. Leadership’s objective is a more credible operating mandate, not a longer compliance file.

How an Arcus engagement can support the leadership decision

A scoped engagement can help diagnose authority and capacity gaps, compare delivery arrangements, map transition and recurring resource requirements, and design the decision record and review process. Potential deliverables include a leadership decision agenda, responsibility map, options paper, resource model and implementation roadmap with acceptance points.

Agree the Nation’s sponsor, information-use arrangements, participants and deliverable criteria at the outset. Emergency-management specialists and relevant partners must supply technical and operational judgments; Arcus management analysis does not replace them. The Nation retains its decisions and authority.

Discuss your preparedness governance priorities →

Review Indigenous consulting services and deliverables · Explore the First Nations Knowledge Centre

Sources and limitations

  1. Office of the Auditor General of Canada. Report 8—Emergency Management in First Nations Communities—Indigenous Services Canada, 15 November 2022. Dated audit findings about federal support; not a current assessment of every Nation.
  2. Indigenous Services Canada, First Nations Leadership Council and British Columbia. Advancing the relationship on emergency management, 20 March 2025. Joint announcement of Phase I commitments; not an evaluation of delivery to an individual Nation.
  3. Indigenous Services Canada. Interim Service Standards for Culturally-Relevant Emergency Management Services, version 7 January 2026. Guidance for EMAP-funded partners, developed with First Nations emergency practitioners; preserves Nation-defined cultural relevance and existing standards.
  4. First Nations’ Emergency Services Society of British Columbia. Preparedness & Recovery, undated; reviewed October 2026. Specialist service description for BC; not an independent effectiveness evaluation.

The decision record, diagnostic, option analysis and fictional financing example are Arcus analytical synthesis. No local field study or validated organizational benchmark is claimed. Confirm current arrangements with the Nation and its relevant partners; the evidence does not establish one governing model for every First Nation.

Return to Emergency Management & Resilience research