Houses, mess, leave, and guardian visibility
Run day and boarding students on one roster: house assignments, mess menus, residential leave, health notes, and parent views that respect who lives on campus versus who commutes. Residential schools need more than a day-school timetable. Schoolyi links hostel rooms, mess enrollment, and boarding leave to the same student profile fees and academics already use. Wardens see house rosters; parents of boarders get dining and room context in the portal without a separate app.
Boarding & residential in Schoolyi
Houses, mess, leave, and guardian visibility. Captured from a demo school so evaluators see the live workspace, not a mock.
Outcomes
Practical results schools report after rolling out this area on the shared calendar and roster.
One student record for academics, fees, and residential life
Families with day and boarding siblings use one parent login
Leave weekends and permissions tracked with academic calendar context
Mess and house staff work from the same roster as teachers
Product truth
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Deep dive
Use these details to turn a product page into an implementation conversation.
Residential schools need more than a day-school timetable. Schoolyi links hostel rooms, mess enrollment, and boarding leave to the same student profile fees and academics already use. Wardens see house rosters; parents of boarders get dining and room context in the portal without a separate app.
Run day and boarding students on one roster: house assignments, mess menus, residential leave, health notes, and parent views that respect who lives on campus versus who commutes. Because Boarding & residential shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Everything included in this module, from daily workflows to exports your team relies on.
Role-scoped workspaces so each team sees only the tasks they own.
Focused pages for evaluators comparing specific boarding & residential workflows during an SMS rollout.
Workflow
A typical path from setup through daily use on Schoolyi.
Part of the Boarding & residential workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Boarding & residential workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Boarding & residential workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Boarding & residential workflow on Schoolyi, connected to roster, calendar, and role permissions.
Deep dive
Long-form context for evaluators comparing modules during an SMS rollout.
Residential schools need more than a day-school timetable. Schoolyi links hostel rooms, mess enrollment, and boarding leave to the same student profile fees and academics already use. Wardens see house rosters; parents of boarders get dining and room context in the portal without a separate app.
Run day and boarding students on one roster: house assignments, mess menus, residential leave, health notes, and parent views that respect who lives on campus versus who commutes. Because Boarding & residential shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.
These areas work closely with boarding & residential and share the same calendar, roster, and role model.
Straightforward answers for visitors evaluating the product.
House masters, Boarding coordinators, Parents of boarders run daily workflows in this module while leadership reviews dashboards and exports when needed.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
Dates, working days, and class structure flow from the shared calendar so downstream modules do not maintain parallel date lists.
Set the academic calendar before enabling dependent workflows, then test one holiday and one working-day exception against the resulting attendance or exam view. Keep the school’s local policy as the authority for edge cases.
Schools often launch admissions, roster, and fees first, then add this module when the foundation data is stable.
Choose the next phase only after the team has reconciled one complete operating cycle. Record the data, role, calendar, and support dependencies before widening access.
Role-scoped workspaces show only the tasks each team needs. Most schools run a short coordinator session plus self-serve docs.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
We'll show how this module fits your school's workflows and which teams benefit first.
Already using Schoolyi? Sign in
