MSCA COFUND 2027 (HORIZON-MSCA-2027-COFUND-01): Co-funding of regional, national, and international doctoral and postdoctoral programmes

MSCA COFUND 2027 (HORIZON-MSCA-2027-COFUND-01): Co-funding of regional, national, and international doctoral and postdoctoral programmes

MSCA COFUND 2027 (reference HORIZON-MSCA-2027-COFUND-01) is a Horizon Europe action that supports organisations that recruit and develop doctoral and postdoctoral researchers through co-funded fellowship programmes. The official MSCA site presents the call as a forthcoming opportunity with a launch date of 8 December 2026 and a submission deadline of 6 April 2027. This is not a one-person fellowships-only announcement. It is a programme-level route: institutions design and manage programmes that can then deliver structured research careers, with co-funding from the EU and complementary support from national or regional structures.

For teams targeting 2026/2027 funding cycles, this call is strategically important for three reasons. First, COFUND is one of the few mainstream European instruments that directly improves institutional hiring capacity by subsidising programmes rather than only individual research proposals. Second, the programme can serve as a bridge between institutional funding logic and long-term researcher development. Third, because the announced opening and deadline are explicitly in the 2026–2027 window, it is one of the few high-impact EU routes for institutions to plan in advance while still staying within the current Horizon Europe period.

Key details at a glance

The key dates above are taken from the official MSCA call page and include several “TBC” markers in the call notice. That matters for planning: deadlines are stable publication points for preparation, but teams should still monitor updates up to the moment submission is opened and before the system deadline lock.

What this opportunity is and why it is different from ordinary grants

If you have applied to research calls before, one easy mistake is to map everything into the same mental model. COFUND calls differ in three practical ways.

First, the action is structured around programmes. The official MSCA page describes this area as support for co-funding regional, national, and international programmes and explicitly frames COFUND as support for institutions and systems. That is very different from single grant submissions where the proposal is just one project idea.

Second, the programme type supports talent development architecture. In COFUND, proposal quality is not only about scientific output; it is also about demonstrating programme quality, supervision quality, fairness, continuity, and institutional readiness. The same text that describes MSCA actions repeatedly emphasizes spread of best practices, international mobility, and cross-sectoral mobility of researchers.

Third, implementation is split across sources. The official wording says the MSCA contribution is provided as a COFUND allowance per researcher-month and explicitly welcomes funding synergies with other funding frameworks such as Cohesion-related channels. In practical terms, this means your financial model has to be coherent in how EU support interacts with beneficiary financing.

A practical consequence: if your internal planning only imagines the EU as “top-up money,” you may submit a technically plausible proposal with a weak continuity model. This is the most expensive proposal mistake in these calls. You are expected to document not just “we can do this project,” but also “we can run this model in a stable and compliant way after EU support is layered in.”

Who should consider applying and when it may not be a good fit

This is an attractive option for institutions that already run or want to create serious training and talent pipelines. Strong candidates are often:

• Public or private research organisations with established HR and support systems;
• Universities that can demonstrate long-term commitment to hiring postdocs and supervising career-ready pathways;
• National or regional programme hosts that already coordinate multi-stakeholder partnerships;
• Regions or institutions that can use international, inter-sectoral, or interdisciplinary recruitment patterns to improve research talent outcomes.

This opportunity is likely less suitable if the applicant is not ready to act as a programme-level implementer. COFUND is not a one-off award where a principal investigator uploads a proposal and waits. The burden of preparation is much broader: governance, compliance, finance, and continuation logic all become part of the assessment context.

There is also a timing consideration. If your institution is in exploratory mode and does not yet have an HR framework for programme-level fellowships, the 2026/2027 cycle may still be useful as a pre-application exercise, but you should avoid early submission until internal readiness is complete.

Good fit signals (quick practical indicators)

A good fit usually shows these signs before writing starts:

• Clear ownership: a specific office, directorate, or team can own the programme.
• Realistic host pipeline: you can describe how candidates are recruited, onboarded, and supported.
• Finance governance: you can already show how EU and non-EU parts will be combined without exposing gaps.
• Compliance readiness: legal and administrative teams can act on call-specific country and participation conditions quickly.

Warning signs (pause before writing)

• No clear programme owner;
• No process for recruitment and monitoring;
• No clarity on whether the beneficiary can sustain positions beyond immediate EU support;
• No designated person for portal submission and document control.

Eligibility, scope, and where uncertainty should be treated as a design risk

COFUND eligibility has two layers. The first layer is what is visible in call summaries: it is a COFUND action for doctoral and postdoctoral fellowship programmes, and the beneficiary-side model matters. The second layer is call-specific legal text that lives in the Funding & Tenders Portal and Work Programme annexes.

The official MSCA and REA pages are consistent on this pattern:

• COFUND is a co-funding mechanism for organisational programme models, not a generic cash prize.
• Full eligibility and participation conditions are in the formal call documents.
• Submission and review systems are via the EU portal.

As a result, the safest way to avoid false assumptions is to build your internal checklist around three buckets:

1. Eligibility bucket: beneficiary type, country/participation context, and required registration/access steps.
2. Programme design bucket: doctoral/postdoctoral architecture, recruitment rules, international collaboration design, and training value.
3. Implementation bucket: reporting, governance, continuity commitments, and cost model across EU and non-EU funding.

If any bucket is empty at the concept stage, your team should treat that as a pre-submission blocker. It is better to delay drafting the narrative and complete administration early than submitting under assumptions.

Financial architecture: why the budget narrative must go beyond the headline figure

This call announces EUR 51.25 million as indicative total budget. That does not mean every applicant receives a fixed amount. For COFUND the relevant logic is programme-level co-funding.

In practice, your budget should demonstrate:

• EU-fundable cost components aligned with call mechanics;
• Non-EU co-funding or beneficiary-side costs where required;
• Compliance with any ceiling/structure in the portal texts;
• Clear timing of expenditure and hiring stages.

The MSCA pages also emphasise timeline and process for EU-funded projects and signature windows. Use this to avoid planning illusions. A submission can appear strong but fail on credibility if the continuation phase is not modelled with concrete funding assumptions and governance commitments.

The call summary includes “TBC” for key milestones after submission. That status is important. If your budget has no contingency for potential timing shifts, it can collapse under implementation pressure. Strong teams build a realistic spread:

• Core costs for the EU-supported period;
• Beneficiary funding bridge and obligations;
• Shared cost assumptions for recruitment and training infrastructure;
• Buffer assumptions for review rounds and start-up activities.

Application process: practical workflow from announcement to submission

The MSCA site and REA guidance pages use a similar workflow sequence for this family of calls:

1. Monitor official MSCA call page for opening and deadline windows.
2. Access the EU Funding & Tenders Portal and ensure the organisation profile is in place.
3. Track call-specific eligibility and required documentation.
4. Prepare an institutional governance package (ownership, legal role, budget framework).
5. Draft and submit using the portal proposal workflow by the deadline.

For 2027 planning, a useful internal milestone plan is:

• By mid-October 2026: finalize internal decision whether to bid and appoint core team.
• Late November 2026: complete legal/technical checklist against call expectations and assign portal responsibilities.
• Early December 2026: complete first full outline draft (program design + budget logic + partner map).
• First half of January 2027: conduct internal technical and compliance review.
• By end of February 2027: finalize narrative and all attachments.
• March 2027: run submission dry run and verify portal metadata.
• By 6 April 2027: submit and capture submission confirmation.

This timing is deliberately conservative. Even if not mandated by the call, it is the difference between a rushed submission and a reviewed submission.

The REA guidance reiterates that MSCA proposals are submitted through the portal and that calls have dedicated guidance materials. Even if the exact 2027 COFUND-specific documents are not fully visible at first glance, the process model remains the same: know your call, prepare early, submit in portal, then track review communication.

How to build a competitive proposal in this action

A competitive COFUND 2027 concept usually does better when it looks like a real programme, not a stitched report.

1) Start from institutional rationale, not only from researcher-level ambitions

Explain why your programme exists and what policy or training gap it addresses. The official framing repeatedly links MSCA to best practices and mobility-based researcher development. A COFUND application should show this clearly: “what problem this programme solves that ordinary funding does not.”

2) Design recruitment and support architecture first

Because the action supports fellowship programmes, define:

• how candidates are identified;
• how host environments are structured;
• what supervision and mentorship model applies;
• how mobility or career transfer is built into the programme.

The reviewer reads this as practical feasibility, not rhetorical intent.

3) Make continuity explicit

COFUND is not only an award. It is a structure. Your strongest applications explicitly map out continuity of support and programme sustainability after award windows. Even when exact continuation mechanics vary by applicant, the narrative should still explain what remains after EU-funded stages and how your beneficiary-level resources will support that stage.

4) Be explicit on governance and transparency

The call is not just evaluation by scientific merit, but by implementation credibility as well. Add practical, reviewable governance elements:

• clear decision ownership;
• recruitment governance;
• data and reporting cadence;
• conflict-of-interest and fairness checks.

5) Use official process channels as your backbone

Given the “TBC” nature of post-deadline milestones, build your proposal so every major claim can be checked against official wording in the call and portal pages. If your proposal references a term that appears only in one guide page, cite where the team gets that interpretation from.

Required documentation set (minimum practical pack)

A useful preparation pack for this type of submission should include at least the following:

• Administrative pack: legal identity details, internal authority approvals, roles, and signatures.
• Eligibility and participation pack: documents tied to eligibility checks and beneficiary-level conditions.
• Programme design pack: description of doctoral and postdoctoral structure, recruitment tracks, training components, expected outputs.
• Budget pack: line-items reflecting co-funded and beneficiary-supported portions.
• Compliance and sustainability pack: governance architecture, reporting logic, and continuity arrangements.
• Portal pack: submission-ready documents in the correct template and format, ready for upload.

Without a clean submission pack, teams often lose time during final validation and then submit with unresolved compliance defects.

Common mistakes that repeatedly reduce scoring and acceptance chances

Treating COFUND like a classic individual grant

The first and most frequent issue is writing the proposal as if it were an individual project. This is a programme framework action; your narrative must map institutional capability.

Ignoring the non-EU portion of funding logic

COFUND co-funding means the budget must show both the EU-related and beneficiary-related picture. If costs are framed only around a single EU-funded tranche, reviewers question implementation resilience.

Underestimating continuation requirements

Even when the call summary shows launch and deadline only, later milestones are visible as post-deadline checkpoints. If continuation is left vague, the submission looks reactive.

Missing portal readiness

Several organisations only discover the submission issue late: user permissions, missing fields, malformed attachments, wrong template versions, or missing signatures. Start portal checks early.

Using broad claims without concrete programme evidence

High-level language about mobility and impact is common. The higher-performing submissions link those claims to programme mechanics: hiring process, training modules, support systems, and reporting flow.

Not treating official links as mandatory

This action points to MSCA pages, REA pages, and the Funding & Tenders Portal. If teams use secondary summaries only and never confirm call-level requirements, they submit against the wrong rule version.

Frequently asked questions

Is this a fellowship award for a single researcher?

No. COFUND is a programme-level action for organisational support of doctoral and postdoctoral fellowship schemes, though your recruited researchers benefit from that structure.

Is this opportunity likely to remain open beyond April 2026–2027?

The public call notice already indicates an opening date and a 2027 deadline with timeline markers. Always monitor official pages for updates, because some items are marked “TBC” and are not always final at initial publication.

Who should lead the application internally?

A central office should lead eligibility and portal submission. A dedicated research lead should manage scientific framing. Finance and HR leads should co-own budget and continuity sections. Fragmented ownership is a frequent source of late mistakes.

Is funding only for EU Member States?

The public summaries and MSCA context place this action in the EU/Horizon Europe context and the official site also links to associated-country participation logic. The exact country and participation conditions are call-specific and published through call and work programme documents.

Official links and recommended next actions for teams preparing now

• Official call page (public summary): https://marie-sklodowska-curie-actions.ec.europa.eu/calls/msca-cofund-2027 (redirects to the funding page)
• Official funding page snapshot: https://marie-sklodowska-curie-actions.ec.europa.eu/funding/msca-cofund-2027
• REA overview for COFUND context and additional portal entry points: https://rea.ec.europa.eu/funding-and-grants/horizon-europe-marie-sklodowska-curie-actions/msca-co-funding-regional-national-and-international-programmes-cofund_en
• REA MSCA application workflow guidance: https://rea.ec.europa.eu/funding-and-grants/horizon-europe-marie-sklodowska-curie-actions/horizon-europe-msca-how-apply_en
• EU application infrastructure: https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/home

Suggested 90-day preparation plan from 2026-05-31

If your team is in an initial planning stage today, use the next 90 days to close structural gaps before the official window is live. Start with beneficiary eligibility confirmation, then map programme scope, then build a draft continuity budget. COFUND is one of the few calls where teams often fail not on idea quality but on process quality. The difference between a weak and strong submission is usually not “more science,” but cleaner implementation architecture and explicit, evidence-backed eligibility planning.