Where Council Stops and Administration Starts: Drawing the Decision Line
The single most common source of friction inside a First Nation government is not money. It is the question of who decides what. A Chief who signs purchase orders for a $40-million water plant is doing the Band Manager's job. A Director of Operations who decides which elders' homes to renovate first is doing Council's job. Both situations create rework, resentment, and audit findings.
The fix is not personality. It is structure. Communities that move capital projects on time almost always have a written decision matrix that names who recommends, who approves, who is informed, and who executes — for every category of decision, at every dollar threshold.
Recent context
Ottawa's March 2026 governance announcement put real money behind the principle that governance and capacity are foundational to service delivery — $283.3 million over two years for First Nations governance and capacity building. That money is most useful where roles are already clear. Where they are not, the dollars expose the gaps.
The governance and project-management angle
A workable boundary is simple: Council sets direction, priorities, policy, and risk tolerance. Administration designs, recommends, executes, and reports. Capital projects test that boundary because every major project requires both political mandate and operational execution within the same year. A delegation of authority bylaw, a project charter that explicitly names the steering committee, and a quarterly Council report that focuses on decisions rather than activities — these three artifacts will resolve eighty percent of role conflict.
How XNM helps
XNM Consulting drafts delegation-of-authority frameworks, capital decision matrices, and project charters tailored to each Nation's election cycle, by-laws, and risk appetite. We sit with Chief and Council and the senior administrative team together so the boundary is built once, in the open, and survives staff turnover and elections.
Practical takeaways
Write it down. An unwritten boundary is a future dispute. A short delegation-of-authority bylaw is worth a hundred meetings.
Anchor decisions to dollar thresholds. Below $X, the Band Manager decides. Above $Y, Council approves. The numbers can change; the principle should not.
Use a RACI on every capital project. Name the Responsible, Accountable, Consulted, and Informed parties before the first shovel.
Report decisions, not activities. Council reports should make it easy to see what was decided and what remains pending.
Refresh after every election. New Councillors need the matrix briefing on day one, not month six.
FAQ
Does a delegation of authority bylaw weaken Council?
No. It protects Council's time for the decisions only Council can make and shields elected leaders from operational liability they were never meant to carry.
What if our community prefers consensus over written rules?
Written rules and consensus practice are not in tension. The matrix codifies how consensus is reached and what happens when it is not — which is exactly when communities most need clarity.
The bottom line
Strong Nations do not blur the line between Council and administration. They draw it deliberately, write it down, and revisit it. That single piece of governance discipline is the difference between a capital plan that gets built and one that gets revisited every election.