Website and admissions
Programme pages, fee information, admission notices, downloadable forms and a gallery that the office updates itself before every new session.
A school's website is judged in seconds by a parent deciding where to admit a child. The systems behind it are judged every day by the staff who keep records straight. We build for both, starting with the part costing your office the most time.
Choose the module that solves today's problem. The rest can follow without rebuilding.
Programme pages, fee information, admission notices, downloadable forms and a gallery that the office updates itself before every new session.
Circulars, exam routines, holidays and results published once and visible on the site, so the office stops answering the same phone call forty times.
Question banks, timed papers, automatic marking and result publication, with an audit trail of who submitted what and when.
Schools run on a calendar, not on sprint velocity. We plan around your session dates.
Website, admission information and notice publishing go live while the office has time to learn them, ahead of the rush that follows results.
Training for the staff who will actually publish, plus a short guide. If a feature needs to wait for the holidays, it waits rather than disrupting classes.
Question setup, practice runs with a small group, then the real paper. Results are checked against the office's own lists before anything is published.
Review what the staff avoided using, fix it, and add the next module only when the first one is part of the routine.
Two Birgunj schools, two different problems, the same care about daily use.
Yes, if the interface matches the task. We design around the two or three things a teacher actually does — enter marks, publish a notice, check a submission — and keep the rest out of the way. Training happens with the people who will use it, on their own devices.
Marks are entered against a fixed subject and student list, totals are computed by the system rather than by hand, and publishing is a separate confirmed step. The office can export the same data to compare against its own record before anything goes public.
Usually not. The site and staff tools run in the browser on existing computers, and online exams run on whatever devices the school already provides, provided the network can carry the session. We run a practice paper to find the limits before exam day.
We can store student and fee records, but we prefer to add that only when the school is ready to keep them updated. Half-maintained records are worse than a clean spreadsheet, so the process matters as much as the software.
Tell us what the office repeats most often. We will suggest the smallest system change that removes it.
Talk to the team ↗