Governance and stakeholder ownership
Joint-organiser responsibilities for an event
Two organisations put their names on one event, and each assumes the other is handling the awkward parts.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Co-hosting works when you agree in writing, before work starts, which organisation owns each workstream, who holds the money and contracts, whose brand leads, and who decides when you disagree.
Settle those five things first. The rest of the plan can follow.
Split by workstream, not by effort
Divide the event into workstreams such as programme, registration, venue and suppliers, communications and finance. Give each to one organisation as lead, with the other consulted.
Avoid splitting every task fifty-fifty. Shared ownership usually means no ownership.
Five questions to settle in writing
- Money: who collects fees, who pays suppliers, and how a surplus or loss is shared.
- Contracts: which organisation signs with the venue and major suppliers, and who is named on them.
- Brand: whose name leads, how both logos appear, and who approves public wording.
- Attendee data: which organisation holds registration data and how the other may use it. Ask each organisation's data protection contact or adviser to confirm what applies.
- Decisions and disputes: who decides, what the escalation path is, and what happens if the event must be postponed or cancelled.
Questions for legal and finance
Liability, insurance, tax treatment, signing authority and data-sharing terms are matters for your legal, finance and data protection advisers. This page does not give those conclusions.
Take your draft split and these questions to them: who is the contracting party, who bears cost if the event is cancelled, what must be in a written agreement, and how may personal data be shared between the two organisations.
Make it run
- Draft the split as a one-page table and list the five answers beside it.
- Have each organisation's authorised person confirm it.
- Build a joint RACI matrix and decision-rights matrix from it.
- Agree a single contact person for suppliers and for attendees.
- Review it at each milestone and record changes in the decision log.
Worked example · Fictional example
A fictional association and university centre co-host a forum
Fictional organisations and figures. The split shown is an illustration only.
A fictional logistics association and a fictional university research centre host a one-day forum for 200 people. They agreed the association leads venue, suppliers and registration, and the centre leads programme and speakers.
Money flows through the association's account, with a written record of how any surplus is shared, confirmed by both finance contacts. Both logos appear, with the association's first on printed material. Public statements need both communications contacts' approval. Each side asked its own adviser about data-sharing before registration opened.
| Workstream | Lead | Consulted | Notes |
|---|---|---|---|
| Programme and speakers | University centre | Association | Programme sign-off by both |
| Venue and suppliers | Association | University centre | Association signs contracts |
| Registration and data | Association | University centre | Data-sharing terms confirmed by advisers |
| Communications | Association | University centre | Both approve public wording |
| Finance | Association | University centre | Surplus split recorded in writing |
Use this yourself
Joint-organiser responsibility checklist
Fill this with both organisations and keep the signed or confirmed version with the project file.
- Event name, date, both organisations and named representatives:
- Workstreams and which organisation leads each:
- Who collects fees and who pays suppliers:
- How surplus or loss is shared (confirm with finance):
- Which organisation signs venue and supplier contracts:
- Whose brand leads, logo placement and who approves public wording:
- Which organisation holds attendee data and what the other may do with it (confirm with data protection advisers):
- Who decides on programme, budget changes and postponement:
- Escalation route if the two organisations disagree:
- Single contact for suppliers and for attendees:
- Questions passed to legal and finance advisers, and their replies:
- Review dates:
Handle it in-house, or bring in help?
Your team can usually handle this when
- The two organisations have co-hosted before and have a working split.
- One organisation clearly leads and the other contributes content.
- Both finance and legal contacts have confirmed the terms.
Outside planning help earns its fee when
- It is the first joint event and responsibilities are unclear.
- Each organisation has its own approval chain and the two clash.
- Suppliers receive mixed instructions from both sides.
Need one person coordinating both organisations?
A conference project lead can facilitate the split, write it up, build the joint responsibility and decision tables, keep a single supplier channel and run the decision log. Legal, finance and data protection conclusions stay with your own advisers.
Questions organisers ask
Do we need a written agreement?
A written split is strongly advisable. Ask your legal adviser whether a formal agreement is needed and what it should say.
Who should be the single supplier contact?
One named person from the organisation that signs the contracts, with a deputy.
What if the two organisations disagree?
Use the agreed escalation route and record the outcome in the decision log.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.