Quote:
Originally Posted by Sperkowsky
We are working on two.
One is a so called Constitution thats still imo too vauge another is a student and I's project with 9 pages of policies so far.
|
That's better than nothing...
Typically, in an organization of this type, the constitution/charter will have the group's structure: What leaders do they have, who's in charge of what, requirements to be an officer, and various other "legal" type items (this last would probably include the whole "who's a member" determination). So that's your answer to the "two officers didn't have a lot of time invested"--one of the items might be that officers who aren't putting in the time may be removed and replaced by other officers. Again, this is your "team structure".
The policy document is what I would consider the "team handbook" (others might call it "bylaws"). It would have some of the same information as the constitution in that it would reference the stuff laid out in there, but would also have items like team dress code, attendance policy, how to get the team to let you represent them at competition, grade policy, role of mentors (yes, please please put that in--it could save some internal hassle later), just to think of a few items offhand.
One thing that you should be absolutely sure to include--in both!--is the process to change them, should that be needed (hint: it will be, at some point in the future).
__________________
Past teams:
2003-2007: FRC0330 BeachBots
2008: FRC1135 Shmoebotics
2012: FRC4046 Schroedinger's Dragons
"Rockets are tricky..."--Elon Musk
