First Nations Management & Leadership · Arcus perspective
How to Redesign Departments Around Community Services Instead of Funding Programs
A community member may experience one issue while the administration sees several programs, budgets and reporting requirements. A housing concern might involve maintenance, health, financial support and capital planning. Organizing each funded activity separately can make accountability visible within programs while leaving the overall service difficult to navigate.
The design challenge is to connect services without losing the controls, expertise and responsibilities that make them workable. Chiefs, Councillors and senior administrators should not assume that funding arrangements can be ignored or that every service belongs in a single department. This article considers how to use community service needs as a design lens while respecting the Nation’s mandates, institutions and circumstances. Examples are hypothetical and no universal departmental model is proposed.
What does the evidence support about service integration?
ISC’s New Fiscal Relationship Grant evaluation found that some participating First Nations used funding flexibility to adapt or expand services, while limited funding and staff capacity constrained its use. The evaluation engaged 44 Grant First Nations and seven non-Grant Nations or organizations; it identifies self-selection and limited member perspectives as important limitations.[5] The evidence concerns a funding arrangement, not a test of departmental mergers. It supports examining usable flexibility and capacity together.
A contrasting historical case comes from England’s National Audit Office. Its 2017 review found improved joint working under the Better Care Fund alongside unmet financial and service targets, and insufficient evidence for assumed sustainable savings from integration.[6] Different institutions and services limit direct transfer. The relevant caution is that collaboration, service experience and cash savings are distinct results.
Arcus’s management inference is to redesign the service relationship and preserve a clear account of funding responsibility. Choose a reporting-line change only when it resolves a demonstrated authority or coordination problem that a lighter arrangement cannot adequately address.
Start with the service experience
Choose a limited number of important service journeys and examine how people move through them. Identify the questions they bring, the places they contact and the decisions required. Include the experience of employees who help people navigate boundaries, because informal coordination can reveal work that the organizational chart does not show.
Distinguish inconvenience from a material service gap. Repeating basic information, receiving conflicting advice or not knowing who owns the next step may have different consequences depending on the service. Leadership needs to understand those consequences before selecting the scale of organizational change. A focused referral improvement may be sufficient in one case; another may require a different allocation of responsibilities.
For a hypothetical home-repair request, the service journey might begin with an inquiry and continue through assessment, prioritization, authorization, scheduling and confirmation of completion. Map who owns each stage and how information moves. Do not assume that the person who first receives the request is accountable for every decision needed to resolve it.
Keep funding accountability visible
Service design should examine the conditions attached to each responsibility and resource. Identify the relevant agreements, reporting obligations, approval requirements and restrictions before proposing to combine functions or budgets. Obtain appropriate advice where interpretation is required. A management design exercise cannot itself change the conditions under which funds or responsibilities have been accepted.
Separate the service model from the accounting view. Some activities may be coordinated through a common service process while retaining distinct financial records and reporting. Other combinations may be impractical or inappropriate. The organization should assess these choices explicitly rather than assume that an integrated service requires every administrative system to be merged.
FMB’s Administrative Governance guidance describes policies, delegation and monitoring within its financial-administration framework.[2] These questions help identify the accountability that a proposed model must preserve. Confirm local applicability and define who remains responsible for commitments, controls and reporting after the service arrangement changes.
Distinguish three causes of fragmented service
An access or handoff problem: responsibilities are workable, but members cannot find the right service or referrals lose ownership. Trace cases from first contact to completion. A shared access route and referral standard may address this without merging departments.
An authority conflict: several managers make incompatible decisions about the same service journey, and existing escalation cannot resolve them. Examine repeated exceptions, conflicting priorities and the decisions that remain open. A service owner needs authority to resolve specified conflicts or obtain a timely decision; another coordination meeting may not be sufficient.
A resource or mandate constraint: the service is clear but necessary capacity, funding permission or specialist authority is absent. Confirm the constraint rather than treating it as departmental resistance. Consolidation does not make an ineligible cost eligible or supply a missing professional capability.
Test these explanations with staff and service users through appropriate processes. They can coexist, and improved access may expose previously unmet demand. A higher caseload after integration is not automatically inefficiency; examine whether people are now reaching support they previously could not access.
Identify the work that benefits from being together
Group activities because of meaningful dependencies, not simply because their titles sound related. Examine shared community needs, staff capabilities, information requirements, resources and recurring decisions. Ask whether a common manager would have a coherent mandate and the authority to resolve the issues that bring the activities together.
Some services may need close operational integration while others require specialist independence or a separate institutional relationship. A shared access point does not necessarily imply a shared department. Likewise, a common department does not automatically create a coordinated service if teams continue to use incompatible processes and priorities.
In a hypothetical arrangement, community intake might help people reach several distinct service teams. A clear referral standard and named case owner could improve continuity while preserving specialist responsibility. Compare that model with departmental consolidation before deciding that a reporting-line change is necessary. The design should explain what becomes easier and what new coordination work it creates.
Assign ownership across service boundaries
An integrated service needs someone to own the whole process, including the points where responsibility moves. That person does not necessarily supervise every employee involved. Define the authority to establish standards, address unresolved handoffs and bring cross-departmental issues to the appropriate decision-maker.
Without this ownership, integration can depend on employees repeatedly negotiating exceptions. Those efforts may help individual cases while leaving the underlying system unchanged. Record common problems and identify who can authorize a durable response. A service owner should have a route to decisions rather than merely a responsibility to chase colleagues.
The CCP Handbook connects community-driven priorities with implementation and monitoring.[1] Use that connection to define what the service model is meant to achieve. Departments should support the Nation’s priorities, while the service process gives leadership a way to see whether the chosen arrangement works in practice.
Design the workforce around the proposed service
Identify the work employees would perform under each option and the skills required. A broader service mandate can require different knowledge, supervision and support. Do not assume that combining teams means every employee should become interchangeable or take on responsibilities outside their competence.
FMB’s Human Resources guidance connects job descriptions with qualifications and training.[3] Apply that relationship to the proposed roles. Identify where development, specialist advice, recruitment or revised supervision would be needed. Include this investment when comparing models rather than treating training as an implementation detail to be resolved after approval.
Discuss the design with employees in a way that seeks practical evidence and distinguishes proposals from decisions. Explain which questions are open and how input will be used. If a selected model affects individual employment arrangements, obtain appropriate advice and follow the applicable process. A structural recommendation should not be presented as a predetermined outcome for particular people.
Establish information arrangements before joining processes
A connected service may need information to move across functions, but convenience is not sufficient justification for unrestricted access. Identify what information each role needs, who authorizes its use and what the Nation’s policies and other applicable requirements permit. Confirm these arrangements before building a shared intake or record system.
FNIGC describes OCAP® as principles supporting First Nations ownership, control, access and possession of information, with Nation-specific application.[4] The practical design question is how the Nation wishes to govern information across the proposed service. A common department or software platform does not settle that question automatically.
For a hypothetical referral, a receiving team may need enough information to contact the person and understand the service request, while detailed records remain with the originating service. Determine the appropriate arrangement with the relevant authorities and specialists. Service integration should make responsibilities clearer, including the responsibility to protect information.
Service-to-Structure Design Framework
This original framework connects the community-facing service with the organizational decisions behind it. It is a discussion tool rather than a validated assessment. Use it to compare options and identify conditions that must be addressed before a new departmental arrangement begins.
Journey: the service people need to navigate
Describe the issue, access points, decisions and expected handoffs. Identify where the current arrangement creates avoidable uncertainty or repetition. Keep the account grounded in actual service experience while protecting personal information and distinguishing recurring patterns from isolated incidents.
Mandate: the responsibilities that must be preserved
Map institutional, program and funding responsibilities alongside the journey. Identify approvals, controls and specialist functions that the new arrangement must respect. Record questions requiring advice rather than treating organizational convenience as authority to change a commitment.
Ownership: the person accountable for coordination
Define who maintains the service process, resolves handoff problems and seeks decisions about shared priorities. Explain the relationship with departmental managers and governing authorities. Ownership should include an actionable mandate, not simply an expectation that someone will persuade others to cooperate.
Capability: the people and systems required
Identify workforce, supervision, information and support needs. Compare them with current capacity and include transition resources. A model that depends on capabilities not yet available should explain how and when those capabilities will be developed or obtained.
Learning: how the arrangement will be reviewed
Choose evidence that reflects the service problem, such as unresolved referrals, repeated requests for information or unclear decisions. Interpret results with employees and service users through the Nation’s appropriate processes. Use the findings to improve the arrangement rather than claim that a new chart proves successful integration.
Arcus can help map service journeys, compare departmental and coordination options, and identify the authorities, capabilities and transition decisions needed for a workable model.
Compare models using a service-and-funding accountability record
Extend the Service-to-Structure Design Framework with one record for each proposed shared activity. State the community-facing purpose; the service owner and decision authority; the program or funding responsibilities that remain distinct; the staff and information required; the method for attributing costs; and the evidence needed to confirm permissions and results. This is an original Arcus management aid, not a substitute for interpreting the Nation’s agreements.
Shared access with separate departments can suit a navigation problem. A common intake or referral role helps people reach the correct specialist, while program decisions and financial controls remain separate. Include the continuing cost of navigation and handover follow-up. Reject an arrangement that merely transfers the burden of finding a service to a new employee without giving that role a workable escalation route.
A service owner across departments can suit recurring dependencies that require common standards and conflict resolution. Specify which decisions the owner can make and which remain with departmental or governing authorities. Resource that work rather than adding a full coordination mandate to an already occupied role.
Departmental consolidation may be proportionate where activities share a coherent mandate, capabilities and recurring management decisions. It can reduce some interfaces while creating a larger supervisory span and new internal boundaries. Preserve specialist controls and required institutional separation. A single manager’s title does not establish common information permissions or interchangeable staff skills.
Make the transition and recurring costs explicit
Consider a fictional comparison for one service journey. A referral redesign requires 80 setup hours and 16 hours of coordination per month. A consolidation requires 240 setup hours and 24 hours of coordination per month while separate program reporting remains necessary. At an assumed blended resource rate of $75 per hour, the first option represents $6,000 of setup effort and $14,400 annually; the second represents $18,000 of setup effort and $21,600 annually.
These invented figures describe only the specified work. They exclude employment changes, systems migration, specialist advice, training, disruption and other costs that a real proposal must identify. They are not market rates or predictions that consolidation is always more expensive. Staff time consumes capacity but does not necessarily create an equal new cash expenditure.
The comparison asks what additional benefit justifies the larger commitment. If a referral repair can address the observed problem, there may be no case for the more extensive change. If unresolved authority prevents essential decisions, the lighter option may be inadequate despite its lower resource requirement. Compare both against access, completed handoffs, decision delay and service quality, not only internal administration cost.
Finance should confirm a defensible allocation of shared costs before implementation. A service record can connect the work for members, while the financial record preserves the appropriate attribution and reporting. Never assume that an equal split across programs is permissible or accurate merely because staff work in one department.
Use an explicit implementation gate
Leadership should authorize the selected model after the accountable roles, funding conditions, information arrangements, transition resources and service safeguards are resolved. Start with a bounded journey where feasible, maintain a route for unresolved cases, and review both service experience and program accountability. Scale only when the evidence supports the change; preserve or revise parts that do not work.
Implement through a manageable service boundary
Where appropriate, begin with a defined service journey or a limited coordination change. Establish the current operating arrangement, the transition responsibilities and the point at which the new process begins. Preserve essential services and provide a clear route for problems that the proposed model has not anticipated.
Review the experience before extending the model. A successful access improvement may be worth adopting elsewhere without requiring a wholesale departmental merger. Conversely, a trial may reveal that authority or management responsibilities need a broader redesign. The purpose is to learn which organizational change supports the Nation’s services, not to force every program into a single preferred structure.
Arcus Advisory
Discuss a service-led organizational design review.
Arcus can help diagnose access failures, authority conflicts and resource constraints; compare shared access, cross-department service ownership and consolidation; and prepare a decision on the operating model. Deliverables can include service-journey maps, a service-and-funding accountability record, decision-rights options, a workforce and transition-cost assessment, and an implementation roadmap.
Implementation support can help establish handover responsibilities and review access, unresolved referrals and continuing funding accountability. The scope should distinguish service benefits from expected cash savings and identify questions requiring the Nation’s financial, legal or professional advisers.
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 Services Canada. Evaluation of the New Fiscal Relationship Grant. Web page modified August 20, 2026; data collected August 2024–March 2025. Findings 5 and 8 and methodological limits; not a departmental-merger evaluation.
- UK National Audit Office. Health and social care integration. February 8, 2017. Historical English health-system evidence; no direct First Nations impact or savings estimate.
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.