Keyholder Policy and Proposal Procedure added

src/SUMMARY.md

@@ -44,6 +44,8 @@
         - [Entrance Lobby](./policies_and_procedures/induction/entrance_lobby.md)
         - [Main Workshop](./policies_and_procedures/induction/workshop.md)
         - [Basement](./policies_and_procedures/induction/basement.md)
+    - [Keyholder Policy](./policies_and_procedures/keyholder_policy/README.md)
+    - [Keyholder Proposal Procedure](./policies_and_procedures/keyholder_proposal/README.md)
     - [Keyholder Induction](./policies_and_procedures/keyholder_induction/README.md)
     - [Code of Conduct](./policies_and_procedures/code_of_conduct/README.md)
     - [Grievance Procedure](./policies_and_procedures/grievance_procedure/README.md)

src/policies_and_procedures/keyholder_policy/README.md

@@ -0,0 +1,32 @@
+# Keyholder Policy
+
+Being a keyholder is a responsibility.
+You are expected to open up for other members and are responsible for the safety of the space when you do.
+Every member does not have an automatic right to become a keyholder.
+
+When you are an active keyholder you are responsible for the space and all that goes on within it.
+You are responsible for the safety of others and the safety of yourself.
+You may have to deal with incidents, accidents and medical emergencies.
+Keys will only be granted if members believe you are able to cope with this.
+
+If you are the active keyholder you must not leave the space until you have clearly handed over to another keyholder.
+The space can not be left unlocked without a current keyholder in the building.
+
+Keys will only be granted if at least three current keyholders can vouch for the honesty or safety of the applicant.
+Any rejection should not be considered an insult but the applicant should take any reason(s) for rejection seriously and try to address them if they can.
+
+We have no set duration you need to be a member before you can ask for a key but the applicant needs to know other keyholders well enough for them to be proposed and seconded.
+Three months from a member who attends once a week, or a year for a member who attends once a month is a good guide to the minimum duration.
+Not knowing the applicant enough is the top reason for applications being rejected.
+
+A keyholder has the right to ask a member not to do something or to leave the building.
+Keyholders do not have any other authority granted to them by being a keyholder.
+A keyholder is not of a higher standing than any other member.
+
+A key can be relinquished by the keyholder or withdrawn by the board at any time.
+If a key has been relinquished the member they will need to reapply for practical reasons but there experience of being a keyholder is likely to result in most applications being fast tracked.
+
+A keyholder is required to undergo an induction and sign the keyholder agreement before receiving a key.
+The keyholder must be subscribed to the Maker Space admin email list.
+All important keyholder messages will have a subject starting “Keyholders”.
+The keyholder may be required to undergo refresher inductions in time to remain a keyholder.

src/policies_and_procedures/keyholder_proposal/README.md

@@ -0,0 +1,36 @@
+# Keyholder Proposal Procedure
+
+The member requesting a key asks a current keyholder to sponsor their application.
+The current keyholder should only agree to sponsor an application if they fully trust the member requesting the key.
+
+The keyholder sponsoring the application posts the application to the Maker Space admin list.
+They should give some background to the applicant and why they feel they should be issued with a key.
+
+A minimum of two extra keyholders need to second the application by replying to the original post.
+These members should only second an application if they fully trust the member requesting the key.
+Although not mandatory it is wise for the member requesting the key to ask two keyholders to do this in advance.
+
+A Security Officer will be appointed for the proposal.
+This should be a board member and by default, this will be the Membership Officer.
+The Security Officer can and should recuse themselves if they are not seen as impartial.
+In this case another board member will take over the tasks of Security Officer relating to the application.
+
+All members (including keyholder and non-keyholders) will be able to comment on the proposal for seven days.
+Any member can object publically on the list or in confidence by emailing the Security Officer.
+
+If after seven days two or fewer objections have been raised and no objections are considered serious and pertinent to the application by the Security Officer, the application has been fast tracked.
+The applicant can be issued with a key after a keyholders induction and signing the keyholders agreement.
+
+If after seven days three or more objections have been raised, or one or more objection that are considered by the Security Officer to be serious and pertinent to the application the application can not be fast tracked.
+The applicant will be informed of the issues raised by the Security Officer and given the chance to withdraw the application to give time to address these issues.
+Alternatively they can respond to the issues raised and ask the board to make a final decision at the next board meeting.
+
+At the board meeting the Security Officer will summarise any issues raised.
+The applicant can respond to this in person or in writing.
+
+The board can either:
+- decide that issues raised are serious and need addressing before an application can be considered again
+- decide that the issues are not serious or just invalid and the applicant can be issued with a key after a keyholders induction and signing the keyholders agreement
+- decide that the proposal needs further review and can be postponed until a later meeting.
+
+A member can re-apply after withdrawing or being rejected at any time if outstanding issues have been addressed.