# Community Partner MOU templates

**URL:** <https://discourse.codeforamerica.org/t/community-partner-mou-templates/50>\
**Category:** Partnerships\
**Tags:** templates, guides\
**Created:** [May 25, 2018, 5:24pm UTC](https://discourse.codeforamerica.org/t/community-partner-mou-templates/50 "2018-05-25T17:24:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![chris](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/chris/32/10_2.png) [@chris](https://discourse.codeforamerica.org/u/chris)\
**Post date:** [May 25, 2018, 5:24pm UTC](https://discourse.codeforamerica.org/t/community-partner-mou-templates/50/1 "2018-05-25T17:24:41Z")

</div>

There was a conversation in Slack a while back where a couple MOU templates were shared that brigades have used with community partners. Let’s dig those up and turn this into a wiki indexing them.

Please reply if you have links to them or any others!

---

<div class="post-metadata">

**Author:** ![jillzey](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/jillzey/32/659_2.png) [@jillzey](https://discourse.codeforamerica.org/u/jillzey)\
**Post date:** [May 26, 2018, 4:21pm UTC](https://discourse.codeforamerica.org/t/community-partner-mou-templates/50/2 "2018-05-26T16:21:01Z")

</div>

To solidify partnerships and set expectations, we use a [Skilled Volunteer Engagement Agreement.](https://docs.google.com/document/d/1_R27KRHgokJG_scCo-U6uu9kISxqLwQIOhKKKUYW8SE/edit?usp=sharing). That link is for the template that we use. We have found it really helpful in the past.

---

<div class="post-metadata">

**Author:** ![chris](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/chris/32/10_2.png) [@chris](https://discourse.codeforamerica.org/u/chris)\
**Post date:** [July 26, 2018, 9:34pm UTC](https://discourse.codeforamerica.org/t/community-partner-mou-templates/50/3 "2018-07-26T21:34:19Z")

</div>

Here’s one that Code for Philly has used: [https://docs.google.com/document/d/1ohzkIKLOb1V8HzeCw-OMl1rLHQg9ll6DADMabTP8-Z0/edit](https://docs.google.com/document/d/1ohzkIKLOb1V8HzeCw-OMl1rLHQg9ll6DADMabTP8-Z0/edit)

---

<div class="post-metadata">

**Author:** ![chris](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/chris/32/10_2.png) [@chris](https://discourse.codeforamerica.org/u/chris)\
**Post date:** [July 26, 2018, 9:34pm UTC](https://discourse.codeforamerica.org/t/community-partner-mou-templates/50/4 "2018-07-26T21:34:56Z")

</div>

And here’s one from Open Austin shared by @mateo: [https://docs.google.com/document/d/1O5iZXLmwGhBp566FSPUijVet7kvXuWKfL1cf7pylKkg/edit?usp=sharing](https://docs.google.com/document/d/1O5iZXLmwGhBp566FSPUijVet7kvXuWKfL1cf7pylKkg/edit?usp=sharing)

---

<div class="post-metadata">

**Author:** ![Micah](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/micah/32/812_2.png) [@Micah](https://discourse.codeforamerica.org/u/Micah)\
**Post date:** [January 19, 2021, 5:08pm UTC](https://discourse.codeforamerica.org/t/community-partner-mou-templates/50/5 "2021-01-19T17:08:47Z")

</div>

Here’s our “[Partner Packet](https://drive.google.com/drive/folders/1Xyp_85NOPMdUKOO52Mbikz5p5KjzjvCC?usp=sharing)”: 4 documents (and an overview) that can be used when setting expectations and roadmaps for selecting, initiating, developing and closing projects. This information is destined to always be a work in progress (even on a quick skim now I see things I want to change ), but it is a helpful starting point. There are a few things this info attempts to do:

[Project Selection Guidelines](https://docs.google.com/document/d/1-m-G6XrrhspheVBKIeMxj_DiOJSk86c_zCzkJSUcGXA/edit)

- helps people quickly understand which types of projects are best suited for work in our brigade
- good talking-piece to help orgs & members consider project scope before committing to the work

[Operating Principles](https://docs.google.com/document/d/1jpJMCuBvIi_m51_xLeDk6rq0U3inS22JzpLJhUaeN_o/edit)

- Important for helping partners see the project as a whole, including their role & the responsibility of ultimately owning the project
- Great checklist for brigade/proj leaders to make sure we cover the things that are easy to forget

[Project Proposal](https://docs.google.com/document/d/1a0PUUlPTHNRhUIIpXph7p25Mt_-wqErYvDu7eS3gBmQ/edit?usp=sharing)

- Intended as a discussion piece to focus attention on proj aspects that are often skipped or punted
- _ **Not a substitute** _ for a thoughtful conversation

[Post-Project Follow-Up](https://docs.google.com/document/d/1pZE3W5vpc-i_WeVWkcHxpjQZa6fjmDoJhCYQ_TEsvB0/edit?usp=sharing)

- Checklist for crossing T’s and dotting I’s when wrapping up a project
- Important expectation setting for project leads to clarify that “deploy to prod” **≠** “done”, but also that projects should (ideally) be finite.

---

<div class="post-metadata">

**Author:** ![Mari](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/mari/32/992_2.png) [@Mari](https://discourse.codeforamerica.org/u/Mari)\
**Post date:** [July 1, 2023, 6:53am UTC](https://discourse.codeforamerica.org/t/community-partner-mou-templates/50/6 "2023-07-01T06:53:57Z")

</div>