First Nations Management & Leadership · Arcus perspective
First Nation Organizational Charts: What a Good Structure Actually Looks Like
An organizational chart can look orderly while leaving the most important questions unanswered. Employees may know whose name sits above theirs yet remain uncertain about who sets priorities, approves an exception or resolves a disagreement between departments. A useful chart should represent a working organizational design, supported by clear mandates and decision arrangements.
For First Nations leaders, the chart also needs to respect the Nation’s own governance, institutions and responsibilities. There is no universally correct shape. This article explains how Chiefs, Councillors and senior administrators can develop and assess a chart without confusing visual simplicity with an effective organization. Illustrations are hypothetical, and the original framework is intended for management discussion rather than formal certification.
What evidence supports a useful organizational chart?
FMB’s Human Resources guidance describes a current chart showing governance, management and administrative positions, with controlled updates and access for those to whom it applies. It also addresses approved job descriptions.[3] This is guidance within the FMB financial-administration framework, not empirical proof of an optimal chart shape or a universal legal requirement.
A separate implementation lesson comes from the UK National Audit Office’s March 2024 review of the FCO–DFID merger. It found substantial progress in integrating structures and policies, alongside unresolved systems and HR issues. Benefits were not systematically measured and cost tracking was incomplete, preventing a value-for-money conclusion; the report also identified examples of improved integrated responses.[5] This large foreign-government case cannot predict results for a First Nation. It illustrates why a completed structure and evidence of improved organizational performance are different claims.
Arcus’s inference is to approve a chart together with a record of the work, authority and capacity behind its positions. The chart can then communicate a tested design rather than stand in for the design decisions.
Define what the chart is intended to show
Decide the chart’s purpose before drawing it. A public overview may explain the main institutions and service departments, while an internal management chart may identify positions and reporting relationships. A transition chart may show approved future responsibilities. These are different documents and should be labelled so readers understand their scope.
Avoid combining every relationship in one diagram. Governance, employment supervision, service coordination, advisory support and institutional ownership may require different explanations. Using the same line for all of them can imply authority that does not exist or obscure authority that needs to be clear.
For a hypothetical administration working with a separate service entity, a diagram might show the relationship without placing that entity inside the administration’s reporting hierarchy. Confirm the actual arrangement and explain it in accompanying text. The chart should describe the Nation’s institutions accurately rather than make them fit a familiar corporate template.
Start with responsibilities and services
Identify the responsibilities the organization must carry and the services it is intended to support. Group work based on meaningful dependencies, management needs and the Nation’s priorities. Drawing boxes first can encourage leadership to allocate work around existing titles or preferred candidates instead of examining the operating model.
The CCP Handbook connects community-driven priorities with implementation, resources and monitoring.[1] An organizational chart should support those connections. Ask how each proposed department contributes to the direction the Nation has established and what work it must coordinate with others. Not every priority requires a separate department, but each material responsibility needs a clear organizational home.
Distinguish current commitments from future possibilities. A long-term development idea may deserve attention without appearing as an established operational unit. If the chart includes planned functions, label their status and identify the decisions or resources required. Readers should not need to guess whether a box represents an active service, an approved vacancy or an option under consideration.
Give each position a coherent mandate
A position should bring together work that can be managed responsibly. Review the decisions, relationships and capability involved, not just the list of tasks. A role assembled from unrelated gaps may become difficult to recruit, supervise or evaluate even when every individual task is legitimate.
FMB’s Human Resources guidance connects organizational roles with job descriptions, qualifications and development.[3] The chart and job descriptions should tell the same story. If a proposed reporting line places a manager over a service they lack the authority or support to oversee, the design needs further work.
Consider a hypothetical shared operations role covering facilities, procurement and project coordination. These functions may have useful connections, but the mandate must explain priorities and access to specialist expertise. A broad title should not conceal incompatible demands or responsibilities that require qualifications the organization has not provided for.
Diagnose the reason reporting lines are not working
Unclear authority: employees know their supervisor but cannot identify who can approve a recurring decision. Trace actual requests and compare the chart with delegations. Clarifying authority may be more useful than changing the supervisor.
Insufficient management capacity: responsibilities are understood, but reviews, coaching or decisions wait because the manager has too much concurrent work. Review the work and available time, including vacancies, locations and technical demands. A clearer diagram alone will not create capacity.
Cross-service conflict: different managers set incompatible priorities for shared work. Examine which decisions conflict and whether the escalation route functions. A defined service owner or coordination arrangement may resolve this; a formal reporting change is another option when it addresses the demonstrated cause.
Distinguish these explanations from a temporary vacancy, an outdated chart or a change in service demand. Several causes may coexist. Avoid treating a structural review as evidence about an individual’s performance.
Make reporting relationships meaningful
Each reporting line should represent a defined management responsibility. Explain who sets work priorities, provides supervision, reviews performance and addresses unresolved issues. A line that exists only because every position needs to connect somewhere can create an appearance of accountability without a workable management relationship.
Examine the demands on each manager. The number of direct reports matters alongside service complexity, employee capability, locations and the management support available. Avoid applying a universal ratio. The question is whether the role can provide the contribution the organization needs under realistic operating conditions.
Where employees receive technical advice or project direction from someone outside their reporting line, explain how that relationship works. Conflicting priorities need a resolution route. A dotted line can be useful if its meaning is defined; it becomes confusing when different readers interpret it as supervision, advice, partnership or an optional communication channel.
Connect the chart with delegated authority
Reporting lines do not, by themselves, establish every decision a position may make. Review the relevant mandates, policies and delegations alongside the chart. Identify matters requiring governing decisions and those assigned to administration. Confirm the applicable arrangements rather than assuming that a familiar title carries a standard set of powers.
FMB’s Administrative Governance guidance discusses policies, delegation and monitoring within its financial-administration framework.[2] Use those questions to test whether accountability and authority align, while checking local applicability. If a manager is accountable for a service result but cannot secure essential decisions, show how that dependency will be managed.
For a hypothetical capital project, the chart might identify a project manager, a departmental sponsor and an executive reporting relationship. An accompanying decision schedule should explain who recommends, authorizes and monitors material commitments. Adding more boxes or lines cannot substitute for clarity about those distinct responsibilities.
Show the support functions the organization relies on
Front-line departments depend on finance, human resources, information, facilities and other support. A chart should make important responsibilities visible without implying that every capability must be provided through a separate internal position. Shared arrangements and external specialist support may need accompanying descriptions rather than conventional reporting lines.
Identify who owns the relationship with each support provider and how priorities or service concerns are addressed. Otherwise, employees may be expected to obtain help from a function that has no clear obligation or capacity to respond. The chart should prompt those operational questions rather than conceal them behind a generic administration box.
Information stewardship deserves explicit attention. FNIGC’s account of OCAP® emphasizes First Nations control over information and Nation-specific application.[4] An organizational chart may identify responsible roles, but it does not determine access permissions or information-sharing arrangements. Those require appropriate policies, decisions and practical controls alongside the design.
Organizational Chart Integrity Framework
This original framework tests whether the diagram represents an organization that can operate. It does not rank Nations or establish a preferred structure. Use it with job descriptions, mandates and decision arrangements to identify gaps before leadership approves a proposed model.
Completeness of responsibility
Can every material service, management function and institutional responsibility be located in the design? Identify work that is shared, obtained externally or planned for later. A missing box is not always a problem, but unexplained ownership of essential work requires attention.
Coherence of roles
Does each position hold a manageable combination of responsibilities supported by appropriate capability? Compare the chart with job descriptions and actual work. Identify roles that are overloaded, fragmented or dependent on assumptions about an individual rather than a sustainable position design.
Clarity of relationships
Can readers distinguish supervision, governing oversight, technical advice and service coordination? Define the meaning of different lines and explain important relationships in plain language. If a diagram requires extensive interpretation, consider separating it into a clear overview and supporting detail.
Alignment of authority
Do responsibilities connect with the decisions and resources needed to perform them? Identify relevant delegations, limits and escalation routes. A chart should expose authority gaps so they can be resolved through the appropriate process, rather than imply that drawing a line has resolved them.
Credibility of implementation
Can the organization resource and introduce the proposed arrangement? Identify vacancies, training, transition work and necessary approvals. Distinguish an approved target from the structure currently operating so employees and community members receive a reliable account of how the organization works today.
Arcus can help test the chart against actual services, decisions and management work, identify gaps and develop an operating model supported by clear roles and implementation steps.
Use a position record to test each material box
Extend the Organizational Chart Integrity Framework with a short Position and Authority Record. For each material position, identify its purpose, recurring decisions, supervisor, relevant delegated authority, required capability, budgeted capacity, service dependencies and current status. Distinguish an occupied position, an approved vacancy and a proposed future role. Keep personal employment information in the appropriate restricted system.
Then compare three realistic choices. Retain reporting lines and clarify decisions when the structure is workable but mandates or escalation are unclear. Add a coordinating or specialist arrangement when departments need shared expertise or an accepted service owner. Change reporting lines or add management capacity when ongoing supervisory or decision demands justify the transition and recurring cost. Record what each option solves and the dependencies it leaves unresolved.
A worked capacity check
Suppose a fictional manager has 12 hours a week available for supervision and cross-service decisions after their other responsibilities. Planned supervisory work requires eight hours and coordination requires six: 14 hours in total. The two-hour gap is a prompt to examine the assumptions, not a universal staffing ratio. Adding a dotted-line responsibility that consumes another three hours increases the gap to five hours unless other work changes.
Leadership could simplify or delegate appropriate work, provide defined support or redesign the role. The choice depends on authority, service complexity and the availability of qualified people. Count the work transferred to another role as well as the time released from this one. Otherwise a seemingly efficient chart can hide an unfunded workload elsewhere.
Separate transition costs from the annual commitment
For a second fictional illustration, a role-and-delegation clarification uses 80 setup hours and four maintenance hours a month. At an assumed resource rate of $75 an hour, these represent $6,000 initially and $3,600 annually. Adding a half-time management position with an assumed fully loaded full-time cost of $120,000 creates a $60,000 annual employment-cost assumption, before recruitment, transition or other costs. The two options do not buy equivalent capability.
These figures are invented arithmetic examples, not Arcus market prices or recommended salaries. Existing staff time may consume capacity without the same amount of new cash spending. Test affordability against the actual continuing workload, funding and employment arrangements. A cheaper clarification is inadequate if the problem is a material shortage of qualified management capacity; an additional manager is difficult to justify if an unresolved delegation is the real constraint.
Before implementation, identify the approving authority, update the related mandates and job descriptions through appropriate processes, brief affected roles and establish a baseline for decision delays, unresolved escalations and supervisory work. Review the change after an agreed operating period. A shorter approval path is useful only if decision quality, controls and service responsibilities remain sound.
Test the chart with real management situations
Before approval, trace a few representative scenarios through the proposed model. Ask how an urgent service issue reaches the right decision-maker, how competing departmental priorities are resolved and how a manager obtains specialist support. Include a routine process as well as an exceptional issue so the design is tested beyond crisis response.
Discuss the findings with employees and relevant leaders through the Nation’s chosen process. Practical questions can reveal gaps that a visual review misses. Record the design decision and any unresolved conditions. Avoid treating a chart review as an assessment of individual employees or using it to pre-empt an applicable employment process.
Once the arrangement begins, maintain a current version and identify who owns updates. Changes in positions, services or delegations should prompt consideration of whether the chart and supporting documents remain accurate. A good organizational chart is a clear reference for a working management system, and its value depends on the decisions and practices that support it.
Arcus Advisory
Discuss an organizational structure and role review.
Arcus can help diagnose authority gaps, overloaded management roles and conflicting service responsibilities; compare clarification, coordination and structural options; and prepare an implementation decision. Deliverables can include current and proposed charts, Position and Authority Records, decision-rights schedules, capacity and recurring-cost comparisons, and a transition roadmap.
Implementation support can connect approved changes with role documentation and management reporting. Measures can include decision delays, unresolved escalations and whether the expected supervisory work is being completed. The review should preserve the Nation’s institutional choices and appropriate employment processes.
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®.
- UK National Audit Office. Progress with the merger of the FCO and DFID. March 25, 2024. Implementation review of a large UK departmental merger, not a First Nations organizational-chart study or causal estimate of structural benefits.
The management analysis, hypothetical illustrations and original framework are 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.