First Nations Management & Leadership · Arcus perspective
How to Clarify Delegated Authorities in First Nation Government
A dollar limit is only one part of authority
A delegation schedule can appear clear because it assigns spending limits to job titles. Yet staff may still be uncertain about who may select a supplier, approve an exception, sign an agreement, change its scope or authorize payment. These are different decisions, even when they relate to the same expenditure.
The management insight is to define the decision before assigning the limit. A person may have authority to approve a routine purchase within an approved budget while lacking authority to accept unusual contract terms or establish a continuing service commitment. Treating all of these as one signature can hide the real risk.
The Nation’s laws, governing instruments and authorized delegations determine what can be assigned and what remains reserved. This article offers a management design method; it does not create authority or prescribe legal thresholds. Uncertainty about the underlying power must be resolved through the Nation’s appropriate process and advice.
Primary guidance shows why conditions matter
FMB’s Administrative Governance guidance addresses records, qualifications, performance expectations, monitoring and review of delegated responsibilities in the FAL context. It also identifies responsibilities that remain with Council under that framework. This demonstrates that delegation involves conditions and accountability, with applicability to be confirmed for each Nation.1
Tsawwassen First Nation’s publicly posted Procurement Policy, amended in May 2023, distinguishes purchasing processes, exceptions, conflict requirements and approval of changes to standard contract forms. It illustrates several decision dimensions within one process. Its thresholds and institutions belong to that Nation and are not proposed as a template for others.2
The practical inference is to connect the authority schedule with the workflow it governs. A table of positions and amounts is insufficient if staff cannot identify the decision, conditions and evidence required at the point of action.
Map the decision sequence
Choose a recurring activity and separate its decisions. For a purchase, the sequence might include confirming the need and budget, choosing a procurement route, selecting an option, accepting contractual terms, confirming receipt and approving payment. The actual sequence and required separation depend on the Nation’s rules and risk controls.
For each decision, identify its source of authority, the role permitted to exercise it, applicable limits, required advice or approvals and the record to retain. Identify what happens when a condition is not met. Do not leave exceptions to informal interpretation by the most senior person available.
Extend the exercise beyond finance. Delegation may concern service scheduling, public communications, access to information or management of staff. Different categories require different controls. A financial signing schedule should not be treated as a general authorization for unrelated decisions.
Distinguish ambiguity from reluctance and capability gaps
When managers repeatedly seek approval for routine work, the cause may be an unclear delegation. It may also be a history of decisions being reversed, insufficient knowledge to assess the issue or a reasonable concern that an exception applies. These explanations require different responses.
Examine a few escalated cases. Ask what information the manager had, which rule they relied on and what consequence they expected from deciding independently. Compare that account with the written delegation and the supervisor’s expectations.
If the rule is clear but managers lack technical support, provide advice and development. If decisions within authority are routinely reversed without explanation, address the management practice. If the delegation genuinely omits the decision, amend it through the proper route. Raising a spending limit will not resolve every form of hesitation.
Choose how much discretion to delegate
Rule-based delegation works for repeatable decisions with clear criteria and reliable information. It can improve consistency and speed. Its limitation is that unusual cases may not fit the rule, so an exception route remains necessary.
Conditional discretion allows judgment within defined boundaries, such as an approved purpose, budget, risk category or requirement for specialist advice. It suits variable work but requires capable decision-makers and meaningful monitoring. Vague instructions to use good judgment are not enough.
Retained approval is appropriate for reserved matters and decisions whose consequences justify review at another level. Its cost is time and attention. Identify why the approval is needed and what evidence will allow the reviewer to decide, rather than retaining every decision because delegation feels uncomfortable.
Temporary delegation can support a vacancy, leave period or time-limited initiative where permitted. Specify its scope, start, expiry and review arrangements. Temporary convenience should not become an undocumented permanent change in authority.
Design limits around the commitment, not only the transaction
Consider duration, reversibility, cumulative exposure, policy implications and effects on other services. A modest initial payment may create a longer obligation or require future staffing and maintenance. A decision can be financially small but consequential for fairness, privacy or a public commitment.
Use a hypothetical software purchase. The licence cost may fit a manager’s limit, while the terms create multi-year renewal costs, data access obligations or dependence on another department. The manager needs to know which parts can be approved locally and which require additional review.
Define how related commitments are assessed under the Nation’s rules. Do not design the process so that dividing an initiative into smaller transactions changes the required scrutiny without changing the underlying exposure. The appropriate calculation and approval route should be explicit and confirmed locally.
Where a decision spans several roles, specify the final decision owner and the purpose of each supporting approval. Multiple signatures can provide separate checks; they can also conceal that nobody has reviewed the whole commitment.
Provide coverage and conflict routes
A delegation that works only when one individual is present is fragile. Identify authorized alternates and the conditions under which they may act. Staff should be able to confirm that coverage is in force without relying on an informal message or an outdated list.
Create an appropriate route when the usual decision-maker has a conflict or is the subject of the matter. The alternate must have valid authority and sufficient independence for the decision. Convenience is not a substitute for the Nation’s conflict requirements.
Document urgent procedures in advance where possible. Urgency may justify a different route under the applicable rules, but it does not automatically remove limits. Record the rationale and any required subsequent reporting. Do not treat retrospective acknowledgment as proof that an earlier action was authorized.
Budget for confidence and control
Delegation can reduce repeated escalation, but it transfers work as well as discretion. Managers need time, information and competence to assess decisions. Finance, procurement, human resources or other advisers may face additional demand even as the executive receives fewer routine requests.
Estimate the transition effort: reviewing governing instruments, mapping decisions, updating documents, briefing staff and testing unusual cases. Then estimate recurring costs: maintaining the schedule, training new role holders, reviewing samples and responding to exceptions.
Compare the cost of these controls with the consequences they address. Intensive pre-approval may be justified for some decisions; proportionate retrospective review may be sufficient for others where permitted. The aim is credible control at a workable cost, not the largest possible number of approvals.
Measure the actual change. Track avoidable escalations, incomplete requests, decisions returned for correction and exceptions identified in review. A decline in approvals reaching Council is not sufficient if unauthorized commitments or poorly supported decisions rise.
Test before wider adoption
Pilot the revised schedule in one decision category. Use a routine case, an exception, an absence and a conflict scenario. Ask the people who would perform the work to identify the valid decision route and the evidence they would retain. Record where their interpretations differ.
Resolve those differences before implementation. Align the delegation with relevant job descriptions, procedures and system permissions through the appropriate authorized processes. A software permission alone does not establish authority, and a written delegation that cannot be exercised in the workflow will create workarounds.
Review a sample of actual decisions after the pilot. Check whether the intended person acted within scope, obtained required advice and retained an adequate record. Revise the process where it creates avoidable uncertainty. Maintain a controlled current version and a clear route for future amendments.
The Arcus decision-specific delegation 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.
Source
Question: Where does the power to delegate come from?
Decision evidence: Confirm the governing instrument and identify reserved matters before assigning decisions.
Decision
Question: What exact choice may the role make?
Decision evidence: Separate recommendation, approval, commitment, implementation and verification as relevant.
Conditions
Question: What limits and checks accompany the authority?
Decision evidence: Specify purpose, exposure, advice, evidence and exception triggers.
Capability
Question: Can the role exercise the authority reliably?
Decision evidence: Provide knowledge, information, time and valid coverage for absence or conflict.
Assurance
Question: How will the Nation know the delegation works?
Decision evidence: Maintain records, review decisions proportionately and update the approved schedule.
Turn the design into an operating commitment
Begin with a decision category that repeatedly creates delay or conflicting interpretations. A useful deliverable is an approved, testable decision route supported by the people and information needed to use it.
Arcus can help map decisions, compare delegation options and design practical operating and review routines. The Nation and its appropriate advisers confirm the underlying authority and authorize changes.
The result should be understandable at the moment of decision: what the role may do, under which conditions, with what evidence and where to go when the case falls outside those conditions.
Sources and limits of the evidence
- First Nations Financial Management Board — Administrative Governance. Delegation guidance in the FAL context; local applicability and reserved powers require confirmation. No universal legal allocation of authority is asserted.
- Tsawwassen First Nation — Procurement Policy (2022), amended May 15, 2023. Publicly posted policy illustrating different decisions and conditions within procurement. No thresholds are imported and no claim about implementation effectiveness is made.
Research reviewed October 18, 2026. Decision frameworks, options and hypothetical illustrations are Arcus management synthesis. No client outcomes or universal savings or impact benchmarks are claimed.
Governance & Leadership collection · Keep governing decisions clear in Council agendas · Organization design services · Arcus consultant directory