Step 3 of 6 · Student intake and lifecycle

Student registration

Create the authoritative student, family, placement, health, and document record after an inquiry qualifies.

Student registration in LiveSchools365 Admissions

Student registration is a Admissions workflow in the Student lifecycle area of LiveSchools365 school management software. Create the authoritative student, family, placement, health, and document record after an inquiry qualifies. Schools use it so A documented admission lifecycle with traceable decisions, complete student records, and controlled placement changes.

Move prospective learners from first inquiry through registration, record verification, promotion, and transfer. The people who typically work here are Admissions team, Administrator, Principal. The rest of the module stays one click away, so an inquiry, register, invoice, or stock movement does not have to be re-typed into another product.

What this workflow changes

Complete admission profile This sits inside Admissions rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
Validated academic placement This sits inside Admissions rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
Supporting-document upload This sits inside Admissions rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.

How it fits the rest of Admissions

Open these related Admissions guides when you want the step before or after Student registration:

Admissions dashboard — Prioritize new inquiries, overdue follow-up, qualified applicants, and the next admission task.
Student inquiries — Capture family interest, desired placement, contact details, and follow-up status before creating a student record.
Student records — Find registered students, filter by placement, review details, edit records, and open the printable admission form.
Printed admission form — Produce the official admission form for review, signature, filing, or handover after registration details are verified.
Student promotions — Advance an enrolled student into the next academic year, campus, grade, and section while preserving placement history.
Student transfers — Move an active student between campuses, grades, or sections without losing the previous enrolment context.

How schools evaluate this screen

During a demonstration or trial, Admissions team, Administrator, Principal should complete one realistic example: a new inquiry, a section register, a fee receipt, a notice, or a stock issue, depending on the module. Then confirm that the same record appears on the dashboard, the related report, and the next workflow. That is the test of a school ERP: one operational picture instead of parallel files.

Trend Developers can walk this exact screen against your admission, attendance, exam, or fee process. You can also start a 14-day trial and use the matching live form after sign-in.

All Admissions workflows · Start a trial · View pricing · Request a demonstration

Guide depth

Interface

Desktop interfaceComplete operational workspace with demonstration data

Complete admission profile

Validated academic placement

Supporting-document upload

Page anatomy

Fields, controls, and effects

Use this reference to understand what each area accepts and what it changes.

Student identity and admissionCode, admission number, date, name and contact · Input

Purpose: Create the official identity used by academic, fee, communication, and reporting workflows.
Rules: First name, admission date, academic year, campus, and grade are required; student code is generated on save.
Application effect: Creates the student and current enrolment.

Academic placementAcademic year, campus, grade, section and roll selects · Input

Purpose: Place the student in the correct active class.
Rules: Choose parent values first; section must belong to the selected campus and grade.
Application effect: Controls class rosters, attendance, timetable, exams, and billing scope.

Personal and health informationDates, selects and text · Input

Purpose: Record identity, background, previous school, health notes, and address needed for student care.
Rules: Use verified documents and restrict health notes to relevant facts.
Application effect: Supports safeguarding, identification, and administrative reporting.

Father / guardian and motherContact and socioeconomic fields · Input

Purpose: Create family contacts and relationship context for the student.
Rules: Leave a relationship section blank when it does not apply; verify mobile numbers.
Application effect: Supports authorized communication, family lookup, and emergency contact.

DocumentsImage and file uploads · Input

Purpose: Attach the student picture, birth certificate or ID, transfer certificate, and other admission evidence.
Rules: Use PDF, PNG, or JPEG files up to the displayed size limit.
Application effect: Keeps evidence linked to the registration for later review.

Fee discountPercentage · Input

Purpose: Record an approved student-level concession when applicable.
Rules: Enter only an authorized percentage.
Application effect: Provides the admission concession input used by fee processing.

Save studentCommand · Output

Purpose: Validate and commit the complete registration.
Rules: Resolve required-field and placement errors before saving.
Application effect: Creates the student record and makes it available to downstream modules.