First Nations Management & Leadership · Arcus perspective
How First Nations Can Clarify Roles Between Chief, Council, CEO and Executive Director
Role ambiguity often becomes visible when an important decision stalls. One person believes a recommendation is awaiting approval; another believes the decision has already been delegated; a third is asked to implement work without the information or authority required. The immediate disagreement can appear personal, while the underlying problem is that the organization has never made the relationship explicit.
For a First Nation, clarifying roles requires attention to its own governance arrangements, laws, jurisdiction and institutional mandates. Chief, Council, CEO and executive director are not interchangeable labels, and the authority attached to them cannot be assumed from common usage. This article offers a practical management process for resolving overlap while respecting the Nation’s right to determine its arrangements. Examples are hypothetical.
Map the mandates before comparing job titles
Begin with the governing instruments, policies, resolutions and agreements that establish responsibilities. Identify the bodies and roles involved, including traditional or hereditary leadership, elected leadership, boards and separate service institutions where relevant. A shared organization chart can display a relationship without establishing a power to direct another institution.
Distinguish governing responsibilities from executive and departmental work, then identify where the current allocation is unclear. Some organizations use both CEO and executive director titles for different mandates. Others use one title for the principal administrative role. The review should establish what the positions actually do before drawing conclusions about duplication.
Where authority is legally uncertain, seek appropriate advice through the Nation’s process. Role-clarity work can organize the questions and identify operational consequences; it should not treat a workshop agreement as sufficient to override a law, governing instrument or binding agreement. Record any decision that depends on further interpretation or approval.
What documented governance arrangements tell us
Teslin Tlingit Council’s public governance description distinguishes a legislative General Council, a politically responsible Executive Council and an administrative branch. It also lists an executive director within its executive structure.[5] This documents one Nation’s institutional arrangement, not a tested model for every First Nation. It illustrates why the word “executive” alone cannot establish whether a position carries political direction, administrative responsibility or both.
FMB’s Administrative Governance guidance states that senior-manager tasks may be assigned to more than one person under its described financial-administration framework, with each reporting directly to Council.[2] That is a specific permitted arrangement, not a general recommendation for divided management. It is also a reason to verify applicable instruments before insisting that every Nation must use a single executive reporting model.
The practical decision: which arrangement makes the required work executable, accountable and affordable within this Nation’s mandates? The documents establish institutional possibilities and requirements; they do not provide comparative evidence that one arrangement produces better services.
Use recurring work to identify the overlap
Collect examples of decisions that repeatedly generate uncertainty. These might involve annual priorities, department work plans, hiring approvals, service exceptions, external commitments or reporting to leadership. Focus on the process rather than naming an individual as the cause. Several people can act reasonably within different understandings of an undefined role.
For each example, trace the request, recommendation, approval, action and reporting. Ask where the process paused or returned for clarification. Compare the written arrangement with actual practice. If employees routinely seek informal approval beyond the stated authority, investigate whether the formal delegation is trusted, understood or adequately supported.
A hypothetical partnership proposal illustrates the issue. An executive may explore an opportunity, while a governing body retains authority to commit the Nation. Clarify the point at which exploration becomes a proposal requiring approval, the information leadership needs and who may communicate a commitment. The same title cannot substitute for those specific decisions.
Separate accountability from contribution
Many decisions require several contributors. That does not mean that every contributor should have the same approval role. A finance leader may assess affordability, a service director may explain operational consequences and an executive may recommend an option, while the governing body makes a reserved decision. Each contribution has value without creating several competing final authorities.
Describe responsibilities using clear verbs. Someone gathers evidence, prepares a recommendation, approves a commitment, implements a decision or oversees results. Avoid relying exclusively on broad phrases such as supports leadership or ensures effectiveness. These can be useful statements of purpose but do not resolve who does the work when a deadline approaches.
FMB’s Administrative Governance guidance addresses delegation and documentation within its financial-administration framework.[2] The Nation should confirm the applicable requirements and record the authorities its own arrangements permit. A person should not be held accountable for a result without clarity about the decisions they may make and the matters they must escalate.
Distinguish three causes of apparent role conflict
The mandates contradict one another. Two documents or instructions assign the same final decision to different roles. Trace their source, scope and approval; obtain the appropriate interpretation or amendment. A personal working agreement cannot settle a contradiction it has no authority to change.
The mandate is clear but the handover is incomplete. Both executives understand the allocation, yet work arrives without a recommendation, cost assessment or necessary service information. Examine a sample of delayed decisions. A defined submission and response process may solve more than changing titles.
The assigned workload exceeds available capacity. Responsibilities are understood and submissions are usable, but the responsible role cannot complete them in the required period. Compare recurring obligations, interruptions and available skilled time. A new chart will not create that capacity.
Use disconfirming evidence. If complete submissions move promptly under the current arrangement, the delay may concern preparation rather than authority. If both executives independently describe the same allocation but decisions still queue, investigate workload and dependencies. If each gives a different answer about who can commit resources, resolve that inconsistency before using performance targets to assign blame.
Define the CEO and executive director relationship explicitly
Where both roles exist, identify the distinct organizational problem each is intended to solve. One may carry responsibility for the overall administration while another leads a specific entity or service. Alternatively, the titles may reflect historical arrangements that no longer describe the work. Neither interpretation should be assumed without examining the mandates.
Test the relationship through actual management responsibilities: setting priorities, allocating resources, supervising directors, coordinating services, managing risk and reporting to governing bodies. Identify which responsibilities belong to each role, which require collaboration and where disagreement is resolved. A relationship described only as working closely together leaves too much to individual accommodation.
Consider affordability and management capacity. Two senior positions can be useful where their mandates are distinct and necessary; they can also create additional coordination if the boundary is poorly defined. Evaluate alternatives against the Nation’s work and resources. Do not add hierarchy solely to avoid a difficult conversation about an existing authority gap.
Compare three operating arrangements
One principal administrative executive with delegated service leadership can fit an integrated administration where priorities, staff and resources need a common coordinating point. Test whether that executive has the capacity and information to perform the role. Excessive approvals can simply move the bottleneck upward.
Two executives with distinct mandates in the same administration can fit substantial, separable responsibilities where governing instruments permit it. Specify how shared priorities, budgets and cross-service disputes are resolved. The test is not whether each job description sounds different, but whether a real decision can pass between them without duplicate approval or an unowned gap.
Executives of separate institutions linked by an agreement can fit services governed by distinct boards or entities. Coordination does not itself create a reporting relationship. Establish the parties’ authority and the mechanism for shared work, information and escalation; do not draw a supervisory line that the underlying mandate does not support.
Compare recurring executive and support costs, coordination time, reporting preparation and supervision. Separately identify transition work: mandate review, employment advice where relevant, document alignment, orientation and temporary coverage. Do not count an eliminated role as a full saving if its essential work moves to another executive, an external adviser or an already stretched service director.
Align job descriptions with a role agreement
Job descriptions should reflect the approved allocation, but revising documents independently can preserve contradictions. Develop a shared role agreement first, then align individual descriptions, reporting schedules and procedures with it. FMB’s Human Resources guidance discusses current organizational charts and job descriptions.[3] These tools should reinforce a coherent operating arrangement.
Include the boundaries of the role, not only its responsibilities. Identify what the role may decide, what it recommends, which relationships it must maintain and which matters remain outside its mandate. Describe the support required from other functions. A manager cannot reliably deliver a cross-departmental result if those dependencies are invisible.
Where changes may materially affect employment, obtain appropriate advice and follow applicable processes before making commitments. Explain the distinction between clarifying an existing responsibility and changing a role. Staff should understand how the process affects their work and where they can raise a concern about an impractical or inconsistent allocation.
Design the reporting relationship for decisions
Reports should support the recipient’s responsibilities. Leadership may need assurance about progress, risks and decisions requiring approval, while an executive needs operational information to direct work. Sending everyone the same detailed report does not establish that either purpose is being served.
Agree on routine reporting and urgent escalation separately. Define what triggers immediate attention, what can wait for the normal reporting cycle and who prepares a decision recommendation. Where a request is returned for further work, state what is missing. Otherwise, the organization may repeatedly circulate information without advancing the decision.
The CCP Handbook connects priorities, responsibilities and implementation.[1] Use that connection when designing reports: show how the work advances the Nation’s agreed priorities and identify the support or decision needed. A clear role agreement should make it easier to understand who owns progress and why a matter has reached a particular forum.
Role Clarity Agreement Framework
This original framework organizes a practical agreement between related leadership and management roles. It is a discussion tool, not a legal instrument or validated assessment. The Nation must determine how an agreement should be authorized and incorporated into its governing and administrative arrangements.
Mandate and result
State why the role exists, the responsibilities it carries and the results it is expected to support. Identify the source of authority and relevant institutional boundaries. Avoid defining the role solely by the preferences or strengths of its current occupant.
Decisions and limits
List recurring decisions the role makes, recommendations it prepares and matters it escalates. Confirm required consultation, approvals and limits. Use realistic examples to test whether another person could apply the arrangement consistently.
Relationships and support
Identify the roles that supply information, specialist advice or implementation capacity. Explain how joint work is coordinated and how disagreement is resolved. Collaboration should be supported by a process rather than depend entirely on personal goodwill.
Reporting and review
Agree what information demonstrates progress, when it is reported and what triggers further attention. Set a review point for the agreement. Responsibilities should be revisited when mandates or operating conditions change, rather than allowed to drift informally.
Work the agreement through a shared-service decision
Consider a fictional Nation with an administration CEO and a health-service executive director. A shared intake proposal requires a choice about common records, staff time and service standards. For illustration only, assume the health executive can design health operations, the CEO coordinates administration-wide resources, and the appropriate governing body retains approval of the new cross-service commitment. The Nation must verify its actual allocation; these assumed titles confer no authority elsewhere.
The health executive prepares the service requirement and risks. The administration team assesses shared systems and staffing. The CEO assembles the cross-service recommendation with unresolved choices visible. The authorized body decides the reserved commitment; the named operating leads implement their respective parts. A request to explore the option is recorded separately from approval to begin operating it.
Suppose coordination uses two executives for one hour weekly and three managers for thirty minutes each. That is 3.5 person-hours per week, not a one-hour commitment. If an approved responsibility agreement reduces the executives’ joint meeting to thirty minutes while the managers’ work remains unchanged, the total becomes 2.5 hours. The illustrative one-hour release is capacity, not automatic payroll savings. If the meeting disappears but the coordination moves to email or rework, no equivalent saving has been demonstrated.
Add a disagreement route: identify which body resolves a cross-service priority conflict, what information it receives and what operations continue meanwhile. If the health entity has a separate governing mandate, replace the assumed internal route with the authorized inter-institutional arrangement. The exercise should expose that distinction before implementation.
Protect information in the clarification process
Role mapping may involve sensitive organizational or personal information. Determine what participants need to know and what should be reported in aggregate or through a restricted process. A concern about an individual should not be circulated as an example merely because it illustrates a difficult reporting relationship.
FNIGC’s guidance describes First Nations control over information through the principles of OCAP®, including Nation-specific application.[4] Respect the Nation’s direction on collection, access, use and stewardship. Clear responsibilities for information are part of role clarity, particularly where executives, governing bodies and separate service entities have different mandates.
Where the process identifies a complaint, suspected misconduct or another issue requiring a distinct procedure, refer it appropriately. Do not use a general role workshop to decide an individual matter without the authority or procedural protections it requires. Keeping these processes distinct protects both participation and the credibility of the organizational work.
Test the agreement and maintain it
Before final approval, walk through several ordinary and exceptional decisions with the people involved. Ask each participant to explain the route independently. Differences in the answers reveal what still needs clarification. Revise the agreement before relying on it to hold someone accountable for a new expectation.
Implement the agreement through orientation, updated documents and practical reporting routines. Review exceptions without assuming that every departure reflects deliberate noncompliance. A repeated exception may indicate an unrealistic process, insufficient capacity or an authority question that was never fully resolved.
Role clarity is strongest when people can explain the same arrangement and use it under pressure. The goal is not to eliminate collaboration but to make collaboration dependable. The Nation should be able to trace a priority through an authorized decision, responsible implementation and meaningful oversight, even when the individuals occupying the roles change.
Arcus Advisory
Discuss the decision facing your Nation.
An Arcus engagement can map institutional mandates, diagnose recurring handover failures, compare executive operating arrangements and help leadership select an implementable allocation. Deliverables can include a mandate map, a tested Role Clarity Agreement, a workload and cost comparison, aligned role descriptions, an escalation protocol and an implementation review. The work should identify which decisions require the Nation’s own authorization or appropriate legal and employment advice. Its value is a usable operating arrangement with observable responsibilities, not a promise that changing titles will resolve every disagreement.
Related research and consulting
For governance-versus-administration boundaries, see Chief and Council vs. Administration. For specific decision limits, see How to Clarify Delegated Authorities.
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®.
- Teslin Tlingit Council. Governance. Undated institutional description, reviewed October 20, 2026; General Council and Executive Council mandates and executive structure. Documentary evidence of one arrangement, not an outcome evaluation.
The management analysis, fictional examples 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.