====== Scrutineering ======

Scrutineering helps *//race officials and teams//* keep structured records per car and event — setup before track time, reports after sessions, and history on the car file.

===== For programme administrators =====

Open *//Admin → Scrutineering//*.

==== Event passes ====

1. Choose the *//event//* (race weekend).
2. Create or activate a *//scrutineering pass//* for that event.
3. Hand the *//scanner link or QR//* to authorised scrutineers (technical delegates, lane staff).

Passes can be *//retired//* when the event ends so handsets stop accepting new entries.

==== What officials record ====

^ Step ^| Purpose ^
| *//Setup baseline//* | Structured capture of car configuration before running |
| *//Session report//* | Notes and checks after a session or in Parc Fermé |
| *//History//// | All reports stay on the ////car//* for later review |


===== For scrutineers (handset) =====

1. Open the *//scan URL//* provided by the race office (often a QR on the pass).
2. *//Scan the car QR//* on the vehicle or paperwork.
3. Follow the prompts for *//setup//// or ////report//* — use structured fields instead of only photos.
4. Submit — the team admin sees the same record in the console.

Handsets use a *//limited public scan view//// (tokenised link). Scrutineers do ////not//* receive full team admin passwords.

===== Privacy and scope =====

- The scan surface shows only what the *//pass//* allows for that event.
- Full car strategy, budgets, and unrelated events remain in admin behind login.

===== For team managers =====

- Ensure each entered car has a *//QR//* printed before scrutineering opens.
- Compare *//setup baseline//* to later reports when investigating setup changes.
- Use car *//history//* when responding to stewards — one chronological thread beats scattered photos in chat apps.

===== Series owners =====

Scrutineering is optional per championship. Activation, retention, and rights to imagery remain *//contract matters//* between promoter, ASN, and teams — the platform supplies the workflow, not regulatory approval on its own.