Xirag Register for early access

Xirag for Education

Xirag education for school management

For schools, colleges and universities: admissions, student records, attendance, timetables, exams, fees, transport, hostel and library on the same core as every Xirag module, with named seats, maker-checker approvals and an audit trail you can prove.

Register for early access See the capabilities

Education modules are planned; fees run on Xirag Payments. Every workflow works for people on their own. Agents are not offered at launch; they are provided on request later.

Xirag for Education · Student journeyDemo
  1. Enquiry
  2. Admission
  3. Fees
  4. Classes
  5. Exams
  6. Certificate
  • CRMEnquiry from Ananya's guardian (demo), call logged
  • eSignAdmission form and consent signed by the guardian
  • PaymentsTerm 1 instalment paid to the student's virtual account
  • CheckerMark change in Maths approved by the head of department
Illustrative mock-up with fictional demo data; most steps are planned education modules, not a live console.
Capabilities

Education ERP for everything a campus runs

From the first enquiry to the final certificate, each area builds on Xirag modules that already share people, departments, approvals and the audit trail.

  • Admissions and enquiries

    Enquiry forms on your website, every call and visit on one timeline, admission stages and signed forms.

    Planned · builds on CRM, Website Builder, eSign

  • Student records

    Student and guardian profiles, documents, promotions and transfers, across every campus of a trust.

    Planned · builds on Contacts, Admin

  • Attendance

    Daily and period attendance for students and staff, leave requests and same-day absence alerts to guardians.

    Planned · builds on Calendar, Messenger

  • Timetable

    Periods, rooms, teacher loads and substitutions, and exam schedules on the shared calendar.

    Planned · builds on Calendar, ToDo

  • Exams and report cards

    Assessments, mark entry with a second approver for changes, grading schemes, report cards and transcripts.

    Planned · builds on eSign, audit trail

  • Fees and scholarships

    Fee schedules per session, instalments and late fees, concessions and scholarships, receipts and statements.

    Planned · builds on Xirag Payments

  • Transport and hostel

    Routes, stops and riders; rooms, allocation and mess; their fees as fee heads, their vendors under contract.

    Planned · builds on CLM, Payments

  • Library

    Catalogue, issue and return, holds, and fines that land on the student's fee account.

    Planned · builds on Payments

  • Parent and student communication

    Notices, messages and calls to guardians and students, and one app for attendance, marks and fees.

    Planned · builds on Messenger, Dialer, Gate

  • Staff and payroll links

    Staff in departments with delegated admins per campus, and their work on named seats; payroll through an export or a partner.

    Planned · builds on Admin

  • Analytics

    Enrolment, attendance, results and fee collection dashboards, drawn from the same records and audit events.

    Planned · builds on the shared core

Beyond a campus ERP

What one agentic core changes

A campus system keeps records. Xirag also keeps who is responsible, who approved what, and a record nobody can quietly rewrite.

  • Seats outlive staff changes

    "Class teacher 7B" or "Fee accounts" is a seat. When a teacher leaves mid-year, the seat's tasks stay with the seat.

  • Agents that draft, people who decide

    On request, agents can draft timetables, flag students at risk from attendance and marks, chase overdue fees and prepare report-card comments, and a person approves each. Agents are not offered at launch; they are provided on request later.

  • Maker-checker on marks and waivers

    A mark change, a fee waiver or a scholarship needs a second person to approve it, and the approver is never the one who asked.

  • A record that cannot be quietly edited

    Marks, certificates and fee changes are written to an audit trail where each entry is linked by hash to the one before, so an edit shows.

  • Signed admissions and consent

    Admission forms, guardian consent and transfer certificates go out for signature with Xirag eSign.

  • An admissions funnel, not a list

    Every enquiry, call and campus visit sits on one timeline in Xirag CRM, so no prospective family falls through.

  • One login for everyone

    Staff, guardians and students sign in once, with codes or push approvals, or through the institution's own identity provider.

  • Built for trusts and campuses

    Departments and delegated admins per campus, with the whole trust visible to the people allowed to see it.

Fees powered by Xirag Payments

Fee collection on a real payments stack

Fees run on Xirag Payments, the stack Xirag provides to payment aggregators and gateways, with versioned APIs and signed webhooks for the portals you report to. Xirag Payments is in development and runs in a sandbox; money movement is partner-backed.

Explore Xirag Payments
  • Fee schedules per sessionWith an approval record
  • Instalments and late feesOn every fee demand
  • Concessions and scholarshipsApproved by the head of institution
  • Refund on withdrawalBy a dated deduction schedule
  • A virtual account per studentBank transfers matched to the student
  • Split to trust and hostel accountsAllocation by fee head, partner-backed
  • Student ledger and reconciliationYearly fee statements
  • Counter receiptsCash, cheque and demand draft
Trust for student data

Built to protect the people you teach

Student and guardian data deserves more than a password. These are the principles the product is designed around.

  • Audit trail

    Every change to a record is written with who, when, before and after, linked by hash to the entry before it.

  • Maker-checker

    Sensitive changes need two people: one asks, another approves, and both are on the record.

  • Consent first

    Guardian consent is recorded per purpose before a student's data is shared, and every consent is on the audit trail.

  • Role scopes

    People see what their role and department allow. An agent, when a client asks for one, acts only within the scopes of its seat.

These are design principles of the product, not certifications.

Early access

Shape Xirag for your institution

Register for early access, or tell us how your school, college or university runs admissions, exams and fees today.

Register for early access Talk to us