Application review workflow

Application review is where an intake is either kept tidy or allowed to drift. The queue at /admissions/applications is the working surface: filter by cycle and stage, open a record, check the documents, write internal notes, and move it forward or reject it. Everything downstream — tests, interviews, shortlists, offers, enrolment — reads the same application, so a record left half-reviewed blocks a later step rather than the current one.

Before the queue is useful

1. The cycle is created and open at /admissions/cycles, with its form configuration settled.
2. Class sections for every intake grade exist at /classes with a seat capacity, because the offer stage refuses to run without one.
3. The intake target per section is set at /admissions/intake-plan.
4. The Admissions committee is assigned at /committees with a chair, since that is what grants access and defines the in-charge.

The daily pass

1. Check the funnel and the remaining seats on the /admissions dashboard, remembering that outstanding offers already reserve seats.
2. Open /admissions/applications and filter to newly submitted records.
3. On each record, verify the three required documents and note anything the committee will need later.
4. Advance or reject. The family sees the new status on the tracking page, and an email goes to the parent address on the application.
5. Schedule tests or interviews in batches for the applications that are ready, rather than one at a time.

Rejections and withdrawals both stay in the pipeline as records rather than disappearing, which matters at audit time and when a family reapplies in a later cycle. Internal notes are exactly that: they are visible to staff on the application and are never included in the emails the family receives, so the review trail can be candid.