Innovative Solutions Canada 2026: The Complete Guide to ISC Challenge & Testing

Innovative Solutions Canada (ISC) is the federal program most often misclassified as a grant. It isn't. ISC is a procurement-innovation program run out of Innovation, Science and Economic Development Canada (ISED), and every dollar that flows out of it flows as a contract for delivered work, not as a non-repayable contribution. That distinction shows up in every part of how the program is run — the application is a proposal against a stated departmental requirement, the money comes via a procurement vehicle, and successful Phase 2 prototypes can lead directly to follow-on federal contracts. This guide walks through how the two ISC streams actually work, who they're for, where applications fail, and how a Canadian SME should think about ISC alongside SR&ED and other federal programs.

What ISC is, and why it's procurement — not a grant

Innovative Solutions Canada launched in 2017 as the federal government's answer to a structural problem: Canadian SMEs were under-represented in federal procurement, and many promising domestic innovations were dying in the gap between "interesting demo" and "first paying customer." ISC was modelled on the U.S. SBIR program (Small Business Innovation Research) and built around the same insight — that the federal government, as a buyer, can shape the innovation economy more efficiently than as a grant-maker. Instead of writing cheques and hoping commercialization follows, the government posts a real operational problem, buys feasibility work to figure out which solutions are credible, and then buys prototypes of the most promising ones.

That mechanism is the first thing to internalize. ISC contracts are procurement contracts. They are governed by federal procurement rules, signed by Public Services and Procurement Canada (PSPC) or the sponsoring department, and paid against delivered milestones — a feasibility report at the end of Phase 1, a working prototype at the end of Phase 2, or a successful operational test in the Testing stream. The legal instrument is a contract for goods and services, not a contribution agreement.

For a Canadian SME, the practical implications are different in three ways from a traditional grant:

• Revenue, not assistance. ISC dollars hit your books as contract revenue, not as government assistance against a project. That changes the SR&ED math, the financial statement treatment, and how investors read the cheque.
• IP and deliverables. Procurement contracts have explicit deliverables and IP terms. You generally retain background and foreground IP, but the Crown gets specified usage rights to what it paid for. Read the contract.
• Follow-on procurement is the point. A successful ISC Phase 2 prototype can lead to a sole-source or expedited follow-on procurement by the sponsoring department. The grant-style mental model — "spend it, claim it, move on" — misses the most important downstream outcome.

The two ISC streams

ISC runs two operationally distinct streams. They serve different stages of innovation and have different procurement mechanics.

Throughout the rest of this guide, when we say "ISC" without qualifying which stream, we mean the Challenge Stream. That's where most of the program's dollar volume flows and where most operating SMEs end up engaging. The Testing Stream is structurally simpler but more passive — you qualify, you wait, you hope a federal partner picks you up.

Challenge Stream — Phase 1 (feasibility) vs Phase 2 (prototype)

The Challenge Stream is a two-phase, gated procurement. The two phases are designed to do different things, and treating them as a single continuous workflow is one of the most common ways applicants stumble.

Phase 1: feasibility

Phase 1 is a small feasibility contract. The standard ceiling is up to $150,000, with some challenges authorized to award up to $300,000 where the underlying problem demands more rigorous early work. The contract length is typically around six months. The deliverable is a feasibility report — not a working prototype.

What a department is buying with Phase 1 is essentially "thinking work" against a specific problem: can your proposed approach plausibly solve it? Will it integrate with the operational environment the sponsoring department actually has? What are the technical risks, the regulatory questions, the cost envelope? Phase 1 is also where the department learns enough about your team and your approach to decide whether you're worth a Phase 2 contract.

Two practical points on Phase 1:

• The cap is real. The Phase 1 ceiling is a hard contract ceiling, not a budget guideline. Build a feasibility plan that fits inside it. Proposals that quietly assume Phase 1 will balloon don't get signed.
• The feasibility report matters as much as the technical work. Phase 1 is also a sales document for Phase 2. A clean, well-structured feasibility deliverable that explicitly identifies the prototype risks and the Phase 2 path makes the Phase 2 case much easier to make.

Phase 2: prototype

Phase 2 is where the real money sits. The standard ceiling is up to $1,000,000, with some challenges authorized for up to $2,000,000 where the prototype scope warrants it. The contract length is typically 18 to 24 months, sometimes longer. The deliverable is a working prototype that can be demonstrated in or near the sponsoring department's operational environment.

The critical thing to understand about Phase 2 is that it is not automatic. Most Phase 1 contracts do not advance to Phase 2. Only Phase 1 contract holders are eligible to compete for the Phase 2 contract for the same challenge, but they have to compete on the strength of their feasibility deliverable. Where multiple SMEs were awarded Phase 1 contracts for the same challenge, only one (or a small number) will get Phase 2. Where the Phase 1 deliverable raised more red flags than answers, the department may choose to award no Phase 2 at all and walk away from the challenge.

What happens after Phase 2

This is the part of ISC that mainstream coverage usually under-reports. A successful Phase 2 prototype — one that demonstrably solves the sponsoring department's problem — can lead to follow-on procurement by that department. The legal mechanics vary, but the practical effect is that the department now has a Canadian-made solution, evidence that it works in their environment, and a procurement path to buy it operationally. For an SME, that follow-on contract is often worth more over time than the Phase 1 + Phase 2 contracts combined.

That said, follow-on procurement is not guaranteed and is governed by all the usual federal procurement rules. Treating the follow-on as a certainty when modelling your business is as wrong as ignoring it entirely. The right framing is: ISC's structural value is that it builds a credible federal reference customer, and that reference customer can become a real procurement relationship if the prototype delivers.

Testing Stream — government as first customer for pre-commercial tech

The Testing Stream is structurally different. Instead of departments posting problems and SMEs proposing solutions, innovators with pre-commercial technology submit their innovation to a qualification pool, and federal organizations select innovations they want to test in real operational environments. ISED then puts a contract in place to buy the test from the innovator.

"Pre-commercial" is the operative word. ISC's published criteria treat an innovation as eligible if it's not yet available in the marketplace, represents a significant modification to existing applications, or delivers an improvement in functionality, cost, or performance over state-of-the-art alternatives. The technology has to be ready to test in an operational environment — meaning past the lab bench, not yet on the open market.

Contract values in the Testing Stream scale with the test scope. In practice, contracts typically fall in the ~$100K to $1M range, though larger tests are possible where the operational requirements warrant. The contract pays for the testing activity itself — supplying units, supporting the test in the field, instrumentation, data collection, analysis. The innovator retains IP in their underlying technology; the test generates evidence of operational performance.

The Testing Stream's mechanics are passive from the innovator's side. You submit, you qualify, you wait. Matching depends on whether a federal organization expresses interest in your innovation, which depends on whether your technology happens to solve a real operational problem inside a department that knows about the qualification pool. There's no application deadline to push against and no formal evaluation rubric you can game.

Testing Stream is often the right vehicle for hardware, instrumentation, defence-adjacent technologies, materials, healthcare devices, and other physical innovations where "test in an operational environment" is a meaningful concept. Software-only innovations can qualify but tend to be harder to match unless they touch operational federal infrastructure directly.

Eligibility: Canadian SME, Canadian IP

ISC's eligibility rules are tighter than most federal innovation programs, and the tightness is by design. The program exists to direct federal procurement toward Canadian small businesses, so the gates are oriented around exactly that.

The 500-FTE threshold is the cleanest line in the rules and the one applicants check first. The Canadian IP requirement is more nuanced — it's not that every patent has to be Canadian-issued, it's that the SME applying needs to have the rights to deliver the solution to the federal government from Canadian operations. Foreign-parented companies with Canadian subsidiaries can participate, but the work and the IP rights need to land in Canada in a way that withstands procurement-side scrutiny.

Past-performance and team capability also matter. ISC is procurement, not a grant, and procurement officers are evaluating whether your company can actually deliver against a federal contract. Teams that have shipped pre-commercial products before, that have the engineering depth visible on paper, and that have a track record of milestone-based work tend to score better than teams pitching their first piece of revenue.

How to find live challenges

This is the part that throws first-time applicants. ISC challenges are not centrally posted in a single, predictable feed the way some grant programs publish intake windows. The two surfaces to watch are:

• CanadaBuys (canadabuys.canada.ca). The federal procurement platform. ISC Challenge opportunities are posted here as solicitations alongside other federal tenders. Filter for ISC or for the sponsoring department, and check regularly — new challenges are posted on a rolling basis, not on a fixed annual cycle.
• The ISC portal on ised-isde.canada.ca. ISED maintains a current-challenges listing on the program page. This is the easier place to scan for plain-English challenge descriptions; CanadaBuys is the place to download the actual solicitation documents.

Challenges are sponsored by individual federal departments and agencies — National Research Council, Department of National Defence, Health Canada, Innovation Hubs, Environment and Climate Change Canada, Public Services and Procurement Canada itself, and many others. Each challenge has a specific problem statement, evaluation criteria, and closing date. The closing windows are typically four to eight weeks from posting, which is shorter than most grant deadlines and is a real planning constraint.

The Testing Stream uses a different surface. Innovators submit their pre-commercial innovation through the ISC application process (the same ISED portal), are evaluated against the pre-commercial criteria, and qualifying innovations enter the testing pool. From there, the matching is partner-driven.

Application flow and evaluation

The Challenge Stream application is closer to a federal proposal response than to a typical grant application. The mechanics:

Evaluation is criteria-driven and weighted. Each challenge publishes its specific criteria and weights. The common headings are technical merit, benefits to Canada (jobs, IP retention, ecosystem effects), financial proposal credibility, and team capability. Proposals that don't visibly address each criterion lose points by default — evaluators are scoring against the rubric, not reading for narrative quality.

Stacking ISC with SR&ED

This is where most SMEs need careful advice, because ISC contract revenue interacts with SR&ED in ways that aren't always obvious. The core principle: SR&ED treats most government assistance as a reduction to qualified expenditures, and the CRA's treatment of ISC contract payments has specific tax considerations that should be confirmed with your tax advisor for your particular fact pattern.

The simplest framing is that ISC payments are contract revenue earned for delivering work, not a non-repayable contribution against your costs. That changes how SR&ED qualified expenditures need to be calculated when the underlying engineering hours were also funded by the ISC contract. The practical implications:

• You generally can't double-recover the same dollar of expense. If an engineer's hours were paid for through an ISC contract, the SR&ED-claimable portion of those hours needs to reflect that. The CRA has well-established positions on contract payments and qualified expenditures — ignoring them creates audit risk.
• Contract payments and government assistance are treated differently for SR&ED purposes. ISC contract revenue and a grant-style contribution are not the same tax animal. The treatment turns on the facts of the arrangement, including whether the work has been done under a contract for goods and services. Get a tax opinion before assuming.
• Documentation discipline matters more, not less. The technical narrative for SR&ED needs to be defensible alongside the ISC deliverable. If the same engineer's time is reported one way to ISED and a different way on the SR&ED claim, you have an inconsistency CRA will find.

The practical posture we recommend with clients: do the engineering work, claim ISC contract revenue cleanly, claim SR&ED on the portion of work that genuinely meets SR&ED criteria net of the contract recovery, and document the apportionment rigorously. Don't hide ISC revenue from CRA, don't claim SR&ED on hours that ISC paid for in full, and get advice on the contract-versus-assistance distinction for your particular contract terms. The wrong move — double-claiming the same engineer hour through both an ISC contract and a full SR&ED hour — is the kind of pattern that turns a routine SR&ED review into a problem.

Why ISC fits founders aiming for federal contracts (vs grant-seekers)

One of the most useful filters when deciding whether to apply to ISC is to ask what you actually want out of the federal government as a counterparty. Grant-seekers and procurement-builders are different profiles, and ISC favours the latter.

An SME building toward a future where the federal government is a customer — defence-adjacent, healthcare instrumentation, environmental monitoring, public-safety hardware, infrastructure software, anything where Ottawa is a credible buyer — should treat ISC as a strategic priority. The Phase 1 contract is small, but the trajectory from Phase 1 to Phase 2 to follow-on procurement is the most direct path Canada has to federal-customer revenue for innovating SMEs.

An SME with no realistic federal procurement future — pure consumer SaaS targeting U.S. buyers, for example — will usually find ISC's effort-to-cheque ratio worse than IRAP or SR&ED. The program is engineered to deliver federal-customer outcomes, and those outcomes only matter if the federal government is plausibly a customer for your product.

Common reasons proposals fail

From the Challenge Stream proposals we've worked on and observed, rejection patterns are consistent:

• Wrong challenge. The proposal addresses what the SME wants to build, not what the sponsoring department actually asked for. ISC challenges are problem statements, not topic areas — proposals that drift off the problem fail at the evaluation stage no matter how strong the underlying technology is.
• Generic "benefits to Canada" language. Every challenge weights benefits to Canada (jobs retained, IP held in Canada, ecosystem impact). Boilerplate paragraphs that could be lifted into any application don't score. The benefits need to tie to the specific work being proposed.
• Financial proposal that doesn't fit Phase 1. Phase 1 has a hard ceiling. Proposals that quietly carry more than $150K of work plan (or $300K for higher-cap challenges) without acknowledging the gap are non-compliant.
• No path to Phase 2. Phase 1 proposals that don't articulate what a credible Phase 2 prototype would look like — even at a high level — signal an incomplete solution. The department is buying Phase 1 because Phase 2 might follow; if Phase 2 isn't visible from your proposal, the Phase 1 work isn't worth buying.
• Team capability gaps. Procurement evaluators look at past performance, engineering depth, and delivery track record. A proposal that doesn't make the team's capability legible — bios, prior delivery, references — loses points it didn't need to lose.
• Eligibility self-misclassification. Companies that have grown past the 500-FTE threshold (sometimes via acquisitions), companies with IP that doesn't sit in Canadian operations, and companies that have outgrown the SME definition occasionally apply anyway and are screened out at the eligibility check.
• Missed compliance details. ISC is a procurement instrument. Procurement-style compliance details — mandatory criteria, document requirements, formatting rules, certifications — matter. Missing a single mandatory submission element makes the proposal non-compliant regardless of how strong the technical content is.

Related programs in the Canadian procurement-innovation stack

ISC sits in a broader Canadian federal procurement-innovation stack that's worth knowing about. NGen funds advanced manufacturing consortia with a different structure (cost-shared project funding, manufacturing-focused). Scale AI funds industry-led AI commercialization consortia, also on a cost-share basis. NRC IRAP funds firm-level R&D and product-readiness work as contributions, not contracts. Strategic Innovation Fund and its successor Strategic Response Fund target large transformative projects in priority sectors. None of these substitute for ISC — they sit alongside it, funding different parts of the same SME's journey. Use our Grant Finder or browse the program list on the homepage to compare ISC against the rest of the federal stack.

Final thoughts

Innovative Solutions Canada is one of the most strategically valuable federal vehicles for Canadian SMEs with pre-commercial technology and a realistic path to federal-customer revenue. The Phase 1 cheques are small — up to $150,000 for most challenges, up to $300,000 for some — but the trajectory from Phase 1 to Phase 2 (up to $1M, occasionally up to $2M) to follow-on procurement is the most direct route Canada has built between an innovating SME and a federal customer relationship. The Testing Stream serves a different need but rests on the same logic: let the federal government be a first customer for pre-commercial Canadian innovation.

What trips SMEs up most often is treating ISC like a grant. It isn't. The application is a procurement proposal, the money is contract revenue, the deliverables are contracted obligations, and the evaluation is procurement-style scoring. Companies that internalize that shift — reading solicitations the way a defence supplier reads them, building proposals against criteria the way a federal contractor does — convert at materially higher rates than companies that approach ISC as another grant submission.

The two-phase Challenge gate is real and should be modelled honestly. Most Phase 1 contracts do not advance to Phase 2; plan your business assuming Phase 1 may be the end of the line, and treat Phase 2 as upside. On the tax side, ISC contract revenue and SR&ED need to be reconciled carefully — the contract-versus-assistance distinction matters and is worth getting a specific opinion on for your fact pattern. Done well, ISC and SR&ED can coexist inside the same engineering team's work; done sloppily, they create CRA-side problems that are expensive to clean up after the fact.

For Canadian SMEs in defence-adjacent, healthcare, environmental, manufacturing, infrastructure, and other federal-customer-plausible sectors, ISC should be one explicit line on the funding strategy — planned for, not stumbled into.