First Nations Management & Leadership · Arcus perspective
How to Build an Organizational Structure for a Growing First Nation
Growth changes what an administration must be able to do. A Nation may add services, assume new responsibilities or expand its institutions while retaining a structure shaped by earlier requirements. The decision is not simply where to place another position. Leadership needs to understand how the whole organization will carry the work, make decisions and remain accountable as responsibilities change.
A useful structure connects the Nation’s priorities with clear mandates, capable managers, reliable support and manageable coordination. It should also be affordable and suited to the Nation’s governance and jurisdiction. This article offers a practical design sequence for Chiefs, Councillors, Band Managers and executive directors. Examples are hypothetical; no employee count, departmental model or management title fits every Nation.
Establish the responsibilities the organization must carry
Begin with the work the Nation has chosen or is required to perform, within its own laws, agreements and institutional arrangements. Identify current services, approved commitments and credible future responsibilities. Separate confirmed obligations from possible opportunities. A design built around every potential initiative can become expensive before those responsibilities exist.
Describe each responsibility in operational terms. A housing mandate, for example, may involve planning, applications, maintenance coordination, capital delivery, records and financial oversight. These activities may require different capabilities and partners. Naming a housing department does not establish who performs each activity or how decisions connect across the administration.
Review the existing community and strategic plans. The CCP Handbook links planning areas with community priorities and implementation responsibilities.[1] Treat that connection as a design discipline: the structure should support choices the Nation has made, while making resource and capacity implications visible. It should not quietly establish new priorities through the placement of positions.
Understand the current operating model
Separate a growth problem from a process problem
Test three explanations before moving reporting lines. If comparable requests repeatedly stop at the same unclear approval, clarify the authority and required information first. If work has clear authority but qualified staff cannot complete it within the available time, test additional or shared capacity. If competent, adequately resourced teams repeatedly make incompatible commitments across services, examine how responsibilities are grouped and coordinated. Several causes may coexist; a single delay does not establish a structural defect.
Use a short sample of real work to record arrival, active work, waiting, rework and escalation. Ask what observation would weaken the preferred explanation. For example, if clarifying approval requirements removes the delay without increasing staffing, a new management layer has a weaker case. If a temporary resource clears a recurring backlog but coordination remains sound, the evidence points more directly toward capacity. These are practical tests, not a validated diagnostic or a reason to defer urgent support.
Map how services, decisions and administrative support actually work. Identify governing bodies, executive responsibilities, departments, service entities and shared arrangements. Respect the distinct mandates of boards or other institutions. Their appearance on one diagram does not mean that the administration has authority over every activity they undertake.
Ask managers and staff to walk through ordinary work. Where do requests begin? Which decisions move upward? Where are specialist skills or financial approvals needed? Include the informal coordination that makes the current organization function. Removing a reporting relationship can also remove a useful communication route unless the replacement is deliberately designed.
Use the map to identify strengths as well as gaps. A redesign should preserve relationships and local knowledge that support reliable service. If a problem arises from one unclear procedure, it may not justify changing the whole structure. Distinguish work that needs a new home from work that needs better information, resources or management attention.
Choose how work should be grouped
Departments can be organized around services, professional functions, locations, programs or combinations of these. Each approach creates coordination demands. Grouping similar specialists can strengthen technical support; grouping a service journey can improve ownership of the outcome. Neither arrangement eliminates the need to work across boundaries.
Consider a hypothetical capital project that draws on infrastructure, finance and procurement. Placing all project staff in one department might simplify supervision while leaving financial authority appropriately elsewhere. The design must explain how the departments coordinate, who owns the overall schedule and how unresolved decisions reach the right authority.
Compare grouping options against the Nation’s approved criteria. Consider community access, professional requirements, management workload, cost and information governance. Funding accountability must remain clear even where the service model crosses program boundaries. Avoid treating an external funding category as the only possible organizational boundary, or assuming that combining departments removes funding conditions.
Define the work of management
A manager’s role should be more specific than supervising a list of positions. It may include setting priorities, supporting employees, managing budgets, resolving exceptions, coordinating partners and reporting on results. The mix matters when deciding how many responsibilities one role can carry and what support it needs.
Consider complexity alongside the number of employees reporting to a manager. A team working across several locations, technical disciplines or changing service arrangements may require substantial management attention. There is no reliable universal ratio that can replace examination of actual responsibilities. A small team can be difficult to supervise; a larger stable team may have strong routines and experienced leads.
Test the proposed role against a realistic month. Include seasonal peaks, travel, meetings, leave coverage and implementation commitments. If the arrangement depends on the manager personally handling every exception, revisit the role, delegation or support. Adding a management layer is justified only when it performs necessary work and has appropriate authority.
Align authority with accountability
For recurring decisions, identify who recommends, who decides, who implements and who oversees. These roles may be shared across different bodies, but the arrangement must be understandable. Two people described as accountable for the same decision can leave employees uncertain about whose instruction applies.
FMB’s Administrative Governance guidance addresses delegation and documentation within its financial-administration framework.[2] Use the principle of explicit authority while confirming what the Nation’s own laws and policies require. A redesigned chart cannot itself authorize a transfer of responsibilities reserved to a governing body or another institution.
Document escalation for exceptions. For example, a department manager may approve routine work within an established mandate while an unusual commitment requires executive or governing-body consideration. Explain the information needed, the decision route and the response expected. Otherwise, employees may either escalate everything or accept risks that leadership intended to retain.
Build the support functions into the design
Cost the administration required by the new mandate
The federal March 2017 governance evaluation covered 2009–10 to 2015–16, using document and administrative-data review, interviews and case studies across six regions. It identified the need for realistic local costing of governance and administration, employee-retention support and institutional capacity.[5] This is historical program evidence, not a statement of current funding entitlements or an optimal organization chart. Its relevance to a growth decision is the need to price the work around a service, rather than assume the service budget covers the administration it creates.
For each approved responsibility, distinguish direct delivery, management, shared support and transition work. Identify a recurring funding source and its conditions for each. Treat an unresolved contribution as a dependency, not available revenue. Verify current agreements and restrictions with the Nation’s finance leadership before committing to a structure.
Service growth creates work beyond the visible front line. Finance, HR, technology, purchasing, communications and records support may all face additional demands. Evaluate these functions as part of the operating model rather than waiting for a shortage to become a service problem.
A hypothetical new facility illustrates the issue. Its program staff may be funded, but recruitment, payroll, maintenance records and procurement still require capacity. Leadership should see the ongoing support requirement before approving the operating arrangement. Where resources are uncertain, identify the limitation and the decision needed rather than assuming that existing teams can absorb the work.
Shared support can be useful where the scope, service expectations and escalation process are clear. It can also create a bottleneck if demand is centralized without adequate capacity or prioritization. Ask how departments will obtain support, how urgent requests will be assessed and who resolves competing priorities. A shared function needs a service model, not just a central reporting line.
Responsibility to Structure Framework
This original framework tests whether a proposed structure can support the work. It is a management discussion aid, not a scoring system. Apply it to a department, a senior role or a shared arrangement before considering the design complete.
Purpose and mandate
State the priority the unit supports and the services or decisions it owns. Identify the boundaries with governing bodies, other departments and external partners. If the mandate cannot be explained plainly, the reporting arrangement is unlikely to resolve the ambiguity.
Work and capability
Describe the recurring activities, specialist requirements, management work and support dependencies. Compare these demands with available capacity. Identify where training, recruitment or process improvement is required rather than assigning work to an unprepared role.
Authority and coordination
Connect responsibilities with decision rights and required collaboration. Define ordinary decisions, exceptions and oversight. Explain how work will move across boundaries, including the information people may appropriately access and the route for resolving disagreements.
Affordability and transition
Assess ongoing and implementation costs, available resources and the sequence required to begin operating. Identify what must be ready before responsibility transfers. A design is incomplete where its feasibility depends on an unspecified future resource decision.
Use the framework to compare a concrete growth commitment
Consider a fictional new service estimated to add 24 hours of direct delivery, eight of management and ten of shared administrative work each week. Assume existing staff can reliably absorb six of the total 42 hours without displacing approved work. The remaining requirement is 36 hours, but those hours require different capabilities; one full-time appointment is not automatically the answer. These figures are transparent planning assumptions, not a staffing benchmark or an Arcus client result.
Retain the structure and add capacity when the mandate and authority are clear and the workload can be allocated to suitable roles. Price delivery and support separately, including leave coverage. Use a shared or contracted specialist arrangement when demand is intermittent and specialist recruitment would be difficult; include coordination, service availability, information permissions and continuity in the comparison. Create a new department or management role when a durable, coherent mandate requires dedicated accountability and the recurring workload and funding justify it. Include the additional coordination that a new boundary creates.
A fourth option is to stage the new responsibility. If confirmed resources can carry only part of the commitment, leadership can narrow or sequence the service where its obligations permit, while pursuing the missing capacity. This requires an explicit service decision; it should not happen silently through an impossible job description.
The annual comparison should include salary and benefits, specialist contracts, systems and accommodation, supervision, training and replacement coverage. Show recruitment, transition, record migration and temporary backfill separately from recurring costs. Existing staff time has an opportunity cost even where it adds no immediate cash payment. Do not count the same manager’s available hours in both service delivery and transition capacity.
Record the preferred option against all four framework elements, the assumption most likely to change the choice, and the evidence required before authorization. If the service mandate is temporary, a permanent structure may be premature. If a long-term responsibility has outgrown informal coordination, repeatedly extending temporary arrangements may conceal the recurring capacity decision.
Test the design with people who will use it
Walk through realistic service and management scenarios with affected leaders and staff. Ask how an ordinary request, an urgent exception and an absence would be handled. The purpose is to expose gaps while they can still be corrected, rather than seek reassurance that the chart looks reasonable.
FMB’s Human Resources guidance highlights current charts, job descriptions and training plans.[3] These should reflect the approved operating arrangement. They are most useful when employees can connect them with actual work. Where changes may have employment implications, obtain appropriate advice and follow applicable processes before announcing individual outcomes.
Information governance also deserves an explicit test. FNIGC describes the First Nations principles of OCAP® in relation to First Nations control over information and Nation-specific application.[4] Reorganizing a service should not create unrestricted access by default. Determine the records required, approved access and responsibilities for protecting information as part of the design.
Implement a workable model and review its results
Choose a realistic starting arrangement and identify the conditions for later development. A Nation may need to strengthen departmental management before expanding executive responsibilities, or establish a shared process before centralizing a support function. Record these dependencies so that a future structure is not mistaken for an immediate instruction.
Assign implementation ownership, resources and review points. Explain the change to employees and members in terms they can use: who is responsible, how requests move and where concerns should go. Preserve service continuity while authorities, records and working relationships are transferred. The transition should not depend solely on the goodwill of already busy staff.
Evaluate the design against the original problem and the Nation’s priorities. Look for reliable decisions, clear follow-up, manageable workloads and progress on approved commitments. If those results do not improve, examine the explanation rather than defending the diagram. An organizational structure is a practical arrangement to support the Nation’s work, and leadership should be able to adjust it as responsibilities and evidence change.
Arcus Advisory
Discuss the decision facing your Nation.
An Arcus organizational-design engagement can be scoped around a responsibility and workload map, a diagnosis of process versus capacity versus structural constraints, realistic operating-model alternatives, and a costed transition plan. Leadership can use these deliverables to decide what to authorize, which dependencies must be resolved and how to measure service reliability after the change. Scope, evidence access and responsibilities should be agreed with the Nation before work begins.
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®.
- Indigenous and Northern Affairs Canada. Impact Evaluation of Governance and Institutions of Government, March 2017. Historical evaluation of 2009–10 to 2015–16; the executive-summary findings support the costing question, not current funding amounts or causal estimates of restructuring benefits.
The management analysis, hypothetical illustrations and original framework are Arcus analytical synthesis and 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 2026.