Horizon Europe: choose your SME’s consortium role

For a Canadian SME exploring Horizon Europe, a useful starting question is: what part of a collaborative project can your team credibly deliver? Choose a role around that contribution and your available people before offering to coordinate an entire consortium.

This guide helps an owner, R&D manager and finance lead prepare that decision together. It combines current Canadian government guidance with an internal role checklist and a suggested partner brief. The checklist and example are editorial planning tools, not official application forms or evidence that a project will receive funding.

Start with the call and your contribution

Canada’s association with Horizon Europe’s Pillar 2 allows participation under similar conditions to EU entities, subject to restrictions in the specific call. ISED’s Pillar 2 guidance, checked on September 18, 2026, describes consortium participation and call-specific conditions. A Canadian address alone does not establish fit.

Before discussing titles, identify one relevant call topic. Write down the result it seeks and the contribution your business could make. Keep three questions separate: does the topic fit, does the proposed consortium meet its conditions, and can your company deliver its share? This article does not identify an open call or announce a new Canadian funding entitlement.

A vague offer such as “we can help with innovation” gives a prospective partner little to assess. A more useful starting point names a capability, a proposed task, a deliverable and the people available. Describe what is already demonstrated and what remains uncertain.

Compare three roles without treating them as a ranking

ISED’s consortium role guide distinguishes the main responsibilities:

• Partner or beneficiary: contributes expertise to the project.

• Work package leader: takes responsibility for a defined group of tasks, including delivery, resources and risks.

• Coordinator: manages the overall project and serves as the main contact with the European Commission.

Canadian participants may hold these roles in Pillar 2. That permission does not establish that each role suits your company or a particular call.

For an internal decision, compare the work your company can perform with the coordination it can sustain. A specialist contribution can be valuable without project-wide leadership. Likewise, technical strength does not by itself answer who will manage dependencies, consolidate information or resolve a delayed deliverable.

Ask each proposed role owner to explain a difficult week: a partner misses a milestone, a test needs repeating and a key employee is unavailable. Who contacts whom? Who revises the company’s plan? Which decisions require management approval? Concrete answers expose capacity gaps before they become proposal promises.

Run a short capacity review

Bring the technical lead and finance lead into the same conversation. Use these suggested internal checks:

• Technical delivery: name the task owner, backup, equipment and evidence supporting the proposed contribution.

• Coordination: identify who can follow dependencies, arrange discussions and maintain a decision record.

• Financial preparation: assign someone to develop the proposed budget and check the applicable cost and reporting rules.

• Management availability: agree who can commit people and approve changes to the company’s contribution.

• Unresolved conditions: list the questions that require the call documents, the prospective coordinator or a qualified advisor.

Do not turn this into an invented eligibility score. A missing owner means the company has preparation work to do; it does not prove that the program will reject it. Record the gap, the person who will resolve it and the internal decision date.

Prepare a brief a prospective partner can assess

Create a short, non-confidential introduction focused on one topic. The following fields are a suggested working structure, not an official Horizon Europe template:

• Topic: the call identifier and the expected result your contribution would support.

• Capability: the specific process, research skill, test environment or other expertise you can offer.

• Proposed work: a bounded task and its intended deliverable, with assumptions stated.

• Evidence: a public technical description, relevant previous work or another shareable basis for the capability claim.

• Role preference: contributing partner or work package lead, plus the responsibilities you can realistically accept.

• Capacity: the people available for proposal preparation and delivery, with availability still to confirm clearly marked.

• Open questions: interfaces with other partners, timing, budget responsibilities and information-sharing arrangements.

Give the brief to a colleague who did not help write it. Ask them to describe your proposed contribution in one sentence. If they can only repeat your sector or product category, make the task more specific. Keep confidential technical details out of initial outreach until your team has agreed how they may be shared.

A fictional manufacturer’s decision

Imagine a Canadian manufacturer with a useful testing capability and a small engineering team. It sees a potentially relevant collaborative research topic. Its engineers can propose a bounded test activity, but nobody has yet been assigned to manage a multinational project.

The company prepares a partner brief describing its test capability, proposed output and available staff. It discusses joining an experienced consortium first. If the proposed work expands into a package that it can resource and manage, it can assess package leadership separately.

The lesson is to match responsibility to demonstrated capacity. It is not that SMEs must avoid coordinating projects. This fictional example does not establish that the tests, company, costs or consortium would be eligible.

Find experienced collaborators and prepare the next discussion

ISED’s partner-search guidance points to CORDIS project records, the EU Funding & Tenders partner search and National Contact Points. Use these resources to investigate relevant teams and their previous roles. A past project listing does not mean a team is recruiting for your target call.

Before approaching a potential consortium, agree internally on the contribution, preferred role and unresolved questions. Then ask which tasks remain unassigned, how they connect to the expected outcomes, and what the consortium needs from a new participant. Recheck the current call conditions and timing before committing proposal resources.

Our grant application writing guide explains how to connect a project’s claims with evidence. For broader funding options, consult the Canadian grants and funding directory. Keep the consortium decision tied to the specific research collaboration: a clear contribution and an achievable role are the practical outputs of this preparation.