Preserve the evidence before compressing it

Community input may include a desired outcome, a service complaint, a proposed building, a cultural commitment and an urgent maintenance issue. These are different kinds of information. Ranking them as if they were equivalent projects can hide both their meaning and their relationship.

Begin with a traceable register. Record the need in language that preserves its substance, the relevant context, the people or places affected where appropriate, and any proposed response. Group related entries while retaining the original references. Several comments about appointment access may describe one recurring issue; a single comment may identify a serious barrier that deserves attention.

Distinguish the desired outcome from the suggested solution. A request for a new facility may express a need for accessible gathering space. Renovation, shared use, transport or a new building could address that need in different ways. Do not discard the proposed solution, but do not let it define the only alternative before its implications are examined.

Arcus recommends keeping two connected records: the full account of identified needs and the smaller set of approved commitments. The first protects continuity and accountability. The second establishes what will actually receive resources and management attention.

Explain why the list has become difficult to manage

Repeated entries may be inflating the list. Similar concerns gathered through several channels can appear as separate needs. Consolidate them without treating frequency as a precise measure of importance or erasing differences between locations and experiences.

A broad theme may conceal conflicting choices. Combining ten projects under “community wellbeing” reduces the number of headings without reducing the workload. A priority needs an intended result and boundaries, followed by explicit decisions about which actions start, wait or stop.

Urgency may be confused with visibility. A highly visible proposal can attract attention while less visible service risks accumulate. Examine consequences of delay and the evidence behind them. Address obligations and urgent risks through the appropriate process rather than leaving them to compete solely in a popularity exercise.

A funding opportunity may be driving the order. Available project funding can make an action feasible, but it may also create recurring costs or divert scarce staff. Ask what the Nation would be committing to after the initial funding period and what other work would be displaced.

Disagreement may be substantive. Different groups may reasonably value different outcomes. A more elaborate scoring model will not necessarily resolve that disagreement. Present the trade-off clearly and use the Nation’s decision process to determine the direction.

Set criteria before seeing which proposal wins

Agree on the decision purpose, the time horizon and the available resource envelope. Separate essential operating responsibilities and urgent matters from discretionary improvement choices, while making the resource demands of both visible. This avoids a false choice between maintaining basic services and making progress on strategic change.

For the remaining choices, identify a small set of criteria that decision-makers and members can understand. Define what each criterion means and what evidence would support an assessment. Community value, consequences of delay, distribution of benefits, feasibility and long-term resource implications may be relevant, but their meaning must be developed locally.

Record uncertainty alongside the assessment. An estimate based on a completed feasibility study is different from an early assumption. Do not give a proposal an apparently precise score when its costs or likely effects are largely unknown. “Further investigation required” can be a valid decision.

Check for double counting. If community benefit, strategic alignment and social impact all reward essentially the same feature, the model may give it unintended extra influence. Similarly, low initial cost and easy implementation can repeatedly favour small projects while obscuring a more consequential long-term need.

If weights are used, explain them and test plausible alternatives. The exercise is useful when it reveals which judgments drive a decision. It becomes misleading when a decimal score is presented as removing the need for judgment.

Compare four legitimate strategic alternatives

Concentrate on one major change. This can make a consequential result possible and simplify coordination. It also concentrates delivery risk and leaves fewer resources for other needs. Identify what must remain protected if the major initiative takes longer than expected.

Build a balanced set of smaller changes. This can address several experiences and create visible progress. It may increase coordination costs and spread specialist capacity across too many active commitments. Test the combined workload, not just the affordability of each project.

Invest first in enabling capacity. Better information, a staffing capability or a prerequisite plan may make later work possible. These investments can appear less visible than direct services. Explain the later decisions they enable and set a review point so preparation does not become indefinite.

Stage an uncertain proposal. Fund the next justified step rather than the entire concept. A needs assessment, design comparison or limited pilot can reduce uncertainty. Define what would justify expansion, redesign or closure before the first stage begins.

A Nation may combine these approaches. The important discipline is to make the mix intentional and explain what it requires from the operating model, including leadership time, coordination, procurement and ongoing service management.

Make the decision understandable after the workshop

Produce a short record for each selected priority: the outcome sought, the actions approved, the resources committed, the lead role, the first review point and the main assumptions. Keep the detailed comparison as supporting evidence. A polished heading should not substitute for an authorized delivery commitment.

Classify unselected proposals meaningfully. Some are deferred pending resources, some require investigation, some are covered by existing services, and some are not selected after assessment. Explain the reason without implying that the underlying need is unimportant. Where appropriate, identify an alternative response or a route for reconsideration.

Return the proposed direction and its rationale through the Nation’s established engagement and approval process. Describe the limitations of the evidence and material disagreements. A technically consistent model does not confer a mandate or replace community governance.

Review the portfolio when a significant assumption changes: a funding condition, a service risk, a capacity constraint or evidence of a different community need. Reconsider the affected choices rather than automatically rewriting the whole plan. This preserves continuity while allowing the Nation to respond to new information.

Evidence and source notes

1. Indigenous Services Canada, Comprehensive Community Planning Handbook, fourth edition, implementation guidance and Tool 19. Used for its discussion of decision criteria and alternative rankings; the numerical example in this article is original and hypothetical.
2. Squamish Nation, Long-Range Capital Plan project description. Used for the stated planning dimensions. Its historical expected completion date is not evidence of present status or delivered outcomes.

Research reviewed October 18, 2026. Fifty needs and five priorities illustrate a planning problem, not a recommended quota. The portfolio example and six-stage framework are original Arcus analysis, subject to the Nation’s values, governance and operating conditions.