Acadlas School is in development
Your whole school, connected.
Acadlas School is being designed to bring admissions, classes, attendance and fees into one place. Enter a student once, and their record follows them everywhere it's needed.
Acadlas School is being designed to cover:
- Admissions
- Classes and sections
- Attendance
- Fees
- Staff and roles
- Reports
Why Acadlas School
Today, one student lives in seven places.
An admission register, a fee spreadsheet, a receipt book, a phone full of guardian messages. Every change has to be copied by hand, and the copies drift apart.
In Acadlas School, they live in one record.
Admission, guardian, class, attendance and fees are designed to stay attached to the student. Update something once and every screen that needs it sees the change.
Illustration with sample data. Aarav Sharma is a made-up student, and these are not real records.
How it works
From setup to fee receipt, in one flow.
The intended workflow, in six steps that each build on the last. Scroll to watch one made-up student's record fill up.
- 1
Set up your school
Add your school, board, academic year and terms. Everything after this builds on it.
- 2
Shape the academic structure
Create classes, sections and subjects once, then carry them into every new year.
- 3
Admit a student
Capture the student and their guardian in one form, so nothing has to be typed twice.
- 4
Place them in a class
Assign a section and a roll number. Class lists and registers update on their own.
- 5
Take attendance
Teachers mark the register from their phone. Every absence lands on the student’s record.
- 6
Track fees
Fee plans, payments, receipts and balances, all tied to the same student.
Interactive prototype
Try three everyday jobs on sample data.
A first look at how admissions, attendance and fees are meant to feel, from the school office and the classroom.
Illustrative prototype. Everything here is made-up sample data that stays in this browser tab. It is not connected to a school database, nothing is saved or sent, and reloading the page resets it.
Class 6-B register
Tap a student to switch between present, absent and late.
Aarav Sharma
Sample student, Class 6-B, fee plan for 2026–27
| Instalment | Amount | Status |
|---|
Still due this year
₹13,000
₹13,000 of ₹26,000 paid
Sample receipts will appear here. No real payment is taken.
Admit the sample student and their record appears here, linked to class, guardian, fees and attendance. Nothing is saved.
Core capabilities
What Acadlas School is being designed to manage.
Six areas of everyday school administration, all built around the one student record. Each is marked with where you can see it on this page.
- In the prototype
Admissions
Bring a new student in without retyping anything later.
- Student and guardian details captured in one form
- An admission number and a record from day one
- The student appears in their class straight away
- In the walkthrough
Classes and sections
Set up the academic structure once, then carry it forward.
- Academic years, terms, classes, sections and subjects
- Roll numbers and class teachers
- Moving a student updates their class list and register
- In the prototype
Attendance
A register teachers can mark from the classroom.
- Present, absent and late, class by class
- Designed for ordinary phones
- Every absence kept on the student’s own record
- In the prototype
Fees
Know what is due, what is paid and what is left.
- Fee plans by class, split into instalments
- Payments, receipts and running balances
- Fees tied to the same student as everything else
- Planned
Staff and roles
The right people see the right things.
- Teachers, office staff and principals
- Class teachers assigned to their sections
- Access that follows the role
- Planned
Reports
Answers from the records already there.
- Class lists and attendance summaries
- Fees due and fees collected
- Printable, so nothing is re-entered into a spreadsheet
Design commitments
Software that holds a school’s records has to earn trust. These are the principles the build is following. They are not features you can use today, and they are still being built and verified.
Each school’s data stays separate
Acadlas School is designed so that one school can never see another school’s records.
Permissions checked on the server
Access is meant to be enforced by the server, not just hidden on screen.
Made for everyday phones
Registers get marked in classrooms, so every screen is designed for a phone first.
A trail for important changes
Fee receipts and admission edits are intended to record who changed what, and when.
FAQ
Questions schools ask
Can our school use Acadlas School today?
Not yet. Acadlas School is in development and isn't available to schools. This page shows what we're building and how it's meant to work.
What is in the prototype on this page?
A small interactive illustration of admissions, attendance and fee recording, running on made-up sample data in your browser. It is not connected to a database, nothing you enter is saved or sent anywhere, and it resets when you reload the page.
Which schools is it for?
Schools that run classes and sections, terms, attendance registers and fee instalments.
Will teachers be able to use it on their phones?
That is a design requirement from the start. Taking attendance, checking a class list or looking up a student should all work on an ordinary phone. The prototype is a first look, not a finished mobile app.
How will you keep our school’s records private?
Keeping each school’s data separate, and limiting what each role can see, are design commitments for the build, to be enforced on the server. They are not finished or independently verified yet, so we do not claim them as working today.
How much will it cost?
Pricing hasn't been announced yet.
One student. One record. One school.
Acadlas School is in development, starting with the jobs every school does daily: admissions, classes, attendance and fees. The prototype above runs on sample data only.