Make the strategic decision before polishing the proposal

A short application deadline can encourage an administration to begin drafting before it has decided whether the opportunity fits. Once staff have invested time in the proposal, there can be pressure to continue even when the scope has drifted from the original need.

Arcus recommends a brief decision record before substantial drafting. State the community outcome, the proposed contribution, the authority supporting it, the stage of readiness and the resource implications. Then assess the funding opportunity against that record.

This does not require every future project to be fully specified in a strategic plan. A plan can establish a direction while later analysis identifies the best intervention. The important distinction is between developing a credible response to an agreed need and inventing a priority solely because money has become available.

If a worthwhile opportunity introduces a genuinely new strategic choice, bring that choice through the Nation’s appropriate process. Do not disguise it as an already-approved commitment by attaching a broad theme such as wellbeing or capacity building.

Trace the proposal through five connections

Need to outcome. Explain the need using relevant evidence and community direction. State the change the Nation wants to achieve. A broad description of disadvantage does not establish why this particular intervention is appropriate.

Outcome to intervention. Explain how the proposed work is expected to contribute. Identify alternatives considered and why the chosen approach is suitable at this stage. A funder should be able to follow the logic without assuming that the project title proves its benefit.

Intervention to readiness. Identify the prerequisites: information, decisions, design, staffing, partners, access or approvals. Separate confirmed facts from conditions still to be satisfied. If the project is not ready for delivery, a preparatory stage may be the more credible request.

Readiness to resources. Connect the scope with the full effort and cost. Identify cash, staff time, specialist support, management attention and contributions from other departments. Distinguish confirmed resources from applications or assumptions.

Resources to accountability. Assign a delivery lead and reporting responsibilities. Define the evidence that will demonstrate completion and the intended benefit. Align the funder’s deliverables with the Nation’s own accountability needs while respecting its information-governance arrangements.

Diagnose weak alignment before blaming the writing

The priority may be too broad. Almost any project can be linked to prosperity or wellbeing. Specify the actual intended result and the contribution the application would make. If that connection cannot be explained clearly, the proposal may need a strategic decision before a stronger narrative.

The project may be at the wrong stage. A request to implement a solution can be premature if the underlying need, feasibility or operating model is unresolved. Better prose cannot replace missing preparation. Consider whether the next justified step is investigation, design or a pilot.

The funding rules may not fit. A strong strategic project can still be unsuitable for a particular program. Adjusting the description to appear eligible while retaining an incompatible delivery plan creates problems later. Seek clarification, find a better fit or defer the application.

The application may overstate capacity. Staff assigned to several funded projects can become the common constraint. Check the combined workload before making another commitment. The availability of grant money does not create management time automatically.

The evidence may be incomplete. Community feedback can establish an important concern while technical information is still needed to compare responses. Explain the evidence gap and how the proposed stage addresses it. Avoid presenting an early assumption as a verified demand forecast.

Calculate the cost the Nation still carries

Separate the total project cost from the amount requested and the amount confirmed. Identify ineligible costs, required contributions, cash-flow timing, reporting work and ongoing operation. An application budget should make these distinctions visible before leadership commits to delivery.

Consider a hypothetical service initiative with $100,000 in initial implementation costs. A funding opportunity would contribute $80,000, leaving $20,000 to be covered by the Nation or another confirmed source. Once operating, the service would require $30,000 each year for staffing, maintenance and administration that the initial contribution does not cover.

Over an illustrative three-year operating period after implementation, those recurring costs total $90,000. Together with the initial $20,000 gap, the residual commitment is $110,000, before inflation, replacement costs or financing effects. This is an undiscounted planning illustration, not an estimate for an actual service or a statement of any program’s terms.

The project may still be worthwhile. The decision should address whether the recurring commitment is affordable, what benefit it supports and what other work would be displaced. A high proportion of initial funding is not, by itself, a sufficient reason to proceed.

Also test timing. If expenditure must occur before reimbursement, finance needs to assess the cash-flow requirement. If recruitment cannot be completed within the delivery period, an approved budget may still be operationally unrealistic. Match the project calendar with actual capacity and agreement conditions.

Maintain one project record from strategy to reporting

Create a pipeline of potential initiatives linked to the strategic plan. For each, record the stage, readiness gaps, approximate resource needs, accountable role and next decision. This allows the administration to assess opportunities against prepared priorities rather than start from scratch at every deadline.

Use a common project identifier across the strategic register, application, approved budget and implementation plan. Keep the scope and assumptions synchronized. If a funder offers less support or changes a condition, return to the relevant decision before accepting a materially different commitment.

Assign responsibility for checking program fit and responsibility for confirming operational feasibility. These functions may involve different people. A proposal writer should not be expected to authorize staff capacity, recurring spending or a strategic change on the Nation’s behalf.

After approval, translate agreement conditions into the delivery plan and reporting calendar. Keep the Nation’s intended outcome visible alongside the required funded outputs. Completing a report or spending a contribution does not, on its own, establish that the strategic benefit has been achieved.

At completion, document what was delivered, what was learned and which ongoing responsibilities remain. Use that evidence to improve the next funding decision. A strong application is one stage in a coherent strategy and delivery process.

Evidence and source notes

1. Indigenous Services Canada, First Nation Infrastructure Fund Guide, version dated December 19, 2024, reviewed October 18, 2026. Used for the relationship between strategic alignment, deliverables and cost eligibility; not a complete eligibility assessment.
2. Crown-Indigenous Relations and Northern Affairs Canada, First Nation Adapt Program, page modified July 10, 2026. Used to illustrate assessment and planning support at a defined project stage.

Research reviewed October 18, 2026. Program terms can change and must be checked for the particular application. The service-cost example is hypothetical. The six-gate framework is original Arcus management analysis.