Grant Proposal Templates for Canadian Founders (10 Sections, 2026)

The Executive Summary is the only section many reviewers read in full. At NRC IRAP, first contact goes to a client engagement advisor, who decides whether to refer you to an industrial technology advisor, so your short project description does the triage; if the project's commercial fit isn't clear in the first paragraph, the application slides to the bottom of the queue. Treat this as marketing copy, not boilerplate.

What it must contain, in order: (1) one-sentence project description; (2) the problem in one sentence; (3) your solution and why you're the team to deliver it; (4) the dollar ask, total project budget, and your contribution; (5) the measurable outcome at month 12 and month 24; (6) a one-line credibility anchor (revenue, customers, prior funding, IP).

What NOT to do

• Do not cut-and-paste your About-Us page. Reviewers can spot it instantly.
• Do not bury the dollar ask in paragraph four. State it in paragraph one or two.
• Do not write the Executive Summary first. Write it last, after the Narrative and Budget are locked.

Plan a rewrite after the rest of the proposal is done. Most founders underestimate the rewrite phase.

The Project Narrative is the body of the proposal. In federal applications it's typically called the "Project Description" or "Statement of Need." For non-profit funders it's the "Need Statement" + "Approach" combined. Either way, this is where you make the substantive case — and where most first-time applicants over-write.

The reviewer scoring rubric for this section almost universally tracks five elements: (1) the problem and evidence it exists; (2) why your approach is the right approach (versus alternatives); (3) what you will actually do, with enough specificity that someone could replicate it; (4) why your team is the right team; (5) what success looks like at the end of the funded period.

What NOT to do

• Do not lead with your company history. Lead with the problem.
• Do not assume the reviewer is an expert in your field. Define every acronym on first use; explain technical concepts in plain language with at most one analogy.
• Do not promise more than you can deliver in the funded period. Reviewers compare your stated timeline to the work-plan in item #8 — inconsistencies are penalty flags.

This is the section reviewers weigh most; leave room for two revision passes.

Every Canadian funder uses a slightly different budget format, but the categories are remarkably consistent: salaries and benefits, contracted services, equipment and supplies, travel, indirect/administrative, and other direct costs. Federal programs (IRAP, Mitacs, NSERC) require salaries to be broken out by role with day-rate justification; provincial programs accept aggregate salary lines.

Your budget must total to your dollar ask — verifying this is the first thing a program officer does. Budgets that don't reconcile, or that have categories the program explicitly excludes (e.g., capital equipment for an HR program), are auto-flagged. CRA-style documentation rigour matters here: every line should map to a quotation, vendor agreement, or salary schedule you could produce on request.

The co-funding column

Most matching-fund programs (CanExport, IRAP, Strategic Innovation Fund) require a column showing your contribution alongside the requested amount. The match is real money, not in-kind labour, unless the program explicitly says otherwise. Misreporting in-kind as cash co-funding is one of the most common claw-back triggers.

What NOT to do

• Do not use round numbers for everything. $50,000 for "salaries" looks invented; $48,375.20 looks researched.
• Do not include ineligible expenses. Read the program's eligibility-of-expenses page before opening Excel.
• Do not skip the quarterly cash-flow table if requested. It signals you've thought through delivery.

Funders increasingly fund outcomes, not activities. Your Evaluation Plan answers the question "how will the funder know their money worked?" The strongest evaluation plans use a results-based-management (RBM) framework: distinguish outputs (what you produced), outcomes (what changed for stakeholders), and impact (long-term system change). This is the same logic Treasury Board uses for its own program evaluations.

Your plan should specify: indicators (the thing you'll measure), baselines (where you start), targets (where you'll be at month 12 and month 24), data sources (how you'll collect the data), and reporting cadence (when you'll report it). Reviewers look for indicators that are measurable without doubling your project's overhead.

What NOT to do

• Do not promise quarterly third-party evaluations on a $50K grant. Right-size the rigour to the budget.
• Do not list 30 indicators. Five to eight, well-chosen, signal discipline.
• Do not confuse outputs (workshops delivered) with outcomes (skills gained). Reviewers grade on this.

Sustainability is not the same as fundraising. A strong sustainability plan describes how the work continues without this funder's money — through earned revenue, partnership cost-sharing, in-kind continuation, or graduation to a different program. Foundation funders in particular use this section to filter out "grant-dependent" applicants from "investment-grade" ones.

Your plan should answer four questions: (1) which elements of the work are time-limited (no need to sustain) versus ongoing? (2) For ongoing elements, what's the cost? (3) Where will that money come from at month 25, 36, 48? (4) What's your plan-B if your primary sustainability path falls through?

What NOT to do

• Do not write "we'll apply for more grants." That's not a sustainability plan; that's the absence of one.
• Do not over-promise. Funders compare your stated revenue projections to your actual financial statements (item #9).

Partnership letters confirm that a third party will contribute something specific (cash, in-kind, data access, end-user testing, regulatory expertise) by a specific time. The strongest letters quantify the contribution. The weakest say "we support this important project." Reviewers can tell the difference instantly.

For Mitacs Accelerate, NSERC Alliance, IRAP-with-partner, Innovation Solutions Canada, and any provincial economic-development program with a co-funding requirement, partnership letters are a hard gate. Missing letters or letters that don't quantify the contribution = automatic deficiency-flag and a 2-4 week delay while you go back and ask for revisions.

What a strong partnership letter contains

• The partner's letterhead, signed by someone authorized (Director-level minimum for organizations > 50 staff).
• Specific dollar amount (cash) or specific in-kind contribution (hours × rate).
• The timeframe of the commitment, matching your work plan.
• The partner's stake in the outcome — why they're in.
• Contact information for verification.

Partner letters take 1-2 weeks of calendar time to come back signed. Start early.

A Theory of Change (in non-profit speak) or Logic Model (in federal speak) is essentially the same thing: a structured map showing how your inputs (money, people, partners) translate into activities, outputs, outcomes and impact. Federal program-officer training across PHAC, ESDC, and Innovation, Science and Economic Development Canada uses this model.

The pedagogy hasn't changed in 20 years, but the application has: in 2026, federal evaluators expect the Logic Model to align line-by-line with the Evaluation Plan (item #4). Mismatches between the two are one of the most common deficiency-flag reasons. If your Logic Model says "outcome X" and your Evaluation Plan doesn't measure X, you fail the alignment check.

What NOT to do

• Do not use 12 boxes when 6 will do. Reviewers prefer compressed, readable models.
• Do not make this section text-only. The diagram is the deliverable. Build it in PowerPoint, export PNG, embed.
• Do not skip the assumptions row at the bottom. Reviewers check for it.

The first version takes longest; subsequent grants reuse the same Logic Model with light edits.

A Work Plan can be a Gantt chart (best for projects > 12 months), a milestone table (best for shorter projects), or both. Federal R&D programs (IRAP, Mitacs, NSERC) almost always require a Gantt. Foundation funders are happier with a milestone table. Either way, it must show what gets done when, who's responsible, and what counts as "done."

The Work Plan must reconcile to: your Project Narrative timeline (item #2), your Budget cash-flow (item #3), and your Evaluation Plan reporting cadence (item #4). Inconsistencies between these four documents are the second-most-common deficiency reason in our review of program-officer feedback (after budget reconciliation errors).

What NOT to do

• Do not show every task. Reviewers want major milestones, not your daily standup notes.
• Do not start every task in month 1. Reviewers know nothing real starts in week one — the lead-time on hiring, equipment, partner agreements is real.
• Do not skip the dependencies. Showing that "task B depends on task A" signals project management maturity.

Most rejections are not because the project was weak. They're because something on the attachments list was missing, illegible, or mis-formatted. A complete Canadian grant application typically attaches: articles of incorporation, last two years of T2 financial statements (or audited financials for non-profits), CRA business number confirmation, key-person CVs (max 2 pages each), proof of insurance, and partner letters (item #6).

Some federal programs add: tax-clearance letter from CRA, proof of provincial business registration, environmental-impact attestation, and intellectual-property declaration. Provincial programs sometimes require a recent payroll-remittance summary and proof of WSIB/CSST coverage.

What NOT to do

• Do not submit the attachments out of order. Most portals require a specific naming convention; deviating costs you a deficiency flag.
• Do not submit scans of scans. Reviewers can tell. Use the original PDF or re-export from source.
• Do not submit a 12-page CV. Two pages, max. Lead with the relevant credential.

If you need audited financials or CRA letters, request them now; they take 1–2 weeks to arrive.

Letters of Inquiry (LOIs) are required upfront by most foundation funders and a growing number of corporate giving programs. They're typically 1-2 pages, sent before the full proposal, and screened by program staff. If the LOI is approved, the foundation invites you to submit a full application. If it's not, you have saved yourself a full application.

The Cover Letter is shorter — usually a single page accompanying a full proposal. It introduces your organization, references your prior contact with the funder (if any), and points the reviewer to the most important parts of the proposal. Federal programs increasingly accept (but rarely require) cover letters; foundations expect them.

What NOT to do

• Do not use the LOI as a "lite" version of the proposal. It's a different document with different conventions.
• Do not skip the LOI step where one is requested. Sending a full unsolicited proposal triggers an automatic decline at most foundations.
• Do not write to "Dear Sir or Madam." Find the program officer's name. Foundation websites list them.