[lkg9999]

We had similar issues our first two years. We would start with a large group of students, and by the middle of build season only a handful would be left. We implemented a few changes last summer that have had a large impact on the rate of participation:
- We implemented a team Code of Conduct with a written contract that both the student and their parent signs. In the Code of Conduct are the rules on participation at meetings and events. We found that unless we did this no one would show up to fundraising events or help with scouting.
- We implemented a system of student-led team leads. During the fall, we met weekly and each workstream had at least one project they were working on. Programmers got to work with previous robots, drive train tried out new mechanum wheels, etc. This helped keep the new kids engaged.

I'm curious as to how other teams keep track of attendance? Do you have a formal sign-in system at each meeting?