====== Race weekends and logistics ======

*//Race projects//// (menu: ////Race projects//// / logistics) is where you build the ////weekend pack//* your crew relies on: who travels, where they stay, session times, car and driver line-ups, and notes.

===== Concepts =====

^ Term ^| Meaning ^
| *//Race project//* | A championship or test programme container for your team |
| *//Event//* | One race weekend (circuit, dates) |
| *//Session//* | Practice, qualifying, race, or test block within the event |
| *//Crew assignment//* | Which staff member is linked to which role or car for that event |


===== Typical workflow =====

1. Open *//Race projects//* and select your project (or create one if you are allowed).
2. Open the *//event//* for the upcoming weekend.
3. Add or update *//sessions//* (times and labels match what you publish to crew).
4. Assign *//hotels////, ////hire cars////, and ////locations//* where your programme uses them.
5. Link *//cars//// and ////drivers//* from car management to this event.
6. Add *//crew//* from the team roster to roles for the weekend.
7. Publish or share the *//briefing//* link / QR so members see their personal pack.

===== Travel and booking links =====

Where configured, hotel and car-hire rows can include *//affiliate booking links//* (e.g. Booking.com). Crew book through the link; commission may be tracked for the programme. You do not need to re-type bookings into a separate spreadsheet if everyone uses the pack link.

===== Weekend briefing (crew-facing) =====

Each event can expose a *//member-specific briefing//// (PDF or web view) keyed off a ////membership QR//* or token:

- Crew scan their membership QR at a kiosk or open a link from the logistics pack.
- They see *//their//* assignments and sensitive notes allowed for their role — not the whole team’s private rows.

Briefing pages use the same *//team colours and logo//* as your membership card theme.

===== Tips =====

- Build the pack *//before//* crew travel so hotels and transfers are one click away.
- Keep session labels aligned with official timetables to avoid paddock confusion.
- After major changes, tell crew to *//refresh//* their briefing — cached PDFs may be from an earlier publish.