Reviewers of joint proposals have learned to spot a particular pattern: one partner wrote it and the other approved it.
It shows in the structure — one side's work described in intellectual terms, the other's in logistical ones — and it is increasingly treated as a weakness rather than a formality.
What reveals a one-sided proposal
- One partner's role described only as data collection or site access.
- The research questions all arising from one side's prior work.
- A budget where one side has no discretionary lines.
- No outputs led by the other partner.
- Local context appearing as background rather than as expertise.
Writing it jointly in practice
- Develop the research question together in a call, before any drafting.
- Each side drafts the sections closest to its expertise.
- Agree the division of intellectual leadership, not only of tasks.
- Both sides review the whole document, not only their own parts.
- Start six months before the deadline, not six weeks.
Making the case for the partnership
- State explicitly why this question requires both parties.
- Show prior joint work, even something small.
- Name what each side contributes intellectually.
- Describe the plan for continuing beyond this project.
Budget as evidence
- Reviewers read budgets for signals about the real relationship.
- Local staff time funded properly signals a genuine partnership.
- Discretionary budget on both sides signals shared control.
- A budget where one side receives only per-sample payments signals a service contract.
Practical process
- Use one shared document with clear ownership of sections.
- Set internal deadlines well ahead of institutional ones.
- Allow for two sets of institutional approvals with different timelines.
- Circulate the final version to everyone before submission.
One thing worth remembering
Reviewers read the budget for what the narrative will not say.
A proposal can describe an equal partnership in every paragraph, and a budget in which one side has no discretionary spending and no funded staff time will say the opposite — clearly, and to the only readers who matter.
Câu hỏi thường gặp
What reveals a one-sided proposal?
One partner's role described only as data collection or site access, research questions all from one side's prior work, no discretionary budget lines for one side, no outputs they lead, and local context as background rather than expertise.
How do you write jointly in practice?
Develop the research question together before drafting, have each side draft sections closest to its expertise, agree intellectual leadership not only tasks, both review the whole document, and start six months early.
How do you make the case for the partnership?
State explicitly why the question requires both parties, show prior joint work even something small, name what each contributes intellectually, and describe the plan beyond this project.
Why do reviewers read the budget?
Because it signals the real relationship — properly funded local staff time and discretionary budget on both sides signal genuine partnership, while per-sample payments signal a service contract.
What process works?
One shared document with clear section ownership, internal deadlines well ahead of institutional ones, allowance for two sets of approvals, and circulating the final version before submission.
