Gritticon SMS · Pilot cohort open
The register, the notebook, the staffroom approval chain — that is competence, not chaos. Gritticon SMS puts the school’s existing way of working on screen: attendance, timetable, exams, payroll, transport, and a parent app carrying your school’s name. Built for India’s CBSE, ICSE, and state-board schools.
The platform, counted
Not projections. Every figure here maps to something you can open on a screen during the walkthrough.
17
Modules
From attendance to admissions — switched on per school.
250
Permissions
Atomic capabilities your school assembles into its own roles.
5
Action types
View, create, edit, delete, manage — granted one at a time.
2
Apps
The staff platform, and a parent app under your school’s name.
Why schools keep it
Staff are fast and confident with their manual ways for a reason. Software that demands they abandon that becomes a data-entry chore done after the real work. SMS starts from the existing routine and removes friction from it — if anyone still runs a parallel register, we treat it as our defect to fix.
Every school names and organises itself differently. So we ship fine-grained capabilities — the atomic things a person may be allowed to do — and your school assembles them into roles under the names you already use. Two schools with different org charts both get exactly their structure.
A class teacher sees her room. A coordinator sees 10-A, 10-B, 10-C. The principal sees the school. Access is scoped to classes and sections, so nobody drowns in matters that were never theirs — and nobody is answerable for work they never owned.
Payroll, attendance summaries, promotions — the system prepares the tedious part and presents it for a human decision. Every approval is stamped: what the system calculated, who approved it, and when. The audit trail is there to protect your people, not to police them.
Leave slip → coordinator → principal is not bureaucracy; it is how accountability is shared in a school. SMS keeps your approval flows and makes them faster — it never bypasses authority.
Every automated path has a visible manual escape hatch. The knowledge that “I can always fix it myself” is exactly what lets staff trust the automated way.
Every desk in the building
Roles are not shipped by us — your school assembles them. But these are the people whose Tuesdays we designed around.
The whole school, without asking anyone for it.
The desk everything passes through.
Her room, and nothing that was never hers.
Three sections, scoped exactly.
Payroll that survives being questioned.
Routes, stops, vehicles — same login as everyone else.
One group, many schools, no bleed.
One app, one child, no permission maze.
Access, honestly done
Most systems answer one of these and call it access control. A school needs all four.
01
Modules your school has chosen — nothing you didn’t ask for cluttering the screen.
02
View, create, edit, delete, manage — granted per action, assembled into roles your school defines and names.
03
One section, one class, or the whole school — authority scoped the way schools actually delegate it.
04
Their own child. No roles, no permission maze — identity and ownership, nothing else.
Going live
No big-bang cutover. We move one desk at a time, and the register stays open until nobody reaches for it.
01
Not a requirements document — a working day. Which registers get opened, who signs what, which WhatsApp group carries the real information. We map the school as it runs, including the parts nobody would put in a brochure.
02
Classes, sections, subjects, departments, and your role names — assembled from capabilities into the exact org chart you already have. Nothing is renamed to suit us. If your school calls it Incharge, the screen says Incharge.
03
We start where the pain is loudest — usually attendance or fees — and get that desk fully working before touching the next. A staff member learns one screen, not a system.
04
We do not ask anyone to stop their manual method on day one. When a desk stops reaching for the register on its own, that desk is done. If it never stops, that is our defect to fix — and we come back and fix it.
05
The parent app goes live only once the staff side is trustworthy. A parent seeing wrong attendance is a harder problem than a parent waiting two weeks longer.
Trust, shown not claimed
Every claim on this page is something we can open and show you during the walkthrough. If we cannot show it, it is not written here.
250 individual capabilities across 17 modules, each in five flavours — view, create, edit, delete, manage. Your school assembles them into roles under your own names. Nobody receives a bundle of authority they did not ask for.
Permission answers what a person may do; scope answers over whom. A class teacher is granted her room, a coordinator her sections, the principal the school — so nobody drowns in matters that were never theirs.
Consequential operations record who acted, what changed, and when. It is written in language a principal can read, kept module by module, and survives a module being renamed — history is never stranded by a label change.
Every record belongs to a school and is filtered by it on the way out — a property of how the data is built, not a setting somebody has to remember to switch on. Campuses in a group do not see each other.
Every permission and scope check runs on our servers, not in the browser. The screen decides what to draw; it never decides what you are allowed to do.
Data is encrypted in transit and at rest, backed up automatically, and sessions are scoped per school and user with automatic expiry. Documents and images are stored apart from the records that reference them.
Know Your Child
KYC is the companion app for parents and students, white-labeled per school: your logo, your colours, your name on the app stores. The feed comes first — sports day, the science exhibition, the annual-function rehearsal — so fees arrive as a line in a story the parent is already part of.
Asked by real schools
No. The staff platform runs in a browser — any reasonably modern device with an internet connection. The parent and student app is a normal install from the app stores. There is nothing to put on a server and nothing for an IT department to maintain.
It comes with you. Students, staff, classes, and historical records are imported before you go live — we do the mapping, not your office staff. We start the import from whatever you actually have, including spreadsheets that were never meant to be a database.
Good — that is the case we built for. We do not ship a fixed set of roles. We ship 250 individual capabilities, and your school assembles them into roles under the names you already use. Two schools with completely different org charts each get exactly their own.
We go desk by desk rather than all at once, so the honest answer depends on how many desks you want moved and how your data arrives. What we commit to is that no desk is called done until the person at it has stopped reaching for their register on their own.
That is the only question that matters, and it is on us, not on them. If a teacher keeps a parallel register, we treat it as a defect in our product and come back to fix it — we do not treat it as a training problem or a discipline problem.
Yes. The app is white-labeled per school — your name, your logo, your colours, published under your school on the app stores. Parents are not asked to download something called Gritticon.
No. The system does the tedious part and stops. It calculates the payroll, prepares the attendance summary, proposes the promotion list — and then a person approves, with a record of who approved and when. Every automated path also has a visible manual override.
Each school’s records are scoped to that school, filtered on the way out, and encrypted in transit and at rest. Within your school, visibility is whatever your roles and class scopes say it is. Campuses in a group do not see one another.
Pricing is per school, billed annually, and starts at ₹50,000 per year — it depends on which modules you switch on and your size, never on how many students you enrol. We publish the starting price rather than making you ask, and we would rather quote you exactly after seeing how your school runs.
Your data is yours and you can export it. We would rather lose a school cleanly than hold one hostage — a school that stays because leaving is painful was never really a customer.
Support is available in English and Hindi today. Regional-language interfaces are on the roadmap and not yet shipped — we would rather tell you that than imply otherwise.
Bring your registers, your Excel sheets, and your WhatsApp groups. We’ll show you the same day, lighter.