← All posts

A portal for a school, academy or training centre: what it needs

Students, parents, teachers and the office all want different things from a school portal. Here is what a school, academy or training centre portal should include, what to leave out of the first version, and how I build one.

Author
Elie Chaaban
Published
Reading time
7 min
Topics
Custom Portals, CRM, Education, Planning

Most schools, language academies, tutoring centres and training companies run on a mix of tools: a spreadsheet of students, a WhatsApp group per class, a shared drive of timetables and a receipt book in the office. It works until a parent asks for last term's grades and nobody can find the file, or a fee reminder goes to the wrong family.

A portal pulls this into one place where each person sees what they need and nothing more. This article is for owners and administrators who are about to hire someone to build one: who uses it, what it should include, what can wait, and how the build usually goes.

Four audiences, four different portals

The first thing to accept is that a school portal is really several portals sharing one database. Each audience logs in with different needs, and the design should start from them rather than from a feature list.

The office or administration needs the full picture: enrolments, classes, schedules, fees, staff, documents and reports. This is the heaviest part of the system and the one used all day.

Teachers and trainers need their classes, their timetable, a fast way to take attendance, a place to enter grades or feedback, and a way to post material or notices to a class. They will not tolerate slow screens or ten clicks to mark a register.

Parents, in a school or for younger students, want to know: is my child there today, how are they doing, what is due, what do I owe, and what is happening this week.

Students, especially adults in a training centre or older students in a school, want their schedule, their material, their results and, for courses that end in a certificate, proof that they finished.

In an adult training centre the parent role may not exist, while companies that send staff on your courses may need their own view. Getting this list right shapes the permissions, navigation and data model. My post on roles and permissions in a business app goes deeper on how to define who can do what.

The core records

Underneath the screens, a school portal is built on a small number of records that link together. If these are modelled well, most features become straightforward.

When you write your brief, describe how your institution actually organises these. "We have three intakes a year and students can move level mid-term" is far more useful to a developer than "we need class management".

Features that matter most

Enrolment and student records

The office should be able to register a student, attach guardians, assign them to a class and store the documents you collect, such as ID copies, previous reports or medical notes. Sensitive documents need tighter access than the rest of the record: a teacher may need to know about an allergy but not see a scanned passport.

If you take applications, an online form that feeds straight into the system, with simple statuses such as received, accepted and enrolled, saves a lot of retyping.

Timetables and schedules

Teachers and students should see their own week, not a giant grid. A cancelled session or room swap updates in one place and notifies the people affected; online sessions hold their meeting link.

Attendance

Attendance is the feature teachers touch most, so it has to be fast: open the session, everyone is marked present by default, tap the absent ones, save. It should work on a phone in a classroom with patchy Wi-Fi, which means a page that loads quickly and handles a dropped connection gracefully.

Parents then see same-day absences, and the office gets reports without compiling them by hand.

Grades, feedback and reports

Some institutions use numeric grades, some use levels, some only write comments. The portal should follow your system rather than force a generic one. Teachers enter results per assessment; the system calculates term results using your rules and produces a report card or progress report you can download as a PDF and, when you are ready, publish to parents and students.

Grades should not appear to families the moment a teacher types them; the office usually reviews and releases them together.

Material and assignments

Teachers upload files or links per class and set assignments with due dates. If you already use a learning platform for course content, the portal can link to it rather than replace it.

Fees and payments

For many institutions this is where the money is lost: unclear balances, missed instalments and manual receipts. The portal should hold a fee plan per student or family, generate instalments, record payments and show a clear balance to the office and to parents.

In Lebanon, most families pay by bank transfer, Whish or OMT, so the practical first step is recording those payments against the right instalment and issuing a receipt from the system, rather than building online checkout. Reminders for upcoming and overdue instalments then go out automatically.

Notices and messages

Announcements to a whole school, a grade, a class or one family should come from the portal, so there is a record of what was sent and to whom. Email and in-portal notifications are the base. WhatsApp notifications can be added for urgent or high-value messages, with the usual care about templates and opt-in.

Two-way parent and teacher messaging is useful but creates expectations about response times; decide the policy first, then build to it.

Arabic, English and sometimes French

Many schools and centres in Lebanon and the GCC work in more than one language. A bilingual portal is not just translated labels: it needs right-to-left layouts in Arabic, student names stored in both scripts where you use them, report cards that print correctly in each language, and notices that go out in each family's preferred language. This is far easier to plan from the start than to retrofit. My post on bilingual Arabic and English builds explains what doing RTL properly involves.

Privacy and access

A school portal holds information about children and families, so access control is not optional. At a minimum:

Check which data protection rules apply to you and tell your developer early. Encrypted connections, tested backups and a patched server should be standard on any build.

What to leave out of version one

It is tempting to list every feature above and ask for all of it at once. A better path is to launch with the parts that remove the most daily pain, get staff and families using it, then add the rest.

A sensible first version for many institutions is: student and guardian records, classes and enrolment, timetables, attendance, fees with payment recording and reminders, and notices. Grades and report cards often come next, timed for the end of a term, with assignments and messaging after that.

Also plan the move from your current tools. Student lists, family details and fee balances usually live in spreadsheets, and they need cleaning before import.

Web portal or mobile app?

For most institutions, a responsive web portal is the right start: the office works on desktop, teachers on a phone or laptop, and parents open a link from a notification. One codebase, every device, no app store review.

A mobile app becomes worth it when parents and students use the portal daily and you want reliable push notifications and a home-screen presence. Because I build web portals with Next.js and mobile apps with React Native, both can share the same backend, so starting on the web does not mean starting over later.

How I build it

The stack I use for portals like this is a Next.js web app, a .NET Core or Node API depending on the project, and a Postgres database, deployed with Docker on a Linux server with automated deployments through CI/CD, monitoring and daily backups. It is the same approach I used for NeonTask, a field-service platform I built solo with a Next.js web app, a .NET Core API and a React Native app for technicians: several roles sharing one system, each with its own view.

I usually work in stages: map your roles, academic structure and fee rules; agree the first version; build the office side first, then teachers, then families, with a staging version you test throughout; import and clean your data; and launch at the start of a term where possible.

Timeline and cost depend on how many roles you need at launch, how complex your grading and fee rules are, how many languages you work in, and how much data needs migrating. A clear brief is the fastest way to a useful estimate.

You can see what I build on the custom portal and CRM development page and in my work. If you run a school, academy or training centre and want a portal that fits how you actually operate, send me an email or book a call with a short description of your setup, and I will tell you how I would approach it.

More from the blog

Let's work
together