Skip to main content
Education

A course is run with order not by verbal reminders

We implement operating systems for education institutions: student registration and sections, attendance and absence, fees and instalments, timetables and rooms, courses and grades, and documented internal attendance certificates — sized to your institution: a school needs registration, attendance, fees and parent communication; a training centre needs courses, batches and certificates; a university needs programmes, credit hours, courses and an academic record; and an online platform needs content, progress and subscriptions. What they share: what is not recorded cannot be proven — not to a guardian, not to a reviewer, not to a student appealing a result.

Request an institution assessmentSee the institution types
  • Four institution types, four scopes
  • Our certificates are internal attendance records
  • No pass rates and no student outcome figures
  • Student data is never shared and used for nothing else
  • No smart tutoring and no automated assessment

Direct answers

The questions asked first

Do you issue accredited certificates?

No, and we are neither an education provider nor an accrediting body: what we build is an internal attendance certificate issued by your institution from its own system — it evidences that a student attended the course and completed its hours, and claims no accreditation, equivalence or recognition from anyone. Any accreditation or licence remains the institution’s responsibility and its process with the competent authority, and we produce the document from recorded data rather than from a ready template. Anyone selling you a “certified certificate” as a system is selling a promise they do not own.

Do you guarantee higher pass rates or student results?

No. Student results are set by teaching, content, the student, the family and circumstances, not by an administrative system. What we do commit to is that grades, attendance, absences and appeals are recorded in order and with their source, that who changed a grade, when and why is known, and that every document is verifiable from its data rather than from a separate file. A promise of a pass-rate improvement in this sector is a promise its maker does not control, and we do not make it.

How do you handle student data, some of whom are minors?

By four rules: the data stays in the institution’s systems and remains its property; we use it for nothing beyond the scope of work; we share it with no third party; and we minimise what is collected to what genuinely serves the operation — no extra data “just in case”. Since many students are minors, the lawful basis for collection and guardian consent are the institution’s responsibility rather than ours, and we implement the technical controls it requires: least-privilege permissions, an access log and a defined retention period. We issue no compliance certificate and give no legal advice.

What usually stops systems projects in education institutions?

Three things we see repeatedly, none of them technical: unclean student data — duplicated names, conflicting sections and inconsistently labelled grades — making every report suspect; grades held in a separate spreadsheet per teacher, so there is no single record and no trace of an edit; and fees and instalments managed by hand, so follow-up slips and arrears surface at term end. That is why we start with the student data, the sections, the grade record and the fees, before any promise of a report or an indicator.

Context

Why this sector is different in the Kingdom

Four operational realities impose clear requirements on the system — with no market figures and no targets.

Education sits within Vision 2030 priorities

Education is one of the strategic sectors in the Kingdom’s Vision 2030, with a general direction towards output quality and digital service — context that explains the demand for documentation and measurement, while we publish no numbers or targets, because they are not ours and we cannot verify them.

Context, not a figure

Student data, many of them minors

In many stages the data concerns children, so it is built on minimisation, precise permissions, an access log and a defined retention period — while the lawful basis and guardian consent remain the institution’s responsibility.

Minimal data and an access log

An academic year with a strict rhythm

Registration, terms, exams and results are dates that cannot be postponed, so the system must hold up at the registration peak and in results season without stalling, and separate the permissions of each stage.

A peak that cannot stall

Documents requested constantly

An attendance certificate, a grade transcript or a status letter — requested by the student, the guardian and authorities — must be issued from recorded data rather than assembled by hand each time.

A document from its data

We state the context because it explains the requirements — not to sell with it: we publish no market size, no growth rate, no programme target and no expected improvement percentage, and we issue no accreditation certificates. The institution is responsible for licensing, accreditation and the lawful basis for its students’ data; we implement and document the controls.

Institutions

Four institution types — and four different scopes

The same sector does not mean the same project. Read your type first, then what fits you — and, plainly, what does not.

School or school group

Grades and sections · daily attendance · fees and instalments · guardian communication

What it suffers from
Registration sits in spreadsheets, attendance in registers or on a teacher’s device, grades in each teacher’s file, and fees are followed up by phone, so a student’s full status is never in one place.
What fits it
Organised registration by section and grade, daily attendance in one record, grades in a central record showing who edited what and when, fees and instalments with published follow-up, documented guardian communication, and documents issued from their data.

What does not fit you: Running a complex academic record or an advanced guardian portal before student and section data are stable, biometric or gate access before attendance is disciplined, and a mobile app before the central record is trusted.

Training centre or institute

Courses and batches · trainers and rooms · attendance certificates

What it suffers from
Each course runs on its own file: enrolment in a spreadsheet, attendance on paper, the certificate written by hand, and the room booked by phone, so bookings collide and who actually completed their hours is unknown.
What fits it
Courses and batches with a declared capacity, enrolment tying the participant to their batch, attendance with recorded hours, an internal attendance certificate issued from data rather than a template, conflict-free room and trainer scheduling, and completion reporting per batch.

What does not fit you: A full e-learning platform before enrolment and attendance are controlled, certificates without recorded hours, and complex payment integration before batches and capacity are stable.

University or college

Faculties and programmes · credit hours · registration, courses and academic record

What it suffers from
Master data is enormous: programmes, courses, prerequisites, sections and grades, while registration runs on a legacy system and the academic record is assembled by hand when a transcript is requested.
What fits it
A programme, course and prerequisite structure; term registration with section capacity and prerequisite checks; a central academic record issuing transcripts from its data; permissions by academic role; and a clear trace of every grade edit.

What does not fit you: Replacing every system in one term, running complex online registration before courses and prerequisites are cleaned, and connecting an LMS before the academic record is stable.

E-learning or remote training platform

Content and recorded courses · learner progress · subscriptions and payments

What it suffers from
Content and progress sit in separate tools: who actually completed a lesson and where learners stop are unknown, subscriptions are followed up by hand, and certificates are issued with no completion record.
What fits it
Content structured into paths, recorded progress per learner, subscriptions and renewals with published follow-up, an internal attendance certificate issued on a recorded completion, and per-course completion and consistency reporting with no claim about results.

What does not fit you: Labelling the platform “smart learning” or automated assessment we neither built nor own, issuing certificates with no completion record, and running complex subscriptions before the progress record is stable.

The bands here are indicative guidance rather than an official classification, and the criterion is the nature of the obligation: a school owes a student, a guardian and fees; a centre owes a course, a batch and an attendance certificate; a university owes a programme, credit hours and an academic record; and a platform owes content, progress and a subscription. More than one can coexist in an institution, and each has a different starting point.

Symptoms

What usually shows up in education institutions

Eight recurring symptoms, each with a different root cause — which is why the treatment differs even when the complaint sounds the same.

Duplicated or conflicting student data

The same student is registered twice or in a different section, so numbers are double counted and every report becomes suspect.

Cause: no central record

Attendance in registers or scattered devices

Attendance is recorded in a register or on a teacher’s device with no consolidation, so a student’s consistency is unknown and cannot be evidenced when needed.

Cause: no unified record

Grades in a file per teacher

The grade lives in the teacher’s file and an edit leaves no trace, making an appeal or a review hard to answer.

Cause: no trace of edits

Fees and instalments followed up by phone

Arrears are discovered at term end and follow-up is verbal with no record, so amounts are lost and collection is late.

Cause: unrecorded follow-up

A room or trainer double booked

Booking runs by phone or a diary, so a clash repeats and the course is rescheduled after participants have arrived.

Cause: no central schedule

A document assembled by hand every time

A transcript or status letter is assembled from several files on every request, arriving late and possibly carrying a copying error.

Cause: a document without a source

A certificate with no recorded hours

An attendance certificate is issued for someone whose hours were never recorded, making the document weak under any verification and embarrassing the institution.

Cause: a certificate without a record

Broad access to student data

A user can open records they do not need with no access log — the first thing asked about in any privacy review.

Cause: access without a role

Components

What we implement in the institution

Eight components built in order according to your type; we do not implement all of them for an institution that does not need them all.

Student and section register

One student with one record: their data, section and status, without duplication or conflict — the base everything else is built on.

The base

Attendance and absence

Daily recording in one record per section, with the absence reason where captured, and consolidation showing a student’s consistency instead of searching registers.

Documented consistency

Grades and the edit trail

Grades in a central record, with who edited a grade, when and why, because an appeal and a review are answered by the trace rather than by memory.

A trace per edit

Fees and instalments

An instalment plan with published follow-up and a guardian contact log, and arrears reporting readable in its time rather than at year end.

Collection with follow-up

Timetable, rooms and trainers

A conflict-free schedule for rooms and trainers, a declared capacity per batch, and a documented change when something is rescheduled.

No double booking

Certificates and internal attendance records

A document issued from recorded data (hours or completion), described as it is: internal attendance, not accreditation or equivalence.

A document from its data

Permissions and the access log

Least-privilege access by role (teacher, administrator, finance, guardian), an access log for every open or edit, and a defined retention period.

Least privilege

Operations and communication reporting

Reports decisions can be read from: registration, attendance, arrears, batch completion and learner progress — with no claim about results.

A decision, not an archive

Method

The method: from student data to operation

Eight stages, each with a published output, starting with cleaning student data and sections rather than with configuration — because a system on duplicated data repeats the error faster.

  1. 01

    Assessment and institution type

    A visit covering registration, sections, rooms and finance, establishing the real type, what runs on paper today, and where the largest operational risk sits.

    Output: an assessment naming your type
  2. 02

    Cleaning student and section data

    Merging duplicates, correcting grades, sections and statuses, and unifying naming — before any configuration, because duplicated data repeats the error.

    Output: a trusted student register
  3. 03

    Configuration and testing

    Configuring registration, attendance, grades and fees, and running a full cycle on anonymised data: registration, attendance, a grade, a documented edit, an invoice.

    Output: one complete tested cycle
  4. 04

    Permissions and roles

    Defining teacher, administrator, finance and guardian roles with each role’s limits, the access log and the retention period — before opening data to everyone.

    Output: approved roles and an access log
  5. 05

    Phased go-live

    Going live on one stage, department or batch first, then expanding — not switching the whole institution in one day nor at the registration peak.

    Output: one stage running, then expansion
  6. 06

    Training on the process

    Training each role on its own process: registration, the teacher at the grade, finance at the instalment, administration at the document — with illustrated guides left with you.

    Output: a guide per role
  7. 07

    Integration and reconciliation

    Connecting e-invoicing and accounting, and an LMS where an interface exists after inspecting it, reconciling fees and balances, and closing a first period.

    Output: a documented close with its differences
  8. 08

    Periodic improvement

    A periodic review: where problems recur, which section shows repeated absence, which document is delayed, and which report nobody uses and should be dropped.

    Output: a periodic improvement report

The durations shown are planning ranges to help you build your schedule, not contractual commitments: the actual duration depends on how clean your data is and how quickly sections and permissions are approved, and can be affected by the registration peak or results season.

Measurement

What we measure in an education project

Indicators read from the operation itself, not promises about student results.

Student and section data completeness

The share of students registered with a correct section and status and without duplication, because every figure after it — attendance or fees — rests on this register.

Attendance-record completeness

The share of days and sections actually recorded, because a gap in attendance weakens any later status letter.

Grade accuracy and edit trace

The share of grades tied to an edit record showing who changed them and when, because a grade without a trace cannot answer an appeal.

Fee and instalment reconciliation

The gap between collected and due per student, because arrears follow-up rests on a matching figure rather than an estimate.

Access-log completeness

The share of student-data opens or edits logged with who performed them and when, because that is what is requested in any privacy review.

We announce no pass rate, no grade improvement, no enrolment or retention percentage and no saving, and no figures about market size or programme targets. What we measure is student and section data completeness, attendance-record completeness, grade-record accuracy with the trace of edits, fee and instalment reconciliation, and how fast documents are issued from their data — figures read from your system about your operation.

Integration

Where the system lives in your institution

We connect what you have instead of forcing its replacement, and we inspect every interface before promising it.

Odoo (accounting, stock and purchasing)

Fees, invoicing and supplies on the same accounting entries and stock, so financial work is not run in two systems.

The primary integration

LMS — where an interface exists

We read progress and completion from the platform only if it exports data through an available interface, and after inspecting it; we supply no platform and no content.

An explicit boundary

E-invoicing and payments

Connecting the fee invoice to the statutory integration with a submission and response log, and the payment provider you hold a merchant account with — with no card data through our systems.

With a documented log

Guardian communication

Messages and templates managed from settings with sending limits, the guardian’s consent to the channel before sending, and a record of what was sent.

With guardian consent

Authority and platform portals

Connecting what can genuinely be connected among portals or platforms, after inspecting the interface; if none is available we say so and promise nothing.

After the interface check

Boundaries

Where our scope stops — written before you ask

In education, systems get conflated with accreditation, licensing, academic content and hardware, so the separation is written out plainly.

Accreditation, licensing and certified credentials

We are not an education provider, an accrediting body or a licensing authority: we issue no accredited, equivalence or recognition certificates, and what we build are internal attendance records issued by the institution from its data.

Academic content, assessment and teaching

We produce no academic content, do not mark, assess or grade, and provide no smart tutoring or automated assessment; our role is operation and documentation rather than teaching.

Hardware, laboratories and access gates

We supply no devices, laboratories, interactive boards, cameras, door-access gates or biometric devices, and install none and connect them only through an interface that exists and has been inspected.

Guaranteed results or percentages

We guarantee no pass rate, no grade improvement, no student results, no enrolment or retention percentage and no saving; those are set by teaching, content, the student and their circumstances.

When what is needed falls outside our scope we say so in the assessment and refer a specialist instead of accepting it and learning at your academic year’s expense. That is written in the contract, not left to courtesy.

FAQ

Questions specific to education institutions

Direct answers on accreditation, data, responsibilities and what we do not guarantee.

Do you issue accredited certificates?

No, and we are neither an education provider nor an accrediting body: what we build is an internal attendance certificate issued by your institution from its own system — it evidences that a student attended the course and completed its hours, and claims no accreditation, equivalence or recognition from anyone. Any accreditation or licence remains the institution’s responsibility and its process with the competent authority, and we produce the document from recorded data rather than from a ready template. Anyone selling you a “certified certificate” as a system is selling a promise they do not own.

Do you guarantee higher pass rates or student results?

No. Student results are set by teaching, content, the student, the family and circumstances, not by an administrative system. What we do commit to is that grades, attendance, absences and appeals are recorded in order and with their source, that who changed a grade, when and why is known, and that every document is verifiable from its data rather than from a separate file. A promise of a pass-rate improvement in this sector is a promise its maker does not control, and we do not make it.

How do you handle student data, some of whom are minors?

By four rules: the data stays in the institution’s systems and remains its property; we use it for nothing beyond the scope of work; we share it with no third party; and we minimise what is collected to what genuinely serves the operation — no extra data “just in case”. Since many students are minors, the lawful basis for collection and guardian consent are the institution’s responsibility rather than ours, and we implement the technical controls it requires: least-privilege permissions, an access log and a defined retention period. We issue no compliance certificate and give no legal advice.

What usually stops systems projects in education institutions?

Three things we see repeatedly, none of them technical: unclean student data — duplicated names, conflicting sections and inconsistently labelled grades — making every report suspect; grades held in a separate spreadsheet per teacher, so there is no single record and no trace of an edit; and fees and instalments managed by hand, so follow-up slips and arrears surface at term end. That is why we start with the student data, the sections, the grade record and the fees, before any promise of a report or an indicator.

Does a small school need a full education system?

No. It needs three things done well: a clean student register by section, unified daily attendance, and fees with recorded follow-up. A complex academic record, an advanced guardian portal, biometrics and a mobile app add setup and entry a small team cannot carry and get abandoned after months so everything returns to registers. An abandoned project is worse than a small successful one — and we say so at assessment stage even when it means a smaller scope for us.

How are certificates issued from the system?

From recorded data rather than from a template: a certificate is issued after a recorded completion or documented attendance hours, carries what can be verified in the record, and is described as an internal attendance certificate issued by the institution — no accreditation, equivalence or recognition from anyone. If an accredited certificate is what is needed, that is the institution’s process with the competent authority, and we produce the document from its data without granting accreditation.

What is out of scope?

Accreditation, licensing and accredited or equivalence certificates; academic content, teaching, marking and assessment; smart tutoring or automated assessment; hardware, laboratories, interactive boards, cameras, access gates and biometric devices; moving student data to external tools without approval; recruiting or pedagogical qualification of staff; running operations on your behalf (we run the system, not the teaching team); system and cloud licences (contracted in your name); and publishing market-size figures or national programme targets. We say all of this at assessment stage, before the contract.

Which type are you?

Tell us your type, student and section counts, number of users, and whether fees and instalments are managed, and we will come back with an assessment naming your type, the fitting scope — and what does not fit you.

  • An assessment that names your type
  • A written scope before any commitment
  • A plain statement of what is outside our scope
Request a proposal

Related topics

We are a systems implementation and integration company, not an education provider, an accrediting body or a licensing authority: we issue no accredited or equivalence certificates, and what we build are internal attendance certificates issued by the institution from its own data. We guarantee no pass rate, no grade improvement, no student results, no enrolment or retention percentage and no saving, and we provide no smart tutoring, no automated assessment and no academic content. We supply no hardware, laboratories, door-access gates, cameras or biometric devices, and connect them only through an interface that already exists and has been inspected. Student data stays in the institution’s systems, is never shared and is used for nothing beyond the scope of work; the lawful basis and guardian consent are the institution’s responsibility as the data controller, and we publish no figures about market size or national programme targets. Durations shown are planning ranges, not commitments.