Chapter Event Policies
Share |

Policy Regarding Red Hat Society Chapter-Sponsored Events

  1. Plan local events which involve other chapters or interested individuals. (example 1)
  2. Use their specific chapter names to advertise and promote such gatherings. (example 1)
  3. Notify HatQuarters of the event if it is large enough that it may conflict with a Red Hat Society event already in the planning stages.

Red Hat Society chapters may not:

  1. Plan events which involve negotiations with outside parties, such as hotels or travel agencies, etc. using the Red Hat Society name. (example 2)
  2. Publicize a chapter-sponsored event as a Red Hat Society event. (example 2)
  3. Plan events which may be considered questionable in nature and use their Red Hat Society affiliation to publicize such events. (example 3)

Example 1 (An example of how to do it):

Queen Mother "A " decides to plan a train hoot to a neighboring town and she wants to invite other local Red Hat Society chapters to join her group. She publicizes the event by stating that her chapter, The Purple Plumes of the Red Hat Society, is planning to go on a train hoot. The train company wants a guaranteed minimum number of tickets sold if they are going to add an extra car to the train for A's friends. A's chapter guarantees that if 300 people don't come, the Purple Plumes chapter will be the responsible party to pay whatever fees are due. "A" makes sure that the train company knows that this is The Purple Plumes' responsibility, not the responsibility of The Red Hat Society, Inc.

Example 2 (An example of how NOT to do it):

Queen Mother "B" decides that she's going to plan a big regional event. She's going to call this one the ?Red Hat Society Northern Regional Convention? because so many people are bound to show up.

She contacts a local hotel to arrange for a discounted rate for her attendees. In order to get the rate, she has to guarantee that a certain number of rooms will be sold. She agrees to the minimum number of rooms and tells the hotel that this is a Red Hat Society event. She forgets to mention that this event is sponsored by her chapter, which will be responsible, and is not a Red Hat Society event, and that she is not an official representative of The Red Hat Society, Inc.

As it turns out, the number of attendees isn't as great as "B" had hoped. She ends up owing the hotel $10,000.00. Since she can't pay it, the hotel calls the Red Hat Society, Inc. and demands payment.

Example 3 (Another example of how NOT to do it):

Queen Mother "X" decides to take a walk on the wild side with her chapter. They're going to the local strip bar. She invites other Red Hat Society chapters to attend and tells the local newspaper about the event. The newspaper publishes an article about the Red Hat Society that would make anyone blush.

We hope that these seemingly silly but all too real examples clarify things a bit.

IMPORTANT: We would very much appreciate it if members planning a large event (involving more than 500 people) would notify Red Hat Society HatQuarters before proceeding, as we may already have an event slated for a similar time and place. This eliminates the risk involved on both sides. If you have thought about putting on a large event and inviting the chapters in your region but have not yet begun serious planning, please contact the RHS via e-mail or phone first (email to events@redhatsociety.com, phone 714-738-0001). That way, we can be sure that any events in the planning phases at HatQuarters will not conflict or compete with your plans. Or, if you'd like, we may be able to collaborate with you on the planning.

These policies are subject to amendment without prior notice.