A system for a school or a college
A school manages people, groups, dates, and approvals. When that lives in forms and email, leadership sees the gap only after it has already become a problem with a parent or a student.
Who it is for
For a principal’s office, a coordinator, or operations at a school, college, or training center. This is an internal process that the required national or campus system does not cover, not a replacement for that system.
Problems this page addresses
Enrollment arrives by email
Status lives in a spreadsheet, and a coordinator updating in the evening cannot see that someone else already approved it in the morning.
The instructor does not see the update
A schedule or a notice changed in the office arrives in the field as a message, and sometimes does not arrive.
The leadership report is rebuilt
Before every meeting, numbers are collected from several files, and there is no single screen to open mid-week.
What you get
The institution’s own statuses
The path uses the words a coordinator actually says - registered, waiting for approval, assigned - not the labels of a generic product.
Instructor access from the phone
The group, the time, and the report use the same data the office updated, without a separate account holding an old copy.
A split between principal, coordinator, and instructor
An instructor does not see another group’s data. A coordinator does not change an admin permission.
Common questions
Does this replace the ministry or campus system?
No. Required systems stay. This page is about the internal process that falls between them: program enrollment, instructor assignment, form tracking, or a report leadership asks for and has no screen for.
Do parents or students sign in?
Only if they have one clear action, such as completing a form or viewing a status. There is no reason to open the coordinator’s screen to them.
How do you roll this out without stopping a semester?
We go live on one cohort or one program. The rest of the institution stays on the old process until that cohort’s statuses are stable.
Related pages
A core system instead of a pile of tools
When the central process - enrollment, handling, scheduling, follow-up - fits no product without bending it, the team becomes the glue. We build the core of that process and leave outside the tools that already do one narrow job well.
A mobile app on the same core as the web
The office works comfortably on a large screen, and the field stays on screenshots and group chats. We build the phone actions on the same server and the same permissions, not as an app with a database of its own.
Rollout and training the team actually uses
A system without practice slides back to WhatsApp in the second week. We hand it over with drills on real routines, a short page per role, and a clear order for permissions and backup so work continues if the person who knew the system leaves.