Admissions
A practical glossary of admissions and enrollment
A plain-language glossary of admissions software terms, from applicant and guardian records to document status, offers, waitlists, permissions, and enrollment handoffs.
Applicant, guardian, and relationship
An applicant is the person seeking admission. A guardian or family contact is a related person who may receive information or complete an action. The relationship is the rule that explains why a person can see or do something; it should not be inferred from a shared email address alone.
Define identity, relationship, and contact separately. This makes duplicate review, changed guardians, siblings, transfers, and family access easier to explain and test.
Application, document, and status
An application is the record of a request for admission. A document is evidence submitted or requested. A status should describe a meaningful stage such as submitted, incomplete, under review, decided, offered, accepted, waitlisted, enrolled, or withdrawn.
Each status needs an owner, entry condition, exit condition, required evidence, family-facing meaning, and correction route. A label without those rules creates inconsistent work.
Decision, offer, and handoff
A decision is an approved outcome. An offer is the communication and terms that follow that decision. Acceptance is the family’s response, while enrollment is the controlled handoff into the student record.
GOV.UK procurement guidance recommends minimum necessary data, access control, security, supplier accountability, and clear end-of-contract responsibilities. Use these terms consistently when discussing permissions, exports, and retention.
Permission, audit, and source of truth
A permission defines an action such as view, create, edit, approve, publish, export, correct, archive, or delete. An audit record helps explain who changed what and when. A source of truth is the approved system or record for a value.
The U.S. Department of Education data governance checklist connects quality, access, security, lifecycle, sharing, disposal, and monitoring. A glossary should clarify responsibility, not make complex governance sound simpler than it is.
Make the next action clear
Use this guidance to improve one bounded part of a practical glossary of school admissions software. Name the owner, affected record, evidence needed, and review date. Keep the test small enough for admissions staff to complete and specific enough for a later audit.
Check both an ordinary application and one meaningful exception. If either depends on undocumented knowledge, add the missing definition, training note, permission rule, or support route before calling the next step ready.
