Two separate questions. This report answers “who was present and hasn’t submitted” — the flags below. The bucket rules further down answer a different question: which bucket (Invigilated or Guided) a student is allowed to submit into. A student can be inside their bucket window and still be flagged late here, and vice versa.

What this report flags

Not submitted

Marked Attended, required to submit, and no matching LEAP file exists yet. These are the chase-ups, and they also stack up in the backlog at the top of the report until resolved.

Late

Submitted, but after their deadline. For anyone required, that is 45 minutes after their own exam finishes — the exam starts at the session start and runs its own subject’s length, so the cutoff differs by subject (English Paper 1 and Paper 2 are timed separately). For a Guided student in a non-Checkpoint week, it is instead the 7-day window.

Duplicate

The same assessment uploaded more than once. Not a missing file, but worth checking which one counts.

Not required

A Guided student in a non-Checkpoint week. They may submit (and have 7 days to), but it is not a problem if they don’t — so they are never chased, never appear in the backlog, and are excluded from the percentage. In a Checkpoint week this never applies: everyone present is required, and no session is reported as Guided.

Backlog

Every still-outstanding required non-submitter from the first LEAP day up to the day before the report, oldest first. A late submission clears a student from it automatically. It sits above the day’s report deliberately, so it can’t be skipped.

Definitions

Invigilated LEAP

A supervised exam sitting — timetable events with type LEAP.

Guided LEAP

An exam session inside a normal-looking lesson — any Class event for an HSC course during a LEAP week. Appears as a regular HSC class, but is treated as an exam session during the program.

Attendance

The student's booking is marked Attended, and it counts only for the subject stamped on the booking (its leap_subject). A shared invigilated room seats many subjects — sitting one subject's paper earns rights for that subject alone, and a booking with no stamp earns nothing. Tutorials and non-HSC events never qualify.

Checkpoint Weeks

The 1st, 4th, 8th and 11th weeks of the 12-week program. During these, Guided sessions are treated as Invigilated sittings — attending one earns the same rights.

Lockout window

From the session's start until 24 hours after it ends. Inside it an attendee submits as Invigilated; after it, their submission falls back to Guided.

One submission per exam

A submission in either of exam N's boxes locks the other box, whatever its marking status (the already_submitted verdict, added 13 Jul). A student may resubmit into the same box while its window allows — never the sibling. So "attended but flagged outstanding" clears only by submitting; switching boxes is not an option.

Checkpoint Weeks (program weeks 1 · 4 · 8 · 11)

Every session that week counts as an invigilated sitting — Guided attendance is promoted. One question decides everything: are they still inside the lockout window?

Non-Checkpoint Weeks (all other program weeks)

Invigilated rights come only from an Invigilated LEAP. Guided attendance earns Guided; a lapsed invigilated window falls back to Guided.

The whole rule as one table

Exactly one bucket (or none) is ever enabled — a student can never choose between Invigilated and Guided. Attendance only ever counts toward the subject stamped on the booking. And a submission in either bucket locks the other for good ("One submission per exam" above) — the table shows what a student without a submission may do.

Fine print

• This report is the public.leap_report RPC. A submission matches on the student's subject and week, whenever it was uploaded — so a chased student clears themselves by submitting late. Exam lengths come from public.leap_exam_minutes, ported from the LEAP Clock's LeapSchedule.swift; the Guided 7-day window matches v_guided_grace in the lockout spec.
• Checkpoint weeks come from public.leap_week_numbers() (positions 1 · 4 · 8 · 11). During them, bookings stamped Guided are reported as Invigilated — the same session slot gets reused to run the invigilated sitting, and showing "Guided" next to a Checkpoint badge risks the student not being chased.
• Enforced in the marking.leap_lockouts RPC (agreed 7 Jul 2026; subject match narrowed to the booking's stamp on 11 Jul 2026 after a shared sitting unlocked another subject's bucket).
• The current week's exam number is its position among the calendar's LEAP weeks — week of 6 Jul 2026 is position 1, a Checkpoint Week. Other weeks' exams are always locked.
• The 24-hour window and the checkpoint positions (1/4/8/11) are settings in the RPC.