# data[].attributes.body
In addition to approving policies, we need materials on how to provide a member orientation. If we develop some slides, it could be recorded and shared with members. We also could go over it at the start of each concert cycle.

# data[].attributes.body
Polices can be clear while still allowing for a differentiated approach (eg. a dues waiver for students) or even providing room for exceptions as needed (eg. the Musical Director approving exceptions to attendance expectations on a case by case basis).

# data[].attributes.body
1) Use technology to set up a process to collect and store forms.

2) Set up a digital check in process to track attendance.

3) Set up a Google drive folder which includes all membership documents.

# data[].attributes.body
We need section leaders to be clear on the new membership policies. If they have a role to enforce them, we need to train them before the policies are rolled out to members. If a section doesn't have someone able to serve in this role, combine with another section.

# data[].attributes.body
We need to commit as a board to being comfortable defining our membership expectations and then working to implement and uphold them. If we need more time/space to discuss as a board, we should discuss and not rush through policies without enough time to discuss and work through them.

# data[].attributes.body
The member expectations should be as concise as possible. If is too long and cumbersome, members (actual or prospective) will not read them.

# data[].attributes.body
Members of the board need to have complete knowledge of the policies to avoid sharing inaccurate information.

# data[].attributes.body
Members of the board can lead by example to provide a warm and welcoming environment for all.

# data[].attributes.body
Our Leadership team would need to be educated first and then the general membership.

# data[].attributes.body
Pre-established lecture material would need to be presented to the leadership team to use with the general membership.

# data[].attributes.body
Everything should be consistent all across the board for all stakeholders with room for correction.

# data[].attributes.body
Everything should be placed digitally in a Google Drive folder for easy accessibility to all general membership.

# data[].attributes.body
Section leaders need to be able to report attendance and report section needs

# data[].attributes.body
Members need to have access to to expectations online

# data[].attributes.body
Members need to have online methods to report absences and concert participation

# data[].attributes.headline
membership rehearsal and performance agreement

# data[].attributes.subject
membership rehearsal and performance agreement

# data[].attributes.body
several years ago, Oscar Medina (horn and ex personnel head) designed something similar to attached. We had to state:

which PERFORMANCE were we committing;

within each Performance, which rehearsals / dress-rehearsals were we committing

at the time, I didn't like this document because it felt like i was signing off on every week of my life. but looking back, i see the value of such a document as a personal planning and commitment tool

while i cobbled this sample on the fly, the original document was just as long. My strong suggestion (if this is going to be a paper document) is to fit everything into one page. if it becomes an electronic document, then perhaps present the Member of committing to one Concert and its associated rehearsals at a time

# data[].attributes.attachment_link.title
sample - MWE Membership rehearsal and performance agreement

# data[].attributes.headline
communicating Policies and Procedures to Membership

# data[].attributes.subject
communicating Policies and Procedures to Membership

# data[].attributes.body
if we can incorporate a low cost CRM, why not send out our Policies and then Procedures for members to review. If we have a place to sign / initial our agreement, then so much the better.

Admittedly, the sum of all Procedures is rather overwhelming since it is a comprehensive document. Can we break it down into its smaller subjects to send out and us to agree? for instance, Procedure for auditioning; Procedure for rehearsal attendance, and more importantly WHO to contact in case you cannot attend a rehearsal (the more advance notice, the better); Procedure for accepting / returning ensemble owned equipment; etc

# data[].attributes.headline
BoY Welcome packet and periodic reminders

# data[].attributes.subject
BoY Welcome packet and periodic reminders

# data[].attributes.body
It'd be nice to have an email or text blast at season markers:

beginning of year: WELCOME followed closely by rehearsal attendance exceptions and its line of communication

after each concert, reminder of next rehearsal and the new concert's theme

relaying news of membership (passing away, birth or adoption, wedding / milestone anniversary, etc)