First Nations Management & Leadership · Arcus perspective
The Five-Year Roadmap for Building a First Nations-Controlled Health System
Use five years as a planning horizon
A five-year roadmap can give leaders a shared direction without pretending that every funding agreement, recruitment outcome or service improvement can be scheduled precisely. Its value lies in connecting long-term priorities to the capabilities, decisions and resources needed next. A calendar filled with projects is less useful if it does not show what depends on what.
Arcus’s planning proposition is to combine a stable direction with conditional commitments. The Nation’s health priorities and authority guide the program, while later investments depend on demonstrated readiness, sustainable resources and evidence from earlier work. Five years is an organizing horizon in this article, not a promise that a complete health system can be built within a fixed period.
The roadmap should make three things distinguishable: work that is authorized and funded, work that is planned but conditional, and longer-term aspirations requiring further decisions. This clarity protects credibility with communities and helps managers avoid treating an unfunded ambition as an immediate delivery obligation.
Evidence favours an adaptive planning discipline
FNHA’s public account of its 2026/27 Summary Service Plan describes a refresh informed by engagement, an environmental scan and evaluation findings. It connects goals with strategies, performance measures and annual priorities. This is a concrete example of linking longer-term direction to an updated operational plan; it is not an evaluation showing that a five-year startup sequence will succeed elsewhere.1
Audit Scotland’s 2018 integration review identifies weaknesses in longer-term financial planning and alignment between strategic and operating plans. Its findings support examining whether workforce, information and organizational plans can deliver the strategy. They come from a different institutional context and do not prescribe a First Nations roadmap.2
The sequence below is therefore an original planning framework for adaptation. Existing organizations may already meet some conditions, while a newly formed body may require more time. Urgent service needs may require work in parallel, with appropriate capacity and safeguards. The labels describe a logical progression rather than mandatory annual deadlines.
Year one: establish the mandate and a credible baseline
Begin with the appropriate Nation authorization, a clear service scope and an understanding of existing capabilities. Map current services, access barriers, funding, staffing, facilities, information arrangements and external dependencies. Include community experience and local knowledge through appropriate processes.
Identify the immediate service commitments the organization can support and the longer-term changes it intends to pursue. Distinguish creating a new institution from improving an existing one or accepting transferred services. Each has different establishment and readiness requirements.
The governing decision at this stage is whether the proposed initial portfolio is authorized, affordable and operable. Evidence should include named responsibilities, a realistic funding and cash-flow position, essential support functions and a plan for material gaps. A completed strategic document alone is not sufficient.
Keep urgent improvements visible. A multi-year planning exercise should not delay a practical correction that is already authorized and supported by evidence. The roadmap should distinguish those immediate actions from larger commitments that need further design.
Year two: demonstrate dependable delivery
Concentrate on making the initial portfolio work reliably. Test the service pathways, management routines, payment processes, information arrangements and partner handoffs. Establish useful baselines for service reliability, local workload, access and costs.
Use early evidence to distinguish startup issues from recurring design problems. A temporary training gap may resolve with support. A process that consistently requires more staff time than budgeted may require redesign or additional recurring resources. Do not describe both as short-term implementation noise.
The expansion decision should show what has become dependable, what remains fragile and what additional capability the next service requires. A successful pilot should not be assumed to work everywhere without considering differences in geography, staffing and community priorities.
Protect managers’ capacity to learn and improve. If the organization adds new services faster than it can stabilize existing ones, the roadmap may create a permanent transition rather than a sustainable institution.
Year three: expand through tested capability
Consider additional services, communities or responsibilities where the mandate, resources and supporting arrangements are credible. Reuse capabilities that have demonstrated value, such as shared professional support or a reliable referral process, while adapting the service to local needs.
Compare expansion with strengthening the existing portfolio. A new service may be highly visible, but better continuity or a stronger local workforce may provide greater value. Make the opportunity cost explicit: what will receive less management attention or funding if expansion proceeds?
The decision should include full recurring costs, transition requirements and the effect on current services. Identify the dependencies that remain outside the organization’s control and how partners will address them. Expansion should not rely on unconfirmed cooperation or optimistic recruitment assumptions.
Use conditional commitments where appropriate. For example, planning and engagement may proceed while a larger facility or staffing commitment waits for specified funding and readiness evidence. The conditions should be transparent and capable of being assessed.
Year four: improve integration and address uneven performance
Review the system across service boundaries. Determine whether people experience dependable handoffs, whether some communities carry a disproportionate access burden and whether corporate support has kept pace with delivery. Look for persistent workarounds that have become hidden operating costs.
Consider targeted redesign, shared services or revised partner arrangements where evidence supports them. Integration should be judged by service experience and accountability rather than the number of functions placed under one executive. Some services may work better through agreements than direct consolidation.
Investigate competing explanations for variation. Different outcomes may reflect local needs, workforce stability, service design or external conditions. Regional averages can conceal important differences, while small numbers can make annual comparisons unstable. Use appropriate interpretation and community context.
The governing decision is whether the current model remains fit for the mandate and what changes would improve it. A roadmap should permit redesign when evidence warrants it, rather than defending the original configuration because it appeared in the five-year plan.
Year five: evaluate, renew and choose the next horizon
Assess what the program achieved against its original service commitments and the changes authorized along the way. Separate delivery outputs, improved access or experience, organizational capability and longer-term health outcomes. The organization may reasonably influence some outcomes more directly than others.
Review the full financial position, including recurring commitments, asset maintenance, workforce development and expiring agreements. A successful expansion can still create a future funding problem if temporary grants supported permanent responsibilities. Renewal planning should start before the final year where agreements require it.
Use evaluation to decide what to sustain, strengthen, redesign or discontinue through appropriate processes. Preserve useful institutional knowledge and explain material changes to participating Nations and communities. Evaluation should inform the next set of choices rather than serve only as a retrospective report.
The next roadmap should reflect the organization that now exists, the evidence it has generated and the priorities the Nations identify. Avoid simply extending every project into another five-year plan without testing whether it still matters.
Build the financial and dependency model across all five years
For each initiative, show establishment costs, recurring operating costs, capital needs, maintenance and the timing of funding. Identify which resources are confirmed, conditional or still to be negotiated. Keep potential benefits separate from committed revenue and avoid financing essential operations from unverified savings.
Include a constrained scenario with slower recruitment, delayed capital or a funding shortfall. Identify which commitments can be phased and which require protected continuity. Also consider an opportunity scenario in which funding arrives sooner: the organization still needs the capacity and authority to use it well.
A hypothetical service launched with a two-year grant may require continuing staff and facility costs in years three to five. The roadmap should show the renewal decision, alternative funding route or responsible transition before the grant ends. Hiding that obligation beyond the annual budget would make the service appear more affordable than it is.
Map dependencies among initiatives. A new digital system may require settled workflows and information agreements. A facility may require an operating budget and workforce plan. A broader service mandate may require partner commitments. Sequence the decisions so large irreversible commitments are not made before critical assumptions are addressed.
Choose a planning approach that fits uncertainty
A fixed project schedule can be useful for well-defined work with stable dependencies, but it can create false certainty for a whole-system transformation. A rolling annual plan allows adjustment but may encourage short-term choices unless it remains connected to the longer-term direction. A roadmap with decision gates combines multi-year intent with explicit conditions for major commitments.
For many transformation programs, the third approach offers a useful starting point: maintain the long-term service direction, fund a credible near-term plan and define the evidence required for later decisions. This is a management recommendation to assess locally, not a claim that one planning method universally outperforms the others.
Refresh the roadmap when material evidence changes, such as a revised Nation mandate, confirmed funding, significant service results or a major external dependency. Maintain a clear decision record so adaptation remains accountable. Frequent cosmetic revisions should not replace resolving the decisions that block progress.
The Five-Year Commitment 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.
Authorize
Question: What direction and initial scope do the Nations approve?
Decision evidence: Mandate, service baseline and a credible initial operating position.
Demonstrate
Question: What must work reliably before expansion?
Decision evidence: Service and management evidence, actual costs and resolved critical gaps.
Expand
Question: Which next commitment is supported by capability and resources?
Decision evidence: Option appraisal, sustainable funding and confirmed dependencies.
Integrate
Question: Where does the system still fail across boundaries?
Decision evidence: Community-level variation, handoff performance and targeted redesign choices.
Renew
Question: What should continue into the next horizon?
Decision evidence: Evaluation, future obligations and renewed Nation priorities.
Turn the design into an operating commitment
Prepare a roadmap that shows the initial service promise, the capabilities needed next and the decisions that unlock later commitments. Use the Nation’s priorities and current operating evidence to set the sequence. Identify a responsible owner and funding status for each major initiative.
Pair the roadmap with a funded annual delivery plan and a small set of decision papers for the next governing meetings. Review progress through service evidence, financial commitments and dependency resolution. Change the plan through the appropriate authority when material conditions change.
Arcus can support the five-year roadmap, investment sequencing, organization and service design, and implementation review. A useful roadmap enables leaders to make the next commitment with a clear view of its purpose, cost, prerequisites and implications for the longer-term health system.
Sources and limits of the evidence
- FNHA, release of the 2026/27 Summary Service Plan, April 21, 2026. Public planning account and summary reviewed; the full plan PDF exceeded retrieval limits. No claim that this is a five-year startup plan.
- Audit Scotland, Health and social care integration: Update on progress, November 2018. Historical audit findings on planning and alignment; not a prescribed First Nations implementation schedule.
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 · Building a First Nations health organization · Organization design services · Arcus consultant directory