Difference between revisions of "Resolution Committee"
Line 7: | Line 7: | ||
or group of related problems involving a staff member arises and | or group of related problems involving a staff member arises and | ||
reach(es) a critical level. | reach(es) a critical level. | ||
+ | |||
+ | (I think we should add something about the membership of the RC: it should | ||
+ | have a mix of people: those most involved in the situation, plus one or two | ||
+ | members from outside the situation. -- Shawn) | ||
2. An RC is always created within the framework of the current grievance | 2. An RC is always created within the framework of the current grievance | ||
Line 50: | Line 54: | ||
proposed, items have been placed on the appropriate groups' agendas, and | proposed, items have been placed on the appropriate groups' agendas, and | ||
its written report has been provided to the staff collective. | its written report has been provided to the staff collective. | ||
+ | |||
+ | (What if the issue happens again? New RC? Perhaps it dissolves after a set | ||
+ | amount of time? -- Shawn) |
Revision as of 17:11, 22 December 2004
Here are my initial thoughts on how a resolution committee could work. These are off the top of my head, may be incomplete, and I reserve the right to change my mind on all this.
1. A resolution committee (RC) is composed of members of the staff collective selected by the Human Resources committee (HR) when a problem or group of related problems involving a staff member arises and reach(es) a critical level.
(I think we should add something about the membership of the RC: it should have a mix of people: those most involved in the situation, plus one or two members from outside the situation. -- Shawn)
2. An RC is always created within the framework of the current grievance and discipline policy as agreed to by the staff collective. This policy is not outlined here, but must be followed by the RC. (This would include documentation of incidents, warnings, meeting professional goals, etc.)
3. An RC is charged with the task of resolving the problem(s). The RC's first duty is to specify the scope of the problem(s) and communicate that to the staff collective and any others are likely to be directly affected by the problem. The staff collective should raise any concerns, including changes in scope and the appropriateness of the RC's formation at the first available opportunity. The staff collective may require the HR to dissolve the RC, re-form it, or adjust its scope.
4. An RC is empowered to communicate with all other groups, committees, and individuals at Free Geek for the purpose of investigating the problems within its defined scope.
5. An RC must propose a recommended strategy for resolving the problem as quickly as possible and in the best interests of Free Geek as a whole. This strategy should be outlined in specific steps that can be implemented to address the problem.
6. The RC may put items on agendas of any group at Free Geek in order to bring the problem(s) to resolution. These items should be dealt with by those groups as items with a high degree of importance.
7. An RC may recommend to the staff collective that a staff member be terminated. In this case, the reason for termination must be specifically described and the decision must be considered by the whole staff collective. The person under consideration for termination must be able to speak, but is not allowed to block the decision of the larger group. The person under consideration for termination may choose a representative, either a third party or another member of the staff collective to speak on his or her behalf as well.
8. An RC must report on its findings in writing to the staff collective and any others are likely to be directly affected by the problem.
9. An RC is automatically dissolved when its recommended strategy is proposed, items have been placed on the appropriate groups' agendas, and its written report has been provided to the staff collective.
(What if the issue happens again? New RC? Perhaps it dissolves after a set amount of time? -- Shawn)