Writing a joint grant proposal with collaborators

Most research funding is now awarded to teams rather than to individuals. Funders want projects that combine methods, institutions and sometimes countries, and many calls require named co-investigators or partner organisations. That makes the grant proposal itself a collaborative piece of writing, and one with a hard deadline, a strict page limit and real money attached.

Joint proposals tend to go wrong in the same few ways: the idea is not really shared, roles and budgets are argued over at the last minute, and the institutional paperwork is left until the final week. This guide walks through how to plan and write a joint proposal so that it reads as one project, not several stapled together.

1. Start with a shared question, not a shared deadline

A funding call is a good prompt to work together, but it should not be the whole reason. Reviewers can usually tell when partners have been added to meet an eligibility rule. Before you write anything, agree in one or two sentences what the project will find out that none of you could find out alone. If you cannot write that sentence together, the proposal will struggle.

2. Read the call together, line by line

Each funder has its own rules on who can lead, who can be paid, what costs are allowed and how the proposal is scored. Read the call document and the guidance notes as a team and write down:

• Eligibility. Who may act as principal investigator (PI) or co-investigator (co-I), and whether early-career researchers, students or overseas partners can be named.
• Costs. What the funder will pay for (staff time, equipment, travel, open access fees, overheads) and any caps.
• Assessment criteria. How the proposal will be scored, and the weight of each criterion.
• Required documents. Letters of support, CVs in a set format, data management plans, ethics statements and so on.
• Internal deadlines. Your institutions’ research offices usually need the final draft days or weeks before the funder’s deadline.

3. Agree roles early and write them down

Decide who will be the lead applicant and who the co-applicants will be, and what each person will actually do. A simple roles table helps both the team and the reviewers:

• Who leads each work package or objective.
• Who manages the budget and reporting.
• Who supervises any staff or students hired on the grant.
• Who is responsible for data, ethics approvals and outputs.

It is also worth agreeing at this stage how publications from the project will be handled. Our guide on agreeing a co-authorship plan before you start writing works just as well for grant-funded projects.

4. Build the budget from the work plan

Budgets cause more friction than any other part of a joint proposal, usually because they are drafted last and in a hurry. Instead, build the budget from the work plan: list the tasks, estimate the time and resources each one needs, and then cost them. This makes the split between partners follow the work, rather than the other way round, and it gives reviewers a budget that clearly matches the project.

Be open about money within the team. If one partner’s institution charges higher overheads, or one country’s salary costs are lower, discuss it early so nobody feels short-changed later.

5. Plan the writing like a small project

• Make one person the editor. Several people can draft sections, but one person should hold the master copy and make the text read in one voice.
• Work backwards from the internal deadline. Set dates for an outline, a full first draft, an internal review and a final version, leaving time for your research offices.
• Write the summary first and revisit it last. The summary or abstract is often what panels read most closely. Drafting it early keeps everyone aligned, and rewriting it at the end makes sure it matches the final plan.
• Use one shared document. Keep a single file with clear version control rather than emailing attachments back and forth.

6. Show that the team fits together

Reviewers are asked whether the team can deliver the project. Help them by explaining why each partner is needed, what each brings and how you will work together. Mention any past joint work, and describe practical arrangements such as regular meetings, shared data storage and how decisions will be made. If the project spans disciplines, say how you will handle differences in methods and vocabulary.

7. Ask for an honest internal review

Before submission, ask one or two colleagues who are not on the team to read the proposal against the funder’s assessment criteria. Ask them to mark it as a panel member would. It is much better to hear that the objectives are unclear from a colleague than from a rejection letter.

8. Leave time for institutional sign-off

Every partner institution may need to approve the budget, confirm eligibility and sign declarations. Some calls also require a formal agreement or memorandum of understanding between partners, either at submission or once the grant is awarded. These steps take time, especially across countries, so start them well before the deadline.

A quick checklist for joint grant proposals

1. We can state in two sentences why this project needs all of us.
2. We have read the call and noted eligibility, costs, criteria and documents.
3. Roles, work packages and responsibilities are written down.
4. The budget is built from the work plan and agreed by every partner.
5. One editor holds the master copy.
6. Internal deadlines for every institution are in the timeline.
7. An outside colleague has reviewed the draft against the criteria.
8. All letters of support, CVs and plans are ready in the required format.

How CollabCite fits in

Many funding calls ask for partners with skills or access your own team does not have. CollabCite helps verified researchers and students find collaborators by field and research interest, so you can build a team before the next call opens rather than in the week before the deadline. See how it works or join as a founding member.