TimetableStudent1 / 5
Student Portal
The four things a student office spends its day answering: where am I meant to be, what did I get, have I missed anything, and did somebody tell me something.
- From
- $749
- Function
- 24
- User types
- 2
- Platform
- iOS & Android
React Native · TypeScript · PostgreSQL · Expo
Inside the app
What it does out of the box
24 connected functions on one schema across 2 user types. Everything below is in the template before a line of customisation.
Timetable
Including changes, with the change visible rather than silently applied. A room that moved without anybody noticing is a room nobody goes to.
Results
As released, with feedback attached. Released to a cohort at once rather than trickling out.
Attendance
Including the gaps and the reasons recorded against them, so a pattern is visible before it becomes a letter.
Absence reporting
A parent reports an absence in one step rather than ringing a line that is engaged at 08:40.
Messages
Only what concerns that student. An institution that broadcasts everything trains everybody to ignore it.
Documents
Letters, statements and forms in one place, so nothing important lives only in an email from March.
User types
Two apps, one student.
A parent seeing exactly one child, and nothing about anybody else, is the requirement that matters most here. It is enforced per record rather than filtered in the interface.
Student, the student
One place for timetable, results, attendance and anything the institution needs them to read. Most questions a student office answers are one of those four.
- Timetable including changes
- Results as they are released
- Attendance, including the gaps
- Messages that concern you
- Documents and letters in one place
Parents, the guardian
The same four things about their own child, so they can ask a useful question rather than a general one.
- Your child’s timetable and results
- Attendance with reasons recorded
- Absence reporting in one step
- Messages from the institution
- No sight of any other student
The limits
What this is not.
The same list we give for every app in the catalogue, because the fastest way to a bad project is a promise made in a meeting that nobody wrote down.
We do not process payments
Course fees are recorded and chased; collection runs through your own provider.
It is not a student records system
Enrolment, fees, statutory returns and awarding-body reporting are Student Records in the business catalogue. This is the portal.
Data protection is yours
Which parent may see which child, and for how long, is a policy question we implement rather than decide.
It does not teach
Course delivery and marking are Online Courses. This is the surrounding administration.
Questions
Questions, answered plainly.
If yours is not here, ask it on the call rather than guessing from a pricing page.
What can a parent see?
Their own child’s timetable, results, attendance and messages. Nothing about any other student, enforced per record on the server rather than hidden in the interface.
What if a parent should not have access?
Access is granted per child and can be withdrawn. Custody and safeguarding situations are real and the system has to allow for them rather than assume a simple family.
Does it connect to our records system?
That is the usual arrangement. This portal reads enrolment and results from wherever the truth lives rather than becoming a second version of it.
Can students report their own absence?
That is a policy decision. Most institutions allow it above a certain age and require a parent below it, and both are configurable.
Do I get the source code?
Yes. Both apps, API, schema, migrations and deployment configuration transfer on delivery.
Related
More on-demand builds.
Click through it before you spend anything.
The preview is the real app with sample data. Open it and judge the software rather than the pitch.