What a Grant Application Asks You For Before You Start

Every grant programme’s website makes the process look easier than it is. Nobody’s lying to you. The public page describes the form, and the form is the small part. This page covers the rest: what you need in hand before you start, what a reviewer cross-checks, and the repeatable reasons small business applications fail.

Treat this as a process guide. We claim no track record of successful applications here, because this page isn’t built on one. It comes from the public application guidance the referenced programmes publish, checked 2026-08-28, plus a plain account of what “documentation” and “narrative” mean once you’re doing the work.

What every application needs, before you touch the form

Whichever programme you’re applying to, four things have to exist before the application is worth starting:

A specific, costed activity. A named training course with a price on it. A named project with a scope and a budget. A technical effort with a start and an end point. “We want to grow” and “we want to be more efficient” won’t survive intake. Every programme covered in the companion guide, Four Ontario Funding Programmes for Trades, Checked and Dated, asks for this at the application stage.

Basic business documentation, current and consistent. Registration or incorporation details, a recent financial statement or tax filing, and payroll records if the claim touches employee costs or wages. Obvious, and still the most common reason an application stalls at intake. The numbers on the form don’t match the numbers in the business’s own books, because somebody filled the form in from memory.

A quote or cost breakdown from whoever does the work. A training provider’s quote, a contractor’s estimate, a supplier’s invoice. Programmes that fund a specific cost, like the Ontario Job Grant funding a named training course, want to see the number before they agree to share it.

Someone who has read the eligibility criteria closely enough to say no. Most applicants skip this, and it saves more wasted time than anything else on the list. Before you write a word, hold the activity up against the programme’s own eligibility rules. A grant directory site’s summary of those rules will mislead you. The SR&ED guide in this series exists because that step gets skipped constantly on the SR&ED side, where the distance between “sounds technical” and “meets CRA’s technological uncertainty test” is wide and easy to misjudge.

What a reviewer is checking for

Consistency. An Employment Ontario officer processing a training grant and a CRA reviewer assessing an SR&ED technical narrative do the same job: they hold the story in the application against the documents behind it. A training grant has to match the real course, the real price and the real employee. An SR&ED narrative has to match the timesheets, project notes and expense records covering the same period. Polished writing won’t paper over a mismatch. It makes the mismatch louder once somebody finds it.

Timing. Most programmes want the application, or in SR&ED’s case the underlying work, to come before the spending or alongside it. Finish a course, pay for it, then apply for a training grant, and you can’t expect the same treatment as a pre-approved application. Check each programme’s own rules before you spend money you intend to claim. SR&ED goes further. The work itself has to have involved the systematic, documented process CRA’s criteria describe, while it was happening. A narrative written afterwards to make routine work sound like R&D won’t hold.

Whether the documentation was written at the time or reconstructed later. This is the most common way an otherwise legitimate claim gets weakened. A timesheet filled in during the week it describes reads differently from one filled in eight months later from memory, and reviewers who see a lot of claims spot it. Project notes written as the decisions were made carry more weight than a summary composed for the application. If a project-based grant or an SR&ED claim is anywhere on your horizon, start keeping better contemporaneous notes today. It costs you nothing, and it’s the one part of this you can never fix retroactively.

Timelines, honestly

A programme’s own page rarely tells you how long the whole thing takes end to end, because the answer depends on how ready your documentation is on day one as much as on how fast the government processes the form. Here’s a rough guide, promised to nobody, based on how the programmes in this series are structured:

• A single-cost training grant (the Ontario Job Grant is the clearest example): with a training quote and current payroll and business records already to hand, the application is a few hours of work. The government assesses on an ongoing basis rather than a fixed cycle, per the program’s page, checked 2026-08-28.
• A project-based grant (the Skills Development Fund Training Stream is the example in this series): budget weeks of preparation. The application wants a defined project scope, a budget, and a narrative explaining the workforce problem you’re solving, which is a long way past attaching one invoice.
• An SR&ED claim: the longest of the three. It needs a technical narrative that satisfies CRA’s three-part eligibility test plus a full accounting of the eligible expenditures behind it, prepared alongside the business’s regular tax filing. Get professional advice here. The technical writing and the underlying documentation both move the outcome, and both take real time to get right.

The honest reasons most small business applications fail

• The activity doesn’t meet the programme’s rules, and nobody checked closely before applying. The most preventable failure on this list. Read the eligibility page itself. A directory site’s summary of it will cost you a submission.
• The documentation contradicts the story. Numbers on the application that won’t reconcile with the business’s own books or payroll records. A technical narrative no timesheet record can back up.
• The narrative dresses routine skilled work up as research or an eligible project, which happens most on SR&ED claims. Being very good at your trade sits in a different category from clearing a technological uncertainty test, and reviewers who assess claims all year can tell them apart.
• The application arrives after the spending it’s meant to cover, on a programme that required it to come first. Read each programme’s timing rules before you commit money you plan to claim back.
• The owner ran out of patience partway through and sent something thinner than it should have been. A rushed application with a vague cost breakdown, or a project description that fits in one paragraph, loses to a specific one. That’s an avoidable way to lose.

None of these failures are exotic. They’re the ordinary, preventable kind, and the unglamorous work heads off every one: read the eligibility rules yourself, keep records while the work is happening, and hold off on the application until you can describe the activity, its cost and its documentation in one clear paragraph. If you can’t write that paragraph yet, you’re not ready to submit.