Procedures

A procedure is your league’s plan for one situation, such as a safety car, a Code 60, a formation lap or qualifying windows. Stewards start it with a button, or it starts on its own when its condition is met. League admins edit procedures and stewards run them.

Phases and triggers

A procedure has phases. Each phase runs its steps in order.

• The first phase’s triggers start the procedure: a steward button, a telemetry condition (for example a flag in iRacing), a timer, or a failure signal (no agent or no steward left).
• Later phases can have triggers too. They only count while the procedure runs.
• Go to a phase moves on, End stops the procedure.

Steps

Step	What it does
Message	A banner to everyone, a class or chosen cars. It can stay up, and can withdraw the procedure’s earlier banners.
iRacing command	A caution, pace laps, a black flag and so on. Only the commands your league allows in Settings.
Chat announcement	A line in the iRacing chat.
Pits	Close or open the pit lane.
Wait	Wait a number of seconds.
Wait for a steward	Shows a button in race control and waits for a steward to press it.
Wait until	Waits for a condition, for example the pace car on track.
Sorting view	Opens the sorting view and shows each car its place.
Countdown	A countdown stewards can cancel.
Branch	Continues one way or the other, depending on a condition.

An example: the custom safety car

The Custom safety car template runs a safety car without any iRacing command, so iRacing stays at green and the pits stay open. Its four phases:

1. code60, started by the Safety car button: a banner to everyone, “Code 60: 60 km/h, single file, no overtaking, pits open”, that stays. Then it waits for a steward to press Safety car deployed.
2. deployed: a new banner, “Safety car: follow the safety car”, and the sorting view opens, so each car sees where it belongs.
3. sorting: waits for a steward to press Field is correct.
4. green: a green flag banner that withdraws the earlier ones, then the procedure ends.

Copy the template and change the texts, the speed or the steps to match your rules.

The editor

Open a procedure on the Procedures page. Each step reads as a sentence, and the strip at the top shows how the phases connect.

The editor marks problems on their phase or step, for example a phase nothing leads to or a command your league doesn’t allow. A procedure with problems can’t be published.

Edits are saved as a draft. Publish makes it the version stewards run. Published versions never change, and a running session keeps the version it started with.

Templates, import and export

• Templates: iRacing’s pace car caution, a custom safety car without iRacing commands, a Code 60 failsafe, and the agent’s local failsafe.
• Export JSON in the editor’s ⋯ menu: copy or download the procedure you’re editing. Versions downloads any published version exactly as stewards ran it.
• Export all on the Procedures page downloads every procedure in one ZIP: each one’s published version, or its draft if it was never published.
• Import JSON: paste a procedure or choose a file, and it arrives as a draft. If your league already has a procedure with that id, it gets the next free one, like code60-2.

Failsafes

• Failsafe: in Settings, pick the procedure that starts when race control loses its last agent (and optionally its last steward). Stewards get a countdown to cancel it.
• Local failsafe: a procedure the agent runs on its own when it can’t reach the server. It can only use steps that work offline. Operators turn it on in the agent’s settings.