> ## Documentation Index
> Fetch the complete documentation index at: https://docs.roadcase.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Event attendance

> Track which team members are attending each event.

Roadcase lets you track attendance for events — specifically, which of your road crew members will be at each show or event. This is essential for planning logistics like transportation and lodging.

## Road crew

Before attendance tracking is useful, you need to mark team members as **road crew**. Road crew members are the people who travel with the tour — as opposed to team members who may have Roadcase access but do not travel (like a manager working from home).

To mark someone as road crew:

1. Go to **Settings > Team**
2. Find the team member
3. Toggle the **Road crew** designation

Only road crew members appear in event attendance tracking.

## Setting attendance status

For each event, road crew members can have one of three statuses:

| Status | Meaning |
| - | - |
| **Required** | This person is expected to attend |
| **Optional** | This person may or may not attend |
| **Not attending** | This person will not be at this event |

Administrators set attendance status from the event detail page under the **Attendance** tab.

## Viewing attendance

The attendance tab on any event shows a list of all road crew members with their current status. This gives you a quick view of who will be at each show.

## Use cases

Attendance tracking is useful for:

* **Logistics planning** — Know how many people need transportation and lodging at each stop
* **Day-of coordination** — See at a glance who is expected at the venue
* **Conflict detection** — Identify when key crew members are marked as not attending

## Dashboard integration

The [dashboard](https://docs.roadcase.app/account/dashboard.md) surfaces attendance-related information for administrators, including availability conflicts where a team member's [block date](https://docs.roadcase.app/guides/availability-and-conflicts.md) overlaps with an event they are marked as required for.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.