Demo Handbook

Metatroncube School ERP

One system a principal, a front-office clerk, a teacher, an accountant, a parent and a student can each log into and see their own job on screen — nothing borrowed from another product, nothing a school has to be trained around for a week.

What this document is

A field guide for running the live demo

This handbook explains what the product does, how the screens fit together, and gives the exact walkthrough for showing it to a school — in the order it lands best. It deliberately stays away from how any of it is built; that part is ours to keep.

The demo runs on a fictional school, St. Aloysius Public School, Coimbatore — 840 students, Grades 1–12, CBSE board. A second persona, Waterloo Heights Academy, Ontario (620 students, Grades 1–8), exists for Canadian prospects and doubles as the closing beat: the same system, rebranded, in minutes.

Before you open the call

The demo cast & their logins

Six people, six logins. Every login below is a real, working account in the demo database — log in as whichever person's story you're telling.

RoleNameLoginPasswordSees
Principal / Admin Rekha Nair demo1234 Everything — every dashboard, every module
Front Office Sunitha R demo1234 Admissions, student records, the fee counter
Teacher Arun Prakash demo1234 His own classes only — attendance, marks
Accountant David Fernandes demo1234 Fees, invoices, payments
Parent Meera Krishnan demo1234 Her two children only
Student Aditya Krishnan · Grade 8-A demo1234 His own record only

Meera has two children — Aditya (Grade 8-A) and Ananya (Grade 5-B). Ananya has no login of her own; she's reached through the child switcher inside Meera's parent login. That switcher is deliberate — it's the single most convincing feature in the whole portal, so give it real screen time rather than rushing past it.

The same password everywhere is a demo convenience only. A real school rollout issues its own credentials through a proper invite-and-reset flow — never say "demo1234" is how a live school would actually work if asked.

How the product is organized

Nine areas, one shared record of the school

Every area below reads from and writes to the same underlying student, so nothing ever needs re-entry between them — an admission becomes a student, a student's enrollment decides their fees, their class, their timetable and what their parents can see.

01

Student & Academic Records

The academic calendar, programs and grades on offer, sections within each grade, rooms, every student's profile, and every guardian linked to them. A student's enrollment for the year is the one thread everything else follows.

02

Admissions

A public application form outside any login, a visual pipeline from Applied through to Accepted, and a one-click Enroll that turns an applicant into a full student record with every field and document carried over.

03

Fees & Payments

A fee structure set once per grade — tuition, lab, library, transport, priced separately — billed by term, concessions shown as a visible discount line, and online payment with an instant receipt.

04

Attendance

A class roster that opens with everyone marked Present by default; a teacher only touches the exceptions. Built for a phone, one-handed, in a corridor between periods.

05

Timetable

One shared weekly schedule seen from three angles — a student's own week, a teacher's own week, or any class's full week for admin staff. No teacher or room can ever be double-booked.

06

Examinations & Report Cards

Grading scales — CBSE, ICSE, IB, Cambridge, Ontario, plain percentage — are settings a school configures, not new development. Marks go in on one grid; grades and a print-ready report card follow automatically.

07

Parent & Student Portal

A secure outside login for guardians and students. Every screen shows only records for the people actually linked to that login — enforced by the system itself, on every single request.

08

Online Learning

Each class can carry its own lessons — a video, a handout, a quiz. Enrolled students see their courses automatically, the moment they're enrolled, with nothing to configure per student.

09

School Branding

A school's logo, colours and name apply everywhere — staff screens, the parent portal, every printed report. Because branding is a setting rather than something built in, running (or showing) a second school is minutes, not a rebuild.

The live demo, scene by scene

Eight scenes, in the order to run them

Each scene below is a real, complete piece of a school day. The story line is written to be read aloud, almost verbatim, as you click. Run them in this order — each one hands the next its setup.

1· Morning dashboard 2· Admission 3· Fees & payment 4· Attendance 5· Parent view 6· Marks & report card 7· Timetable 8· Online learning
01

The principal's morning

"This is the first screen Rekha sees at 8am."

  1. Log in as Principal (principal@demo.school).
  2. The dashboard is already on screen, above the fold: today's school-wide attendance percentage, this term's fee collection (collected vs. outstanding), admissions in progress by stage, and student strength by grade.
  3. Click through the attendance figure to see exactly which grades have dropped below 85%.
What this provesEvery figure on screen is computed live from real records — nothing here is typed in separately, and nothing reads zero because a feature isn't actually wired up.
02

A new admission

"A parent applied online on Sunday night. Here's Monday morning."

  1. Open the public application form in a fresh tab — no login needed. Fill in the student's name, date of birth, grade applied for, a parent's name, phone and email, and attach a birth certificate.
  2. Submit — the parent sees an application number on screen immediately.
  3. Log in as Front Office (office@demo.school): the new applicant is already sitting in the pipeline at Applied.
  4. Move it forward — Document Verification → Interview → Offered → Accepted.
  5. Click Enroll: the applicant becomes a full student record with an admission number, placed into a grade for the current year.
What this provesEverything entered on that public form Sunday night — including the attached document — is already sitting on the enrolled student's record Monday morning. Nobody retypes a single field.
03

Fees and a parent payment

"The fee structure is set once. Everything after that is automatic."

  1. As Accountant (accounts@demo.school), show Grade 8's fee structure — tuition, lab, library and transport priced as separate lines, billed across the term.
  2. Open Aditya's invoice for this term, generated straight from that structure.
  3. Apply a 15% sibling concession to his sister Ananya's invoice and show it recalculate live — as a visible discount line, never a quietly lower total.
  4. Switch to Meera's parent login. Open Fees, pay the term online through the test payment screen.
  5. Payment succeeds — a receipt is ready to download immediately, and the accountant's outstanding figure drops with no page refresh.
What this provesThis posts a real accounting entry, not a status flag — the exact same one the school's books use, updating everyone's screen at once.
04

A teacher takes attendance

"This is the thing teachers do every single day, so it has to be fast."

  1. Log in as Teacher (teacher@demo.school). He sees only his own classes.
  2. Open Grade 8-A, today's second period. The roster loads with every student already marked Present.
  3. Mark two students absent, one on leave. Submit.
What this provesUnder three taps for the whole class. Submitting the same roster twice never creates a duplicate. And Arun cannot open Grade 5-B by guessing a different link — that boundary is enforced by the system, not by a button someone remembered to hide.
05

The parent sees it immediately

"No phone call, no note in a diary."

  1. Switch straight to Meera's parent login, ideally in the same browser session — the contrast lands harder when it's immediate. The child switcher shows both Aditya and Ananya.
  2. Aditya's attendance already shows today's absence — seconds after Scene 4, not the next day.
  3. The month view shows the whole term's attendance pattern as a percentage.
  4. Switch to Ananya: her own, separate record.
  5. Live, on the call: try to open a different family's child by editing the page address directly — show that it's refused.
That refusal is the feature, not an apologyIt's a better answer to "how do you keep one family's records away from another" than any slide could be — show it happening, don't describe it.
06

Marks and a report card

"Term-end, and the report cards write themselves."

  1. As Teacher, open Grade 8-A → Mathematics → this term's exam. Enter marks for the whole class on one grid — tab key only, no mouse.
  2. Save — grades compute themselves straight from the CBSE grading scale.
  3. As Principal, generate Aditya's report card.
  4. The PDF opens: school logo, every subject, marks, grades, an attendance summary, the class teacher's remark, a signature block.
What this provesThe grading scale is a setting, not code — swap CBSE for IB or Cambridge and the grades on this same report change with no development. The PDF prints clean on A4, nothing clipped.
07

Timetable

"Everyone sees the same timetable, from their own angle."

  1. As Student (Aditya), view this week — day, period, subject, teacher, room.
  2. As Teacher (Arun), view his own week — where he's teaching, and when.
  3. As Principal, view Grade 8-A's whole week.
What this provesOne shared schedule, three honest viewpoints, readable on a phone screen.
08

Online learning

"And the classroom extends past the classroom."

  1. As Student, open Courses — "Mathematics: Algebra Basics" is already waiting there because he's enrolled in that class; nobody invited him by hand.
  2. Open it: a short video, a PDF handout, a five-question quiz.
  3. Take the quiz, submit, see the score immediately.
  4. As Teacher, see who in the class has finished it.
What this provesThe video plays inline, the score saves the moment it's submitted, and every enrolled student already has access — zero setup per student.
Not a scene — the last thing you show

The closing beat: rebrand to a second school

Same system
Different school

Swap the logo, name and colour scheme over to the second demo school — Waterloo Heights Academy, Ontario — and reload. Same system, a different school, done in minutes, live on the call.

This is the detail that justifies running one system across several schools rather than one installation per school: branding is a setting a school owns, not a rebuild a developer has to do for them.

St. Aloysius Public School

Coimbatore, India

Board
CBSE
Grades
1–12
Students
840
Currency
₹ INR

Waterloo Heights Academy

Waterloo, Ontario

Board
Ontario
Grades
1–8
Students
620
Currency
$ CAD
Answering honestly, without stalling the demo

If they ask about…

These are real, deliberate cuts for this demo — not gaps discovered live. Say so plainly and move on; it reads as confidence, not evasion.

RoadmapPayroll
RoadmapLibrary management
RoadmapTransport management
RoadmapHostel management
RoadmapInventory & assets
RoadmapAutomatic timetable generation
RoadmapWhatsApp integration
RoadmapBiometric / RFID attendance devices
RoadmapMultiple branches under one login
RoadmapStatutory financial report packs
Say this"That's on our roadmap — it isn't part of what we're showing today. Happy to talk timeline and pricing for it separately."
The question every school asks

How family data privacy actually works

A parent or student only ever sees records for people directly and individually linked to them on file — never because they simply hold a "parent" or "student" login in general. That link is checked again, freshly, on every single screen they open, for every child's fees, attendance, marks and timetable, with no exceptions carved out anywhere.

That's exactly why Scene 5's refused-access moment can be shown live rather than staged for the slide deck: the restriction isn't a setting someone has to remember to switch on, it's simply how every request is answered.