Ops Mode unlocks the write controls on the timetable so the ops clerk can record actual times as the day progresses. All other officials see the same page in read-only mode — only the clerk's device needs to be in Ops Mode.
Click the Ops Mode button in the controls bar at the top of the timetable page. A PIN prompt will appear. Enter the four-digit operations PIN and click Unlock. The button label changes to Exit Ops and the timetable reveals the input fields and action buttons for each session.
The PIN is set in api/config.php on the server. It is the same PIN used for all write operations (setup, session edits, actuals). Contact your system administrator if you do not have the PIN.
While Ops Mode is active the automatic 30-second page refresh is paused to prevent the form from being wiped mid-entry. The footer shows Auto-refresh paused (Ops Mode). Refresh is restored as soon as you exit Ops Mode.
If you type into any field without saving, a yellow warning banner appears at the top of the page: Unsaved changes — auto-refresh paused. Save or clear each row to resume. This also suppresses auto-refresh even outside of Ops Mode until every row has been saved or cleared.
Each session row gains four time input fields in the Actual column group once Ops Mode is active. Enter times in HH:MM format. Fields that are not applicable to a session type are hidden.
| Field | When to use |
|---|---|
| Grid | The time cars were released from pit lane onto the assembly grid. Race sessions only. For reference and record-keeping; does not affect timetable predictions. |
| GFL | The time the green flag was shown / formation lap started. Only shown for sessions with a planned formation lap (GFL flag set). When entered, the predicted race start becomes GFL time + GFL minutes. |
| Start | Actual race or session start time — lights out (standing start) or rolling-start trigger. When entered, the status automatically changes to Active and the predicted start is anchored to this time. |
| Finish | Actual chequered flag time. When entered, the status automatically changes to Done and the predicted finish is anchored to this time, cascading updated predictions to all subsequent sessions. |
Each time input has a small clock icon (⏱) to its right. Clicking it stamps the current time into that field. Use this for real-time logging — glance at the track, click the button the moment the event occurs, then save the row. You can still type over the value if you need to correct it.
Always click Save after entering times. Fields are not sent to the server until you click the Save button for that row. The unsaved-changes banner reminds you if any row has unsaved data.
In most circumstances you do not need to touch the Status selector. The two most common transitions happen automatically:
Only set the status manually when something out of the ordinary occurs:
| Status | When to set manually |
|---|---|
| Red Flag | The session has been stopped mid-race. The row is highlighted red. You can resume the session later by changing the status back or by entering new times. |
| Cancelled | The session will not run at all. It is struck through on the timetable and removed from the prediction cascade — subsequent sessions shift forward by the cancelled session's duration. |
Pending is the default for any session that has not yet started — you never need to set this manually. Active and Done are set automatically by saving an actual start or finish time respectively.
The Override column group lets you adjust predictions in real time without altering the original scheduled values, which remain visible for comparison.
Enter a number of minutes to replace the session's scheduled duration for all future finish-time predictions. Use this when a session is being extended (e.g. extra laps declared) or shortened (e.g. cut due to time pressure). Leave blank to use the scheduled duration.
Enter a number of minutes to replace the turnaround gap after this session when cascading start predictions to the next session. Use this when you know a grid or track condition is causing a delay beyond the scheduled gap. Leave blank to use the scheduled gap.
Overrides do not appear in the Scheduled columns — they appear only in the Override columns, making it easy to see at a glance how actuals differ from the original plan. Clear an override by deleting the value and saving.
Each session row has a 📝 notes button (visible in Ops Mode). Clicking it opens a small panel below the row with additional recording fields:
Each session row has its own Save button in the Ops column. Clicking Save sends all fields for that row to the server in a single update — times, overrides, status, and notes together.
If the save is successful the row refreshes immediately with the updated predicted times and the unsaved-changes banner clears for that row. If an error occurs an alert is shown — check your network connection and try again.
Each row is saved independently. Saving one row does not save changes in other rows. Work through the session list top to bottom and save each row as you go.
Click Exit Ops in the controls bar. The input fields and action buttons are hidden, and the 30-second auto-refresh resumes. Any unsaved changes in open rows will be lost, so save all rows before exiting.
Other officials' devices are read-only and are never affected by entering or exiting Ops Mode on the clerk's device.