Moving enquiries out of a notebook helps only if the office can still see who needs a reply, what is missing, and what happens after approval.
Give every enquiry a next action
Capture the student's name, class interest, guardian contact, source, and a short note. Assign a follow-up date where appropriate. Avoid scattering the decision history across separate messages.
For example, an enquiry awaiting a transfer document should have a clear missing item and follow-up date, rather than simply staying marked as pending.
Separate the decision from enrolment
An approved application may still need payment, student details, or class allocation before it becomes a usable student record. Make those checks visible to the person completing admission.
- Review the application and record the decision
- Confirm the required documents and student details
- Record the applicable admission payment
- Select the correct active class and section
- Check guardian details before preparing family access
Review the queue together
Use a short daily review of enquiries awaiting contact, applications awaiting a decision, and approved admissions awaiting completion. These are different queues with different next actions.
Before rollout, walk one fictional application through the full process and confirm that its resulting student record retains the information your office needs.