Completion of the plan changes the work

During comprehensive community planning, much of the effort is directed toward listening, understanding relationships, articulating values and developing a shared direction. After endorsement, the work expands into project development, resource allocation, operating decisions and sustained accountability.

The planning team may have built strong relationships and a detailed understanding of community input. Those capabilities remain valuable. They do not automatically provide authority over departmental budgets, the ability to resolve competing commitments or the technical capacity to deliver every initiative.

Arcus recommends a deliberate implementation agreement. Identify the community plan’s continuing stewardship, the leadership decisions required, the administration’s coordination responsibilities and the resources available for the first delivery period. Establish how these roles work together rather than assuming the planning coordinator will absorb every unfinished task.

The agreement should make the transition visible: which parts of the plan are long-term direction, which proposals require further investigation, which initiatives are approved to proceed and which responsibilities continue as ordinary services. This protects the plan from being treated either as a ceremonial document or as an immediate promise to deliver everything.

Find the actual cause of the implementation gap

The transition may never have been assigned. The plan is endorsed, but nobody has a defined responsibility to convert proposals into decision-ready initiatives. Establish coordination ownership and the authority to obtain information and bring conflicts forward.

The plan may contain proposals at different stages. One action may be ready for a modest operational change, while another needs a feasibility assessment or a broader community decision. A single “not started” status conceals these differences. Identify the next justified step for each significant proposal.

The operating model may not support the direction. A priority can fall between departments or require a capability the administration does not have. Assigning it to the nearest existing team without resources can create a nominal owner and no real delivery capacity.

Several plans may compete for the same resources. A CCP, housing plan, capital plan and departmental strategy can contain overlapping work. Separate project lists may produce duplication or incompatible schedules. Identify the common initiative and reconcile the commitments.

The community feedback loop may have weakened. Members may see little connection between their input and later administrative choices. Regular reporting should explain what has advanced, what has changed, what is waiting and why. More internal project meetings will not resolve a missing public account.

Create a register that distinguishes readiness from importance

For each significant CCP action, record the intended outcome, its relationship to other goals, the next decision, the accountable role, readiness gaps and an initial resource assessment. Preserve links to the relevant community input and the plan’s original language.

Use meaningful stages. An action may be under investigation, ready for a decision, approved but awaiting resources, in delivery, completed, or subject to a deliberate pause. Define the evidence needed to move between stages. Avoid treating an unfunded aspiration as an active project simply because it appears in a work-plan spreadsheet.

Importance and readiness are separate judgments. A high-priority need may require preparatory work before a major investment. A simple ready-to-start project may be worthwhile but less consequential. Make both visible so early successes do not unintentionally displace difficult long-term priorities.

Group related actions where they contribute to one result, but retain the dependencies. A community gathering-space priority might require a service-needs assessment, an operating decision, a facilities option and a resource plan. These should be coordinated without pretending that one approval resolves every later choice.

The register should support a manageable first delivery period. Keep the full set of needs visible while limiting active commitments to what the Nation has authorized and can support.

Fund the connecting work as well as the projects

Implementation requires work that may not belong neatly to one project: maintaining the register, coordinating dependencies, preparing leadership decisions, communicating with members and reviewing results. If that work is invisible in the budget, it may be repeatedly displaced by immediate service demands.

Consider a hypothetical first-year portfolio of six initiatives. Each initiative requires four staff-hours a month for a substantive update and coordination, creating 24 hours of departmental effort. Portfolio reconciliation, decision preparation and community reporting require another 16 hours. The combined workload is 40 staff-hours a month, or 480 hours over twelve months under these assumptions.

That estimate covers coordination and reporting, not the work of delivering the six initiatives. Assigning one coordinator does not eliminate the departmental contribution. Equally, asking six departments to report independently does not remove the need to reconcile the whole portfolio.

Use local evidence to estimate the actual workload. Include participation supports, technical analysis, information management and the transition from temporary project funding to ongoing operations. A smaller initial portfolio may be appropriate if the connecting work would otherwise consume capacity needed for essential services.

Assess the value of the coordination process as it develops. If updates are lengthy but decisions remain unresolved, simplify the reporting and strengthen the decision route. If dependencies keep surprising the team, improve the shared view before adding more initiatives.

Use the first delivery period to establish the system

Begin by mapping existing work against the CCP. Some actions may already be underway through other plans or ordinary services. Recognize that work and clarify its contribution instead of creating duplicate initiatives. Identify gaps that require a new decision or capability.

Choose an initial combination of commitments that balances visible progress, urgent needs and preparation for larger priorities. Explain the selection and the capacity assumptions. Keep a record of deferred actions with a review trigger rather than allowing them to disappear from view.

Schedule a recurring management review of dependencies and exceptions, with a clear route to leadership decisions. Establish a community reporting rhythm that fits local participation and communication practices. Use consistent information, adapted appropriately for each audience.

At the end of the first period, assess more than activity completion. Ask whether responsibilities were workable, resource estimates were credible, decisions arrived when needed and members could see the relationship between the plan and delivery. Correct the implementation system before expanding the portfolio.

The CCP continues to provide a broad community direction. Implementation makes successive commitments within that direction, learns from their effects and brings consequential choices back through the Nation’s processes.

Evidence and source notes

1. Indigenous Services Canada, Comprehensive Community Planning overview, implementation and monitoring phases. Used as process guidance, not a prescribed organizational model.
2. Squamish Nation, Land Development Strategies Update, Stá7mes implementation discussion. Used for the stated integration of related plans; mixed-date content is not treated as proof of present completion or approval status.

Research reviewed October 18, 2026. The six-initiative workload example is hypothetical. The six agreements are original Arcus management analysis, to be adapted to the Nation’s own governance and community processes.