First Nations Management & Leadership · Arcus perspective
First Nations Health Transformation: What Happens After the Funding Agreement Is Signed?
After a health transformation agreement is signed, the decisive question is which responsibilities should move next, with what authority, support and accountability. Moving more work into a new institution does not, by itself, establish greater practical control over the services that matter to communities.
Arcus’s central management proposition is that a transfer should be designed around a complete service responsibility: the decisions, people, resources, information and partner commitments needed to make that responsibility work. Where only the visible program moves, a Nation-led organization may inherit delivery expectations while essential decisions remain elsewhere. Conversely, transferring every support function at once can overload a capable team and delay improvements that could begin sooner.
This analysis is for Chiefs, Councillors, health executives and senior administrators choosing an implementation sequence. It compares realistic operating choices, identifies evidence that would support or challenge them, and develops the existing Agreement-to-Operation Framework into a practical decision record. It does not interpret a particular agreement or prescribe a governance model for every Nation.
What the agreement settles—and what the operating model must still resolve
First establish the actual scope of the signed instrument. A funding arrangement, agreement in principle and service-transfer instrument can serve different purposes. Ask the designated legal and agreement advisers to identify confirmed responsibilities, conditions, unresolved negotiations and the approvals required for the next step. A public announcement cannot substitute for that reading.
ISC’s health transformation overview describes support for First Nations-led institutions to increase control of health-service design and delivery. It describes several regional initiatives rather than a single institutional blueprint.[1] The organizational task is therefore to translate the participating Nations’ actual direction into decisions that people can exercise. Determine who may change priorities, approve spending, engage personnel and revise service arrangements, including where authority remains with another party.
Imagine, as a hypothetical management example, a new organization taking responsibility for coordinating community referrals. An intake team has been hired, but the organization cannot resolve an eligibility dispute, secure a specialist appointment or obtain information from a receiving provider. The team may be competent while the service remains unreliable. Adding another intake coordinator addresses workload only if workload is the constraint; it does not resolve authority or partner-response problems.
For each proposed responsibility, distinguish three things: what the organization is accountable for, what it can decide, and what it must obtain from partners. A material gap between those three columns is a design issue to resolve before assuming that a reporting relationship or additional funding will make the service operational.
The evidence challenges a simple centralize-or-decentralize choice
The 2024 FNHA evaluation, covering 2019/20–2023/24 and finalized in 2025, reports benefits from bringing decisions closer to communities alongside difficulties with coordination, service consistency and role clarity. It also describes disagreement over the organization’s balance between enabling community delivery and delivering services. These are findings from the BC setting, not a verdict on other regional models.[5]
ISC’s 2023 cluster evaluation of health infrastructure support, covering 2015–2021, found complementary programs operating separately and identified weaknesses in collaboration, sustainable resources and reporting. Its national scope broadens the questions leaders should ask, but it does not establish the best structure for an individual Nation.[6]
These findings support an organizational distinction rather than a universal prescription: the location of a decision and the location of the capability supporting it need not be identical. A community can retain a priority-setting decision while obtaining specialized support through a jointly authorized arrangement. Equally, a shared organization can fund or coordinate services without being the employer of every person delivering them. The mandate and agreements must make those relationships real.
The practical test is to examine functions separately. Community engagement, payroll, service planning, clinical oversight and purchasing do not have the same requirements. Leaders should ask which decisions need proximity to community knowledge, which capabilities benefit from being shared, and which handoffs create unacceptable uncertainty. Choosing one model for every function can conceal the most consequential trade-offs.
Three operating choices, with different obligations
Strengthen community delivery with shared support
Under this option, participating Nations retain agreed service-delivery responsibilities while a shared entity provides selected capabilities, such as procurement support, workforce planning or financial administration. It may be appropriate where local organizations have trusted relationships and functioning services but cannot readily maintain every specialist role.
The benefit to test is stronger local control supported by accessible expertise. The risk is a shared office that adds another approval layer without reducing local work. Specify who can request support, what service is provided, who decides contested priorities and how communities can seek correction. A nominally shared capability is of little value if local staff must maintain a duplicate process because the shared service is unreliable.
Establish direct delivery for selected responsibilities
A Nation-led or collectively mandated institution may directly employ teams and operate agreed services. This can be a reasonable option where the mandate is clear and an integrated team could address a service gap. It requires more than recruitment: supervision, facilities, records arrangements, quality systems, workforce cover and partner relationships must be supported.
The trade-off is more direct operational responsibility, with continuing costs and potential concentration of decisions away from communities. Test how participating Nations will influence priorities and how local variation will be accommodated. Direct delivery should be compared with strengthening an existing provider; creating a new employer is not automatically the most effective route to a better service.
Use a staged combination
A third option combines local provision, shared support and selective direct delivery, with responsibilities changing as capability develops. This permits a narrower next step, but only if interim arrangements have named owners and review points. Without those commitments, a temporary hybrid can become a permanent ambiguity in which each institution believes another is responsible.
Define the conditions for changing the arrangement. These could include a functioning recruitment and supervision model, an agreed information-sharing arrangement or demonstrated partner responsiveness. Describe what would justify retaining the interim model as well as what would trigger the next transfer. Staging should be an explicit strategic choice, not an indefinite postponement of difficult decisions.
Diagnose the binding constraint before changing the chart
A service delay can arise from demand exceeding available capacity, authority being too dispersed, a broken handoff, or a capability that has never been funded. These explanations imply different actions. Before proposing a new department, examine a small, authorized sample of the work: where a request waits, why it waits, and which decision or resource would release it.
If employees spend most of the delay waiting for an external approval, investigate delegation or partner arrangements. If authorized staff cannot keep up with a stable process, assess workload, staffing and coverage. If requests are repeatedly returned because required information differs among organizations, resolve the interface before assuming that more personnel will solve it. Use de-identified operational evidence where possible and obtain the appropriate authority for any review of records.
Do not treat all constraints as internal management failures. An operating model cannot create unavailable housing, eliminate a funding restriction or compel a partner to accept a new obligation. Record those dependencies separately, with the party able to address them. Otherwise, an organizational review can recommend internal restructuring for a problem that requires negotiation, investment or a broader policy response.
Challenge the preferred explanation with contrary evidence. A long vacancy may suggest recruitment difficulty, but filled positions with repeated rework may point to unclear roles or inadequate systems. A fast central approval process might still produce poor decisions if it excludes community knowledge. Ask whether the proposed remedy changes the mechanism causing the problem, rather than merely creating a visible management response.
Fund the recurring responsibility, not just the transition project
Compare options using a common service scope. Include the cost of continuing local work, shared support, travel, supervision, facilities, information systems and partner coordination. Then distinguish one-time establishment costs from the recurring operating commitment. An option can look inexpensive if essential work is omitted or assumed to be absorbed by existing employees.
Test the proposed model under a vacancy, a demand increase and the end of time-limited funding. Ask which responsibilities would still be met and which would become dependent on exceptional effort. Where cost estimates are uncertain, state the assumptions and the decision that depends on them. An unverified savings target should not determine whether an important capability is included.
ISC’s cluster evaluation identified both financial and human-resource constraints and misalignment between intended outcomes and available resources.[6] That evidence supports checking the full operating requirement; it does not justify a standard administration percentage or a staffing ratio for every organization. Build the resource case from the actual mandate, service geography, workforce conditions and chosen responsibilities.
Keep transition capacity visible. Employees maintaining services may also be asked to document processes, develop new systems and participate in engagement. Decide which current priorities can be adjusted, what temporary support is warranted and who remains responsible for routine decisions. A launch budget that pays for software but leaves no time for implementation is not a complete implementation budget.
Protect continuity while retaining the purpose of transformation
FNHA’s historical transition account separated the mechanics of transfer from subsequent service redesign and described work on systems, assets, programs and organizational culture.[3] This illustrates a useful sequencing distinction. It is not a timetable to copy, and preserving an inherited arrangement at transfer should not become a reason to leave its limitations unexamined.
For each affected service, document the current responsible organization, the proposed responsible organization and the conditions for the change. Relevant service and clinical authorities must define and approve readiness and continuity arrangements. Management should make dependencies and escalation clear, including who acts when a planned condition is not met. An executive target date is not evidence of service readiness.
A hypothetical administrative transition could begin with planning and support responsibilities while an existing provider retains delivery. That approach may reduce immediate disruption, but it needs a clear route for resolving problems between the two organizations. If a service gap is already causing harm, an excessively slow sequence can also carry consequences. Compare the risks of proceeding, delaying and taking a narrower step, with the appropriate professional advice.
Workforce communication should distinguish authorized organizational decisions from employment matters still subject to advice and applicable procedures. Map work, supervision and support before making promises about individual outcomes. Explain what employees can rely on now, what remains unresolved and when the next decision will occur, while protecting personal information.
Information governance is part of the operating model
FNIGC describes OCAP® in terms of ownership, control, access and possession and emphasizes that First Nations apply the principles in their own circumstances.[4] A shared institution should therefore establish how participating Nations wish to govern information before choosing systems that make those decisions difficult to implement.
Identify separately the information needed for care, administration, funding, organizational oversight and research. The fact that the same organization handles several functions does not establish permission to combine their records. Confirm access, custody, sharing and use with the designated Nation authorities and appropriate privacy, legal and clinical advisers.
The practical design question is whether authorized users can obtain what they need without unnecessary disclosure. Governing leaders may require information on access and implementation without identifiable patient details. A shared service may need processing access without authority to reuse data for unrelated analysis. Resolve those distinctions in responsibilities and agreements before treating a common database as evidence of integration.
Agreement-to-Operation Framework: a decision record
This original Arcus framework is a management discussion aid, not a validated readiness score. Apply it to one proposed responsibility at a time. Record the evidence, uncertainty, accountable decision-maker and next action for each condition. The reasons to reconsider below identify questions requiring resolution; the authorized leaders and relevant professionals determine the decision.
Mandate: What has actually been authorized?
Evidence to bring: An agreed responsibility statement, the relevant authority and remaining conditions.
Reason to reconsider: A responsibility is proposed whose authority or scope remains disputed.
Model: Where should decisions and delivery sit?
Evidence to bring: A comparison of local, shared and direct-delivery options, including partner obligations.
Reason to reconsider: The preferred chart leaves a service handoff or decision without an accountable owner.
Capability: Can the selected model carry its full workload?
Evidence to bring: A costed operating requirement, workforce and supervision arrangements, systems and transition capacity.
Reason to reconsider: The case assumes unfilled roles, unfunded support or savings that have not been demonstrated.
Continuity: What must be true before this step proceeds?
Evidence to bring: Service and clinical readiness decisions by the relevant authorities, with current responsibility and escalation documented.
Reason to reconsider: A material readiness condition is unresolved and no acceptable alternative has been authorized.
Accountability: How will Nations know the change is useful?
Evidence to bring: Community-defined results, information-governance arrangements, review dates and a route for changing the model.
Reason to reconsider: Reporting tracks project completion without showing whether the intended service improvement is occurring.
A leadership team can use the record to distinguish an authorized next step from a future ambition. Instead of declaring the whole organization ready or unready, it can authorize a defined responsibility, subject to named conditions, while retaining a different arrangement for another service. That makes the sequence reviewable and avoids treating organizational maturity as a single numerical score.
Where leadership and partners disagree about the next transfer, an independent assessment can compare the options against the same responsibility, evidence and operating requirements.
Discuss an operating-model and implementation assessment with Arcus →
Test whether access changes—not only whether the organization launches
Lavoie and colleagues’ iPHIT study used Manitoba administrative data from 1986–2016 and found an association between access to a broader complement of local primary healthcare and lower hospitalization rates for ambulatory care sensitive conditions. The paper appeared online in 2020 and in the Canadian Journal of Public Health in 2021.[7] This is observational, historical evidence from Manitoba; it does not isolate the effect of a new authority or establish that one governance structure causes better outcomes.
Its relevance to the leadership decision is the distinction between institutional activity and service access. Incorporating an organization, filling a position and installing a system are implementation milestones. The organization should also examine whether people can obtain the intended services, whether referrals reach a responsible recipient and whether communities experience the changes they prioritized. Select measures with participating Nations and service leaders rather than importing a dashboard unchanged.
FNHA’s description of its governance arrangements expressly notes that its work does not replace provincial ministry and regional health authority services.[2] Results therefore need to be examined across institutional boundaries. If the new organization processes requests faster but people still cannot obtain the next service, investigate the remaining constraint before reporting the transformation as successful.
Combine operational measures with authorized community feedback and a clear baseline. Examine changes in demand, staffing, funding and partner services that could explain the result. A favourable trend is a reason to investigate what is working, not proof that the new structure caused it. An unfavourable trend should prompt diagnosis rather than immediate attribution to the workforce or community.
What leadership should commission next
The next useful product is a short decision brief supported by a sufficiently detailed operating case. Define the proposed responsibility, the alternatives, expected community benefit, full resource requirement, dependencies and evidence still missing. Name the authority for the decision and explain what remains with partners during implementation.
An internal team may be able to prepare this work where the scope is bounded and relationships are clear. Independent management support can be useful when institutions disagree about responsibilities, several operating models remain plausible or current executives cannot both maintain services and evaluate the options. Commission an assessment of the actual decision, rather than a new chart detached from the service problem.
Arcus’s organizational-design and transformation work can support responsibility mapping, management-capacity assessment, comparison of operating models and implementation planning. Useful outputs could include a function-by-function options analysis, decision-rights map, workforce and support-function requirements, and a staged implementation record with dependencies and review points. Agree the scope with leadership; Nation authorities retain decisions, and clinical, legal and other specialist matters require the relevant expertise.
Arcus Advisory
Resolve the operating decisions behind your next transfer.
If responsibilities, support functions or partner commitments remain unsettled, Arcus can help assess the current arrangement and compare practical implementation choices. An initial discussion can establish the decision to be supported, the evidence available and whether independent organizational advice would add value.
Related research and consulting
When Has a First Nation Outgrown Its Organizational Structure? Seven Warning Signs
Arcus Organization Design consulting · Arcus consultant directory · Health Transformation collection · First Nations Knowledge Centre
Sources, findings and limitations
- Indigenous Services Canada. First Nations health transformation. Updated August 9, 2024. Policy context; not verification of every initiative’s current stage.
- First Nations Health Authority. Our governance structure. Undated web resource. BC institutional example; not a universal allocation of authority.
- First Nations Health Authority. Transition and transformation. Historical account of the 2011–2013 transfer. Historical systems and transfer sequence; older future-tense passages are not current instructions.
- First Nations Information Governance Centre. The First Nations Principles of OCAP®. Undated web resource. Principles and Nation-specific application; not a substitute for an organization’s information-governance decisions.
- First Nations Health Authority. 2024 Evaluation of the FNHA: Final Report, 2019/20–2023/24. Finalized 2025. See section 1.5 on limitations and section 5.4 on regionalization. Multiple evidence streams; respondent bias and concurrent emergencies limit interpretation. Findings describe the evaluation period, not all subsequent changes.
- Indigenous Services Canada. Cluster Evaluation of Health Infrastructure Support for First Nations and Inuit. 2023; fiscal years 2015–2021. Executive summary, relationships and program outcomes. Data quality and uneven interview participation constrain national generalization.
- Lavoie JG et al. The relationship between rates of hospitalization for ambulatory care sensitive conditions and local access to primary healthcare in Manitoba First Nations communities: results from the iPHIT study. Canadian Journal of Public Health. 2021;112:219–230. DOI: 10.17269/s41997-020-00421-3. Abstract and publication record verified. Observational historical Manitoba evidence; no causal estimate of a new health authority.
Research reviewed October 17, 2026. The thesis, options analysis and decision framework are Arcus management synthesis, not proprietary empirical findings or a validated diagnostic. Hypothetical examples do not describe clients. Evidence from BC and Manitoba is not a prescription for another Nation. OCAP® is a registered trademark of the First Nations Information Governance Centre (FNIGC).
Contact Arcus about an organizational assessment or implementation engagement →