Find your school’s next connection
Start with the work you want to simplify. Find the feature, see who uses it, and explore what it connects to.
01 / A useful starting point
There isn’t one starting point for every school. Choose a priority to build a focused path through the features.
Choose your priority
School foundation
Start with students, guardians, teachers, classes and sections, then connect each person to a school-scoped account. Administrators gain a clearer foundation for daily operations without rebuilding the same relationships in separate tools.
Classroom work
Teachers can open the relevant schedule, complete attendance and continue into supported academic work. The saved record remains connected to the student, class and date used by the next relevant school or family view.
Parent and student context
Keep circulars, fee status, homework, materials and published results inside the relevant role experience. In-app and push notifications are coming at launch; WhatsApp and non-login SMS are not the update path.
Fee workflow
The school can maintain supported fee structures and records while the linked parent reviews status or uses configured online payment. Payment-gateway transaction charges remain separately payable by the school.
Academic journey
Bring academic structure, schedules, assigned work, study materials, exam setup and published results into one connected journey. Grading scales and board-specific report-card formats can be configured around the school's approved structure.
School operations
Authorised administrators can manage supported route records, capacity context, Student assignments and transport fee settings. Parent and Student delivery, live GPS and fleet operations are outside the current scope.
02 / The complete directory
Explore the eleven feature guides by the work they support. These are connected areas of Schylva—not separate package tiers.
Browse by school work
Connected areas of one platform.
Not separate package tiers.
Search needs JavaScript. All eleven feature guides and category links remain available below.
11 of 11 features
School foundation
Build the school context that daily records, role views and communication depend on.
Keep students, guardians, teachers, classes and sections in one operating context.
Who uses itAll four school roles
Prepare school-scoped administrator, teacher, parent and student accounts with configured login verification and available permissions.
Who uses itAll four school roles
Academic day
Keep classroom actions and published academic information tied to the same student and class context.
Record the class roster once and make the supported school and family views available.
Who uses itAll four school roles
Connect classes, schedules, homework, materials, exams and published results.
Who uses itAll four school roles
Maintain class and teacher schedules and publish the relevant view.
Who uses itAll four school roles
Connect exam setup, marks, configurable grading scales, board-specific report-card formats and published results.
Who uses itAll four school roles
Give teachers a supported publishing path and families one place to find assigned work and protected materials.
Who uses itTeachers · Parents · Students
Family experience
Keep fee status and targeted school updates connected to the relevant student and family context.
Keep supported fee structures, status, offline records and configured parent online payment together.
Who uses itSchool administrators · Parents
Publish targeted circulars and supported acknowledgements, with in-app and push updates planned at launch.
Who uses itAll four school roles
Operations and insight
Organise transport work and review operational, attendance, results and fee-status information.
Organise supported route records, capacity context, Student assignments and fee settings in the administrator workflow.
Who uses itSchool administrators
Review supported operational, attendance, results and fee-status summaries.
Who uses itSchool administrators
03 / How they work together
School information moves through a connected structure—not eleven separate tools. These four stages explain the relationship.
Foundation
Student information and user access connect people, classes and accounts.
People → Classes → Role access
Daily school work
Attendance, timetables, academics, homework, exams and fees stay attached to the right school record; Transport remains an authorised administrator assignment workflow.
Timetable → Attendance → School record
Role views
Administrators, teachers, parents and students use focused experiences rather than one unrestricted dashboard.
Academic setup → Homework → Published results
Reach and review
Circulars keep the audience connected to the underlying school context while analytics supports review.
Targeted circular → Role update → School summary
Two different web workflows, shown with approved demo data. These captures do not depict a single shared record or native mobile apps.
Original reviewed-assignment capture; sample QA wording and review state are preserved.
Look for: the submission state, awarded marks and teacher feedback. The original sample wording and review state are preserved.
Student view, not Parent messaging. The original notice text and acknowledgement states are unchanged.
Look for: notices awaiting acknowledgement and read circulars. This is a Student view, not a Parent messaging screen.
04 / The people using it
Access follows the person’s role and school context. It does not give every account the same controls or an unrestricted dashboard.
School administrators
Work across all eleven connected capability areas, from school structure and access to daily records, operations and review.
Teachers
Use attendance, timetables, academics, homework and materials, exams and school communication in the relevant class context.
Parents
Review attendance, fees, timetables, results, materials and circulars for the linked child.
Students
Use attendance, timetable, homework and materials, results and circulars in the Student experience.
05 / Scope, without the small print
Separate the available web experience, planned native apps and the capabilities outside today’s scope before you shortlist.
The web application supports desktop, tablet and mobile views. Every product capture on this page is from the web application.
Dedicated apps are in development for all four roles. Native workflows and screenshots will be confirmed at launch. In-app and push updates are planned for launch.
Explore the mobile-app planConfirm your school’s configuration and written scope during evaluation.
Transport is currently an authorised administrator workflow; Parent and Student transport delivery and fleet operations are outside the current scope.
06 / Make a useful shortlist
Bring operations, academics, finance and rollout into the same conversation. Take these five questions into your evaluation.
Read the school-software buyer’s guideTrace the action from the person who records it to the administrator, teacher, parent or student who must use it.
Ask vendors to show the actual workflow using safe sample data, including the saved record and the relevant role view.
Separate current web capability, confirmed mobile launch scope and later ideas before comparing vendors.
Record boundaries such as full accounting, live GPS, WhatsApp, payroll or enterprise identity requirements.
Review setup, initial migration, roles, training and acceptance checks with the people responsible for rollout.
Before you decide
Features, role access, school fit and what comes next.
Schylva includes eleven connected feature areas: student information, user and access management, attendance, academic management, timetables, exams and results, homework and study materials, fee management, school communication, transport management and school analytics. Open the detailed feature guides to review each supported workflow and current boundary.
They are connected capability areas within Schylva. The feature pages organise the product for evaluation; they do not describe separate package tiers.
Schylva supports school administrators, teachers, parents and students through school-scoped, role-appropriate accounts. The actions and information available depend on the user's role and the supported school workflow.
Dedicated iOS and Android apps are in development for all four roles. Confirm the supported native workflows at launch. The screenshots here show responsive web, not released native apps.
Schylva is intended for schools across CBSE, ICSE, State Board, IB, Cambridge and other school contexts. Schools should review their exact academic structure, grading and reporting requirements during the demo and implementation discussion.
No. WhatsApp and non-login SMS notifications are not supported. The current release does not send login verification codes by SMS. In-app and push notifications are the school-update path coming at launch.
No. Schylva manages the supported school fee workflow, including configured online payment and offline payment records. It is not presented as a complete accounting system, and payment-gateway transaction charges remain separately payable.
Yes. Book a tailored demo and identify the feature areas and role journeys your school wants to inspect. Schylva can then focus the walkthrough on those supported workflows and current boundaries.
Your school. Your priorities.
Choose the workflows and roles you want to inspect. We’ll shape a 45-minute demo around your school’s priorities.