First Nations Management & Leadership · Arcus perspective
How to Implement an Organizational Review After Council Approves It
Council approval gives an organizational review an important decision point. It does not automatically produce revised authorities, supported managers, functioning processes or a manageable transition. The work after approval is to translate the decision into an operating arrangement that employees can understand and the Nation can sustain.
The first task is to establish exactly what was approved. A report may contain recommendations, options, illustrations and matters requiring further advice. Chiefs, Councillors and senior administrators need a clear account of which elements are authorized and what conditions remain. This article offers implementation guidance that must be adapted to the Nation’s own decision processes and circumstances. Examples are hypothetical and no particular governing or employment arrangement is assumed.
What implementation evidence adds to the approval decision
The First Nations Health Authority’s evaluation of 2019/20–2023/24, published in June 2025, describes communities leaving shared health-service organizations to exercise greater control over delivery. It found that this transition required financial and administrative information, planning and new agreements, followed by support to administer contracts and operate services. The report also identified a burden on supporting teams where no dedicated disengagement budget existed.[5] The relevant lesson is that approving the destination does not fund the work needed to reach and sustain it.
This is evidence from a specific British Columbia health-governance setting, not an estimate of the cost or duration of every organizational review. The evaluation combined several evidence sources but acknowledged respondent bias and disruption from concurrent public health emergencies. Its findings support testing transition capacity, rather than prescribing a particular structure.
A different setting exposes a related coordination problem. The UK National Audit Office’s March 2026 shared-services update found progress in plans and procurement, but continuing risks from unclear central ownership of departmental onboarding, weak technical leadership and fragmented management of dependencies.[6] A First Nation should not copy that government’s scale or structure. The comparison shows why a completed workstream can still fail to produce an integrated service when nobody can resolve decisions across workstreams.
Diagnose the delay before adding implementation resources
Use recent stalled decisions or service transactions to distinguish three explanations. Several may coexist; a broad label such as “resistance to change” is not sufficient evidence.
- Unresolved design: two managers give different answers about who approves a transaction. Examine the approved mandate, delegations and an actual disputed case. If competent people cannot agree what the future process requires, return the design question to its authorized owner. More training will otherwise teach competing interpretations.
- Insufficient transition capacity: the process is understood, but named staff cannot complete migration, training or supervision alongside essential work. Compare the work needed with protected hours, vacancies and service obligations. Reduce simultaneous changes, arrange backfill or purchase a defined contribution. Another steering meeting does not create delivery time.
- Unproven operating readiness: authority and staff time exist, but a sample request fails at a system permission, record handoff or partner dependency. Test the end-to-end process with a permitted test case. Fix the failure and repeat that specific test before transferring the service.
Ask staff affected by the change to challenge this diagnosis. A concern about service quality or information authority may be substantive evidence, not a communication problem. Record what would disprove the preferred explanation and who will examine it.
Convert the approval into a decision record
Read the governing decision alongside the final report and identify the approved scope. Distinguish recommendations accepted for implementation from matters accepted in principle, deferred or returned for further work. Record conditions, resource decisions and any approvals still required. Where the decision is unclear, obtain clarification through the appropriate process rather than rely on informal interpretations.
A hypothetical report might recommend a revised departmental structure, propose options for a shared support function and identify workforce questions for further assessment. Approval of the structure should not be treated as authorization for every associated option. An implementation record should make those differences visible so employees do not receive conflicting explanations.
FMB’s Administrative Governance guidance discusses responsibilities, delegation, policies and monitoring within its financial-administration framework.[2] These questions are useful when translating a review into action, while local applicability must be confirmed. The implementation team should know which decisions it may make and which matters must return to the appropriate authority.
Establish ownership of implementation
Name an accountable implementation lead and define the relationship with the executive, managers and governing body. The lead needs authority to coordinate the approved work, obtain information and seek decisions. Responsibility without access to those contributions can turn the role into a reporting function that cannot resolve practical obstacles.
Clarify the contribution of each workstream owner. Human resources, finance, information, service operations and communications may each carry important tasks, but their work is interdependent. Identify where one team’s decision or deliverable is required before another can proceed. A shared schedule is useful only if those dependencies are understood.
Avoid expecting an already overloaded executive or manager to absorb implementation without changing priorities. Identify the time and support required, including temporary assistance where justified. If resources are unavailable, leadership needs a decision about sequence or scope. A plan that depends on sustained unrecognized extra work is not yet a credible implementation arrangement.
Sequence decisions before activities
Build the plan around the decisions that make implementation possible. These may include mandates, delegations, role descriptions, staffing processes, systems access and service standards. Some activities can proceed together; others depend on an approved design or advice. Identify those relationships before announcing dates that the organization may be unable to meet.
The CCP Handbook links implementation with priorities, resources, approvals, work plans and monitoring.[1] Those connections provide a useful discipline: each significant action should have an owner, the necessary authority and a clear contribution to the approved direction. A long list of tasks is less useful if leadership cannot see what decisions are holding them back.
For a hypothetical department transfer, the reporting line might be ready before financial authorities, records access and employee support. Moving the box on the chart first could create avoidable confusion. Define the minimum conditions for a safe transfer and distinguish the target date from confirmation that the organization is ready.
Address people and roles through the appropriate process
Translate the design into coherent roles, then determine the applicable process for introducing changes. Organizational recommendations and individual employment decisions are connected but distinct. Obtain appropriate advice on material role, selection, compensation or employment implications. Do not use the review report as a substitute for the required decisions or procedures.
FMB’s Human Resources guidance connects job descriptions with qualifications and development.[3] Apply that relationship to new and revised roles. Employees need to understand their responsibilities, the authority supporting them and the skills or support they will need. A new reporting relationship is incomplete if the person supervising the work lacks time or capability to do so effectively.
Communicate what is approved, what is being worked through and how affected employees will receive information. Avoid guarantees about individual outcomes that leadership cannot support. Provide an appropriate route for questions and distinguish public organizational information from confidential matters requiring a separate discussion or formal process.
Protect services during transition
Identify essential services and the risks created by the change. Decide who remains responsible while roles transfer, how urgent issues will be handled and what temporary arrangements are authorized. Employees should not need to guess whether current or future procedures apply to a live service request.
For a hypothetical shared intake function, implementation may require testing referral routes, confirming records responsibilities and training employees before the new service begins. A clear fallback arrangement can help address issues discovered during launch. It should have a named owner and review point so that temporary exceptions do not become an unmanaged second operating model.
Information transfer deserves deliberate control. FNIGC’s account of OCAP® emphasizes First Nations ownership, control, access and possession, with Nation-specific application.[4] Confirm who may access records, which responsibilities move and how the Nation’s information arrangements apply. A structural change does not automatically authorize broader access to every record held by the former team.
Approval-to-Operation Framework
This original framework connects an approved review with five implementation conditions. It is not a validated readiness score. Use it to identify the evidence leadership needs before a material change begins and to make unresolved decisions visible without implying that every issue must be solved before any progress is possible.
Authorization: the decision is understood
Record what was approved, what conditions apply and what remains open. Identify who may make implementation decisions and how changes to scope will be authorized. The team should be able to distinguish carrying out the decision from making a new decision on behalf of leadership.
Design: the operating arrangement is specified
Connect roles, reporting relationships, delegated authority and service processes. Identify the supporting documents and practical instructions people need. A chart or recommendation is an input to this work, rather than proof that the future organization has been fully defined.
Readiness: the necessary conditions exist
Confirm workforce, training, systems, records access and service continuity arrangements. Identify who accepts any remaining risk and what temporary support is required. Readiness should be based on evidence appropriate to the change, not solely on whether the planned launch date has arrived.
Support: employees can use the new arrangement
Provide supervision, clear answers and a route for resolving early problems. Managers need time and authority to help employees apply new responsibilities. Communication should explain the current operating model and avoid presenting unresolved proposals as settled instructions.
Learning: the change is reviewed against its purpose
Assess the management problem that prompted the review. Identify a small number of useful indicators and obtain practical feedback through the Nation’s appropriate processes. A completed task list should be considered alongside whether decisions, services and management responsibilities now work more reliably.
Arcus can help translate approved recommendations into decision records, workstreams, readiness conditions and implementation reporting while the Nation retains ownership of its decisions.
Maintain a decision and issue record
Keep one current record of significant decisions, dependencies and unresolved issues. Explain the owner, required next step and consequence of delay. The record should help the implementation lead obtain action, rather than become a catalogue of concerns that are repeatedly reported without resolution.
Separate design questions from implementation defects. A missing access permission may be a practical task; repeated conflict over who owns a service may indicate that the approved design needs clarification. Bring material changes back through the appropriate authority. Avoid allowing informal exceptions to quietly rewrite the model without leadership understanding the implications.
Review the work at sensible decision points rather than treating every task as equally important. Confirm what is ready to proceed, what needs further work and which priorities should change. If a dependency cannot be resolved, revise the sequence openly instead of maintaining an unrealistic schedule that encourages employees to work around required controls.
Compare delivery options on the same cost boundary
Internal coordination suits a bounded change when a manager has protected time and access to the required expertise. Its main cost is displaced work; apparent savings disappear if essential services deteriorate. Phased implementation suits changes that can be separated without breaking shared processes. It limits simultaneous workload but extends temporary interfaces and may require duplicate supervision. External coordination can help with a time-limited integration burden or specialist gap. It adds fees and onboarding effort while leaving the Nation responsible for policy, employee and service decisions.
Consider a fictional comparison for the same accepted handover. An internal approach uses 120 existing staff hours valued at C$65 per hour (C$7,800) and C$2,000 of additional training and backfill: C$9,800 of total resource use and C$2,000 of incremental cash. An assisted approach uses 60 existing staff hours (C$3,900), C$5,000 of external support and the same C$2,000 of training and backfill: C$10,900 of resource use and C$7,000 of incremental cash. Existing salaries are assumed already funded; the internal-hour values are not added again to the cash requirement. Taxes, travel and other costs are excluded and would need consistent treatment in an actual comparison.
The assisted option uses C$1,100 more total resources and C$5,000 more cash while releasing 60 internal hours. That release matters only if leadership identifies the essential work those hours will protect. It is not an automatic cash saving. The assumed rates and hours are illustrative, not Arcus fees or sector benchmarks.
Test sensitivity before selecting the cheaper-looking option. If internal coordination requires 40 additional hours, its resource cost rises by C$2,600. If the external scope excludes systems configuration, its quoted fee understates the accepted handover. In either case, estimate the continuing supervision, licenses, reporting and service workload separately. Temporary project funding does not establish recurring affordability.
Use an acceptance decision to complete each material handover
Extend the Approval-to-Operation Framework with one short acceptance record. This is Arcus analytical synthesis, not new empirical research. For each material service or authority transfer, record:
- The decision: the exact responsibility moving, the authorized decision-maker and the effective date.
- The evidence: approved role and authority documents, a completed service test, trained cover, permitted records access and the recurring resource provision.
- The remaining conditions: unresolved dependencies, the person able to resolve each one and the consequences if it remains open.
- The choice: proceed, proceed within explicitly limited scope, or defer the affected transfer. A limitation must have an owner, expiry and workable service arrangement.
- The review: a date and service indicators that would prompt correction, escalation or reversal through the appropriate authority.
For a fictional intake transfer, a successfully routed request is useful evidence, but it is insufficient if its receiving manager cannot authorize the next step. Accept the whole service path or limit the initial scope to requests for which the required authority exists. Do not count a signed handover document as evidence that this missing condition has been resolved.
The implementation lead assembles evidence; workstream owners verify their contributions; the authorized executive or governing body accepts the transfer within its mandate. Review unresolved exceptions, rerouted requests and service turnaround against a recorded baseline. Investigate whether an apparent improvement simply shifted work to another team. Close transition support only when the new owner can operate and maintain the arrangement.
Know when implementation needs additional support
An administration may have the capability to deliver the change internally, especially where the scope is focused and responsibilities are clear. External support may be useful where several workstreams interact, the transition places significant demands on current leaders or independent facilitation would help resolve design questions. Define the contribution and retain clear Nation ownership of decisions.
The practical measure of implementation is whether the approved organization can operate: people understand their work, authorities support decisions, services remain dependable and leadership can see progress and risks. Treat the review as the foundation for that work, and give the transition the management attention required to turn its recommendations into a functioning arrangement.
Arcus Advisory
Discuss organizational review implementation support.
Arcus can help translate approved recommendations into decision records, workstreams, readiness conditions and implementation reporting while the Nation retains ownership of its decisions. 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®.
- First Nations Health Authority. Evaluation of the First Nations Health Authority, 2019/20 to 2023/24: Final Report, June 2025. Printed pages 7 and 34–35: evidence limitations, service transitions and continuing support. A specific BC health-system evaluation, not a general organizational-transition benchmark.
- UK National Audit Office. Update on government shared services, 6 March 2026. Conclusions on ownership, technical integration and dependencies. Comparative public-administration evidence; institutional conditions differ from those of First Nations.
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.