Building a Grants Team in a Small First Nation Government

Most First Nations governments manage 10 to 25 active grants and contribution agreements at any given time, across ISC, CIRNAC, provincial funders, and private foundations — often with a grants function that sits informally across two or three people who each have other responsibilities.

That is not a criticism. It is a resource reality. The question is how to structure the grants function so it is effective within those constraints: clear enough that staff know what they own, documented enough that knowledge survives turnover, and simple enough that a two-person band office can actually run it.

This guide covers the core roles you need covered (even if one person holds multiple), how to structure a small grants function, what the handoff process should look like when staff change, and the systems that make the difference between a grants function that runs on institutional memory and one that can be picked up by anyone.

The four roles every grants function needs covered

In a large organization, these are separate jobs. In a small band office, they are often distributed across two or three people. What matters is not who holds them but that every role is clearly assigned to someone — no role should float.

1. Grant writer / applications lead

Owns the identification of funding opportunities, the drafting of applications, and the submission calendar. In small organizations this is often a designated grant coordinator or an ED who writes applications themselves. This role needs: access to the org profile (mission, programs, past wins), knowledge of current funder priorities, and a deadline management system.

2. Contribution agreement manager

Owns the post-award: CA intake, schedule review, reporting calendar, deliverable tracking, and communication with funders on active grants. Often sits with a program coordinator or the finance manager. This is the role most often left without a clear owner, which is why post-award compliance is where most small organizations struggle.

3. Finance and reporting

Owns expense coding by CA and budget line, budget-versus-actual reconciliation, quarterly and annual financial reports to funders. Usually the band's finance manager or bookkeeper. The critical requirement: they need to code expenses to the CA and budget line, not just to the departmental cost centre.

4. Strategic oversight

The ED or band manager who reviews grant pursuits against community priorities, signs CA documents, and ensures the grants portfolio aligns with what the nation is actually trying to do. This role does not need to be in the day-to-day grants work but does need visibility into the full portfolio.

The two-person grants function: a realistic model

For a band office with two people covering the grants function (often a grant coordinator and a finance person), the most functional split is:

The shared asset between them is the CA register — the source of truth for every active agreement that both people need access to. If that register only lives in one person's head or on their personal laptop, the function is one resignation away from a crisis.

Managing a portfolio of 10 to 25 active grants

At 10+ active grants, the complexity is not any single grant — it is the aggregate. Reporting dates cluster. Deliverable deadlines fall in the same two weeks. A funder calls about a variance on the same day a new CA arrives in the mail. The grants function that handles this well has three habits:

Weekly calendar review

Every Monday: what is due in the next 30 days? Not just this week — 30 days. This is enough runway to request extensions, fix data problems, or get the narrative report drafted before it becomes urgent. Teams that review only what is due this week are always in reactive mode.

One CA intake meeting per new award

When an award letter arrives, the grant coordinator and finance person sit down and do one thing together: read the CA schedules. Extract the budget lines, eligible categories, reporting dates, and deliverables. Enter them in the CA register that day. This 45-minute meeting prevents months of confusion later.

Quarterly portfolio reviews with the ED

A short (30-minute) review of the full grants portfolio with the ED or band manager. What is active, what is coming up, what is at risk, what new opportunities are being pursued. This keeps strategic oversight engaged without requiring the ED to be in the day-to-day.

Turnover: the biggest operational risk in a small grants team

Staff turnover in small First Nations governments is high. Grant coordinators in particular — often younger professionals or contract staff — move frequently. When they leave, they take the context with them: which funders are warm, which CAs have informal understandings with the program officer, which deliverables are on track versus at risk.

The only defence against knowledge loss is making the grants function less person-dependent. Specifically:

• Every active CA must have a complete record in a shared system — not in a personal spreadsheet or email folder. CA number, budget lines, eligible categories, deliverables, reporting dates, and the signed CA document attached. The next person should be able to pick up any grant and understand its full status without asking anyone.
• Funder contacts and interaction history must be shared, not personal. If the relationship with an ISC program officer lives in one person's email, it is lost when they leave. Log funder interactions in a shared CRM: who was contacted, what was discussed, what follow-up is pending.
• A two-week overlap handoff is worth the cost. When a grant coordinator leaves, paying two weeks of overlap to do a documented handoff is cheaper than six months of a new person not knowing what they inherited.

When to hire a dedicated grant writer vs use a consultant

The decision between a dedicated staff grant writer and a contract consultant comes down to volume and continuity:

• Hire staff when you have 8+ active grants annually, when your grants are primarily relationship-based (ISC, CIRNAC, repeat funders), or when post-award compliance work is substantial. A staff person builds institutional knowledge and funder relationships that a consultant cannot replicate.
• Use a consultant for one-time large applications (capital projects, new program launches), when you need specialized expertise for a specific funder, or when your grant volume is too low to justify a dedicated position. Consultants work best when the organization can brief them well — which requires having a clear org profile and CA register to hand over.

Many small First Nations organizations use a hybrid: a part-time internal coordinator who owns the CA management and funder relationships, supplemented by a consultant for major applications. The internal person keeps the institutional memory; the consultant brings writing capacity and specialized knowledge.