The handoff that matters
Enrollment is the system boundary: the accepted applicant becomes the same student record used by fees, attendance, grades, transport, and the parent portal.
Workflow journey
Admissions to enrollment
Move an applicant from public application through review, offer acceptance, and live student enrollment without retyping the record. See the workflow, ownership, rollout sequence, and boundaries before choosing a school management platform.
At a glance
A useful page should answer the next operational question
Move an applicant from public application through review, offer acceptance, and live student enrollment without retyping the record.
Who this is for
- Admissions teams
- Registrars
- Prospective families
Start with the evidence
Use the linked product and documentation pages to validate the workflow against your school’s data, roles, policies, and deployment.
Read the supporting materialHow it works
Follow the handoffs, not just the feature list
A clear sequence makes ownership, exceptions, and the next system action visible.
- 01
Collect
Families apply and upload the documents required by the active intake cycle.
- 02
Review
Admissions staff validate records, schedule tests or interviews, and record committee decisions.
- 03
Offer
The team sends an offer, tracks acceptance, and keeps waitlist movement visible.
- 04
Enroll
Accepted applicants become student records with class placement and fee context.
Product truth
What to verify before rollout
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
Available now
Capability status
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Teams in the workflow
- Admissions teams
- Registrars
- Prospective families
Deep dive
Decisions, handoffs, and boundaries
Use these details to turn a product page into an implementation conversation.
Exception handling
Incomplete documents, declined offers, waitlist promotion, and duplicate applicants remain explicit states instead of disappearing into inboxes.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Questions, answered
Straightforward answers for visitors evaluating the product.
Can families track an application without an account?+
Yes. The public track flow is separate from the staff workspace and exposes only the applicant status and allowed actions.
Does enrollment create a second student profile?+
The intended workflow is a direct enrollment handoff into the live roster, with duplicate checks before the record is created.
Continue exploring
Related planning and product pages
Follow the next link based on the question your team needs to answer.
Turn the page into a rollout conversation
We can walk through the workflow with your school’s roles, calendar, data, and first-term priorities.
Already using Schoolyi? Sign in