User Tools

Site Tools


technodogs:forms:code_of_conduct_guardian

(right click on page and choose print)


FIRST Team #3707 Code of Conduct

The Brighton Robotics Team “TechnoDogs” abides by the FRC Student Safety Handbook, the Brighton High School Student Code of Conduct, and honors “Gracious Professionalism,” both by mentors and students.

Gracious Professionalism is defined as “a way of doing things that encourages high-quality work, emphasizes the value of others, and respects individuals and the community.” ( Dr. Woodie Flowers, (1943 - 2019) EAB Chair Emeritus & Distinguished Advisor, https://www.firstinspires.org/about/vision-and-mission)

The following Team 3707 Code of Conduct outlines specific expectations that Team 3707 has agreed upon for the dated season. In the most paramount effort to honor integrity and a commitment to excellence the following guidelines have been established, to be executed at Brighton High School and all other venues:

  1. If a student has become a threat to the security and safety of themself, or others, and has a documented history of negative incidents, they will be asked to remove themselves from Team 3707 for the remainder of the season, and an interview will be effectuated to consider whether the student may return to the team for the subsequent school year.

  2. Profanity, discourteous language or behavior, or rude/aggressive language will not be tolerated. Bullying, and all other forms of bullying including via social media, will absolutely not be tolerated, and may result in removal from the team.

  3. Students given opportunities to observe, practice, perform and execute procedures during both large group activities or small group breakout sessions, but choose not to use the time as indicated, will be asked to leave the activity. Negligence is a dangerous behavior that has no place on this team. Negligence can be defined as oblivious behaviors or a lack of respect for the work-place.

  4. Sexist, racist, and otherwise pejorative language - verbal, written, or otherwise presented- will not be tolerated.

  5. Disparaging others’ work or sub-teams that you are not a part of will not be tolerated. This team requires a lot of smaller groups with a multitude of talents to make things happen efficiently.

  6. The team has a hierarchy for decision-making starting with each student, then team leads, team captains and ultimately the coach. A decision can be escalated in the order above. Any student or group of students can form a data-driven argument and escalate up to the coach. The coach makes the final decision if it escalates to them. We don't have the time or resources to second guess, continue to complain, or disparage others because a decision isn't agreed with. Move on, if the decision is wrong it will likely be quickly obvious and then a competing approach can be put forth.

  7. Students may not leave during practice times without permission of a coach or mentor and signing out before they leave and signing back in when they return.

  8. Students must ride with a parent mentor. College-aged mentors may not shuttle students.

  9. If the team is attending a team event, students must ride with a parent mentor, on the bus, or with their own parent or guardian. They may not drive themselves to a team-sanctioned event.

  10. Students will dress appropriately. We are the face of Brighton Robotics and what the world sees makes an impression. The school dress code is in effect at team events. Dress for Safety: The build room, machining room and other areas that the team uses require closed toed shoes, safety glasses, no hoodie ties. Long hair (past the bottom of your chin) should be tied back, regardless of gender.

  11. If during practice, you find yourself with nothing to do, ask. There is often something to be done. If not, shadow someone and learn something new. The more you know, the stronger the team becomes.

If a member has been asked to eliminate an unwanted behavior or action, and is verbally warned, but fails to acknowledge the request or warning or correct the incident, the Disciplinary Levels found in the Disciplinary Levels section of this document will be followed. For an example, see the In Practice section.

If a student builds a history of 3 incidents, they will be asked to remove themselves from all team activities for the season. For 2 incidents, a parent/coach/student/mentors meeting will be necessary to address the incident(s). See the following Disciplinary Levels for more information.

Disciplinary Levels

(can be skipped depending on severity of incident)

  • Level 1 -First Occurrence - Discussion between coach, mentors and student of incident and why it goes against Gracious Professionalism or the safety rules. The student is asked to leave for the day. The parents are notified. The Incident will be documented with the date.
  • Level 2 -Second Occurrence - Parents are called and asked to come in. Coach, mentors, student and parents are included in a discussion of infraction, example of acceptable behavior, and why it goes against Gracious Professionalism or safety guidelines. The Incident will be documented with the date.
  • Level 3 -Third Occurrence - Parent notification and removal from the team for the season. An interview will be conducted by the coach and mentors to consider whether the student may return for the next season. They will be referred to the BHS principal with corresponding documentation.

In Practice with Example Language

Discourteous and potentially dangerous behavior, including side discussions, distracting horsing around etc. when coaches, team leads, team members, mentors are leading a discussion, conducting a design, build or practice session will result in:

  • A coach, team lead, team member or mentor will address the offending party/parties by name and ask politely:
    "Betty-Jo, Bobby-Sue, can we please (stop unwanted behavior - not to swear, have one discussion, listen to the speaker, pay attention as we need feedback, adhere to restrictions for an event such as covid restrictions etc.)"

    Betty-Joe and Bobby-Sue, student(s), are expected each to acknowledge the request with a polite response
    "ok, sorry, will do, I hear you, I will stop, I understand"

  • If behavior continues, a warning will be given verbally by a coach, team lead, team member or mentor, politely:
    "Betty-Jo, Bobby-Sue, this is a verbal warning (not to swear, have one discussion, listen to the speaker, pay attention as we need feedback, adhere to restrictions for an event such as covid restrictions, etc.)"

    Betty-Joe and Bobby-Sue, student(s), are expected to acknowledge the warning with a polite response
    "ok, sorry, will do, I hear you, I will really stop this time, I understand this is my warning"

  • LEVEL 1: If behavior continues, a coach or mentor will be informed, if not already involved, and conduct a discussion with the student(s). Then, they will politely ask the offending party/parties to leave and if not immediately possible, move to another area until they are able to leave the practice, event, competition for the rest of that day. Offending party/parties parents will be contacted. Behavior and consequence documented with the date.

  • LEVEL 2: If the offending party/parties receive a 2nd documented request to leave, parents are called and asked to come in for a meeting. Coach, mentors, student(s) and parents understand that one more request to leave and the student will be asked to resign from Team 3707 for the remainder of the season.

  • LEVEL 3: If the offending party/parties receive a 3rd documented request to leave, they will be asked to resign from Team 3707 for the remainder of the season. An interview will be conducted by the coach and mentors to consider whether the student may return for the following season. They will be referred to the BHS principal with the corresponding documentation.


Parent:

I have reviewed the code of conduct with my student. I understand the need for the COC and agree to impress upon my student its importance as well as accepting the consequences of behavior in contradiction with it.

 
 Signature:    ____________________________________________                 Date: _______________
 
 
 Printed Name: ____________________________________________
 
 
technodogs/forms/code_of_conduct_guardian.txt · Last modified: 2022/10/07 18:06 by worthing

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki