How to Build a Workforce Plan for a Growing First Nation

First Nations Knowledge Centre / Workforce, HR & Leadership Capacity

First Nations management research

How to Build a Workforce Plan for a Growing First Nation

Growth changes the work before it changes the organizational chart. A workforce plan should explain which services will expand, which capabilities will be needed and when the Nation can responsibly commit to them.

Translate community priorities and operational demand into a phased workforce decision. Connect roles, skills, time and costs instead of treating the plan as a list of requested positions.

Define growth in operational terms

A growing population, new infrastructure, expanded services and additional responsibilities can each change workforce demand. They do not necessarily increase every department’s workload at the same rate. Some work grows with the number of transactions, some with complexity and some with the hours during which a service must be available.

Start with the changes the Nation expects to manage. Distinguish approved commitments from proposals and uncertain opportunities. A funded service launch requires a different staffing response from a project still awaiting a feasibility decision. Record when each change could occur and what must happen first.

Do not begin by applying a generic employees-per-member ratio. Such a ratio can conceal differences in mandate, geography, service delivery, infrastructure and the work performed by partner organizations. It may be useful as a question for investigation, but it is a weak substitute for understanding the actual work.

Arcus recommends a workforce plan that connects demand, capability, timing, operating choices and affordability. The plan should show both the preferred path and the conditions under which a different path would be needed. This makes it useful when growth arrives faster, slower or differently than expected.

Published role design connects workforce planning with growth

Pacheedaht First Nation’s published Human Resources Director role explicitly links workforce planning with organizational growth, funding and operational priorities. It also includes organizational analysis, skills development and succession responsibilities.1 This is evidence of how one Nation describes the intended function, not a demonstration of staffing effectiveness or a prescription for every Nation’s structure.

The First Nations Financial Management Board’s Human Resources presentation connects organizational structure with position authorization, job descriptions, hiring, orientation and employee development.2 Its guidance is framed around financial-management-system practices. It does not establish current employment law or determine the precise division of authority within another Nation.

The management implication is that workforce planning needs a route into actual organizational and employment decisions. A forecast has limited value if it does not influence budgets, role design, recruitment timing and development. The method below is Arcus analysis, to be adapted to local governance and operating arrangements.

Build a demand baseline before forecasting positions

For each significant service, identify its outputs, volume, complexity, service standard and coverage requirements. Use information already available from work records, service requests and staff experience. Verify definitions so that departments are comparing similar units rather than combining incompatible counts.

Separate recurring services from temporary development work. A new facility may require design and commissioning support before opening, then a different mix of operations, maintenance and administration afterward. The temporary project team and permanent service team should not be treated as the same staffing requirement.

Identify work that is currently hidden: backlog, deferred maintenance, unrecorded coordination or duties absorbed by managers. A forecast based only on completed activity may understate demand when the team already cannot meet it. Conversely, a backlog should not automatically be converted into a permanent position if a time-limited response can resolve it.

Record the main demand drivers and their evidence. Examples include the number of facilities, service cases, transactions, operating hours or new responsibilities. Include complexity and travel where they materially affect time. Use a reasonable range when the data cannot support a single precise estimate.

Translate work into skills and usable capacity

Identify the capabilities needed to perform the work: technical expertise, administration, supervision, community relationships, information management or other requirements specific to the service. Record which capabilities must be available locally and which could be supported through a shared arrangement.

Estimate available capacity after accounting for leave, learning, coordination and other legitimate duties. Paid hours and task-delivery hours are different quantities. Use local evidence and transparent assumptions rather than a universal productivity factor.

Consider an illustrative service expecting 1,200 transactions a year, averaging 1.5 hours each. That creates 1,800 hours of transaction work. Suppose recurring service coordination and required reporting add 300 hours, producing 2,100 hours of annual demand. If one full-time role has 1,400 hours available for those tasks after other duties, the workload equivalent is 1.5 full-time roles.

This calculation does not automatically justify hiring one and a half people. Coverage, specialist requirements and peak periods may require a different arrangement. The assumptions may also be wrong. If transaction time is two hours rather than 1.5, demand becomes 2,700 hours including the same coordination work, or approximately 1.93 role equivalents at 1,400 available hours.

The sensitivity matters more than false precision. Validate the time estimate, inspect the process and identify whether complexity varies across transactions. Do not reduce essential quality or relationship work merely to make the staffing arithmetic fit an existing budget.

Distinguish shortages from design and timing problems

More volume may require more capacity. If the work is necessary, the process is reasonable and demand is sustained, additional staffing may be justified. Check when the increase begins and whether funding supports its duration.

More complexity may require a different skill mix. Adding general administrative hours may not solve a need for specialist judgment. Consider development, access to expertise or a redesigned division of work.

A new service may create a start-up peak. Training, records preparation and implementation can temporarily increase demand. Model that transition separately from steady operations so permanent staffing is not based on an exceptional period.

Existing processes may create avoidable work. Repeated information entry or unclear handoffs can consume capacity. Improvement can be an alternative, but estimated efficiencies should be treated as uncertain until demonstrated. Do not commit the same hoped-for saving to several new services.

A shortage may be a coverage problem. A service can have adequate annual hours and still be vulnerable when only one person can perform a critical task. Backup and scheduling may matter as much as total staffing.

Compare permanent, developmental and shared responses

Permanent recruitment is appropriate for enduring work that forms a coherent role and can be sustainably financed. It requires realistic lead time for approval, search, selection, onboarding and development. The plan should distinguish the hiring date from the date full capability is expected.

Internal development can build capability and career opportunity, but it needs protected learning time and supervision. Forecast the temporary reduction in available capacity while learning occurs. Avoid counting a developing employee as fully available in both the original role and the intended future role.

Temporary or shared expertise can bridge a transition or meet intermittent specialist demand. Define the local coordination required, information access, response expectations and knowledge transfer. Compare the full service arrangement rather than only the hourly rate.

Work redesign can combine related duties, separate incompatible responsibilities or remove duplication. Changes should be assessed with those doing the work and approved through the appropriate process. A new title without a changed workload is unlikely to resolve a capacity gap.

Phased service expansion may be the most responsible option when the necessary capabilities cannot be ready immediately. Explain what can begin safely and effectively, which prerequisites remain and what evidence would support expansion. This is a strategic choice that should be visible to leadership and affected members.

Show first-year and continuing financial commitments

A workforce budget should include salary, employer costs, equipment, workspace, supervision, training and any transition support. Identify costs already covered elsewhere so the estimate neither omits necessary resources nor counts them twice.

In a hypothetical example, a role has an $80,000 annual salary and employer costs estimated at 20% of salary, producing a $96,000 annual recurring employment estimate. A six-month start would create $48,000 of those costs in the first year under this simplified assumption. Add $8,000 for one-time recruitment and setup, giving a first-year estimate of $56,000.

The second-year employment estimate would still be $96,000 before changes in pay or costs, plus any continuing resources not included in the assumption. A first-year budget of $56,000 therefore does not establish long-term affordability. Use the Nation’s actual cost structure and funding conditions; the percentages and amounts here are illustrative.

Compare a base scenario with plausible faster and slower growth. Identify which costs are committed, which can be phased and which depend on a later decision. Keep uncertain grants visible as assumptions rather than confirmed recurring revenue.

Original Arcus decision framework

Six decisions in a growth workforce plan

01 · DEMAND

Define the work that changes

Connect growth with service volume, complexity, coverage and timing.

02 · CAPABILITY

Specify the skills required

Identify expertise, supervision and local relationships needed for delivery.

03 · CAPACITY

Test the available time

Account for current work, learning, leave, peaks and critical backup.

04 · OPTIONS

Choose the operating response

Compare recruitment, development, redesign, shared support and sequencing.

05 · AFFORDABILITY

Fund the full commitment

Separate transition costs, partial-year costs and continuing resources.

06 · TRIGGERS

Authorize the next step on evidence

Set review points and conditions for accelerating, delaying or changing the plan.

Can the Nation explain why each proposed role is needed, when it must be ready and what resources will sustain it?

Make the plan a recurring management decision

Start with the services most affected by growth or continuity risk. Prepare a common demand-and-capacity record with department managers, HR and finance. Reconcile shared support requirements so several departments do not assume access to the same unavailable specialist.

Bring leadership a phased set of decisions, including the evidence, alternatives, costs and consequences of delay. Distinguish approved positions from contingent proposals. Set triggers such as a confirmed service mandate, a sustained workload threshold or a verified opening date, using measures suited to the work.

Review assumptions against actual demand and workforce availability. If volume rises but work time falls after a demonstrated process improvement, revise the forecast. If complexity increases or recruitment takes longer, change the sequence or support model. Record the reason so the plan remains accountable as well as adaptable.

The result is a workforce plan that develops with the Nation’s priorities and operating reality. It provides a reasoned path from growth to capability, rather than a fixed list of positions detached from the services they are meant to support.

Plan the workforce behind growth

Connect future services with practical staffing choices

Arcus supports First Nations with demand analysis, workforce scenarios, role and organization design, capability development and phased resource plans.

Discuss your workforce plan

Explore human resources services

Evidence and source notes

  1. Pacheedaht First Nation, Human Resources Director role, strategic workforce planning and capacity-building responsibilities. Used as published role design, not an assessment of outcomes or confirmation that recruitment remains open.
  2. First Nations Financial Management Board, Human Resources presentation, organizational structure, hiring and development sections. Historical guidance in an FMS context; not used as current legal advice or a universal allocation of authority.

Research reviewed October 18, 2026. Workload, salary and employer-cost figures are hypothetical. The six decisions are original Arcus management analysis. Actual service standards, employment arrangements and approval processes must reflect the Nation’s circumstances.