Roadmap
What is built, what is not, and what is deliberately out of scope.
Shipped
- Academics: years, terms, classes, sections, subjects, allocation, bell schedule, clash-checked timetable, calendar, syllabus and lesson plans
- Admissions: the full pipeline, waiting list, idempotent conversion into a student and guardian
- People: the roll, guardians, staff, enrolment history, documents, bulk import, ID cards, promotion
- Attendance: day and period registers, roll-wide default with exceptions, guardian notification, staff attendance
- Fees: heads, structures, concessions, invoicing, counter collection, add-on driven online payment
- Assessment: exams, papers, marks, grade scale, computed report cards, explicit publication
- Homework: assignment, submission, grading
- Communication: targeted circulars with read receipts, leave, per-recipient notifications
- Facilities: library, transport, hostel, inventory
- Reports: nine, with CSV export
- Public website with admission enquiries
- REST APIs for all three apps, with a generated reference
- The parent home feed, cursor-paged and deep-linked
Next
Parent–teacher messaging. message_threads and thread_messages exist and the admin uses them, but no parent or teacher route exposes them. This is the largest gap between the domain and the apps.
A payment webhook endpoint. Verification is app-initiated today: the app returns from the gateway and calls verify. A gateway that only calls back server-to-server needs a route that resolves the attempt by its gateway reference and settles it. The settlement path is already idempotent, so this is a route rather than a redesign.
Teacher-side leave approval for a class teacher. Leave is visible to teachers; approving is an admin action.
Timetable substitution. Recording that another teacher covered a lesson, and reflecting it on both timetables.
Under consideration
- Per-subject attendance analytics for a term
- Fee reminders on a schedule rather than manually
- A parent-facing school calendar subscription (iCal)
- Report-card PDF templates per school
- Multi-language content for the public site beyond UI strings
- Biometric or RFID attendance import
Deliberately out of scope
Multi-school administration. One deployment, one school. The absence of a tenant column is what makes a leak between schools structurally impossible rather than a matter of remembering a WHERE clause.
Learning management. Homework and marks are here; course content, video lessons and online quizzes are a different product.
Accounting. Fees and payroll are tracked and receipted. A general ledger, tax filing and statutory payroll compliance are not.
Holding funds. Payments go directly to the school's own gateway account. SkoolyHub never takes a cut and never holds money.