How-to Guides

How policies are written

Writing policies is a difficult task, they cannot be too specific or too broad, must be consistent and  clear, and enforceable in some way.  Not everything warrants a policy, in fact the less policies you have the better. The best policies are valid for a long period of time and need little to no amendments. It is always good to start with the purpose of the policy (why), followed by possible implementation paths (how) and examples of how it will affect the organization (what). Pictured below is the Golden Circle from Simon Sinek. For a more formal approach to writing policies, check out this document

image-1619321559166.png

https://eregs.github.io/guidelines/ 

How policies are decided

  1. The new policy is drafted in this book (create new page and assign a sponsor)
  2. The new policy is discussed and refined (allow editing and keep revisions)
  3. The Samara organization is voting on the policy
    1. Freeze editing and set status  (admin only)
    2. Loomio vote (link to the policy page) OR
    3. DHO 90/30 vote (when available)
  4. When passed, the policy is enacted
    1. Change status to passed and add date
    2. Assemble team and timeline to execute policy
  5. When updated, the policy is amended
    1. Freeze is lifted (admin only)
    2. Note is added for amendment
    3. Make edits (try to do in one session)
    4. Policy is voted on again (#3)
    5. Link to revision page is added