Education · Negros Oriental, Philippines
Academic management for a school that runs from Grade 1 to college: enrolment, multi-stage grade approval, four honours algorithms and certificate generation, across nine roles.
A school that teaches from Grade 1 to college runs four grading systems at once. Elementary and Junior High average their quarters; Senior High awards honours per grading period; College works on an inverted 1.0–5.0 scale with weighted GPAs. Every grade passes through several hands before it is final — and an honours certificate printed from a grade nobody approved is the kind of mistake a school cannot take back.
One system, nine roles: administrator, registrar, principal, chairperson, instructor, teacher, adviser, student and parent. A grade moves from entry to submission, validation and approval, with time-limited edit windows and return-for-revision at every step. Honours are computed by four level-specific algorithms, and a certificate can only be issued against an approved honour — serial-numbered and printed from editable templates. Every page and every action declares the permission it needs from one table, so what a person can see and what they can change never drift apart. It began as a Laravel capstone for the college, and was rebuilt from the ground up in Next.js, Prisma and SQLite.
The path a College grade takes. Nothing skips a step, and nothing is printed until the last one is done.
The instructor enters the grade inside a five-day edit window.
Submitting locks it. Changing a midterm recomputes the semester average.
The chairperson validates it — or returns it, with a reason, for revision.
The level's algorithm qualifies honours: weighted GPA on the inverted 1.0–5.0 scale.
Approving an honour issues a serial-numbered certificate, ready to print.
Elementary, Junior High, Senior High and College — each with its own grading periods, scales and honour rules, not one model bent to fit all four.
Entry, submission, validation and approval, with five-day edit windows (three for advisers) and return-for-revision with a stated reason.
Four level-specific algorithms, written as pure functions and covered by unit tests. Re-running them never overturns a decision already made.
Editable HTML templates with placeholder tokens, sequential serials and print-ready output. A certificate cannot exist without an approved honour behind it.
Page guards, action guards and the sidebar all read the same permission table — and an automated check fails if any portal page skips its guard.
Five reports with charts; CSV and Excel exports scoped by role and level; CSV imports previewed before anything is written.
The same school, seen from four of its nine portals. Pick a role to see what it works on — every name here is generated demo data.
Students, staff, grades awaiting review and honours pending approval — with approved honours by level and the activity log beside them.
Each level grades differently: quarter averages, Senior High honours per grading period with a cumulative floor, and College's inverted scale with weighted GPAs. One shared formula would be wrong for three of them.
Four separate honours algorithms, each a pure function with its own unit tests, run by one service. Re-running them is idempotent and never overturns an approval or rejection already recorded.
With nine roles, the classic failure is a sidebar that hides a page the URL still serves, or a button that calls an action the role should not reach.
Every page and every action goes through one of two wrappers that demand an ability from a single table and check it on the server. A build check fails if any portal page skips the wrapper.
Signed cookies are fast and stateless — which usually means an administrator cannot revoke one before it expires.
Each account carries a sessions-valid-from timestamp, read on every request. Ending someone's sessions takes effect immediately, and an automated check proves an already-issued cookie stops working.
A public demo needs a database people can change, on a host whose filesystem is read-only.
A seeded SQLite file ships with the build and is copied to temporary storage at start-up, so every instance is writable and resets itself — with Turso available when it needs to persist.
Captured from the live product — the site, and the app where there is one. Select any screen to enlarge it.
The manual steps between your tools, removed — quotes, bookings, invoices, reminders and handovers running without anybody retyping anything.
A site that loads fast, answers the question the visitor arrived with, and gets maintained every month instead of ageing quietly in the background.
The sign-in page has a one-click switcher for all nine roles, with a fully generated school behind it — so anyone evaluating the system can try it as a registrar, a chairperson or a parent.
Tell us what is not working. We'll tell you what it would take.
BUSY BUREAU
