Board Orientation: Difference between revisions
From Pumping Station One
| (7 intermediate revisions by 2 users not shown) | |||
| Line 93: | Line 93: | ||
* Online banking | * Online banking | ||
* PEX Cards | * PEX Cards | ||
== Annual Report == | == Annual Report == | ||
| Line 110: | Line 109: | ||
All cash payments are to be deposited in the dropbox in the safe; it's currently mounted on the wall. On the envelope should be their name and the date of the deposit. | All cash payments are to be deposited in the dropbox in the safe; it's currently mounted on the wall. On the envelope should be their name and the date of the deposit. | ||
'''Members should be informed that cash payments can take a while to be processed and that they really | '''Members should be informed that cash payments can take a while to be processed and that they really establish recurring payments through the member management system - [[Wild Apricot]] and [[Stripe]].''' | ||
==== Processing the Payments ==== | ==== Processing the Payments ==== | ||
For each cash payment, update the member's record in | For each cash payment, update the member's record in Wild Apricot. | ||
NOTE INSTRUCTIONS WERE FOR ZOHO, NOT WILD APRICOT, VERY OUTDATED | |||
* Set their membership level to their payment amount (if applicable.) | * Set their membership level to their payment amount (if applicable.) | ||
| Line 141: | Line 141: | ||
'''To add''': how to handle members who spend member points on a temporary upgrade instead of a refund | '''To add''': how to handle members who spend member points on a temporary upgrade instead of a refund | ||
=== Checks === | |||
Need to pass along the blank checks. | |||
== Running Votes == | |||
Most of the business conducted by PS:1 is decided by member votes. Running votes is the responsibility of the Secretary. | |||
* A new vote should go here: [[ | * A new vote should go here: [[2017 Votes]] (or the equivalent page for the current year) | ||
* When a vote | * When the vote sponsor has informed the board that a proposal is ready for a vote (usually after discussion on the mailing list), a proxy statement needs to be emailed to all full members. | ||
* This email needs to be sent at least 5 days before the vote - so the Thursday before a Tuesday vote. | * This email needs to be sent at least 5 days before the vote - so the Thursday before a Tuesday vote. | ||
* To send the vote notification email, select "Mass Mail" from the dropdown menu when logged in to the members.pumpingstationone.org. Edit an existing vote email changing the dates (they're in bold), save, and send to full members. | * To send the vote notification email, select "Mass Mail" from the dropdown menu when logged in to the members.pumpingstationone.org. Edit an existing vote email changing the link to the vote and the dates (they're in bold), save, and send to full members. | ||
* | ** Don't forget to change the dates in the email subject line! | ||
* | * In addition to a proxy statement announcement, it's helpful to send out a reminder email the day before proxies are due. | ||
* | * Proxies are sent to the votes@ account. (Credentials in LastPass) Try to check this account before the deadline for proxy votes; if a proxy is incorrectly completed, you can let people know that they can re-send a proxy. | ||
** | * Copy one of the spreadsheets in the Google Drive to track proxy votes. There's also a space there to track who voted in person and vote totals. | ||
** | * At the meeting for the in-person vote, have all full members sign in on a [[https://drive.google.com/open?id=0ByyGnsLiSGNWRkhnLU1YY2J3WjQ Vote Roll Call Sheet]] | ||
* Once the voting is done, update [[ | ** Any members who are present should have their proxy votes removed from the vote spreadsheet. | ||
** Record which members are present for the vote. | |||
* Once the voting is done, update [[2017 Votes]] as well as the votes page. I also generally note whether a vote passed in the minutes and on the vote page. Mailing list announcement also isn't a bad idea. | |||
== Task Management == | == Task Management == | ||
| Line 168: | Line 168: | ||
RTs can have attachments, comments, email replies, and statue changes. It is good to record status updates in tickets so that there is no bottleneck in case someone else needs to pick up the ticket, or has a question. | RTs can have attachments, comments, email replies, and statue changes. It is good to record status updates in tickets so that there is no bottleneck in case someone else needs to pick up the ticket, or has a question. | ||
[[RT | [[RT Procedures]] documents RT basics as well as how to handle the most common RT tickets (general questions, new members, paypal cancellations, member points, etc.) | ||
== Meetings == | == Meetings == | ||