Management information system

MIS for Al-Beruniy International School

A role-aware school MIS connecting people, classes, attendance, grades, assignments, timetables, support, and aggregate reporting across one academic data model.

Al-Beruniy International School 2026 Full-stack architecture and implementation Private staging, walkthrough on request

Screens

  • ABIS MIS presented across desktop and mobile dashboards
  • ABIS MIS administrator dashboard with aggregate school records and management actions
    Totals, not records Students, teachers, groups and subjects as four counts, with no individual named anywhere.
    The management panel Manage users, grades, assignments and timetable, none of which a learner view offers.
  • ABIS MIS reports and analytics overview with academic and attendance measures
    Five views, one record set Grades, attendance, teacher workload and student progress are tabs over the same school records.
    Export CSV One button takes the aggregate result out to external reporting.
  • ABIS MIS teacher dashboard with lessons, groups, grading, assignments, and attendance actions
    The same dashboard, narrowed Lessons today, groups, work to grade and what's upcoming, in place of the school-wide counts.

Desktop and mobile

A prepared portfolio composite shows the role-aware MIS across desktop and mobile without cropping the interface.

Administrator overview

The administrator overview summarizes the school model and routes authorized staff into users, grades, assignments, timetables, and reporting.

Reports and analytics

Reporting brings academic records, assignments, grades, attendance, and workload into one date-aware operational surface.

Teacher workspace

The teacher workspace narrows the same system to lessons, attendance, assignments, and grading work.

1 / 4

System

People and roles School structure Learning activity Attendance and grades Role dashboards Reports and analytics RBAC One school model, four role perspectives People and roles School structure Learning activity Attendance and grades Role dashboards Reports and analytics RBAC One school model, four role perspectives

Features

Role-scoped command palette

Command+K searches only what your role is allowed to see.

Active child selector for parents

One parent, several children. Switch, and every page follows.

Grades gated by attendance status

A grade needs Present or Late. Changing that clears the grade.

Public password assistance intake

A sign-in help page, separate from the authenticated ticket queue.

Timetable subgroups covering all students

Split a class slot into subgroups. Every student lands in exactly one.

Teacher access scoped to subjects

Teachers see the subjects they teach. Homeroom teachers see everything.

Decisions and tradeoffs

Problems we hit

Clearing grades when attendance changes

Problem

Grades can only exist with matching present-or-late attendance, so changing a teacher's attendance record to absent invalidates dependent grades.

Our solution

Count, confirm, clear in one transaction

The server calculates the affected count, waits for teacher confirmation, and clears the grades in the same transaction that updates attendance. Legacy write routes enforce the same invariant.

Background polling resetting the idle timeout

Problem

The idle timeout is defined as real user inactivity, not token age, which background polling from the notification centre does not represent.

Our solution

Separate activity from background traffic

Background requests from the notification centre and other polling features are excluded from resetting the inactivity clock. This required separating user-activity tracking from background request handling at the session layer.

Decisions we made

Shared academic entities, not feature pages

Decision

The primary decision was to build around shared academic entities instead of feature-by-feature pages.

Why we made it

That makes reporting possible because attendance, grades, assignments, and workload can be evaluated against the same people, subjects, and groups.

Desktop density, responsive learner access

Decision

The second decision was to keep high-density administration and reporting on desktop while maintaining responsive learner access.

Why we made it

Students and parents may check schedules or assignments from smaller screens; administrators still need broad, scan-friendly working surfaces.

Support built into the product

Decision

The system also includes support and language selection as part of the product rather than launch-only assistance.

Why we made it

A multi-role school system needs a clear way to recover when users cannot complete a workflow.

Next

Contact

Let's talk.

For professional opportunities, collaborations, or selected freelance work.

Open to conversations Frankfurt, Germany Europe/Berlin