---
# System prepended metadata

title: MIP41c4 (Facilitator Onboarding) Template
tags: [Amendments]

---

---
title: MIP41c4 (Facilitator Onboarding) Template
tags: Amendments
url: https://github.com/makerdao/mips/blob/Core-Unit-Offboarding-Process-Amendment/MIP41/MIP41c4-Subproposal-Template.md
---

# MIP41c4: Facilitator Onboarding (Subproposal Process) Template

## Preamble

```
MIP41c4-SP#: #
Author(s):
Contributors:
Tags: template
Status:
Date Applied: <yyyy-mm-dd>
Date Ratified: <yyyy-mm-dd>
```

## Sentence Summary

## Paragraph Summary

## Specification

### Motivation

- Why are you applying to become a Facilitator?

### Core Unit ID

- Specify the Core Unit ID.
- This element specifies which Core Unit you are proposing to onboard to as a Facilitator.

### Facilitator name and information

- This element must contain the Forum name of the Facilitator, as well as other names and IDs in Maker related communication channels. Additionally it must contain the Facilitators Ethereum address used for Budget Implementation control and other authorizations.

### Facilitator Commitment

- The Facilitator Commitment is a detailed description and plan of what the Facilitator plans to do in order to achieve success for the Core Unit. There is a lot of flexibility in what a Facilitator can write in their commitment, including organizational structure and theory, plans for the budget, hiring and infrastructure plans, etc.
- The Facilitator commitment should also contain targets and goals that can be observed by Governance, if appropriate. This helps Governance to see whether the Facilitator is living up to their expectations.
- A crucial part of the Facilitator Commitment are clear commitments to transparency. The Facilitator should commit to an effective plan that will allow Governance and other stakeholders, such as contributors contemplating doing work, to gain direct insight into what is being worked on and who are taking care of what responsibilities.

