Day and boarding together
The value is one child record with residential context, not a second isolated database.
For boarding teams
Coordinate houses, rooms, mess, leave, wardens, and parent visibility alongside the same student record as day-school operations. See the workflow, ownership, rollout sequence, and boundaries before choosing a school management platform.

Dashboards, approvals, and cross-department visibility.
Product screenshots
Captured from a demo school, at a size search engines can fetch. Open the module for the rest of the workflow.
At a glance
Coordinate houses, rooms, mess, leave, wardens, and parent visibility alongside the same student record as day-school operations.
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
A clear sequence makes ownership, exceptions, and the next system action visible.
Place boarders into houses, rooms, and responsible residential staff.
Maintain mess menus, meal context, leave requests, and residential notices.
Keep boarding records aligned with attendance, calendar, transport, and fees.
Give guardians appropriate room, warden, dining, and leave status visibility.
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.
The value is one child record with residential context, not a second isolated database.
Health, safeguarding, visitor, and emergency procedures require explicit school policy and should not be inferred from a generic portal.
Boarding includes houses, beds, mess, roll call, outings, clinic, and safeguarding records, but those records are not separated per campus in a multi-school deployment.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Straightforward answers for visitors evaluating the product.
The parent model supports linked children, while boarding-specific views remain scoped to the boarder.
Test the guardian link and publication boundary with a sample family before inviting the wider parent community. Confirm that each linked child exposes only the records the school intends.
No. It can organise operational records but does not replace safeguarding governance or emergency policy.
Treat that boundary as an explicit procurement or deployment decision. Document the responsible owner and any supporting process before rollout.
No. Boarding records do not carry a school identifier, so groups with several campuses should confirm whether one shared boarding record set is acceptable.
Treat that boundary as an explicit procurement or deployment decision. Document the responsible owner and any supporting process before rollout.
Continue exploring
Follow the next link based on the question your team needs to answer.
Transport assignment
Assign students to routes and stops, keep fleet context current, and connect transport charges to the student and parent view.
Read the pageFirst 90 days of a school software rollout
Sequence foundation data, one visible workflow, role training, and evidence-based expansion instead of attempting a big-bang launch.
Read the page
We can walk through the workflow with your school’s roles, calendar, data, and first-term priorities.
Already using Schoolyi? Sign in