What makes consortium projects hard?
A consortium puts several organizations under one grant. Each has its own systems, culture, staff and rules. They share a goal but not a boss. Without clear agreements, small differences grow: reports arrive late and in different formats, money moves slowly, and each partner has a different idea of what “done” means.
The fix is not more meetings. It is clearer agreements, set early.
A consortium also brings real benefits: wider reach, local knowledge, shared skills and a stronger case to the donor. These benefits come only when partners trust each other. Trust grows from clear agreements, honest talk about problems and fair treatment of smaller organizations, which often carry the most delivery risk with the least power.
What should you agree before work starts?
Put these in writing, in the partnership agreement or a short governance note.
- Roles. Who leads, who delivers what, who reports to the donor.
- Decisions. Which decisions the lead takes, which need all partners, and how long a decision may take.
- Money. How funds pass to partners, on what schedule, against what evidence.
- Reporting. What each partner reports, how often and in which format.
- Standards. Which policies apply, such as safeguarding and procurement, and who checks them.
- Change and disputes. How budget or plan changes are proposed, and what happens if partners disagree.
Check the donor agreement for rules on partners and sub-awards. Rules differ by donor and country.
How do you keep one picture of results?
If each partner measures differently, the totals mean little. Use a single results framework with the same indicators for everyone, and write a short definition for each one. Our article on the indicator reference sheet shows how.
Then agree a single reporting calendar. A common pattern is that partners send their data to the lead a fixed number of days before the donor deadline, so the lead has time to check and combine it.
Keep in mind that adding up partner counts can double count people who were reached by more than one partner. Say how you handle this in your report.
Hold a short onboarding session for partner staff on the template and the definitions. Use real examples: “Here is a training. Here is how we count it. Here is a count we would not accept.” Offer a named person at the lead organization who can answer questions in the first quarter.
Check the first report from each partner more closely than later ones. Early feedback fixes habits before they spread. Share common errors, without naming the partner, with the whole group.
How should money move?
Delays in passing funds are a top cause of partner frustration. Agree a clear process:
- A schedule of payments, tied to the work plan, not to ad hoc requests.
- What the partner must send to receive the next payment, such as a short financial report.
- Who checks it, and how fast.
- What happens to unspent funds at the end.
Our article on managing sub-grants covers this in more detail.
How do you keep partners aligned over time?
Use a simple rhythm. A monthly partner call of an hour, with a fixed agenda: progress, problems, decisions needed, and upcoming deadlines. Share minutes within two days, with each action owned and dated.
Add a short review at the mid-point and the end: what is working in the partnership, what is not, and what to change. Treat feedback from small partners with care, since they may be reluctant to criticize the lead.
Rotate the chair or the host of the call from time to time where partners are equals, so one voice does not dominate. Keep a shared decision log where each decision, its date and its owner are recorded; it avoids later arguments about what was agreed. Our article on the governance decision log explains why this simple record helps.
Be honest about workload. Smaller partners often have thin finance and MEAL teams, and a heavy reporting load can slow their delivery. Ask each partner what support they need, such as a template, a short training or a named contact, and where possible offer it early. Fair treatment of partners is also a protection for the lead, since a partner that feels supported reports more completely and earlier. Review the support plan at the mid-point review.
Where EMPOBase fits
In EMPOBase, Sub-Grants track funds passed to partners, and Donors and Programs keep the grant and project records the consortium works from. External Access can give a donor or auditor scoped, read-only, logged access to what you choose to share. EMPOBase does not make bank transfers, so the payment to a partner stays with your bank process. Check what each person can see by role before you invite anyone. See the platform overview for the modules involved.