First Nations Management & Leadership · Arcus perspective
Centralize or Decentralize? Designing Shared Services Across First Nation Departments
Centralizing a support function can promise consistency and access to specialist capability. Keeping it close to departments can promise responsiveness and a better understanding of the work. Both claims require examination. The useful question is which responsibilities should be common, which decisions should remain local and how the two will operate together.
For a First Nation administration, this decision should reflect the Nation’s priorities, institutions, service needs and resources. A single centralized model is not appropriate for every function, and decentralization does not mean that every department needs its own specialist. This article offers a practical way to compare arrangements within an administration. Examples are hypothetical; the framework is an original management aid rather than a validated assessment or a claim about guaranteed savings.
What does evidence say about shared-service design?
The UK National Audit Office’s March 2026 review found progress in implementation planning and procurement, alongside unresolved ownership of departmental onboarding, inconsistent system configurations and fragmented management of dependencies.[5] These were implementation findings in a large central government, not evidence that a First Nation should adopt that government’s scale, technology or organizational model. They support testing whether anyone can resolve cross-department decisions before assuming that a common platform will produce a common service.
FMB’s administrative-governance guidance, within its financial-administration framework, connects delegation with documented authority, qualifications, work standards, monitoring and review.[2] Arcus’s synthesis is to treat a shared service as an explicit arrangement for work, authority and accountability. Physical location alone cannot establish those conditions. A local function with clear standards can be more reliable than an under-resourced central team; a properly supported common team can offer expertise that separate departments cannot sustain.
Define the service before choosing its location
Describe what the support function actually provides. Human resources, finance, procurement and information services each contain different activities and decisions. Some involve common standards, some require specialist judgment and others depend on day-to-day knowledge of departmental work. Treating the whole function as one indivisible choice can hide useful combinations.
For a hypothetical procurement service, common policies and supplier records might sit with a central function while departments identify requirements and manage delivery within delegated authority. Another administration may need a different arrangement. The design should explain who performs each activity and who owns the result, rather than use centralization as a shorthand for every decision moving upward.
FMB’s Administrative Governance guidance addresses policies, delegation and monitoring within its financial-administration framework.[2] These questions can help distinguish the activities that need common oversight from those that can be assigned closer to services. Confirm local applicability and relevant commitments before changing authority or controls.
Identify the problem the change is intended to resolve
Centralization may be proposed because specialist capacity is fragmented, records are inconsistent or employees cannot obtain dependable support. Decentralization may be proposed because a common function has become distant from service needs or decisions wait unnecessarily. Document the actual problem and its consequences before selecting a model.
Examine whether the difficulty lies in organizational location or in an unclear service relationship. A central team with no agreed priorities may struggle to respond to departments. Moving staff into departments without addressing demand, capability or standards can reproduce the same problem in several places. Conversely, a department may be carrying work that would benefit from sustained specialist support.
Choose a few representative requests and trace how they are handled. Identify waiting, repeated work, unresolved exceptions and the information needed for decisions. Include the perspective of both the support function and service departments. The purpose is to understand the operating constraint rather than collect competing accounts of who is being unhelpful.
Distinguish three causes before selecting a structure
Capacity shortage: Complete requests wait even when authority and requirements are clear. Compare incoming work, available specialist hours, absence coverage and the age of the queue. Moving the same overloaded staff into one team may simply concentrate the backlog.
Rework at the handoff: Requests repeatedly return for missing specifications or inconsistent records. Trace first submissions and returned work. A common intake standard, departmental preparation support or a bounded process trial may address the problem before any reporting-line change.
Priority or authority conflict: Technically complete requests stop because nobody can resolve competing commitments or approve an exception. Check decision records and escalation times. Clarifying decision rights may matter more than adding processing capacity. These causes can coexist; choose an intervention against the demonstrated constraint and review whether it moved.
Compare capability and resilience
A common function may make it easier to maintain specialist expertise and coverage, but only if it has sufficient capacity and a coherent mandate. A small centralized team can become a single point of delay. Departmental resources may provide strong local knowledge while depending heavily on one employee with limited backup.
FMB’s Human Resources guidance connects roles with qualifications, job descriptions and training.[3] Use that relationship to identify the capability each option requires. Consider supervision, development, coverage and succession alongside the number of positions. A proposed model should explain how employees will obtain technical support and how essential work continues during absence or turnover.
In a hypothetical financial support arrangement, assigning one generalist to each department might improve familiarity with local work while reducing access to specialist supervision. A shared team might provide that supervision but require a dependable way to understand departmental priorities. Compare the full operating arrangement rather than assume that either location produces capability automatically.
Preserve a clear decision relationship
Distinguish advice, service delivery, approval and assurance. A support employee may help prepare a decision without owning it. A departmental manager may remain accountable for operational requirements while a common function maintains standards. Unclear boundaries can cause either repeated approval or work proceeding without the intended review.
Describe how disagreements will be resolved. If a department views an issue as urgent and the shared function has other commitments, identify who can establish priorities and what information they need. A service standard is useful only if the organization can resource it and address exceptions through a defined process.
Avoid creating dual supervision without explaining it. An employee embedded in a department may receive operational priorities locally and technical guidance centrally. Define how those contributions interact and who makes employment, workload and performance decisions. A dotted line on a chart should correspond to a practical arrangement people can describe consistently.
Evaluate access and information requirements
Departments need a usable route to support, whether staff are located centrally or locally. Consider service hours, geography, language, technology and the urgency of decisions. A common system may be accessible for routine requests while exceptional matters still require direct discussion with someone who understands the service context.
Information arrangements must be designed deliberately. FNIGC describes OCAP® as principles supporting First Nations ownership, control, access and possession, with Nation-specific application.[4] A shared support function should follow the Nation’s decisions about access, use and stewardship. Centralizing a function does not automatically justify combining every record or giving every team access to sensitive information.
For a hypothetical human resources service, managers may need advice and selected workforce information without access to all employee records. Define the appropriate permissions, records responsibilities and escalation route with the relevant authorities and specialists. The organizational model and the information model should support each other rather than rely on informal workarounds.
Assess resources without assuming savings
Compare the ongoing requirements of each option and the work needed to transition. Include systems, training, coordination, management attention and temporary duplication where relevant. A proposal should distinguish an expected benefit from a verified saving and avoid promising a financial result that has not been supported by analysis.
Consider what happens to departmental capacity when activities move. Removing local support before a common service is ready can leave a gap. Retaining all previous arrangements indefinitely may prevent the organization from realizing the intended benefits. The transition plan should identify when responsibilities transfer and how readiness will be confirmed.
The CCP Handbook connects priorities with resources, implementation and monitoring.[1] Use those connections to assess whether a shared service is an appropriate investment now. A technically attractive design may need to wait for systems or workforce development; a focused improvement to the current arrangement may be the most practical immediate step.
A worked capacity comparison
Consider a fictional service using 180 staff-hours each month across departments. A proposed common team needs 120 hours, while departments retain 45 hours of preparation and follow-up and coordination adds 15 hours. Total recurring effort remains 180 hours. The proposal may improve quality or coverage, but it releases no hours on these assumptions. If transition requires another 60 hours, identify who supplies that capacity while ordinary service continues.
Replace these illustrative inputs with measured demand and local estimates. Price common-team work, retained departmental effort, technology, travel, supervision and transition separately. Released time becomes a cash saving only when a feasible budget change follows; otherwise name the service improvement that will use it. Compare a strengthened local model, a common team and an embedded specialist arrangement on the same cost boundary.
Shared Service Allocation Framework
This original framework examines five choices within a function. It is intended to support a reasoned decision, rather than produce a universal centralization score. Different activities may belong in different places, provided the resulting arrangement remains clear and manageable.
Standard: what must be consistent?
Identify the policies, controls, information definitions and service commitments that require a common approach. Confirm their authority and purpose. Consistency should address a meaningful requirement rather than eliminate local judgment where different service circumstances legitimately need different responses.
Expertise: where should capability be maintained?
Assess specialist depth, supervision, coverage and development. Identify the scale of demand and the consequences of unavailable advice. Explain how employees will remain connected to the work of departments even where technical capability is organized through a common team.
Decision: who should authorize action?
Allocate decisions according to mandate, relevant information and accountability. Distinguish operational choices from common standards and reserved approvals. Define how exceptions reach the appropriate authority without requiring every routine request to pass through the most senior administrator.
Relationship: how will support reach services?
Specify access, priorities, expected contributions and escalation. Identify what departments must provide for the shared function to respond effectively. A service relationship is reciprocal: neither a central team nor a department can deliver reliably if essential information and decisions remain unavailable.
Transition: what must be ready before transfer?
Identify workforce, systems, records, communications and approvals. Name the person who confirms readiness and the fallback arrangement for unresolved issues. Review the model after launch against the original service problem, rather than treat a transfer of positions as evidence of success.
Arcus can help compare common and departmental arrangements, clarify service and decision responsibilities, and assess the resources and transition requirements of the options.
Choose a model the organization can operate
Document the selected arrangement in plain language, with supporting roles, service processes and decision responsibilities. Explain why particular activities are common or departmental and what would justify reconsidering that choice. Avoid leaving employees to infer the model from where desks or budget lines are located.
An organizational review is useful when several functions face overlapping problems or when authority and capacity are unclear across the administration. A focused service design may be sufficient for a defined function. In either case, the strongest decision connects the location of work with the conditions needed to perform it reliably for the Nation.
Turn the framework into a service transfer record
For each activity being moved, record the service and its users; the common standard and authorized local exceptions; the processing owner and approval owner; expected demand and funded capacity; retained departmental work; and the evidence required before transfer. For a hypothetical procurement service, departments could retain requirements and delivery acceptance while a common team maintains supplier records and processes purchases within approved delegations. An exception still needs a named decision-maker.
The administration’s implementation lead should assemble the record with service departments, the common-function lead and finance. The appropriate authority approves any delegation changes. Test representative routine and urgent requests, verify records access and backup coverage, then transfer a bounded activity with a fallback. Review end-to-end completion time, first-submission quality, unresolved exceptions, staff effort and service-user experience. Pause expansion if the original constraint persists or an essential service deteriorates. A transfer date alone is not an acceptance test.
An Arcus engagement can turn this analysis into a demand and handoff diagnostic, a costed comparison of operating arrangements, a service and decision-rights agreement, and a staged transfer plan with review measures.
Arcus Advisory
Discuss the design of your shared support functions.
Arcus can help compare common and departmental arrangements, clarify service and decision responsibilities, and assess the resources and transition requirements of the options. An initial inquiry can describe your challenge and organizational context, and help determine whether an Arcus engagement may be relevant.
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. Update on government shared services. March 6, 2026. Comparative implementation audit; its institutional scale and technology choices are not a First Nations benchmark.
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 20, 2026. The additional cause diagnostic, illustrative capacity arithmetic and service transfer record are Arcus analytical synthesis, not original empirical research.