Consent: 30 Sep 2001
Ultimate decision-making authority in the Takoma Village Cohousing Homeowners Association (TVCHA) resides with the membership as a whole. Decisions of the full membership supercede those of the board, teams (ie committees), interest groups, and individual members.
Lines of accountability move in all directions-from teams to the board; from the board to the teams, and from both teams and the board to the membership as an association and members as individuals. Elements of accountability include ongoing review and evaluation of actions taken by teams and the board.
Teams and the Board (referred to as teams throughout the policy) serve as mechanisms for carrying out the work of the community in ways that reflect the membership’s collective decisions.
Individual Member Responsibilities in Decision Making
Members, as individuals, cannot implement decisions, make donations, or authorize expenditure of TVCHA funds outside of the team structure.
Members are responsible for keeping informed of team and membership decisions that affect them and for providing input on pending decisions using the team structure.
Members have the responsibility to raise their questions and concerns about any decision being made by any team. Questions and concerns must be raised in a respectful manner and at the appropriate time in the decision-making process.
When expressing concerns about a decision, members should:
1. Communicate with the point person for the issue. It is hoped that most questions and concerns can be resolved at this level. It is the member’s responsibility to determine the appropriate point person for an issue and to contact that person directly before moving to the next level.
2. If concerns remain, communicate with the point person for the relevant team.
3. If the issue point person or the team point person is not responsive, communicate with the ombudsperson appointed by the board or any board member.
4. If the issue is still not resolved, the board is responsible for consulting the membership and resolving the issue.
Team Responsibilities in Decision Making
Teams are the primary means for conducting TVCHA business including governance, maintenance, development of proposals, decision-making, implementation of decisions, and identification of work share tasks. Teams are empowered by the membership and must seek to reflect the values and desires of the membership. Teams are responsible for making decisions by consensus, with thought and participation by team members.
It is the responsibility of teams to proactively communicate with the community by posting notices of meetings, detailed agendas, and minutes to the members email listserve and on the Common House bulletin board.
Teams are responsible for ensuring that their sub-teams, user groups, and interest groups are functioning in accordance with this policy. Sub-teams, user groups, and interest groups are responsible for making recommendations to the appropriate team.
Team members who serve as point people are responsible for acknowledging the receipt of questions or concerns and letting individual members know when they can expect a response.
The level of input from the membership that is required before a team makes and implements a decision depends on the type of decision: (1) routine, (2) significant, (3) major, or (4) emergency.
1. Routine Decisions:
Teams may proceed on routine decisions by announcing discussion of the issue on their agenda, achieving consensus within the team, and posting the decision in their minutes. Before implementing the decision, the team must resolve any questions or concerns raised by an individual member.
Routine decisions involve necessary expenditures (i.e., utilities, elevator maintenance, insurance) of any amount approved in the team budget, or meet all of the following conditions:
• Involve minor expenditure of funds (< $1,000) that have been approved in team budget
• Do not involve changes to the use or appearance
• Are limited
• If divergent comments are received, consider upgrading the decision to “significant.”
Examples: purchasing and planting a new bush in already landscaped area, selecting contractor for acoustical study, deciding size of recycling and trash bins, setting technical specifications for web page design, organizing bulletin boards, purchasing kitchen equipment, scheduling meals.
2. Significant Decisions:
In general, significant decisions can be implemented by teams without consensus by the full membership and with or without discussion at a membership business meeting, however, teams must communicate clearly with the membership in the following ways:
• In addition to posting an agenda item, announce to all members that a potential decision is under discussion.
• Establish a clearly defined process for collecting and responding to comments, questions, and concerns. Individual members must have adequate time to comment and a response mechanism must be defined.
• Document the process of receiving comments, questions, and concerns and addressing them in minutes or other communications.
• If divergent comments are received, consider upgrading the decision to “major.”
Significant decisions include those that:
• Involve expenditures of budgeted funds in the range of $1,000 to $5,000.
• Involve non-permanent changes in the use or appearance of common or limited common elements
• Require input from one or more teams
Examples: implementing recommendations of acoustical study, determining need for and use of common storage, deciding web page content and image (i.e., look and feel)
Examples of “clearly defined process” for collecting comments: Presenting options and asking members to mark their preference, survey via e-mail or hard copy to gather input, scheduling a discussion circle to promote dialogue.
3. Major Decisions
Teams must present major decisions to a membership business meeting to be made using the consensus process.
Major decisions are defined as any of the following:
• Involve substantial expenditure of funds (>$5,000)
• Involve permanent or largely irreversible changes to the use or appearance of common or limited common elements
• Set policy, community rules, or precedents.
• Involve issues on which members have expressed widely divergent values and views.
Examples: Fencing the SE corner, policy on user’s fees, use of e-mail.
4. Emergency Decisions:
Emergency decisions are those where the health, safety, or security of residents or facilities will be endangered or damaged if action is not taken quickly.
Emergency decisions should be made by as many team and/or board members as can be effectively included in the decision. If expenditure of amounts in excess of the budget is needed, a board member (preferably the treasurer and/or president) should be included in the decision.
The decision and its implications should be communicated to the membership as soon as possible.
Board Responsibility in Decision Making:
The Board’s responsibilities include, but are not limited to, ensuring that teams are following the wishes of the membership and posting meeting notices, agendas, minutes, communicating decisions, and responding to individual members and the board ombudspeople. Board members will participate in emergency decisions as needed.
This policy will be reviewed in April 2002.
July 2001. Discussed in Teams. Comments sent to Sharon Villines.
1 August 2001. Revised to incorporate comments and address questions and discussion by the Board. Revised by the board and placed on the agenda of the membership meeting.
3 August 2001. Distributed to tvc-members email list.
12 August 2001. Presented for consensus.
18 August 2001. Revised by the Board
26 August 2001. Presented for consensus .
16 September 2001. Revised by Jean Hoff
16 September 2001: Presented for consensus. Concern expressed by member who Will Stand Aside: The policy is overly procedural and does not reflect the neighborly value of co-housing where we talk to each other and make decisions through personal interactions.
Resolution: Respect the decision to stand aside and be certain to document from her the correct phrasing for her concern.
30 Sep 2001: Consent Achieved. Posted 30 Sep 2001