First Nations Management & Leadership · Arcus perspective
How to Redesign a First Nation Administration Without Disrupting Community Services
A redesigned administration should make community services more dependable. Yet the transition itself can interrupt the work: employees receive new reporting relationships before approval limits are settled, files move before responsibilities are accepted, or a manager inherits a service without the information needed to supervise it. The management decision is therefore about the transition as well as the destination.
For Chiefs, Councillors, Band Managers and executive directors, continuity is a design requirement from the beginning. A proposed structure should explain how the Nation will keep delivering services while roles, systems and working relationships change. This article offers a practical management approach. Illustrations are hypothetical, and the appropriate arrangements depend on the Nation’s laws, jurisdiction, priorities and circumstances.
What documented organizational change can teach—and cannot prove
The FNHA evaluation covering 2019/20–2023/24, in its June 2025 final report, describes organizational achievements alongside opportunities to clarify departmental responsibilities and decision-making. Its discussion of regionalization identifies coordination and capacity issues.[5] This is evidence from a large provincial health organization, not a representative study of individual Nations’ administrations or proof that a particular structure causes better outcomes.
The Auditor General’s 2015 examination of selected FNHA governance policies found that communicated policies had limited accompanying implementation guidance.[6] This historical finding is not a claim about present compliance. Together, the cases suggest a practical question: can employees actually exercise the authority that the design assigns?
Arcus’s analytical conclusion is to treat a transfer of responsibility as an operational acceptance decision. Approval of a chart starts the implementation work. Transfer should follow evidence that the incoming owner can handle ordinary work, exceptions and service recovery. This conclusion is a management synthesis, not a validated prediction of transition outcomes.
Begin with the services that must continue
Start the review with a service map rather than a replacement organizational chart. Identify what people receive, how they access it, who performs the work and which other teams make delivery possible. Include administrative dependencies such as payroll, purchasing, records, scheduling and technology access. A service can appear operational while one of these supporting processes is close to failing.
Ask service leaders to describe the consequences of interruption. Some activities can be rescheduled; others need an authorized alternative immediately. A useful continuity discussion distinguishes inconvenience, delayed commitments, financial exposure and risks to people. Leadership should decide which risks require additional protection rather than leaving each department to interpret urgency differently.
For example, moving responsibility for a community facility is more than changing its reporting line. Someone must retain responsibility for maintenance requests, contractor access, equipment records and urgent decisions. A handover that names the incoming manager but leaves these details unresolved transfers a title without transferring operational control.
Separate the problem from the proposed solution
Leaders may begin with a preferred answer: combine two departments, appoint a director or create a central office. Before committing, describe the specific failure the change is intended to resolve. Is a decision delayed because authority is unclear, because a manager lacks information, or because the workload exceeds available capacity? Each explanation suggests a different response.
Trace several ordinary transactions from request to completion. Ask employees where work waits, returns for correction or requires informal intervention. Compare these observations with written policies. Where the official process differs from everyday practice, determine whether the workaround protects service delivery or introduces a risk that the redesign must address.
A process improvement may solve a narrow problem without structural change. Conversely, repeated cross-departmental delays may justify reviewing the operating model. Record the alternatives considered and the reasons for the preferred option. This helps leadership distinguish an evidence-based design choice from a response to one difficult incident or individual relationship.
Choose between process repair, delegated authority and structural change
Repair the process first when requests repeatedly return because information is missing but the service owner and authority are already clear. Test a complete intake checklist and a defined handoff on recent cases. If waiting time falls without changing reporting lines, that weakens the case for a larger restructure. The risk is standardizing a process that still sends too many decisions to one person.
Delegate or redistribute work when complete requests consistently wait for the same approval, or when demand exceeds the available time of a qualified role. Review the work queue and the decisions that actually require senior authority. Delegation needs appropriate limits, competence and review; extra staffing needs recurring funding. Either option can fail if the underlying problem is a disputed mandate rather than workload.
Change the structure when service responsibilities remain fragmented across departments even after mandates, handoffs and delegations are clarified. Compare a shared support function with keeping specialist capacity near service delivery. Centralization may improve consistency but lengthen access or weaken local knowledge; distributed roles may improve responsiveness while increasing duplication and coordination effort. Examine the actual transactions and community access needs that would favour each option.
Use evidence that could change the recommendation. A delay caused by an external approval or uncertain program funding may persist under every internal structure. Record that dependency separately and decide how to manage it. Do not attribute it to employee resistance or assume that a new director can remove it.
Give the transition a clear authority structure
Appoint an accountable sponsor and a transition lead, with a mandate proportionate to the work. Clarify which decisions they may make, which require executive approval and which remain with the Nation’s governing bodies. A transition team should not become an informal route around established authorities, procurement requirements or employment processes.
FMB’s Administrative Governance guidance describes delegation, documentation and monitoring within its financial-administration framework.[2] This is useful design guidance, but the Nation must determine what its own laws and policies permit. Delegating transition work does not mean that leadership can disregard responsibilities reserved to it.
Create a practical escalation route for contested handovers. If two managers disagree about responsibility, identify who resolves the question and by when. Keep a decision log showing the issue, authorized decision and affected services. Without this discipline, temporary arrangements can become permanent through repetition while nobody has formally accepted their consequences.
Design around the employee’s real working day
A proposed reporting arrangement can look sensible until it is tested against actual work. Consider meeting commitments, supervision, travel, on-call responsibilities, seasonal peaks and community-facing duties. Ask whether the incoming manager has time to understand the service and whether employees will know where to obtain decisions during the transition.
Update roles and reporting relationships together with the practical supports employees need. FMB’s Human Resources guidance discusses current organizational charts, job descriptions and training plans.[3] These documents should reinforce a workable arrangement, rather than create the appearance of clarity while approval processes remain unresolved.
Where roles may change materially, obtain the appropriate professional advice and follow applicable processes before making commitments. Organizational design is not a substitute for employment advice. Explain what has been decided, what remains open and how staff input will inform implementation. Employees cannot plan responsibly if rumours become their principal source of information.
Transfer knowledge and information deliberately
Every handover should identify the work, current commitments, unresolved issues, approved procedures and records required for continuity. Assign both an outgoing and an incoming owner where possible. The incoming owner should confirm what has been received and identify remaining gaps. A folder transfer alone is not evidence that responsibility can be exercised effectively.
Information access requires its own decision. FNIGC explains the First Nations principles of OCAP® as supporting First Nations information governance, with interpretation reflecting each Nation’s circumstances.[4] A restructuring does not create blanket permission to share personal, community or organizational information across every new team.
For a hypothetical shared intake function, determine which information employees need to receive a request, which records require restricted access and who authorizes a referral. Resolve these questions before launching a shared system. Preserve the Nation’s control over its information and obtain advice on applicable privacy obligations where necessary.
Sequence the work around dependencies
Do not schedule every change for one launch date merely because a new chart has been approved. Distinguish decisions that can take effect immediately from changes requiring recruitment, training, revised policies or system configuration. The order should reflect operational dependencies: an employee cannot use new authority before the relevant limits and controls are established.
The CCP Handbook connects implementation with responsibilities, resources, timeframes and monitoring.[1] Apply that logic to the redesign. Each workstream needs an owner, a realistic completion condition and a clear relationship to other work. Record capacity requirements explicitly rather than assuming that existing managers will absorb the transition alongside full workloads.
For example, a centralized purchasing team might first support one service with agreed procedures, then expand after the handoffs work. This is a management option, not a universal prescription. Some changes cannot be usefully piloted; others should wait until essential staffing or information requirements are met. Leadership should approve the sequence with those constraints visible.
Budget the transition and the enduring operating model separately
Cost the implementation tasks: mapping services, preparing procedures, configuring access, training, staff communication and overlap between outgoing and incoming owners. Identify which work uses existing employees and which requires additional cash. An allocation of staff time is not automatically a new expenditure, but it still needs a decision about the work those employees will stop or defer.
Consider a fictional eight-week transition requiring 160 hours from existing staff. Assume 80 hours of temporary backfill at $45 an hour, $6,000 of external implementation support and $2,000 of one-time system work. Incremental cash cost is $11,600: $3,600 plus $6,000 plus $2,000. The administration must also accommodate 160 hours of internal transition effort. Backfill covers only half of those hours; the remaining 80 hours require an explicit workload adjustment. These are illustrative assumptions, not Arcus fees, wage benchmarks or client results.
The incoming operating model needs its own annual budget: salary and benefit changes, ongoing supervision, software support, travel and any retained external assistance. Avoid presenting vacant positions as savings until service needs and recruitment plans are resolved. Do not count a transferred task as eliminated work.
A phased transfer may spread the peak workload but prolong coordination and temporary duplication. A single cutover may shorten overlap but require greater preparation and a stronger fallback. Compare both against the consequences of interruption, the ability to reverse the change and the capacity available in the intended period. Where the plan depends on unfunded recurring roles, redesign the scope or resolve the funding before representing the model as sustainable.
Service Continuity Design Framework
Use four connected tests before transferring a responsibility. The framework is an original management aid, not a certification standard or numerical diagnostic. Its purpose is to expose unfinished work while leadership still has choices about timing and resources.
Protect the service
Define the service commitment, interruption risks and authorized fallback. Identify what must remain available throughout the change and who can respond if normal delivery fails. Describe the minimum acceptable arrangement in operational terms that employees can apply.
Equip the incoming owner
Confirm authority, skills, capacity, records and supporting relationships. Ask the incoming owner to explain how an ordinary request and an urgent exception will be handled. Where the answer depends on assumptions, record and resolve them before the transfer.
Test the handoff
Walk through a realistic example with the people who will perform the work. Check decisions, referrals, information permissions and escalation. Include the person receiving the service where an appropriate and respectful participation process is available.
Stabilize and learn
Assign responsibility for monitoring early problems and correcting the design. Retain an escalation route until ordinary work is reliable. A launch date marks the beginning of operational learning, not proof that the transition has succeeded.
Turn the continuity framework into an acceptance record
For each transferred service, the transition lead should assemble a short record identifying the service commitment, outgoing and incoming owners, approved authority, necessary records and access, unresolved risks, fallback and review date. The incoming owner confirms readiness; the accountable executive authorizes the transfer within the Nation’s established decision arrangements. A disagreement remains visible rather than disappearing into a general “ready” label.
Test one ordinary request and one realistic exception before transfer. For a purchasing handover, this might include a complete routine requisition and an urgent request requiring a different approval route. Check that the employee can identify the correct authority, retrieve the records, contact the necessary person and record the outcome. A successful exercise supports readiness; it does not establish that every situation has been tested.
Agree the response to a failed test in advance: repair the missing access, provide temporary qualified support, narrow the transfer or defer it. For an essential service without a workable fallback, unresolved readiness is a reason to change the implementation plan. Do not use a weighted score that allows good communications to compensate for absent operating authority.
During stabilization, the service owner monitors missed service commitments, unresolved requests, repeated handoff errors and staff time spent recovering exceptions. Compare with a pre-transition baseline and consider seasonal demand or external disruptions before attributing improvement to the redesign. End temporary support only when agreed service conditions are met and the owner accepts the remaining workload.
Explain the change in terms members can use
Community communications should answer practical questions: where to go, whom to contact, what changes and how concerns will be addressed. A new department name is less useful than a clear explanation of access and follow-up. Provide information in formats and languages appropriate to the Nation and the services involved.
Do not promise improved outcomes before there is evidence. Explain the intended improvement and how leadership will review whether it occurs. Ask for feedback on the service experience while protecting confidential information. A member should not have to understand the internal restructuring to obtain a timely response.
Preserve familiar contact routes during transition where feasible, with responsibility for redirecting requests. If an old channel must close, identify how outstanding matters will be handled. A communication plan should include the people whose work connects the Nation with partners and external service providers, so that requests do not disappear between organizations.
Know when a formal review is needed
An organizational review is useful when service problems cross several departments, when new responsibilities substantially change the operating model, or when leadership needs independent evidence to choose between alternatives. Define the decision the review must support, the services in scope and the information that may be used.
Ask for implementation requirements alongside design recommendations: transition costs, workforce implications, dependencies and continuity protections. A useful review distinguishes what can be improved now from changes that require resources or additional approvals. It should leave the Nation with a manageable program of decisions rather than an attractive chart with no route into practice.
The test of redesign is whether the organization can reliably carry out the Nation’s priorities. Protecting services during the transition is part of that test. Leadership can begin by selecting one recurring cross-departmental problem, mapping its full journey and using the continuity framework to establish what a safe, workable change would require.
Arcus Advisory
Design the change and the service transition together.
An Arcus engagement could diagnose service delays and handoff failures, evaluate process, staffing and structural alternatives, and help leadership decide which responsibilities should change. Agreed deliverables can include a service-dependency map, decision-rights matrix, operating-model comparison, transition budget and readiness records. Implementation support can help the Nation test handovers, resolve dependencies and measure service continuity. Scope and responsibilities should be agreed around the Nation’s priorities; these are proposed engagement outputs, not claims of demonstrated client results.
Related research and consulting
When Has a First Nation Outgrown Its Organizational Structure? Seven Warning Signs
Arcus Organization Design consulting · Organizational Design & Change collection · First Nations Knowledge Centre
Sources and further reading
- Indigenous Services Canada. CCP Handbook: Comprehensive Community Planning for First Nations in British Columbia, fourth edition.
- First Nations Financial Management Board. Administrative Governance.
- First Nations Financial Management Board. Human Resources.
- First Nations Information Governance Centre. The First Nations Principles of OCAP®.
- First Nations Health Authority. Evaluation of the First Nations Health Authority, 2019/20 to 2023/24. Final report, June 2025; sections 1.4–1.5 and 5.3–5.4. Commissioned evaluation using multiple evidence streams; respondent bias and external disruptions limit interpretation.
- Office of the Auditor General of Canada. Establishing the First Nations Health Authority in British Columbia. Fall 2015, Report 7, paragraph 7.66. Historical findings from selected governance policies, not an assessment of present practice.
The management analysis, hypothetical illustrations and original framework are practical guidance, not a validated diagnostic or a prescription for every Nation. FMB guidance describes its financial-administration framework; local applicability must be confirmed. OCAP® is a registered trademark of the First Nations Information Governance Centre (FNIGC). Sources reviewed October 19, 2026.