Moving From Federal Programs to First Nations-Controlled Health Services

First Nations Knowledge Centre / Health Transformation

First Nations Management & Leadership · Arcus perspective

Moving From Federal Programs to First Nations-Controlled Health Services

Assess both sides of readiness

A receiving First Nations health organization can prepare diligently and still inherit a service that is underfunded, poorly documented or dependent on systems it cannot control. Training the incoming team will not correct an unresolved property issue, a missing software licence or a funding model that excludes essential support. Readiness must therefore be assessed on both sides of the transfer.

Arcus’s central management insight is that transfer readiness has two distinct questions: can the receiving organization operate the service, and is the service being offered in a condition that allows it to succeed? Treating the first question as the entire assessment risks making Nations accountable for inherited weaknesses without the resources or authority to address them.

The strategic objective remains First Nations control, guided by the Nations’ own decisions and priorities. A rigorous acceptance process supports that objective by making obligations, constraints and remedies explicit. It should not become a procedural device for indefinitely postponing self-determination or imposing externally defined standards without appropriate agreement.

What the evaluation evidence reveals

Indigenous Services Canada’s Health Infrastructure Support cluster evaluation explicitly recognizes that programs themselves need to be ready for transfer, including adequate funding, governance and knowledge-transfer arrangements. It warns against leaving First Nations and Inuit to repair programs before fully assuming control. This is a significant distinction from assessing only community capacity. The evaluation concerns a range of programs and contexts; it is not a finding about the condition of any particular service now under negotiation.1

The FNHA technical case study describes the organizational effort required for the 2013 transfer, including new corporate capability, detailed agreements and infrastructure coordination. It records transfer in two phases. This historical case demonstrates that the service package includes supporting capabilities as well as visible delivery roles; it does not prescribe another Nation’s timetable or implementation budget.2

The FNHA’s historical transition account distinguishes the mechanics of assuming responsibility from subsequent service redesign, and identifies agreements covering people, records, assets and other dependencies.3 The local planning implication is to state which improvements are required before acceptance and which belong in a separately funded transformation program.

Separate responsibility, discretion and practical control

For each service, map three things. Responsibility identifies who must deliver and answer for the result. Discretion identifies which rules, spending choices and service arrangements can be changed. Practical control identifies whether the organization can obtain staff, information, systems and partner cooperation needed to exercise that discretion.

A nominally flexible budget may offer little practical control if most spending is committed to unavoidable contracts. A new reporting line may not confer authority over an external hospital referral process. A transferred facility may require repairs before it can support the planned service. These constraints should appear in the decision record, rather than emerge as explanations after transfer.

Test several specific decisions with the negotiating and operating teams: changing service hours, moving a budget between activities, replacing a supplier, responding to a safety concern and obtaining information for a service review. Record who can authorize each step and what conditions apply. Appropriate legal and professional review is necessary for the actual agreements; this is a management diagnostic, not a determination of jurisdiction.

Create an inventory of the service as it really operates

Begin with what patients and community teams rely on, then trace the support behind it. Record services, users, delivery locations, schedules, staffing, contracts, assets, records, licences, funding streams and external partners. Include informal workarounds where staff use personal knowledge or relationships to keep services functioning. The existence of a policy does not establish that the process works in practice.

Assign an evidence status to each item: verified, supplied but untested, incomplete or disputed. A signed equipment list is different from evidence that equipment is serviceable and supported. A staffing establishment is different from filled positions with available coverage. A historical spending total is different from a funded forecast for the receiving organization.

Use a joint issue register that separates inherited deficiencies, new requirements created by transfer and improvements desired after transfer. For each issue, identify its service consequence, responsible party, remedy, funding source and decision date. This prevents every unresolved matter from becoming an undifferentiated risk owned by the incoming chief executive.

Examine competing explanations before accepting a remedy

A service backlog might arise from insufficient staffing, inefficient scheduling, a restrictive eligibility rule or limited capacity in the next provider. Each explanation points to a different remedy. Transferring more employees may help the first problem but leave the others intact. Review a sample of actual cases and compare the proposed remedy with the point where work stops.

An apparent funding shortfall also needs analysis. It may represent an inherited operating deficit, a legitimate new corporate cost, rising demand, a service expansion or a temporary overlap during transition. These should not be negotiated as if they were the same expenditure. Separate the baseline service cost from the cost of the new operating arrangement and the cost of future improvements.

The receiving organization should challenge optimistic assumptions as well as obvious deficiencies. If the forecast relies on vacancies remaining unfilled, unpaid coordination or uninterrupted use of another organization’s systems, it does not describe a sustainable service. Conversely, do not assume every inherited process must be replaced immediately; some can provide a stable bridge while a better model is developed.

Compare transfer pathways with explicit conditions

A staged transfer moves a bounded set of responsibilities when dependencies can be separated and readiness evidence is strong. It can reduce the amount changing at one time. Its cost is a longer period of interfaces, duplicate arrangements and shared accountability. Define who owns any service that crosses the boundary between transferred and retained functions.

A coordinated transfer with temporary support moves a larger package while time-limited agreements preserve selected systems or specialist support. It can simplify responsibility for delivery, but the receiving organization needs enforceable service commitments and a funded route away from the temporary dependency. A support agreement without an exit plan can become permanent dependence.

Deferring a specific component pending remedy may be appropriate when a material dependency is unresolved. Identify the exact condition, the party responsible for correcting it and the service-continuity arrangement in the meantime. Distinguish a narrow unresolved component from an unsupported conclusion that the entire organization is unready.

The choice should follow the Nations’ mandate, the service’s dependencies and the consequences of delay. Compare credible options, including the costs of continuing the present arrangement. A target date creates discipline only when decision-makers can see what remains uncertain and what must happen for that date to be viable.

Negotiate an affordable operating position

Build three financial views: the cost of current delivery, the recurring cost under First Nations control and the one-time cost of establishing that arrangement. Include employer functions, professional oversight, finance, records management, technology, procurement, insurance and facilities as applicable. Some costs may have been absorbed elsewhere in the federal system and may not appear in a local program ledger.

Add a cash-flow view showing when funds arrive relative to payroll, supplier payments and transition commitments. A sufficient annual budget does not guarantee that the organization can meet an early payment obligation. Identify authorized arrangements for timing gaps and avoid assuming access to borrowing or reserves that the governing body has not approved.

Consider a hypothetical service with a $2 million annual program budget and $180,000 of newly required recurring support. If the transfer funds only the $2 million, the operating model has a $180,000 gap before inflation or service expansion. A separate $250,000 establishment grant would pay for setup only to the extent its terms permit; it would not solve a recurring gap. These figures illustrate classification and are not benchmarks or client results.

Agree how uncertain items will be reconciled. Material asset condition, open commitments or incomplete records may need specific investigation and negotiated treatment. The governing body should understand which risks are priced, which are covered by a remedy and which remain unresolved. Specialist advice should address the legal and financial terms of any risk allocation.

Make acceptance a decision supported by evidence

Use readiness gates tied to the service being accepted. Relevant evidence can include authorized staffing and coverage, functioning payment processes, accessible records, tested partner contacts and confirmed responsibilities for urgent issues. Require accountable owners to demonstrate the critical processes, rather than reporting only that a workstream is green.

Give the governing body a concise decision paper: service scope, authority gained, unresolved issues, funding position, evidence tested and available options. Record the consequences of proceeding, narrowing scope or changing timing. Conditions should be specific enough that management can determine whether they have been satisfied.

After transfer, maintain an agreed stabilization period with owners for inherited and new issues. Compare actual service demand, support costs and unresolved dependencies with the acceptance assumptions. Escalate discrepancies through the agreed mechanism. The purpose is to make transferred control workable and support deliberate redesign once the operating position is understood.

The Two-Sided Transfer Readiness Framework

This original Arcus decision framework is a management aid for local adaptation. It is not a validated assessment instrument or a substitute for the Nation’s authority and relevant professional requirements.

01

Mandate and discretion

Question: Which responsibilities and decisions move together?

Decision evidence: Nation authorization, service scope and a tested decision-rights map.

02

Service condition

Question: What is the actual state of the incoming service?

Decision evidence: Verified assets, staffing, records, commitments and a classified issue register.

03

Receiving capability

Question: Can the new organization operate the agreed package?

Decision evidence: Demonstrated corporate and service processes, accountable owners and coverage.

04

Funding and remedies

Question: Are recurring costs and inherited deficiencies addressed?

Decision evidence: Separate baseline, operating and establishment budgets with funded actions.

05

Acceptance and review

Question: Who can accept, condition or defer the transfer?

Decision evidence: Authorized decision paper, specific conditions and a post-transfer review mechanism.

Turn the design into an operating commitment

Commission a joint service inventory and a two-sided readiness review early enough for findings to affect the agreement. Give the receiving team access to the operational evidence it needs through appropriate arrangements. Prioritize issues that could change service scope, cost or the timing of acceptance.

Build the transfer plan around dependencies and decisions. Each critical gap needs an accountable party, a funded response and an acceptance criterion. Preserve a clear record of what is agreed, what is provisional and what remains disputed. Use professional review where the terms affect legal obligations, employment, information or clinical responsibility.

Arcus can support the service inventory, operating-cost analysis, readiness assessment and management decision paper. A focused engagement should leave leadership with a clear view of the control being gained, the capability required and the issues that need resolution before the next commitment.

Discuss a focused design and implementation review →

Sources and limits of the evidence

  1. ISC, Cluster Evaluation of Health Infrastructure Support for First Nations and Inuit. See service-transfer findings on readiness of both communities and programs. Context-specific evaluation evidence, not a review of a current negotiating package.
  2. FNHA Evaluation, Technical Case Study Report. See pages 13–15 on organizational development and the 2013 transfer. Historical evidence; no universal duration or budget inference.
  3. FNHA, Transition and transformation. Historical transition materials describing the 2013 process; not a current offer of terms for another First Nation.

Research reviewed October 18, 2026. Decision frameworks, options and hypothetical illustrations are Arcus management synthesis. No client outcomes or universal staffing, savings or impact benchmarks are claimed.

Health Transformation collection · Transitioning health services without disrupting patient care · Organization design services · Arcus consultant directory

Discuss your Nation’s health transformation priorities →