Should I say that I need a partner for eligibility reasons?

Yes. Partners know how collaborative programmes work, and a country or organisation-type requirement is a normal reason to be approached. What damages the relationship is a manufactured scientific rationale that collapses on the first call. The important thing to add is that the role is a genuine work package with its own deliverables, since the fear on the other side is being a passenger on someone else's proposal.

When should I contact potential partners for a grant call?

As early as the call, and ideally before it, since draft work programmes circulate months ahead in some systems. The hard constraint is not the funder's deadline but each partner institution's internal one for approving a budget and signing a partner declaration, which commonly falls one to three weeks earlier and differs per institution. Ask for that date in the first exchange.

How many times should I follow up?

Once, in the same thread, adding one new fact and making a no easy to send. Time it to the deadline rather than to a fixed interval: with six weeks left, a week is reasonable; with ten days left, two or three days and an explicit explanation of why. After one unanswered follow-up, move to the next candidate. A third message is remembered long after the call closes.

Should I attach the full proposal to a first email?

No. Send a two-page concept note, or offer it and send it when asked. A full draft proposal is unreadable to someone deciding whether to spend half an hour on a call, it makes the request feel like hours of homework, and it exposes an unfinished document to someone who has not yet agreed to anything.

Does the research partner finder write these emails or contact partners?

No. It reads the project description you upload and suggests researchers whose published work sits close to it, each with a short reason. It shows no contact details, drafts no messages and never writes to anyone, and it knows nothing about call eligibility, country rules or a group's capacity. Everything after the shortlist is yours, which is what these templates are for.

Research Consortium Outreach Emails

Three variants for the message that decides whether a stranger joins your proposal, each annotated, plus the timing rules that matter more than the wording.

A consortium invitation is a business proposition sent under a deadline to someone who has never heard of you. It has to say what the call is, what you want them to own, what it is worth, and when they have to decide, and it has to do that without reading as a mass mailing. The three variants below cover a partner you chose after reading their work, a partner who fills a competence the call explicitly requires, and the follow-up. The reasoning behind consortium composition is in how to build a research consortium, and reading the call that dictates all of this is in how to read a grant call.

Variant 1: a partner you chose after reading their work

The strongest opening position, because the reason you are writing is scientific rather than administrative. The message has to prove the choice was deliberate, then move immediately to the concrete: role, effort, budget share, deadline.

Targeted partner, chosen on the science

Subject: [Funder] [call identifier], partner role in [topic], deadline [date]

Dear Prof. [Surname],

I am [name], [role] at [institution]. We are preparing a proposal for [call name and identifier], which closes on [date], and I would like to ask whether your group would join as a partner.

I am writing to you rather than to someone else because of your [year] paper on [specific topic]. The [specific method, cohort, instrument or result] is exactly what our work package on [topic] needs, and we have no equivalent capability in the consortium as it stands.

The project in three lines: [objective]. [Approach]. [Expected outcome].

What we would be asking of you: lead of work package [n], [short description of the tasks], roughly [n] person-months over [n] years, with an indicative budget of [amount] to your institution at the [rate] funding rate for your organisation type.

Where we are: [n] partners confirmed in [countries], including [named partner if it helps], with [coordinator] coordinating. The work plan is drafted but work package [n] is deliberately open, so its objectives and deliverables would be shaped with you.

If this is of interest, could we speak for 30 minutes this week or next? I can send the two-page concept note and the draft work plan straight away, and your research office would need to see the partner declaration by [your internal date] rather than by the funder's deadline.

With best wishes,
[Full name]
[Role, institution] | [ORCID or group page]

Put the call and the deadline in the subject line. A partner who receives three of these a season sorts them by date, and hiding the deadline until paragraph four is the fastest way to lose someone's goodwill.; Name the specific paper and the specific element you need. This is the sentence that separates a chosen partner from a mail merge, and it cannot be written without having read the work.
Quantify the ask in the units a research office uses: work package, person-months, indicative budget, funding rate. A vague invitation to join a proposal cannot be evaluated and is declined by default.; Say what is already in place and what is still open. Being able to shape a work package is often the deciding factor, and a proposal presented as complete is a request for a signature rather than a partnership.; Give their internal deadline, not only the funder's. Institutional sign-off and a signed partner declaration commonly close one to three weeks earlier, and every institution's date is different.; Ask for 30 minutes, not for a commitment. The call is where the role gets negotiated, and a decision requested by email is usually a decision declined.

Variant 2: a competence or a country the call demands

Here the reason is structural: the call requires something your consortium does not have. Say so plainly. Partners know how collaborative programmes work, and an honest eligibility motive is more credible than a manufactured scientific admiration.

Filling a required competence

Subject: [Call identifier] partner needed in [competence or country], deadline [date]

Dear Dr [Surname],

I am [name] at [institution], coordinating a proposal for [call name], deadline [date].

I will be direct about why I am writing. The call requires [the explicit requirement: a partner established in [country], an organisation of type [x], a clinical site, an industrial participant, expertise in [competence]], and our consortium does not cover it. Your group came up as the strongest fit on [the basis: your work on [topic], your [facility or cohort], your role in [previous project]].

This is a real work package, not a name on a list. It would cover [tasks], produce [deliverables], and carry roughly [n] person-months and an indicative budget of [amount]. Nobody else in the consortium can do this part, which is why we need a partner rather than a subcontractor.

The consortium today: [coordinator] plus [n] partners in [countries]. The proposal is at [stage]. Attached to a call with a [date] deadline, the honest timeline is that we would need an answer in principle by [date] and the signed partner declaration by [date].

If it is not for you, I would be grateful for a name. A pointer to the right group is worth as much to me as a yes.

Would you have 20 minutes this week?

With thanks,
[Full name]
[Role, institution]

State the structural reason openly. Pretending that eligibility-driven recruitment is admiration is transparent, and being found out at the first call costs more than the honest sentence would have.; Insist that the role is a real work package with its own deliverables. The fear a partner has in this situation is being a passenger on someone else's proposal, and reviewers criticise exactly that.; Explain why a partner rather than a subcontractor. Most programmes restrict subcontracting of core tasks, and saying so shows you understand the rules they are being asked to sign up to.
Give both dates: the answer in principle, and the signature. The first is a personal decision and the second is an institutional process, and conflating them is how proposals lose partners in the last week.; Ask for a referral if the answer is no. It costs them nothing, it is the most common way a good partner is actually found, and it turns a dead end into a shortlist.; Do not send this to several groups in the same department at once, and never put multiple recipients on one message. Partners talk to each other, and a visible group mailing ends every conversation on it.

Variant 3: the follow-up

Silence usually means the message arrived in a bad week, not that the answer is no. One follow-up is normal and expected under deadline pressure. A second is the point at which you are damaging a relationship you have not yet established.

One follow-up, then stop

Subject: Re: [Call identifier] partner role in [topic], deadline [date]

Dear Prof. [Surname],

Following up briefly on the message below about [call name], which closes on [date].

Two things have moved since I wrote: [the new fact, for example a partner confirmed, the concept note finished, a letter of support secured, the work package objectives drafted]. I have attached the two-page concept note so you can judge the fit without a call.

If the timing does not work, a no is genuinely useful to me this week, and it costs you nothing to send. If someone else in your group would be the better fit, I would be glad of the name.

If it is still of interest, I have kept work package [n] open until [date].

With thanks,
[Full name]

Follow up once, in the same thread, so the original message is visible underneath and the reader does not have to search for context.

Add one new fact. A follow-up that only repeats the first message is a request for attention; one that reports progress is information.

Make the no easy and say it is useful. Under a deadline, an early no is worth almost as much as a yes, because it lets you approach the next candidate while there is still time.

Offer an alternative contact inside their group. Senior researchers frequently delegate this, and naming the possibility gives them a low-cost way to keep the door open.

Time it to the deadline, not to a fixed interval. With six weeks left, a week is reasonable. With ten days left, follow up after two or three days and say plainly why.

After the single follow-up, stop and move to the next candidate. Silence twice is an answer, and a third message is remembered long after the call has closed.

What to leave out, and what to have ready before you send

The failure modes are the same across all three variants, and most of them are about sending too early with too little or too late with too much. Two hours of preparation makes every message shorter.

Leave out your biography and your institution's history. Two lines of context is the maximum before the reader needs to know what you want from them.
Leave out promises you do not control: a budget share your coordinator has not agreed, a work package leadership already offered to someone else, a partner who has not actually confirmed. Every one of those is found out at the first call.; Leave out the full proposal as an attachment. A two-page concept note is the artefact that gets read, and offering it gives you a natural reason to write again.; Have the concept note, the draft work package description and the indicative budget ready before the first email, because the answer to a good message is send me the details today.; Copy your research office and ask for theirs early. The partner declaration, the legal entity details and the registration identifier are administrative work that neither researcher should be doing in the final week.; Write to more candidates than you need for each open role, individually, and keep a written record of who was asked, when, and what they said. Under deadline pressure that list is the only thing that stops two people being offered the same work package.

Frequently asked questions

Four elements, in this order: the call and its deadline in the subject line, one specific sentence showing why you chose them, the role quantified as a work package with effort and indicative budget, and a small ask, normally a 20 to 30 minute call. Say what is already in place and what is still open, give their institution's internal deadline as well as the funder's, and offer a two-page concept note rather than attaching the whole draft.