Skip to main content
Roadmap

WHAT WE ARE BUILDING,
AND WHAT WE ARE NOT.

Published quarterly and updated when it changes. Dates are intentions, not commitments — if something slips we will move it here rather than quietly deleting it.

In progress

SHIPPING THIS TERM.

  1. Q4 2026

    PAYMENT GATEWAY INTEGRATION

    Online payment against an invoice, so a parent can settle a balance from the portal instead of visiting the office. Card details will never touch Skoolarz — the gateway handles them. Starting with regional providers in Jordan and the GCC.

  2. Q4 2026

    TIMETABLE CONFLICT RESOLUTION

    Detection already exists. What is missing is a decent workflow for fixing a clash: suggested alternative slots, the effect on teacher load, and a one-step amendment that carries through to attendance sessions.

  3. Q1 2027

    REPORT CARD GENERATION

    End-of-term report cards produced from the grading formula that is already configured, in both languages, with school branding, as print-ready PDF. This is the single most requested item on our list.

Under consideration

PROBABLY, EVENTUALLY.

On the list, not scheduled. If one of these is decisive for your school, tell us — a real deployment need moves things up the order more than a vote does.

  1. BEHAVIOUR AND INCIDENT RECORDS

    Merit and demerit logging with the same attribution and parent-visibility model as attendance. Held back because getting the safeguarding and access rules wrong here is worse than not having the feature.

  2. LIBRARY AND ASSET LENDING

    Books, laptops, instruments — anything a school lends and wants back. Straightforward to build; we are waiting to see whether enough schools want it in the platform rather than in a dedicated tool.

  3. ADMISSIONS PIPELINE

    Applications, interviews, offers and acceptance, feeding straight into enrolment. Currently schools do this outside Skoolarz and import the result.

  4. NATIVE MOBILE APPS

    The parent portal is a responsive website by choice. We will revisit if we see evidence that install friction is no longer the deciding factor in parent adoption.

Declined

ASKED FOR,
AND SAID NO TO.

Every one of these has been requested by a real school. We think publishing the reasoning is more useful than a silent backlog.

A visual query builder

Schools do not have analysts, and the tools that assume they do get used twice. We would rather answer the operational questions correctly on screen and export clean data for anyone who wants to model it elsewhere.

Gamification for students

Points, streaks and leaderboards. Every school that has tried them reports the novelty lasting about three weeks, after which what remains is a noisier screen and an incentive to game the metric.

AI-generated report card comments

A comment about a child, written by a model, signed by a teacher who did not write it, read by a parent who assumes they did. We are not building that.

Biometric attendance

Fingerprint and face recognition for registers. It solves a problem schools mostly do not have, using the most sensitive category of data there is, on children. No.

Parent-to-parent messaging

Schools ask for it; schools who have it ask to turn it off. Moderating a social network is not a job any school office has capacity for.

Disagree with one of these? Good — several roadmap decisions have been reversed by a school explaining a case we had not considered. Make the argument.