Applications: the queue a family is waiting in
Where submitted forms are read, chased and turned into learners.
An application is one completed admission form, sitting in a queue with a tracking code against it. Applications is that queue. Every row is a family who has heard nothing back yet, which is why the screen is organised around closing the loop quickly rather than reading in depth.
The secretary owns this screen during intake. The daily routine is simple: filter to what is pending, open the oldest rows first, and give every application a decision — approve it, reject it with a reason, or ask for a specific correction. A family that has been waiting a week with no answer will eventually look elsewhere, so the queue length matters commercially as well as politely.
What makes the screen more than a list is the tracking code printed beside each applicant. Give it over the phone and the family can quote it; it is also what appears on the correction request they receive, so a returned application carries the right identity without anyone having to match on a name that two siblings share.
Work one application to enrolment in six steps
The daily loop, then the decision.
-
Step 1
Open Admissions > Applications
The table lists every application with its tracking code, applicant name, form, academic year, contact details, status and the moment it was submitted.
-
Step 2
Filter to Pending and sort by oldest
Use the Status filter and then sort on the Submitted column ascending. What you want is the longest wait at the top of the list, every morning.
-
Step 3
Open the application and read every answer
Click the eye icon. The applicant page shows the profile, every submitted answer grouped as on the form, the documents, and a progress tracker of the admissions steps.
-
Step 4
Ask for a correction on the exact field
Use Request changes on the group that is wrong. Choose whether you want a correction or additional information, write the message, and — if the family simply does not know — add a question only this applicant will be asked.
-
Step 5
Choose Approved and review the enrolment form
Picking Approved in the Decision field opens the enrolment form with the applicant’s mapped answers already filled in. Read them, correct anything wrong there, and save — that is what creates the learner file.
-
Step 6
Check the fee, then confirm
The class fee structure comes across with the enrolment, and the applicant is only cleared once it is settled. Take the first instalment at the counter in the same visit and the file moves from pending to enrolled in one morning.
Reading the queue: the tracking code and the five states
Why the status column is a workflow and not a label.
The tracking code is the identity that never goes wrong
Every application is issued a code when it arrives, and that code — not the name — is what the family quotes on the phone and what appears on every correction request. Names in a school are shared, misspelt and changed; codes are not. Search on it whenever a family calls rather than trying to remember which of three children named Emmanuel applied.
Five states, and each one tells you who owes the next move
Pending means nobody has looked at it yet. Under review means somebody opened it and is reading. Resubmission requested means the ball is in the family’s court. Approved means the learner file exists. Rejected means it will not. Before working a row, check which side of the exchange it is on — spending ten minutes reviewing a file that is waiting on the family achieves nothing.
Under review is a courtesy flag, not a lock
Moving an application to Under review is how two members of staff avoid both working the same file. It is deliberately not a claim on it: whoever opened it first still decides. In a school where intake is handled by one secretary this barely matters; in one where the head of school also reads applications, it is the difference between a clean decision and two contradictory answers to the same family.
Submitted is sorted ascending by default, and should be
The list opens with the newest work at the top, which is convenient and wrong for intake. Switch to ascending on the Submitted column and the queue reorders itself into “how long has this family been waiting”, which is the only ordering that tells you what to do next.
Asking for corrections, group by group
The difference between a family that returns and a family that gives up.
Requests are attached to a group of questions
The applicant page shows the answers grouped as they were on the form — the pupil section, the guardian section, the level requested, the documents. Request changes sits on each group, so a problem with one section is a problem with one section, not a reason to reject the whole application. Two groups on the default form are labelled Resubmission requested once you have asked, so nothing gets lost on a page with fifty fields.
Correction or information — the distinction matters
Ask for a correction means an answer is wrong and should change: a date of birth typed as 2020 instead of 2010, a class that no longer exists. Ask for additional information means something is missing rather than wrong, which is the right frame for a family who never had the birth certificate and needs to know what to do about it. Choosing the right one sets the applicant’s expectations about whether they must fix something or find something.
Ask a question only this applicant sees
Add a question for this applicant lets you ask something the published form did not — a parent’s occupation if you need it for a record, a fee arrangement if this is a staff child. These extra questions are asked of that one applicant, on top of the original form, and their answers appear with the rest. They do not change the form everybody else sees, which is the point: you solve one case without redesigning the questionnaire.
Closing a group is one click
When the family sends the missing answers back, the group shows the response and offers Mark group as complete. Until you press it the group sits in an answered-but-unreviewed state, which is honest — you have the answer, you have not checked it. Press it when the answer is good enough, and the group stops appearing in your list of outstanding work.
What to do instead of chasing
If a family does not return an answer after a reasonable interval, you have three honest endings: reject the application with the reason recorded, leave it pending, or mark the group complete with what you have and deal with the missing detail at enrolment. What you should not do is approve an application while an obviously wrong answer sits unanswered in a group, because that wrong value carries straight into the learner file.
Approving an application without retyping it
Why the decision field opens the enrolment form.
Choosing Approved is a route, not a stamp
Set the Decision to Approved and press Save decision, and Ekati does not simply flip a status. It opens the enrolment form with the applicant’s answers already transferred into the matching fields — name, email, phone, date of birth, guardian details and the requested level resolved against your real classes. The learner file is created when you check that form and save it, not before.
Read it before you save it
This is the last point at which a mistyped date of birth can be fixed without anybody noticing it on a report card three terms later. Compare the applicant’s answers against the form as it has been filled: the requested level, the guardian’s name and phone, the academic year. Anything that did not map cleanly arrives empty, and an empty field on an enrolment form is a phone call on the first morning of term.
Once the learner exists
The application page then offers View learner, which opens the learner’s own record, and the activity timeline carries the whole history — submissions, correction requests, responses, the decision. Nothing is rewritten along the way, which is what you want the first time a parent disputes the level their child was admitted into.
What approval does not settle
Approval is not enrolment. The learner is only enrolled once the class fee structure attached to that class has been settled, so a family can hold an approved application for a week and be genuinely enrolled only after the first instalment. Take the money at the same visit if you can: it turns three separate conversations — admission, registration, payment — into one.
Before and after the queue
The three screens that bracket this one.
-
Where the queue comes from
Admission forms
Design the questions, the opening window and the target class — and make sure the answers map to your records.
-
Where it ends
Enrollments
Approved applicants arrive here with their answers pre-filled; take the first fee payment in the same visit.
-
Check availability
Classes
The requested level has to resolve against a class that exists and has room, or the approval stalls on a manual fix.
-
Track the season
Dashboards
The academic dashboard reads intake figures alongside the rest of the school before you plan next year.
Application questions
Asked by secretaries running an admission season.
-
How do I ask a family to fix one wrong answer without losing the application?
Use Request changes on the group the problem sits in, not on the whole application. Choose Ask for a correction when the answer is wrong, or Ask for additional information when something is missing, write the message, and save the decision. The application moves to Resubmission requested, the family receives the request against their tracking code, and everything they answered correctly stays intact.
-
Why does choosing Approved open a form instead of just changing the status?
Because approval creates a learner, and a learner should not be created blind. Ekati opens the enrolment form with the applicant’s mapped answers already in the matching fields so that you read them once before they become a permanent record. Saving that form is what creates the file; nothing has been enrolled before then.
-
A family says they never received the correction request. Now what?
Check the activity timeline on the applicant page first: it records the request and the response, so you can see whether the family ever opened the form. Then quote the tracking code back to them — it identifies the application unambiguously. If the request is genuinely the problem, resend it from the same group; the applicant sees the original form plus anything you add for them, and both land in one place.
-
Can I approve several applications at once?
No, and for a good reason: approving opens an enrolment form that has to be read, because it creates a permanent learner record. Approving a batch blind is how a wrong date of birth reaches a report card. Work them one at a time — with the oldest pending first, the queue moves quickly enough, and every approval is a decision you can defend.
-
An applicant is approved but not yet enrolled. Is that a problem?
Not yet — but it will become one. A learner is only enrolled once the class fee structure attached to that class is settled, so an approved application can sit for a week if the family has not paid. Keep approved applications on a short list and chase them the same week you approved them, ideally by taking the first instalment during the approval visit.