Skip to content
DotEdx
School & college · one institution

Every decision,
on the record.

DotEdx runs the whole institution — admissions, attendance, fees, exams and approvals — and keeps an append-only trail of who decided what, and against which answers. The evidence an accreditation visit asks for is a report, not a scramble through registers.

School and college campuses together Parent and student portals Fees in rupees, to the paisa

15 Modules, from the enquiry pipeline to the placement offer ledger
4 Separate sign-ins: platform, staff, parent and student — each with its own shell
2 Campus types under one institution, so a trust running both is one tenant
0 Recorded decisions anyone can quietly rewrite — the log is append-only

Workflow, not CRUD

A leave request is a route, not a row.

Most school software stores the form and leaves the deciding to WhatsApp. DotEdx models the chain: who it reaches, in what order, what they could see when they signed it, and what they said. Leave, outreach, workshops, internships and any form you build yourself all travel the same way.

Student raises a leave application Class teacher whoever heads their section Principal decides, from their own queue Register written once, never edited
  • The chain is yours to configure

    Build a request type, add the fields you need, order the approval steps. A step can name a role, a specific person, or whoever heads the student's own class.

  • Nobody approves their own request

    When the chain resolves to the person who raised it, that rung is recorded as not deliberated rather than quietly skipped — so the trail keeps its real length.

  • Answers are sealed once an approver sees them

    Returning something for changes forks a new version instead of overwriting the old one, so an approval always points at the exact content that was signed.

  • One decision per step, enforced by the database

    Two people holding the same role cannot both record an approval by clicking together — the second one is refused, not merged.

Modules

The whole institution, switched on per school.

Every module is sold and switched on separately, and a campus only ever shows what fits it — degree programmes and placements on a college, report cards on a school.

Students & admissions

The enquiry pipeline through to an admitted student, the student master, classes and sections, and the guardian records the parent portal signs in against.

Attendance

Daily marking by the teacher assigned to that section, at-risk thresholds surfaced on the dashboard, and alerts to the guardians who need them.

Fees & finance

Fee structures, demands, counter receipts with their own numbering, dues tracking — and online collection into the institution's own merchant account, never a pooled one.

Examinations & results

Terms, papers and mark entry for schools with printable report cards; internal and external marks with SGPA, CGPA and transcripts for colleges.

Timetable & staff

A weekly period grid that refuses to double-book a teacher or a room, alongside staff records, staff types and leave.

Library, transport & hostel

Catalogue with issue and return, routes and vehicles with their drivers, and room-and-bed allocation for residential campuses.

Communication

Announcements and notices that go out over your institution's own WhatsApp or SMS account and email relay, with a delivery record per message.

Programmes & placements

For colleges: degree programmes, semesters and credit-bearing courses, then drives, employers, applications and the offer ledger.

Approvals

The request types, the chains they travel, the principal's queue, and the register every decision lands in. The module the others lean on.

Who signs in

Four shells, because four jobs.

Nobody sees a screen that would render empty for them. A teaching staff member gets attendance for their own sections; a principal gets everything, read-only, plus the queue only they can clear.

Administrator

Runs the institution

  • Every campus and module the institution bought
  • Staff accounts, roles and staff types
  • Settings, including its own relays and merchant keys

Principal

Sees all, changes little

  • Read-only across every screen in the institution
  • The approval queue, and the authority to decide
  • No accidental edits to somebody else's register

Staff

Scoped to the job

  • One role, many types: teaching, office, accounts, library
  • Teaching staff mark attendance for their assigned sections
  • Accounts reach fees; the library reaches the catalogue

Parent & student

Phone, not password

  • Sign in with a code sent to the registered number
  • Parents: attendance, fees, receipts, results, notices
  • Students: raise leave, outreach and internship requests

Accreditation & reporting

Evidence, collected as you work.

NAAC, NIRF and an affiliating university all ask the same kind of question: show us what happened, who authorised it, and when. If that lives in registers and chat threads, every cycle becomes a reconstruction.

Here, each decision is written once and never edited — it names the step, the approver, the role they held and the version of the answers in front of them. The report is a query over work already done.

Bring your campus onto one record.

If your institution is already set up, sign in with the work email your administrator issued. Parents and students use the phone number the office holds — no password to forget.