M-T1-CP-21-SD-02 — Partnership Invitation Template

Release control

Adaptation note

For leaders from organisations, businesses and community groups, using breakfast for relationship-building. Frame the ask as participation in a conversation, not an assumed partnership. State exact breakfast timing, cost, dietary/access route, discussion purpose, attendee expectations and how potential ideas will be taken forward. The primary action is to RSVP and identify the most relevant representative. Follow with confirmation, dietary/access checking, thanks and a separately agreed partnership conversation.

Instructions

1. Use only as the Multi-Party Partnership Discovery Breakfast overlay under M-T1-CP-09; keep the CP-21 asset code.
2. Address one organisation and one appropriate role per invitation. Explain why that organisation’s perspective is relevant without implying endorsement or a prior partnership.
3. Describe the breakfast as a structured discovery conversation. Do not promise projects, funding, referrals, exclusivity or a partnership outcome.
4. Collect only the representative, response and dietary/access information needed for this event; keep future-contact permission separate.
5. A promising idea moves to a separately scoped and authorised follow-up, not an informal commitment made at breakfast.
6. Resolve every field and complete initiative, privacy, access, dietary, budget and communications review before sending.

Controlled fields

Configured partnership invitation

Subject: Invitation to a partnership discovery breakfast: {{PUBLIC_EVENT_NAME}}

Hello {{FIRST_NAME}},

{{HOST_ENTITY}} invites {{ORGANISATION_NAME}} to join {{PUBLIC_EVENT_NAME}} on {{EVENT_DATE_LONG}}.

{{DISCUSSION_PURPOSE}} We are approaching your organisation because {{INVITATION_REASON}}. {{VALUE_PROMISE}}

This is an invitation to a conversation, not an assumption that your organisation will enter a partnership or support a particular proposal.

What participation involves

• Breakfast time: {{START_TIME}}–{{END_TIME}} {{TIME_ZONE}}
• Arrival: {{ARRIVAL_TIME}}
• Venue: {{VENUE_NAME}}, {{VENUE_ADDRESS}}
• Cost and inclusions: {{COST_TEXT}}
• Who should attend and what to prepare: {{ATTENDEE_EXPECTATIONS}}
• Dietary information: {{DIETARY_ROUTE}}
• Access arrangements: {{ACCESSIBILITY_SUMMARY}}
• How possible ideas will be taken forward: {{IDEA_FOLLOW_UP_PROCESS}}

Please RSVP by {{RSVP_DEADLINE}} at {{RSVP_URL}} and identify the representative best placed to join the discussion. Questions or access requests can go to {{PRIMARY_CONTACT_NAME}} at {{PRIMARY_CONTACT_EMAIL}} / {{PRIMARY_CONTACT_PHONE}} or {{ACCESSIBILITY_CONTACT}}.

Attendance does not create a partnership, endorsement, funding commitment or exclusivity arrangement. Any potential next step will be discussed and authorised separately.

Thank you for considering the invitation. We value a clear answer either way.

Warm regards, {{PRIMARY_CONTACT_NAME}} {{HOST_ENTITY}}

Privacy: Response, dietary and access information will be handled as described at {{PRIVACY_NOTICE_URL}}. Communication preferences: {{PREFERENCE_ROUTE}}

Breakfast and follow-up checklist

• [ ] CP-21 is presented as the breakfast overlay under CP-09, not as a separate canonical initiative.
• [ ] Organisation relevance and the appropriate representative role are documented.
• [ ] Discussion purpose, participant expectations and idea-assessment route are approved.
• [ ] Copy makes no partnership, funding, endorsement, referral or exclusivity promise.
• [ ] Timing, venue, cost, catering, dietary deadline and access provisions are final.
• [ ] Dietary/access data is minimised, access-restricted and covered by the approved privacy route.
• [ ] RSVP, representative identification, privacy, preference and correction routes pass testing.
• [ ] Confirmation and final practical reminder are ready before invitations are issued.
• [ ] Thanks and any partnership conversation are separate, owned follow-ups based on an explicit agreement.
• [ ] Declines and no-further-contact requests are recorded and suppressed.
• [ ] The final invitation contains no unresolved double-brace fields.

Review record