First Nations Management & Leadership · Arcus research
How to Build a First Nation Emergency Management Plan
An emergency management plan needs a clear owner, confirmed relationships and a practical way to remain current. The central management decision is how to connect community direction, coordination arrangements and specialist procedures without making any one document carry every responsibility.
A familiar template can help organize the work. It cannot establish another organization’s commitment, create a spending authority or demonstrate that staff can carry out an assigned role. Arcus’s central insight is that a usable plan requires explicit connections between its parts: who provides information, who decides, who acts and how the next responsible party knows the handover has occurred.
This article helps Chief and Council, senior administrators and emergency coordinators commission, organize and maintain that planning work. It is management guidance, not an operational response manual or certification of emergency readiness. Local emergency professionals and the Nation’s appropriate advisers must confirm technical procedures, applicable authorities and jurisdiction-specific requirements.
What should a First Nation emergency management plan contain?
Begin with the Nation’s territory, communities, institutions, services and relationships. Identify the planning scope and the arrangements that already exist. An approved health procedure, water-system response plan or regional agreement may be an essential input. Rewriting it inside a general document can create inconsistent versions and unclear ownership.
First Nations Health Authority guidance distinguishes community-level communicable disease coordination from tools for health service settings. The community tools address leadership and partner coordination; the service tools support continuity of care. Its June 2026 toolkit announcement describes adaptable guidance that works alongside community knowledge and existing plans.[1] This is a useful example of connected planning responsibilities, not evidence that one document structure produces better outcomes in every Nation.
Arcus proposes three connected layers for organizing the planning assignment:
- Direction and authority: purpose, scope, priorities, governing arrangements, approval responsibilities and the boundaries of delegated decisions.
- Community coordination: role assignments, partner interfaces, information flow, communications responsibilities, resource-request arrangements and the connection to essential services and recovery.
- Specialist procedures and controlled records: technical instructions, facility-specific arrangements, contact information and other material maintained by the people qualified and authorized to own it.
These layers can be sections of a short plan or a set of linked documents. Their value is the clarity of responsibility, not the number of files. Give each document an owner, approval status, version date and review trigger. Explain which information is public and which needs controlled access.
Start with the management problem before choosing a template
Three different problems can produce a request for a new emergency plan.
The document is incomplete or hard to use. Staff cannot locate the current version, role descriptions are inconsistent or several documents repeat conflicting information. Review document ownership and trace a few representative information requests. Editing and consolidation may be appropriate.
The arrangements themselves are unresolved. The document names a partner without an agreed role, assumes access to a facility or refers to an approval no one can identify. Confirm the arrangement with the responsible parties. More polished wording will not close an unaccepted commitment.
The organization lacks capacity to sustain the plan. A coordinator has the responsibility but no protected time, specialist review is unfunded or staff turnover repeatedly invalidates the contact and role records. Examine workloads, vacancies, training and maintenance resources. A new document may simply reproduce the same weakness.
These causes can coexist. Before commissioning a complete rewrite, identify which decisions require leadership, which require partner agreement and which are document-maintenance tasks. A bounded revision can be preferable when the existing plan remains sound. A substantive rebuild may be justified when governance, service arrangements or material risks have changed.
Use current guidance without importing the wrong requirements
B.C.’s planning page, updated September 11, 2026, warns that its older Emergency Management Planning Guide and related resources were developed under former legislation and are out of date. It separately provides current guidance for local authorities.[2] A resource can remain useful as a planning aid while being unsuitable as proof of legal compliance.
Maintain a short source register for the planning project. Record the document, issuer, date, intended jurisdiction, current limitations and the person responsible for confirming applicability. Do not assume that municipal requirements, another Nation’s governance arrangements or a historic funding guide apply unchanged.
The planning team should include people who understand the Nation’s services and community context, as well as the appropriate emergency, financial, legal and technical expertise. Community participation should help identify priorities, access needs and culturally appropriate arrangements through the Nation’s chosen process. It should not become a request for personal health information in an open meeting or public plan.
Where knowledge or information is sensitive, agree on how it can inform planning without unnecessary disclosure. Separate the public explanation of responsibilities from restricted operational records. An appendix is not automatically an appropriate place for personal information merely because it is called an emergency document.
Include recovery before the response plan is finished
The B.C. Auditor General’s March 2026 examination of provincial support for the Village of Lytton’s recovery found that the province expected the village to lead recovery despite insufficient staff and funds. It also identified the absence of a comprehensive recovery framework at the time and difficulty establishing a collaborative partnership with Nlaka’pamux governing bodies.[3]
The examination concerns provincial support for a municipality between June 2021 and March 2025. It is not an assessment of Lytton First Nation’s emergency plan or a comparison proving that a particular plan format prevents losses. Its management relevance is the gap that can arise between assigning responsibility and providing the capacity and relationships to carry it.
Plan how leadership will establish recovery priorities, obtain specialist support, maintain financial records and connect recovery work with continuing government services. Identify who will reassess capacity when the scale of disruption exceeds ordinary arrangements. Response and recovery responsibilities may overlap in time; avoid assuming that the same exhausted staff can simply take on a second full workload.
Do not promise reimbursement or partner capacity that has not been confirmed. Finance should distinguish an eligible expense, an approved commitment, cash available when payment is due and an expected reimbursement. These are separate questions even when a funding program exists.
The Emergency Plan Integration Record
This original Arcus decision tool helps a planning sponsor decide whether a proposed arrangement is ready to be incorporated into the approved plan. It is analytical synthesis, not a validated benchmark. Create a record for each consequential connection between roles, services or partner organizations.
Purpose and scope
Identify the planning situation, service dependency and intended outcome. State what the arrangement covers and which technical or jurisdictional questions need specialist confirmation.
Decision and authority
Name the responsible role and the basis for the decision authority. Identify limits and the route for unresolved decisions. A role title or reporting line alone does not settle this.
Handover and acceptance
Specify the information or request passed between parties, the receiving role and how acceptance is confirmed. Record any partner commitment still awaiting agreement.
Capacity and resources
Identify staff time, relevant capability, facilities, access and financial arrangements. Check whether other plan sections depend on the same scarce people or resources.
Verification and limits
Record the review or exercise evidence, unresolved assumptions and corrective decision. Distinguish a completed document review from an arrangement demonstrated in practice.
Maintenance
Assign a document owner and identify changes that trigger review, such as role turnover, a changed agreement or revised specialist guidance. Keep superseded versions from being mistaken for current instructions.
Use clear dispositions: confirmed, awaiting confirmation, or requiring correction. Do not average them into an overall readiness score. A single unresolved authority or dependency can remain consequential even when many other sections are complete. The sponsor should decide what can be approved, what requires conditions and what must be resolved before being relied upon.
Discuss an emergency planning and organizational readiness review →
Compare practical ways to develop and maintain the plan
A Nation-led refresh with targeted specialist support can fit an established plan whose core arrangements remain valid. The coordinator organizes the work, service owners update their parts and specialists review material changes. This can preserve local knowledge and reduce unnecessary rewriting, provided internal time is protected.
A facilitated planning project can fit fragmented documents or unresolved responsibilities spanning several functions. External support can organize evidence, facilitate decisions and prepare the integrated document set. Leadership and partners still need to make and accept their own commitments. A consultant cannot create those commitments by writing them into a plan.
A shared planning-support arrangement may help several Nations obtain specialist capability or maintain common administrative tools. Each Nation needs to decide which work can be shared, which decisions remain its own and how simultaneous demand will be handled. Shared support should have a defined service scope and escalation route rather than an informal expectation of unlimited availability.
Compare options against the actual gap. Outsourcing document production may not resolve a continuing coordinator vacancy. A shared service may improve access to expertise but introduce scheduling and governance dependencies. An internal project may retain knowledge but compete with daily service delivery. The selection should make these trade-offs visible.
Budget for the plan’s continuing operation
Separate initial development from recurring maintenance and corrective investment. Initial work can include document review, community and partner participation, staff backfill, specialist advice, accessibility, translation and a structured exercise. Continuing work includes updating roles and agreements, onboarding staff, maintaining controlled copies and resolving findings. Equipment or facility improvements require their own scope and cost assessment.
A fictional example shows why the distinction matters. Suppose a planning refresh uses 60 hours of coordination, 40 hours from service owners and 20 hours for partner review and document control: 120 staff hours. At an assumed blended resource rate of $80 per hour, that represents $9,600 of staff capacity. If continuing work requires six hours a month plus a 24-hour annual review, maintenance uses 96 hours, or $7,680 annually at the same assumed rate.
These invented figures are a calculation example, not an estimate for a Nation or a market price. They exclude external fees, participant costs, travel, training delivery, backfill and corrective investments. Existing salaried time does not necessarily create an equal new cash expense, but it still displaces other work. Finance and service owners should identify both the cash requirement and the work that will be deferred or covered.
A modest development budget can therefore conceal a continuing commitment. Before approval, assign the maintenance work to a funded role or explicitly choose another arrangement. Repeatedly postponing updates while presenting the plan as current creates an avoidable information problem.
Move from a draft to an owned planning system
First, authorize the scope. Leadership identifies the sponsor, coordinator, services covered, participation process and decisions requiring approval. Inventory existing plans and agreements so the team can reuse valid work.
Second, resolve the connections. Service owners and partners complete the relevant integration records. Finance reviews resource and cash assumptions. Appropriate advisers confirm technical and authority questions. Track unresolved matters openly rather than converting them into confident prose.
Third, test usability. With qualified emergency support, use representative scenarios to examine whether responsible people can find the current material, interpret their roles and complete agreed handovers. Include situations in which usual people or systems are unavailable. Record findings without exposing sensitive information in the public report.
Fourth, approve with explicit conditions. The approving authority receives the proposed plan, evidence of review, remaining limitations, corrective priorities and maintenance resources. Approval of a document should not be represented as proof that every capability has been demonstrated.
Finally, maintain ownership. Assign updates to roles, preserve appropriate version history and integrate corrective actions into management reporting. Trigger a review when an important dependency changes, as well as at the Nation’s chosen regular interval.
Useful indicators include overdue consequential confirmations, critical roles without an accepted alternate arrangement, time needed to retrieve current material in an exercise, unresolved handovers and corrective actions completed and rechecked. Interpret these in context. A higher number of recorded gaps may reflect better discovery, and a closed action is meaningful only if the change addresses the original problem.
Arcus Advisory
Build the management arrangements behind the plan
Arcus can help leadership diagnose gaps in responsibilities, coordination and capacity; evaluate internal, facilitated and shared support options; and decide the scope and resources for a planning program. Concrete deliverables can include a document and dependency inventory, decision-rights map, Emergency Plan Integration Records, operating-cost assessment and implementation roadmap.
An engagement can also support management reporting on corrective actions and document ownership, working with the Nation’s qualified emergency and technical specialists. Scope should distinguish management support from operational command, legal interpretation and specialist response procedures.
Related research and consulting
Is Your First Nation Ready for the Next Emergency? examines evidence of capability once arrangements are in place.
Indigenous consulting services · Emergency Management collection · First Nations Knowledge Centre
Evidence and limitations
- First Nations Health Authority. Communicable disease emergency response. Undated current resource, reviewed October 20, 2026. See also its toolkit announcement of June 25, 2026. B.C. health planning guidance; not a comparative evaluation of emergency plan formats.
- Province of British Columbia. Create and maintain emergency plans. Updated September 11, 2026. Explicitly identifies older planning resources as out of date. Local-authority guidance is not assumed to apply uniformly to First Nations.
- Office of the Auditor General of B.C. Provincial Support for the Village of Lytton’s Wildfire Recovery. Released March 17, 2026. Examination period June 2021–March 2025; findings concern provincial support for the municipality, not an evaluation of Lytton First Nation’s plan.
The decision framework and cost illustration are Arcus analytical synthesis. The sources support the distinctions and management questions discussed; they do not establish a universal plan design, causal reduction in disaster losses or a validated readiness score.
