Skip to content

Joint proposals

Learn it in the academy: Joint proposals (video)

A joint proposal is one proposal for one funding call, written by several organisations: a lead organisation and its partners. Leading one needs Org plan; partners take part on any plan, because the platform gates starting work, never taking part in it.

The lead’s team owns the proposal — the document, the funder’s form, the budget and the final submission. Each partner writes its own parts and hands them over; the lead accepts them or sends them back.

  1. Open New proposal on the Proposals page and choose Write with partners.
  2. Pick the funding call — the list shows calls open now — and name the proposal.
  3. On the new proposal’s Overview, work down Set up the proposal (below).
  4. Invite your partner organisations from Invite partner org in the header.

A proposal you already started on your own becomes joint the same way: open it and choose Invite partners. Its text moves in with it.

A grant writer can also start one for another organisation, which then accepts to lead — see Write for a client.

The lead’s Overview opens with a checklist. Every step is one click — a dialog right there, or a link to the place it is done — and the card disappears once the required steps are done.

Step Required
Add the funding call Yes — every due date counts back from its deadline
The organisation you write for accepts to lead Only on a proposal a grant writer started
Start the proposal document Yes
Set up files Yes — already done when files stay on the platform, the default for a new proposal
Invite partner organisations Optional
Add the funder’s form, if the call has one Optional
Switch on the budget Optional

Afterwards the funder’s form and the budget are switched on and off under More → Settings, and partners are invited from Invite partner org in the header.

Tab What it is
Overview The checklist, Needs attention (everything waiting, with one action each) and Partner organizations — the roster, with each partner’s answers, paperwork and budget as “n of m accepted”. A partner lands on To do instead
Proposal or Concept The proposal document, in the wiki editor. With a funder’s form, the document is the consortium’s concept and the form’s answers are what gets submitted; without one, the document is the proposal
Application form The funder’s questions, once added — a table with a writing drawer per question
Budget Once switched on — a spreadsheet per partner, totals and checks
Deliveries Paperwork each partner owes — CVs, letters, legal details
Sign-offs Compile, sign, submit and record the outcome — see Sign-offs and submission. A proposal with one organisation calls it Submission
More Activity for everyone, Settings for the lead’s team, and Connect Claude

Confidentiality inside the consortium is enforced by the platform, not by convention:

  • A draft answer is visible to its writer and the lead. Once handed over, the whole consortium can read it, so everyone can check the parts fit together.
  • A partner’s own inputs to a joint question are visible to that partner, the question’s writer and the lead — never to the other partners.
  • Paperwork the lead sets to owner and lead (a CV, an ID) is visible to that partner and the lead only; everything else is shared with the consortium.
  • The lead’s private notes on a question are never shown to partners.
  • The budget is open to every member, drafts included; each partner edits only its own lines.

The header’s “% complete” is the same number for everyone, counted over the whole proposal.

A proposal starts at the Concept stage. Partners can sign the concept; the lead then moves on to the Full proposal from Sign-offs. The concept freezes and stays on record with its sign-offs — moving on never waits for them.

Every member can connect Claude to the proposals they work on — More → Connect Claude. The assistant sees the proposal exactly as that member does and can do what they can, nothing more. See the MCP server.

Something wrong on this page? Report it