1. The accessibility team is responsible for educating, discussing, researching, and improving accessibility in our community at present and in the future. Our goal is to propose ideas for residents and guests to be fully integrated into community life, and to have safe access to the public areas of Mosaic Commons Cohousing and, if possible, access to homes.

2. Members are chosen by self-selection. They need to let the team know if they want to be part of the decision making process. New members and lurkers are welcome.

3. Team decisions are made by a process noted in the addendum.

4. This team may request its own budget at regular budgeting time, or may ask for money from the appropriate team for the relevant changes proposed.

5. The team will report to the plenary when we are working on significant projects and when projects are completed.

6. The Team will work in conjunction with all relevant teams such as Common House room teams, and trustees as needed.

7. The Accessibility Team has power level 3 to ensure that Mosaic will always have a number of designated accessible parking spaces equal to the number of residents who have a handicapped placard, or otherwise need an accessible space, plus one space near the common house.  (See Addendum A)

8. The team has Power Level 4 to make changes that improve accessibility without significantly altering community space. For projects where another team has authority over the space, the two teams will work together and have power level 4.

9. If a proposed change requires more money than our budget, the budget of the connected team, or the discretionary fund allows, the team has power level 2.  We will work with related teams, develop a proposal, and get plenary approval.

10. The accessibility team will accept input from people not on the team by email, personal contact, filling out an appropriate form, survey, etc. The Team can establish a date by which input into a decision is closed. Email is accessibility@mosaic-commons.org.

APPENDIX:

A. If a person needs an accessible space the team will temporarily mark a spot that person can use right away. The team will notify the community to determine if there is any disagreements with that choice.

B. Team decisions are made by at least half of the team saying yes and no one saying no.

Bookkeeper: Diana

The Bookkeeper is the day-to-day financial caretaker for the group:

• Maintain the general accounts and financial records
• Provide members with monthly household statements
• Collect condo fees and keep track of and pay bills and other obligations

Reimbursement Form

BnG is: Dave, Perley, Rich K, John B, Ken, Bob, Buzz

Email the team

Mandate:

The Building and Grounds team is a standing team, whose members will be self-selected. The team will make regular reports to the Mosaic Commons Trustees. The purpose of the Team is to:

1 - Coordinate maintenance of Mosaic Commons infrastructure, which includes most aspects of common areas. See the Buildings and Grounds wiki for a more detailed breakdown. http://wiki.mosaic-commons.org/Teams/TeamResponsibilities

2 - Be the first point of contact for buildings and grounds questions and concerns, per our Operating Procedures. Resources - Supplies and repair bills will be expensed against pre-existing budget line items for maintenance, in the HOA or Cohousing budgets as appropriate. Purchases over $250 will need to be reviewed by the Mosaic Commons Trustees.

Mandate for the Common Resources Team

1. The Common Resources team is a standing team with the general responsibility of overseeing the acquisition and replacement of durable goods that are located in the common spaces of the community. The team has 4 specific roles as defined here:

   Purchasing Process Observer - Common Resources is to ensure community funds spent match our spending values. To that end Common Resources needs to be informed in advance when teams doing their own purchases of durable goods are spending more than $250 on a single item. Once informed (via e-mail to the team list), the Common Resources Team has 72 hours to respond. If the team has an objection, Common Resources will work with the requesting team to overcome the objection. If there are no objections, the purchase is approved.

   Opportunistic Shopper - Common Resources Members will watch freecycle, craigslist, and any other shopping store or site for deals for items which might be of value to the community and might need quick responses to obtain, whether or not a specific request has been made by an individual or team for the items. If consensed upon by the Common Resources team, these items will be purchased out of the Commons Resources budget. Additionally, Common Resources members are a resource for any community teams wishing assistance with purchasing items.

   Cohousing Equipment Reserve Keeper - Common Resources will maintain a list of equipment owned by Mosaic Commons Cohousing, including: last purchase date, estimated replacement price and expected replacement year. To ensure we can replace these items as they wear out, Common Resources will also manage a "reserve" fund, which includes suggesting during the annual budget process what the annual contribution amount should be to fund the reserves.

   Small Team Fiscal Agent - Common Resources Team will hold the budget for common house room teams (and the workshop team) under it’s own budget if those teams do not have a separate line in the annual budget. Those team with budgets under Common Resources can make their own spending decisions up to the amount earmarked for them, but must keep Common Resources informed in advance of any purchase. The Common Resources team will remain in contact with these room teams periodically throughout the year, and if those teams inform Common Resources that they will not be spending their entire earmark, the Common Resources team can chose to spend the remaining amount on other purchases without going to the plenary.

2. Members are chosen by self-selection, and serve as long as they are willing.
3. Team decisions are made by consensus of the members of the team.
4. This team has a line in the annual budget for current year purchases, the amount determined during the cohousing budget setting process each year. In addition, the team oversees the setting of the cohousing reserves budget but not the spending from it.
5. Reports to the plenary about purchases from this teams budget, or purchases the team was involved with, will be issued no less than quarterly, and also when any item costing over $250 is purchased.
6. The Common Resources team will work in conjunction with the common house room teams or any other team that would be acquiring a durable good for a common space.
7. The Common Resources team has the following power levels:
   • Power Level 4 (may make making binding decisions on their own) regarding decisions about spending money out of the annual budget for current year purchases.
   • Power Level 2 (may bring a proposal to plenary) regarding spending from the cohousing reserves.
   • Power Level 4 (may make making binding decisions on their own) regarding choosing of items to purchase once tasked with purchasing something (if there is a team that oversees the space the item is for, must get agreement of that team).
   • The Common Resources team will accept input from people not on the team via email. The Common Resources team can establish a date by which input into a decision is closed.

Steph, Judy, Ken P, Liz, Matt
Sophie (just for kids)
(email team)

Serves as contact for conflict within the group; develops processes for conflict resolution.

Mandate

1. The Community Support (CS) Team is a standing team and our primary mandate is to support the community and relationships in the community. Most of our work is one-on-one but the foundation is really the health of our entire Mosaic community.

CS is responsible for helping individuals to find strategies to resolve the conflicts they have with others. For individual conflicts we use the conflict resolution process described here: link. We also will provide individual emotional support and help people find outside support when requested.

We will help any individual who lives in Mosaic, and any individual who is a member or associate member of mosaic. We will cooperate with the Camelot CS team for issues between people who live in Camelot and people who live in Mosaic or are Mosaic Members or Associate Members.

In conflicts between two individuals CS Members will keep the issue in confidence. If an issue between two people becomes a community wide issue then our primary mandate is the health of the community and we may need to open broader discussion. If we must share with the community the names of individuals involved will not be used and we won't share information without letting individuals involved know what we are going to say.

2. Members of the CS team are chosen by self-selection and are approved by existing members of the team. The CS team may solicit appropriate individuals to join. Email cs@mosaic-commons.org if you are interested in joining the team. The CS email list is confidential and only CS team members may be on the list.

3. Decisions about CS process are made when the members present at a team meeting come to consensus. Community and individual issues are handled by a subgroup of the team; the sub-group informs the rest of the team when they have consensus about how to proceed on an issue, and proceeds if there are no objections from the rest of the team.

4. The CS team may ask for a budget for training and for hiring outside facilitators in case of conflicts that require that.

5. CS will determine when we need to report to the community. Members may ask us at any time if they are concerned about whether we are addressing an issue. Speak directly to a member of the team or send an email to cs@mosaic-commons.org.

6. CS works with any mosaic team or with the Camelot CS team when asked for help.

7, 8, 9. Community support can make their own decisions about how to help people, about whether the issues is a group or individual issue, and whether outside mediation is needed for an issue. If we feel it is necessary we can recommend actions to other teams or to the plenary.

If an individual or team asks us for help someone from community support will get back to them within two days to see if there is an immediate need, and will within two weeks let them know an expected timeline and the names of the community support people working on the issue.

Non-team members are encouraged to ask the CS team questions at any time. We will also solicit input from community members as needed.

San, Sandy, Betsy, Mary
(email this team)

1. The Facilitation and Process Team plans and facilitates plenary General Meetings and attends to process matters in the community. Facilitation and Process are interrelated functions and the sub-teams will sometimes meet separately and sometimes together and may split at a later date if that seems appropriate.

The Facilitation sub-team's primary function is running meetings in ways that make conversations more effective.

Facilitation Tasks:
* plan how to organize and carry-out plenary agenda, based on items provided from Steering
* facilitate plenary meetings
* evaluate plenary meetings
* implement group process within plenary meetings
* be available to facilitate team meetings and discussion circles
* train new facilitators
* manage minute-taking tasks:
** recruit minute-takers
** recommend format for minutes
** distribute minutes
** get approval of minutes at plenary meetings
* ensure there is a child care coordinator for plenary meetings
* set plenary meeting schedule
* arrange facilitation workshops

The Process sub-team's primary function is to define, refine, support, and evaluate community decision-making and discussion processes.

Process Tasks:
* define Color Cards
** make sure there are enough, and correct, cards for plenary gatherings
* document our community decision-making and discussion processes
* define the Process Observer role for plenary meetings
* be available to serve as Process Observers at plenary meetings, in conjunction with CS
* coordinate with Member Integration to introduce new people to our processes
* support team processes:
** be available to help with process-related issues within a team
** be proactive in helping teams learn about group process and decision-making
** be available to assist teams in developing processes that reflect the core values of the community
* be available to help teams or individual presenters get items ready for plenary discussion
* arrange process workshops

2. Members are chosen by self-selection and are re-affirmed yearly. People may choose to be members of only one of the two sub-teams.

3. Team decisions are made by consensus or by another method consensed on within the team. The team may delegate some Process questions to ad hoc teams, with at least one member of Facilitation/Process on the ad hoc team.

4. The Facilitation and Process Team has an annual budget, determined as part of the MC budget process.

5. The team will issue reports to the plenary when the team is developing changes to the community's decision-making process or to the way we handle plenary meetings.

6. The Facilitation and Process Team works in conjunction with other teams:
* Steering to plan plenary agenda items and to facilitate community decisions
* Community Support to handle conflict that arises in General Meetings and to coordinate Process Observers.
* Member Integration to bring new people up to speed with community processes.
* Any team or presenter to help them to be ready for plenary meetings.

7. Power Levels
* The team has power level 2 (may bring a proposal to plenary) for defining and refining plenary decision making processes.
* The team has power level 3 for setting the plenary meeting schedule; arranging workshops; and defining Color Cards.
* The team can make independent decisions (power level 4) about all other team-related tasks.

8. The Facilitation and Process team accepts input from people not on the team by email, personal contact, filling out posted surveys, etc. The team can establish a deadline for input on an issue.

9. The Facilitation email list is a private list, open only to those who are active members of this sub-team and to those who were active and have stepped back for a temporary time (6-9 months).

Any community member can be on the Process sub-team email list, but only those self-declared Process sub-team members can participate in Process sub-team decisions.

Mary, Sandy, Steph, Sophie, Matt H.

The common house cleaning team is responsible for coordinating the rotations for the common house cleaning.

Send to [room]@mosaic-commons.org to get in touch with the team for a specific common house room.

Here are the lists as of October 2010 and who is on them:

bathrooms: Sophie, Ellen
fitness: Sophie, Ellen, Ed, John B., John R., Mariama, Sandy
great-room: Beezy, Sophie, Cat, Mary (2014)
hallways-downstairs: Rich
hallways-upstairs: Sophie, Dave, Ellen, Mary, Noel
hobby-rooms: Sophie, Diana
kids-room: Ellen, Karen, Rich
kitchen: Cat, Noel, Jesse, Dot, Pat (2014)
living-room: Sophie, Dave, Ellen, Noel, Perley
laundry-room: Sophie, Cat, San, Sarah (2014)
multipurpose-room: Sophie, Dave, Bob
music-room: Sophie, Kim, Dave, John R., Karen, Ken, Sandy

---

People who want to volunteer to take on projects to make permanent or hard-to-remove changes in common spaces, such as drilling holes or mounting shelves, should:

(a) consult with the Common Resources Team and the room team for that space (if one exists), to make sure that project is consistent with plans for that space

(b) present a plan for funding

(c) post a drawing or other visual aid for the project in the space and send a note about it to the list. Give the community a week to react, then either post a revised proposal or proceed.

The fitness team is John B, Sophie, Sandy, Ed, Mariama, John R

Mandate:
Fitness Team Mandate:

1) Create a Fitness Room that is both useful and pleasant.
2) Acquire and maintain equipment and fitness room, including reviewing and approving offered equipment
3) Encourage use of equipment
4) Work with the Common Resources team for budgeting and finances
5) Make recommendations to plenary regarding usage restrictions, training, and safety.
6) Make recommendations to plenary regarding structural and other major changes to the space.

Team: Jonathan (Coordinator), San, Sarah, Sophie, Catya
Email: laundry-room@mosaic-commons.org

Mandate for the Laundry Room Team

1. The common house Laundry Room Team is a standing team responsible for equipping the laundry room, organizing it, and keeping it stocked. The team is responsible for setting policy on care of the machines and the space, and making sure that maintenance and repairs are taken care of.

2. Members are chosen by self-selection.

3. Team decisions are made by agreement/lack of dissent, typically over email. Repair decisions are made within the team and then approved by BNG. Purchase decisions are made within the team and then approved by Common Resources.

4. This team does not currently have an annual budget.

5. Reports to the plenary are issued as needed, including machine status and reminder of the rules.

6. The Laundry Room Team works with the teams named above, plus the Hobby Room Team and hosts about guest linens and Great Room and Meals Teams about meal-related laundry.

7. The Laundry Room Team can make decisions at power level 4 (may decide on its own) about policies for the room and supplies to be provided, and works with BNG and Common Resources at a joint level 4 about machine repairs and purchases.

(Power Levels: http://wiki.mosaic-commons.org/Facilitation/PowerLevels)

8. Community members can email the team at laundry@mosaic-commons.org.

Appendix:

Note re budget:
Detergent, bleach, vinegar and other supplies are covered through the Common House Supplies line, repairs through the Maintenance line, and purchases through Cohousing Reserves.

Other team documents:
2016 Laundry Room Guidelines: https://docs.google.com/document/d/1BKXreNeRPxlDijdfI1hTq9GXpm8gSb5vfr9…

Ross (coordinator)
Cat (informal point person for kitchen), Noel, San, Sandy, Liz, Pat, Perley, Judy
email the team

1. The Meals & Kitchen team is a standing team responsible for:

1. Scheduling meals

2. Scheduling people to do the work of meals and meal clean-up, and addressing the needs of cooks and clean-up people.

3. Determining charges for meals and reimbursement rates for cooks

4. Meals accounting, including tracking & billing

5. Setting standards for meals

6. Maintaining our ServSafe certification

7. Ensuring that people who do the work of meals and meal clean-up are trained to follow ServSafe guidelines.

8. Equipping the kitchen (including place settings) through purchases and acceptance of donations of items

9. Organizing the kitchen, including the Kitchen Overflow closet

10. Keeping the kitchen (pantry) stocked

11. Coordinating work in the Kitchen on work weekends

12. Set policy & educate the community about dishes between meals

2. Members are chosen by self-selection and self-identify.  The team email list includes both active team members and other people who do the work of meals.  Kitchen & pantry responsibilities are handled by a subset of the team.

3. Team decisions are made by agreement/lack of dissent, over email or at meetings.  Only active members participate in decision-making.

4. This team separately manages meals accounting and an annual budget from cohousing funds for the Kitchen.

1. Money for and from meals is in an account separate from cohousing funds.  These funds also cover food stocks and other consumables in the kitchen.

2. The annual cohousing budget covers new equipment, replacement equipment (including place settings), knife sharpening, and any fees associated with the ServSafe requirements.  

3. Large appliance replacements are funded through the capital reserves, but will be driven by this team.  Repairs are funded through the maintenance line, and will also be driven by this team.

5. Meals schedules are published regularly. Statistics on meal attendance, how well meal charges line up with meal costs, etc., are sent to the plenary periodically. Reports to the plenary will be issued when new equipment is acquired or ServSafe conditions change.  

6. When notified before scheduling deadlines, the Meals & Kitchen team will help other teams and individuals by scheduling support for food prep and clean-up at community events.

7. The Meals & Kitchen team can make decisions at power level 4 (may decide on its own) about:

   1. Meal scheduling

   2. Meals finances

   3. Kitchen budget spend

   4. Accepting kitchen items as donations

   5. Kitchen & overflow organization.

   6. How the kitchen is used at mealtimes

   7. How the kitchen is used between meals, including dishes, leftovers, and events

   8. Issues pertaining to ServSafe

   It may make decisions at power level 3 (may post a tentative decision) about setting standards for meals.
   (Power Levels: http://wiki.mosaic-commons.org/Facilitation/PowerLevels)

8. Community members can email the team at meals@mosaic-commons.org.
   Donations of kitchen items should be made through communication with this team and not by leaving items in the kitchen.  
   If the kitchen is out of an item that is usually stocked, email pantry@mosaic-commons.org

APPENDIX

We invite anyone who has opinions about how meals are scheduled or billed to be on the Meals email list. It is helpful to have active members who can respond quickly to a needed change and are active on email.

Members are encouraged to participate in meals scheduling times, which happen every two months.  Meals schedules are published via email and a Google calendar.

This team does not meet regularly.   Most discussion and decisions happen on email.

The Meals & Kitchen team can make decisions via email by presenting an idea to the meals email list, waiting at least a week to see if there are any blocks, and responding to discussion by adjusting the proposal.

For changes to our standard practices the team will either have an online discussion or an in-person meeting with the topic announced, followed by a proposal sent to the email list. If there are no blocks in 72 hours after the proposal is sent, the proposal is approved and sent to the community for information.

For items that change significant details of meals we will try to give the community 30 days notice of changes.

Active members of the team are people who come to meals scheduling, come to meals meetings, and/or participate on email. People who do not respond in the set email times are presumed to be inactive for that item, or to be consenting to the decisions.

Any Meals & Kitchen team member may, shortly after a decision is made, request more discussion if they have some reason they could not participate in the decision when it was active.

Members: Mariama, Annamarie, Scott, Judy (mentorship), Cat (Tech/Website only)
Email: integration@mosaic-commons.org

Mandate

1. The Member Integration Team is a standing team responsible for:
   • providing residents with key information such as policies; agreements; where to find things both electronically and physically; and whom to ask for help
   • coordinating mentorship
   • bringing associate household invitation decisions to the plenary, and follow through on the plenary's decisions
   • new member orientation (for both adults and children)
   • social events
2. Members are chosen by self-selection and include individuals with ownership of specific tasks.
3. The team will let the group know how it makes decisions and the timeframes to expect.
4. This team has an annual budget to be determined in 2012 budget planning, to be used for printing welcome kits and holding events. In 2011 the annual budget for social events was $240.
5. Reports will be issued quarterly (or more often if warranted) of scheduled events, new materials available, introductions of new members, and budget status.
6. The Member Integration Team will work with the Tech/Website team to ensure member integration content is available on the website and that new people have access to the website, email lists, and calendaring.
7. The Member Integration Team can make independent decisions about all areas it is responsible for, as per #1 & #3 above.
8. The Member Integration Team is required to get approval from the plenary for budget and changing the scope of its responsibilities.
9. The Member Integration Team will accept input from people not on the team by email, and personal contact. The Member Integration Team can establish dates by which input into decisions are closed.

Ross, Judy, Sandy

Mandate for the Neighboring Fund

1. The Neighboring Fund team is a standing team responsible for

A - Soliciting money for a Neighboring Fund as needed.
- Notifying the community about how to apply for funds.
- Reserving the right to offer funds without an application.
- Receiving requests and managing the distribution of the funds.

B. The Neighboring Fund will be used to support members of Mosaic in paying for meals, hobby room stays and other community activities as deemed relevant by this team.

C. The collection of the Neighboring Fund will be included in the Meals accounting. Distributing funds to other programs, once the distribution is decided, will be arranged between the bookkeepers.

D. There will be no public notice of who receives funds, although the amount of money distributed will be made public.

E. Distribution of money will be decided by the team and given as grants to recipients. The team will be given discretion about whether more than one grant can be offered in any given year.

2. There will be three or four members who will administrate the fund. At least one will be a bookkeeper and at least one will be an at large member of the community. Team members will be chosen by the Team, with announcement of membership or changes in it to be announced to Plenary.

3. Team decisions are made by consensus of the team. Most work of the team will be done by email.

4. Monies for this fund will be collected by free will donation. No additional funds will be used from the budget.

5. They will communicate with the community by email and/or by announcement at General Meeting. There will be a yearly statement of funds collected and distributed.

6. The team will work in conjunction with the bookkeepers from meals and the community.

7. The team will make independent decisions on who receives funds, timing of solicitations for funds and application forms (if relevant).

New Building / Workshop Team Mandate

The workshop ad-hoc team will be managing the process leading to a new workshop building. It's job will be to organize information and feedback from the community, present proposals for decision, and manage execution of those decisions. Approval of this mandate does not automatically assume construction of the building is approved, this mandate is merely documenting how to proceed in the design and speccing off the building.

Selection

Team membership will be via self-selection. Whomever wishes to be on the team may join.

Notes

This team is being established to monitor, manage, and execute a long term complex project. Because of this, several processes must be laid out explicitly.

Due to the length and complexity of the project, it’s been suggested that this team be considered a ‘standing team’, with it’s own mailing list and team members. The minimum number of members on the team will be 3. The name is to be decided.

At various points in this process, decisions will be brought to the plenary for approval before continuing. The team will need in essence 2 power levels. One to bring choices to the plenary for decision, and another to execute on those decisions (this may be implicit in the plenary decision process.)

Membership

Following people have requested to be on the team.
* Ken Porter
* Rich Smith
* John Barrett
* Rich Kramer
* Dave Shevett
* Ben?

Decision process

Team decisions are made primarily via discussion in email. Due to the possibility of people missing meetings, if decisions are discussed during in-person meetings, the decision must be posted to the list for consensus by the rest of the team before being considered accepted, unless the entire team is present at the meeting, or has given a proxy.

When a decision is requested, the requestor will post to the list with the subject line “CONSENSUS:” with a summary in the subject, and then detail within the body of the message. The team may reply “green” to move the process quickly (if the entire team replies, the decision is accepted immediately). If a team member does not reply to the CONSENSUS posting within 96 hours, it’s taken as an accepted request.

For discussion of upcoming requests or decisions, a requestor should open the discussion on the list and allow members to chime in before pushing a CONSENSUS: message out. This allows the CONSENSUS: header to be used discreetly, and those filtering mail based on that header will not necessarily be bombarded with messages.

Before the plenary is presented with information, or before a Decision is brought for consensus, all the team members will, beforehand, agree that the decision and information being presented represents the team's consensus position.

Steps

During each stage of the process, the workshop team will present state of the project information to the community via mailings and updates given at the GM's. In addition, details on the team progress will be posted regularly on a centrally available medium (such as a wiki page or google doc) which the entire community will be able to read / review at any time.

Power Level
Because the team will be checking back in for approval to proceed on each step, the team is requesting Power Level 2 - bringing proposals to the plenary. After consensus is achieved, this team is responsible for executing on the decision (unless otherwise indicated in the proposal).

Phase 1 - Requirements and scope

This phase is purely information gathering and presentation. The team will hold several discussion circles, as well as gather personal input via mailing lists and private conversations to establish the scope and use case
for the building, ranging from "absolute requirements" up to "if I had a million dollars". This will include special purposes (must have a wood shop, etc) and extending to infrastructure requirements (must have heat,
must have running water, etc). Also included will be at least one open discussion during a GM.

The team will translate that feedback into a useful design document describing what the workshop's minimum requirements will be, what its purpose will be, what its capabilities will be, and what it will be used for. This document may also include ‘stretch goals’ for wish list items and approximations regarding priority, or those may be handled separately.

Decision: The plenary will be asked to approve that this document represents the community’s position on the scope of the workshop building, and approve moving to Phase 2.

Phase 2 - Design document with cost analysis

This phase will be the team taking the requirements document from Phase 1 and doing a rough cost analysis. There will be several levels presented, from the minimal needs up through all reasonable items on the wish list. This cost analysis will be relatively informal (ie, with ‘best guesses’ on professional costs, engineering costs, etc), and will be subject to revision once design is settled.

In addition, the team will work with trustees and other members of the community to present several possible financing models. Because acceptance of the design will heavily depend on cost impact, it’s important to have ‘real world’ financing details laid out.

Decision: The plenary will select which design and scope to use, and select a financing model.

Interlude...

At this point the ad-hoc team will be re-evaluated, and further mandate for architectural design, hiring contractors, and actual building the building will be determined."