Sequence template · 4 steps over 20 days

Introducing your organisation to a public institution

For NGOs approaching a municipality, university or public body: a four-step sequence with a formal tone, a clear public benefit and a low-cost first meeting.

Goal. An introductory meeting with the department that owns the topic at a public institution

Step 1Day 0, campaign start

Subject {{org_name}} and {{department}}: a proposal for {{city}}

Hello {{first_name|there}},

{{org_name}} has worked on {{cause_area}} in {{city}} for several years, and much of what we do touches the responsibilities of {{department}} at {{institution}}.

We would like to introduce ourselves properly and explore whether {{programme_name}} could run in cooperation with you rather than alongside you. Public institutions bring reach and legitimacy; we bring people on the ground and a way of working that is already tested.

Could we arrange a short introductory meeting, in person or online, at a time convenient for your team?

Formal register, no first-name familiarity beyond the greeting. Name the department, not just the institution, so the message lands on a desk rather than in a general inbox.

Step 2Day 5

Subject Re: {{org_name}} and {{department}}: a proposal for {{city}}

Hello {{first_name|there}},

To be more specific about the proposal: cooperation with {{department}} would mean a shared plan for {{programme_name}}, clear roles, and reporting that fits your own procedures rather than ours.

It would not mean a request for funding at this stage. We are asking for a conversation and, if it goes well, a letter of intent that lets both sides plan.

If another department at {{institution}} is the right owner of {{cause_area}}, I would be grateful for the name.

Says out loud that this is not a funding request, which is what an institution will assume otherwise. Asks for a redirect if needed.

Step 3Day 12

Subject Documents about {{org_name}} for {{institution}}

Hello {{first_name|there}},

Institutions often ask us for the basics before a meeting, so I am offering them in advance: our registration details, a one-page description of {{programme_name}}, and a summary of results so far in {{city}}. All are available on request.

If it would help to have these forwarded directly to a colleague in {{department}}, tell me who and I will do so.

New subject, practical angle. Offer documents rather than attaching them; public mail systems often strip attachments from unknown senders.

Step 4Day 20

Subject Re: Documents about {{org_name}} for {{institution}}

Hello {{first_name|there}},

This is my final message on the subject for now. If a meeting between {{org_name}} and {{department}} is not possible this term, we understand, and we will remain in touch about {{cause_area}} through public channels.

Should the situation change, one reply is all that is needed and we will arrange the rest.

Thank you for your attention.

Closes formally. Institutions work in terms and budget years, so the close leaves the door open without naming a date.

Use this sequence when the counterpart is a municipality, a university, a school board, a hospital or another public body, and what you want is recognition and cooperation rather than money. The register is more formal than the other templates on purpose. Public servants read email differently from startup founders, and a breezy tone costs credibility.

Who to put in it

Find the department that actually owns the topic, and inside it the head of department or the officer responsible for your cause area. A general contact address is a last resort. Two people per institution is a sensible maximum: the department head and one officer. Their replies and opens combine on one company card, which is the easiest way to see whether the message is moving inside the building; the mechanism is explained in account-based cold email.

Check how each institution wants to be addressed, and whether it publishes rules about contacting officials. Where a public body has a formal channel for proposals, use it and send this sequence only as a heads-up that the proposal is coming.

What to change before sending

The greeting is deliberately neutral. If your first_name data is patchy, change the fallback to the title used locally rather than leaving “there”. Replace “this term” in step four with the planning unit the institution uses (term, budget year, council session). Because public institutions are strict about how personal data is handled, read GDPR and cold email before importing a list of officials, and record where each address came from in a custom field.

How to read the replies and when to stop

Expect slow replies and formal ones. “Please send your proposal to the general office” is not a rejection; do what it says, and stop the sequence for that person with a personal note that you have done so. A meeting invitation from a secretary counts as a yes. An out-of-office is common in public bodies and the classifier will hold the sequence; the autoreply article describes how to resume it after the person returns.

Stop after step four. If there is no response at all, wait until the next planning cycle and try a different department or a different entry point, such as a public consultation the institution is running, and start a fresh sequence with that as the first line. The wider approach for small teams running account-based campaigns is in the account-based outbound playbook.