> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/operations/attendance/readme.md).

# Overview

*Recap of the Attendance Policy from the Team Handbook:*

The attendance policy is designed to ensure students maintain regular participation, which is vital for their success in the program and overall development. The team emphasizes the importance of each student's attendance as it directly affects the travel expenses they are required to cover.

## Attending Meetings <a href="#attending-meetings" id="attending-meetings"></a>

In accordance with school policies, if a student misses at least half of the school day with an unexcused absence or is absent all day with an illness, they are not allowed to attend any extra-curricular activity that day.

### **Taking Attendance**

It is the responsibility of each student to record their attendance each meeting. The team will assist all students in overcoming any barriers they may face in this process.

The team's mentors reserve the right to remove attendance days. Reasons can include, but are not limited to:

1. Leaving early or arriving late
   1. The minimum amount of time you must be at a meeting is 50% of that meeting time or 3 hours, whichever is less.&#x20;
   2. Exceptions will be made for attending another TJHS team or club competition as described below
2. Working on non-robotics related activities while at the meeting
   1. If team mentors or leadership notices that you are off task from robotics activities, you will be alerted and given a warning. If, during that same meeting, you stay off task, you will be told that your attendance for that day is being removed.

## Attendance Modifications

In order to support all students, we have a few types of attendance modifiers that can be requested.

### **Approved Absences**

Students can request to have days not count negatively toward their attendance for the following circumstances:

1. Attending another TJHS team or club competition
   1. *If you do not attend TJHS, this applies to the school you attend*
2. You were sick to the point you were unable to attend school or had to leave early

All attempts must be made to communicate your absence in advance of the meeting. We reserve the right to deny an absence request if it is clear that there was a lack of effort to communicate prior to a known absence.

### **Additional Credit**

We recognize that students cannot attend all meetings. In order to offset missing meetings due to other commitments students can acquire additional credit days for completing RAID Robotics related tasks. We have published the table below as a starting point for understanding what activities could qualify and the respective effort to acquire an additional day of credit.

<table><thead><tr><th width="308">Activity</th><th>Conversion Rate</th></tr></thead><tbody><tr><td>Developing code for current robot</td><td>2 hours of code = 1 additional credit day</td></tr><tr><td>Working on robot CAD</td><td>2 hours of CAD = 1 additional credit day</td></tr><tr><td><em>More activities are being worked on for other subteams</em></td><td></td></tr></tbody></table>

{% hint style="success" %}
Students are welcome to approach mentors to collaborate on other opportunities.
{% endhint %}

Students are responsible for documenting their extracurricular activities and presenting this documentation to mentors to qualify for additional credit. A form is available in Monday for students to request the addition of additional credit days. Documentation must be presented to a mentor to validate the work. Additional credit can be acquired in increments of one day, and multiple increments may be requested simultaneously. To reduce a backlog at the end of the season, requests for additional credit must be submitted within two weeks from the date the work was done.

## Calculating Attendance

### What is in scope

RAID Robotics is a full year team. Attendance is taken from the first meeting through the end of the competition season.

### Attendance Formula <a href="#attendance-formula" id="attendance-formula"></a>

Each students' attendance is calculated via the following formula:

$$
Attendance \ % = { \frac{# \ meetings \ attended + additional \ credit \ days}{available \ meeting \ days - \ approved \ absences} }
$$

This formula allows students to not be penalized for having approved absences, while not gaining from having approved absences. Please discuss with a mentor if you have any questions about this formula

## Attendance Calculator

A quick attenance calculator has been created. Students can use this to calculate what their attendance would be after inputing theoretical values.

This calculator displays the current Attendance % calculation as described above, along with our previous methodology.

{% embed url="<https://team4469.github.io/attendance-calculator/>" %}

## Travel Payment Table

The discount will apply to the following items:

* Hotel
* Transportation
* Lunch

Students will still be required to pay 100% for the following regardless of discount:

* Breakfast (unless provided by hotel)
  * *The team prioritizes hotels with included breakfast when booking travel, however there are circumstances when that is not available*
* Dinner

<table><thead><tr><th>Attendance Percentage</th><th>Discount</th><th>Remaining student responsibility</th><th data-hidden></th></tr></thead><tbody><tr><td>At or above 90%</td><td>100%</td><td>0%</td><td></td></tr><tr><td>75% - 89.9%</td><td>75%</td><td>25%</td><td></td></tr><tr><td>60% - 74.9%</td><td>50%</td><td>50%</td><td></td></tr><tr><td>35% - 59.9%</td><td>0%</td><td>100%</td><td></td></tr><tr><td>Below 35%</td><td><p>0% </p><p></p><p><em>At discretion of team leadership and space availability for you to attend competition. If allowed to attend, 100% responsibility for costs.</em></p></td><td>100%</td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.raidrobotics.org/operations/attendance/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
