Skip to content

One operating system for your entire school

Admissions, student records, academics, fees, attendance, staff, parent communication and school operations run on one connected platform — not six that have to be reconciled.

Built for private schools, international schools, preschools and multi-campus groups. 54 modules available today.

Everything your school needs. Connected.

Schools usually buy an SIS, an accounting package and a messaging tool, then spend the year reconciling them. MyCampusView is one system on one database — the student record admissions created is the record fees invoices, the register marks and the report card is built from.

Nothing above is synchronised overnight. There is one row, and these are eight views of it.

54Modules available today3 more in build, 8 planned — each labelled as such on this site.
1Database behind all of themA fee, an absence and a result read the same student record. Nothing is synced between systems.
11Roles out of the boxAdministrator, principal, teacher, accountant, librarian, transport manager, driver, front desk, HR, parent, student — plus custom roles per school.
100%Of queries scoped to one schoolSeparation is enforced in the data layer and covered by tests that fail the build if a query could cross it.

Everything that isbuilt today.

54 modules are available now, 3 are in build and 8 are planned. Only what works today is named here.

Classes & sectionsSubjectsTimetableHomeworkClassworkAcademic calendarExaminationsMark entryGrading schemesResultsReport cardsCertificatesStudent recordsParents & guardiansStaff recordsStudent attendanceAttendance reportsStaff attendanceLeaveEnquiry captureAdmission pipelineFollow-ups & call logsConversion analyticsOnline enquiry formFront office & visitorsEnrol as a studentFee structuresInvoicesFee collectionPayments ledgerOutstandingConcessionsNoticesMessagesEmail deliveryTransport routes & stopsBuses & driversLive trackingLibraryInventoryEventsSportsSchool websiteAdministrator dashboardAsk MeReports & analyticsHealth scoreFeedbackRoles & permissionsBrandingAudit trailCustom domainMessage templatesProgressive web app

Admissions

Every enquiry on the system from the first phone call.

Admissions is where schools lose the most information and notice it the least — a name on a notepad, a follow-up nobody owned, a family who visited twice and was never called back. MyCampusView records the enquiry today; the pipeline that works it through to enrolment is the release we are building now.

What works today

The enquiry is a record, not a note
A parent who calls or walks in is recorded against the family, with the child, the class they are asking about and where the enquiry came from.
New enquiries are on the dashboard
The administrator’s first screen lists the newest enquiries, so nothing sits unseen in a counsellor’s notebook until somebody asks.
Admission creates the student
When a child joins, the student record, the enrolment and the guardians are written in one step — and the fee structure for that class applies from the same moment.

The pipeline we are building

In build
  1. 01Enquiry
  2. 02Visit
  3. 03Application
  4. 04Offer
  5. 05Enrolled

Drawn from the specification, not from the product. Stage-by-stage tracking, follow-ups with an owner and a date, counsellor assignment and conversion reporting by source are in build — we will tell you the same thing on a call, and show you the enquiry capture that does work.

What sets it apart

Three things a school uses every week, not once at setup.

Ask Me answers from live records. Feedback runs both ways. The health score is built from attendance, marks, homework and fees already in the system — not from a survey nobody fills in.

Ask Me

Speak a question. Get a figure from the school’s own data.

The assistant calls the same services the screens use — attendance, fees, students, classes — with the signed-in user’s permissions. It drafts a notice for approval; it never sends one on its own.

  • School overview — Students, staff, today’s attendance and fee totals
  • Unmarked registers — Sections that have not marked today
  • Attendance report — By class and date range
  • Fees outstanding — Balances still owed, by class
  • Fees collected — Payments in a date range
  • Fee invoices — Find and summarise invoices

Demonstration

Sample shape of an answer — not a live school

Looking up fees outstanding

Forty-one invoices still have a balance, totalling ₹2,48,600. Class 9 holds the largest share. Open Outstanding to chase them — I have not changed anything.

Verify at Outstanding fees. Names and money stay as the tools returned them.

One record. Three products that read it.

Total students

1,284

+1%since last month

94 teachers on staff

Attendance today

94.2%

1,210 present · 74 absent

Collected this month

₹18,40,000

+8.4%since last month

212 payments

Outstanding

₹4,20,000

−12.5%since last month

22 families past due

Academic overview

Head count and attendance by month

AprMayJunJulAugSep
  • Students
  • Attendance %

Fee collection

Across all issued invoices

₹18,40,000

Collected

  • Collected₹18,40,000
  • Pending₹6,40,000
  • Overdue₹4,20,000
  1. CRM

    Admissions & enrolment

    Enquiries land on the system rather than in a counsellor’s notebook, and an admitted child becomes a student record without being typed a second time.

    Admissions & enrolment
  2. SIS

    Student Information System

    One record per student, holding what the school knows about them — and the record every other module reads rather than keeping its own copy of.

    Student Information System
  3. ERP

    School operations

    The office side: fees defined once and collected at the counter, staff and leave, transport with live tracking, and a dashboard that reads today’s figures.

    School operations

Parents and teachers

The office stops answering the same three questions.

Was she marked present. What is the homework. How much is left to pay. Parents can see their own children and nothing else — enforced in the data layer, not by hiding a menu.

  • Attendance, day by day
  • Homework and classwork
  • Fee balance and receipts
  • Results and report cards
  • Notices from the school
  • Their child's bus, live

Teachers work from the same records, on whatever they have in hand

Registers are marked in the classroom on a phone, homework is set from the same screen, and marks are entered against their own classes and nobody else’s. Nothing is collected on paper first and typed in later.

Monday, 11 August

Good morning, Meera

Aarav Sharma

Class 7 · A

Present

Bus 02 · Route 2

Arriving Green Park Market

in about 6 minutes

Fees

Term 2 balance₹30,000

Due 15 September

Homework

Mathematics — exercise 7.2

Due tomorrow

Integrations

Connected to the things a school already uses.

Messaging and payments run through your own accounts rather than ours, so the sender is your school and the money lands in your bank. Below is what is live, what is connected during setup, and what is not built.

Reaching parents

Every message is addressed from the records that hold the numbers, so a changed phone number is changed once.

  • EmailAvailable

    Transactional and bulk email from the school’s own address and domain.

  • SMSConnected at setup

    Template-based SMS through the school’s gateway account, metered per school.

  • WhatsAppConnected at setup

    Template messages through a WhatsApp Business account the school owns.

  • Mobile notificationsConnected at setup

    Push notifications to the parent and teacher experience on the phone.

Money

Payments reconcile against the invoice they were raised from, so collection and outstanding never disagree.

  • Payment gatewayConnected at setup

    Online fee payment with server-created orders and signature-verified callbacks.

  • TallyPlanned

    Export of collection and ledger data into Tally.

On campus

Hardware and location data land on the same records the office already works from.

  • Vehicle trackingAvailable

    Live bus position on a map, per route, from the device on the vehicle.

  • Biometric attendancePlanned

    Device-driven attendance for staff and students.

  • ID card & barcodePlanned

    Card printing and barcode identification for library and attendance.

Identity & platform

How your school’s own systems and domain meet MyCampusView.

  • Custom domainAvailable

    The application and the school website on a domain the school owns.

  • Google Workspace / Microsoft 365 sign-inPlanned

    Staff signing in with the account the school already issues them.

  • API accessConnected at setup

    A versioned HTTP API for reading and writing school data.

Available
Running in production today.
Connected at setup
Built and metered inside MyCampusView. We connect your own vendor account during implementation.
Planned
On the roadmap. Not available today, and we will say so on a call.

Security

Your school’s data deserves more than a badge on a website.

Schools hold children’s addresses, medical notes, photographs and transport stops. That is the reason for the architecture below, and the reason we are specific about it rather than reassuring.

Separation between schools

Every query carries the school it belongs to, enforced in the data layer below the screens. Reading another school’s record by guessing its key returns nothing; passing another school’s id in a filter is overwritten with your own. Tests cover each of those cases and fail the build.

Sessions that can actually be revoked

Opaque session tokens with 256 bits of entropy, stored only as hashes. Not tokens that stay valid until they expire — signing a device out, or changing a password, ends those sessions immediately.

Passwords stored as bcrypt hashes

Hashed with bcrypt at cost 12, with a length-first policy. Nobody at MyCampusView can read a password, and support will never ask for one.

Brute force made expensive

Eight failed attempts lock an account for fifteen minutes, and rate limits apply per account and per address, so neither one account nor a spray across many gets far. Every attempt is recorded with its address.

Access follows the role

Permissions are checked in the service layer rather than by hiding a menu item. A parent reaches their own children; a teacher marks their own classes; the API refuses what the screen would have refused.

An audit trail on what matters

Fee collection, result publication, permission changes and administrative overrides are written down with the person and the time.

Implementation

Getting started with MyCampusView is a term’s work, not a year’s.

A single-campus school of a thousand students is usually live in about four weeks. Migration is the part that takes the time, and we reconcile the totals with your office before anybody signs in.

  1. Week 1

    01Discovery

    We go through how your school runs today — what is on paper, what is in spreadsheets, what your current software does badly. Half a day, usually with the principal and the head of accounts.

  2. Weeks 1–2

    02Configuration

    Classes, sections, subjects, fee heads, grading schemes, roles and branding are set up as your school actually uses them, not as a default template.

  3. Weeks 2–3

    03Data migration

    Student records, guardians, fee history and staff are brought across from whatever holds them now. We reconcile the totals with your office before anyone signs in.

  4. Weeks 3–4

    04Training

    Separate sessions for the office, for teachers and for whoever will administer the system. Short, on your own data, and recorded so a new joiner can watch them.

  5. Week 4

    05Launch

    Attendance and fees go live at a term boundary wherever possible. Parent sign-in is opened once the office is comfortable, not on the same day.

  6. Ongoing

    06Support

    A named contact for the first term, then ongoing support. Every release is applied for you; there is nothing for your IT team to install.

Ready to run your school on one platform?

Tell us how your school runs today — what is on paper, what is in spreadsheets, what your current software does badly. The demonstration follows that rather than a script, and we will be straightforward about the modules that are not built yet.

What a demonstration involves

  • Thirty to forty minutes, on a call, with your screen or ours
  • Roughly how many students and staff you have
  • What you use today for fees and attendance
  • Whether you run one campus or several

No obligation, and no pricing pressure on the first call. If MyCampusView is the wrong fit for your school we would rather say so then.

MyCampusView — school management software, SIS and admission CRM on one platform · MyCampusView