School ERP questions, answered plainly

Most school software is designed around the office's reporting needs, not the ten minutes a class teacher has between periods, so it puts attendance, marks and admin behind the same dense screens. Ecole starts from the opposite end: a class teacher opens their own section and marks only the absentees. What each role actually does shows the same idea applied across the school.

The teacher marks only the absentees; everyone else is left present by default, so there is nothing to tap for a child who turned up. Taking attendance for a full section this way is well under a minute, with no other timing claimed beyond that. It works from a phone, so a teacher without a laptop to hand is not blocked. See what a class teacher does each day.

Yes. Marks entry is a keyboard-first grid that behaves like a spreadsheet, so a subject teacher can move across a section entering scores without reaching for a mouse. It refuses a mark above the maximum as it is typed, naming the child and the part it belongs to, so a typo is caught immediately rather than after printing. A teacher can save partway through and return later.

Yes, for attendance. A class teacher can mark absentees from a phone, which is what makes a full section possible in well under a minute. Marks entry is a keyboard-first grid built for typing many scores quickly, which suits a laptop or tablet best. If your teachers mostly carry phones, attendance is where the difference shows first.

A class teacher can correct a past date, so an accidental mark is fixed once it is noticed rather than left wrong for the term. Because the default is present and only absentees are marked, a mistake usually means one name was tapped instead of another, which is easy to spot and undo. There is no separate error queue or ticket to raise; the teacher corrects it directly.

Yes. A class teacher can correct a past date directly, without needing the office to step in. This covers the ordinary case: a substitute who did not know the register, or a name tapped in error the day before. No separate approval step is described for this correction; it sits with the class teacher who owns that section.

Period-wise attendance is available as a per-school setting, switched on rather than the default. Daily attendance, taken once by the class teacher marking only absentees, is the default. If your school tracks attendance separately for every period, that mode exists, and either way the teacher marks absentees rather than the whole class present.

The principal can see, from their own dashboard, which sections have not taken attendance on a given day, without asking a class teacher to confirm by hand. This sits alongside the same dashboard that shows collections and dues, updating live rather than needing a report run. What a principal sees each day covers the rest of that view.

Ecole does not publish a training duration, since the honest answer depends on the teacher. What is built to lower it: attendance is marking absentees only, and marks entry is a keyboard-first grid that behaves like a familiar spreadsheet rather than a new interface to learn from scratch. A tool slower to pick up than the paper register would not get used.

Yes. Class teacher remarks reach the report card directly, so the person who actually knows the child writes the line a parent reads. This sits alongside marks entry, which a subject teacher completes only for their own subjects and sections. See what a class teacher does through the year.

Receipt numbers in Ecole are gapless, per school, per academic year, even when two accountants are taking money on two counters at the same moment. Each school keeps one counter row per year, advanced under a row lock in the same transaction as the payment, so a failed payment returns its number rather than burning it. Read more on zero-leakage fee counter management.

The ledger is append-only, so the wrong entry is never edited or deleted, by anyone, including us. It is corrected with a reversal that references the original entry, and both stay visible in the record. A reversal is dated the day it is made, never backdated, so the ledger shows when the mistake was found and fixed, not when it happened.

No. A payment is never edited or deleted by anyone, including JalsaX support staff. A genuine mistake is corrected with a reversal that points back at the original entry, so both remain visible rather than one quietly disappearing. This is deliberate: a ledger that can be altered after the fact is not one a correspondent can trust during an audit.

Yes. Receipt numbering is built for exactly this case: two accountants taking payments on two counters in the same second still get gapless, sequential numbers, because the counter advances under a row lock inside the same transaction as the payment. Each accountant can also correct only their own entries, and only on the day they recorded them; anything else needs the principal.

Yes. Fee collection covers cash, UPI, cheque and bank transfer received at the counter, and Ecole issues the receipt and keeps the ledger for each. These are recorded, not processed: there is no payment gateway involved, so the money itself moves however it already does at your counter, and Ecole's job is the receipt and the running record.

No, not in this version. Payments are record-only: whatever a parent hands over at the counter, in cash, UPI, cheque or transfer, gets a receipt and a ledger entry, but there is no payment gateway for a parent to pay from home. If online collection matters to you, say so plainly; it is more honest to tell you now than after onboarding.

It depends on the type. An accountant can grant rule-based concessions such as staff ward, sibling or RTE directly. Merit and discretionary concessions need a principal or correspondent to approve them. Every concession, whichever kind, carries a reason and an approver recorded against it. See what an accountant handles at the counter.

A late fine is available but off by default; a school switches it on if it wants one. Fee heads such as tuition, transport, books, exam and uniform each carry their own installments and term due dates, and a late fine sits alongside those as an optional setting rather than something applied without the school's say.

Yes, there is a Tally-compatible export of the day's transactions, built from the same day-book each accountant closes at the end of their shift, split by payment mode. This is meant for whoever reconciles your books, so the numbers going into Tally match the receipts issued at the counter that day.

Ecole keeps a defaulter list carrying the phone number to ring, and an accountant can also look up any single child by name to see exactly what is owed right now. Nothing here is a stored balance that can drift out of date; what a child owes is computed at the moment somebody asks. See what an accountant does day to day.

A day-book is the record of one accountant's collections for one day, split by payment mode, so the cash on hand can be counted and handed over correctly. Ecole produces this per accountant, per day, and the same data feeds the Tally-compatible export. Read more on fee counter management without leakage.

A bounced cheque is corrected the same way any wrong entry is: with a reversal that references the original payment, dated the day the cheque is found to have bounced, never backdated. The original receipt stays visible alongside the reversal, so the ledger shows both that the cheque was accepted and that it did not clear.

Not if the connection itself is down: Ecole needs an internet connection to work, and there is no offline mode. What it does allow for is a power cut at the office: attendance works from a phone over mobile data, so a class teacher with a charged phone and signal is not stopped by the electricity going, only by the connection itself failing.

No. Ecole needs an internet connection and there is no offline mode to fall back on. We would rather say that plainly than promise offline working that quietly loses a day's attendance or a fee entry when it fails to sync later. If your school's connection is genuinely unreliable, raise it with us before signing up, not after.

Yes, attendance is confirmed to work on a phone, which in practice means over mobile data when the office Wi-Fi is out. This keeps a class teacher's morning register unaffected by a router problem, so long as their own phone has signal. It does not remove the need for a connection altogether; Ecole cannot work with no connection at all.

Ecole needs a live connection to save anything, so an entry that has not reached the server is not recorded until it does. Beyond that general point, we have not published specific behaviour for a mid-entry drop, and we would rather say so than guess. If your counter's connection is unreliable at particular times of day, ask us directly before relying on it there.

Ecole is not published with a minimum speed requirement, only that it needs an internet connection to work at all, since there is no offline mode. Attendance is confirmed to run over mobile data on a phone. Beyond that general point, we have not stated a specific bandwidth figure, and it would be a guess to give you one here.

That depends on the connection where you are, not on Ecole: it needs an internet connection to work and has no offline mode, so patchy coverage shows up as the product being unavailable rather than working in a degraded way. Attendance running on a phone over mobile data helps where broadband is the weaker link, but some connection is still required.

No. There is no offline mode, so attendance, like everything else in Ecole, needs a connection at the moment it is entered; nothing is queued locally to sync afterwards. This is a deliberate honesty rather than an oversight: a sync-later design that occasionally fails silently is worse than one that tells a teacher immediately it could not save.

We have not built one, and we would rather tell you plainly than claim a feature we cannot stand behind. An offline mode that syncs later can lose or duplicate a day's attendance or a fee entry when the sync fails, invisibly until someone notices a number is wrong. See why schools abandon ERP software by month three for more on this kind of overselling.

Ecole ships an eight-point CBSE preset as a starting point: A1 for 91 to 100, A2 for 81 to 90, B1 for 71 to 80, B2 for 61 to 70, C1 for 51 to 60, C2 for 41 to 50, D for 33 to 40, and E below that. This is a preset your school checks and edits, not CBSE's own current circular. See our CBSE page for how it is set up.

The Telangana State preset in Ecole runs ten points: A1 for 92 to 100, A2 for 83 to 91, B1 for 75 to 82, B2 for 67 to 74, C1 for 60 to 66, C2 for 51 to 59, D1 for 41 to 50, D2 for 35 to 40, and E below that. It is a starting point the school checks and edits, not the board's own circular; see Telangana State board setup.

Exam schemes, including weightage per exam, are configuration per school per year, not fixed in the software. The Telangana State preset weights FA1, FA2, FA3 and FA4 at 5% each, SA1 and SA2 at 20% each and SA3 at 40%. The CBSE preset weights periodic tests, multiple assessment, portfolio and subject enrichment at 5% each and the annual examination at 80%. Compare both in CBSE vs state board grading.

Yes. Grade-only co-scholastic subjects are supported alongside subjects marked numerically, so a school is not forced to invent a number for something it grades on a scale instead. This sits within the same exam scheme configuration as theory and practical splits, set per school per year rather than hard-coded into the product.

Yes, where the exam itself splits theory and practical, Ecole keeps them apart in the marks entry grid rather than combining them into one figure. This is part of the exam scheme a school configures per year: exam types, maximum marks, weightage and components are all data, not fixed in the software.

Ecole builds the report card in your school's own format and layout, with your logo, done for you during onboarding rather than handed over as a template to fill in yourself. Schools do not edit templates directly in this version, so a change goes through us. Output is PDF, printed for a whole section in one action.

Yes. Once marks are entered and remarks are in, report cards print for an entire section in a single action rather than one child at a time. Output is PDF, in the school's own format built during onboarding. See what a principal oversees at exam time.

Yes, class teacher remarks reach the report card directly alongside the marks a subject teacher enters. This keeps the report card as one document rather than marks from Ecole plus a separate handwritten remark slip, which is the usual paper-era workaround schools end up patching together.

The marks entry grid refuses a mark above the subject's maximum as it is being typed, naming the child and the exam part it belongs to when it does. This catches the common slip of an extra digit immediately, rather than after report cards have already gone to print.

Not to a year that already has exams: applying a preset a second time is refused rather than merged into what already exists, to avoid quietly duplicating or overwriting entered marks. If you need to redo an exam scheme partway through a year, raise it with us directly rather than reapplying the preset yourself.

Ecole is one price, charged on the students actually enrolled and counted at the start of the academic year, billed once a year rather than monthly. We do not publish a rupee figure here because the number depends on your enrolment, and we would rather quote it properly than post a figure that turns out not to apply to your school. Call or message and you will have it in the same conversation.

No. Data migration and verification are included in the price; there is no separate data-entry or migration charge on top. The work of putting your admission registers, attendance history and mark sheets into Ecole is done by us as part of onboarding, not billed as an extra line item.

We have not published a fixed duration, since it depends on how much history you bring across. What is fixed is the order: your data goes in first, every class teacher checks their own section's list line by line, you run a full term in parallel with your existing registers as the authority, and we switch over only at a term boundary. See migrating from paper registers.

Ecole is billed once a year, on the students actually enrolled and counted at the start of the academic year, rather than a monthly per-student charge that moves as admissions and withdrawals happen through the year. This one-price approach also carries no per-SMS charges and no renewal escalation built in.

No renewal escalation is built into the pricing. The price is set on the students enrolled at the start of each academic year, so what changes year to year is your enrolment, not an automatic markup on the same seats. Export of your data stays free at any time, renewal or not.

No. There are no per-SMS charges in Ecole's pricing, since it does not currently send SMS or WhatsApp messages to parents at all; that is planned later as a paid add-on, not part of the base product today. The one price you are quoted covers what the product does now.

Ecole is built for schools, specifically the day-to-day running of attendance, marks, fees and admissions for a private school. It is not built for or offered to colleges or coaching centres at this stage. See what Ecole does for each role in a school if you want to check your school's setup matches.

Not yet. Ecole is built for schools; colleges and coaching centres are not served in this version. If that changes, it will be a deliberate decision made with actual users of that kind, not a quiet expansion of the same product. For now, treat Ecole as a school-specific tool.

No. Export of student and fee records is self-serve, available any time, without asking us and without a fee, renewal or not. This was a deliberate choice: a school's own records should not be held back by the software that runs them. See what makes the ledger trustworthy.

Onboarding itself can start whenever you are ready: we collect your existing registers and mark sheets first, whatever point in the year it is. The switch to running on Ecole alone still happens only at a term boundary, once a full term has run alongside your existing registers and reconciled clean, never in the middle of a term.

Yes. Export of student and fee records is self-serve, available any time, without asking us and without a fee. This is not a feature you have to negotiate at the end of a contract; it works the same on an ordinary Tuesday as it would if you were leaving. See what makes the fee ledger trustworthy.

Access follows roles: the principal, the correspondent, the front office and the accountant can take money and see fee records, each with their own scoped login rather than a shared password. A subject teacher, by comparison, only sees marks for their own subjects and sections. See what an accountant sees and does.

Support access is a grant created on demand, not a standing login: four hours by default, never more than eight, with the expiry enforced in the database rather than trusted to someone remembering to switch it off. A banner shows on every signed-in screen while it is active, and your school can see who held access and when at Settings, Access.

Yes. The database runs in AWS's Mumbai region and the application runs from Vercel's Mumbai region, so both the data and the running product sit in India rather than overseas. Each school also gets its own address, in the form yourschool.ecole-erp.com.

No. Each school's data is isolated at the database layer, and this is not just a policy statement: automated tests that try to read across schools are written to fail before any release goes out. Your records sit apart from every other school on the platform, by construction rather than by convention.

Yes, there is a log of who changed what, and separately of who opened a child's record or fee ledger. This exists so a question like who edited this student's attendance, or who looked at this family's dues, has a real answer rather than a guess, whether the person asking is your principal or an auditor.

No. The fee ledger is append-only for everyone, including us: a payment is never edited or deleted, by anyone. A genuine mistake is corrected with a reversal that references the original entry, and our own access to your data is limited to a support grant that expires by itself and shows on a banner while it is active. See what makes the ledger trustworthy.

A closed year becomes permanently read-only after promotion is committed, whether a student was promoted, detained, issued a transfer certificate, or marked as dropped. This keeps a completed year's marks and attendance from being altered afterwards, intentionally or otherwise, once the school has signed off on it.

Yes. There is a log of who opened a child's record or fee ledger, alongside the separate log of who changed what. This matters if a parent disputes a balance or a staff member's access needs reviewing; the answer to who looked at this does not depend on anyone's memory.

Ecole is built by JalsaX AI, based in Hyderabad. It is not a side project bolted onto something else; the fee ledger, attendance and exam handling described across this site are the actual product, built and supported by the same team you would call. What Ecole does for each role is a fair summary of the product itself.

The office is at Gokul Nagar, FCI Road, Mallapur, Hyderabad, Telangana 500076. If Mallapur is not convenient for you, that address does not have to be a barrier: you can call or WhatsApp +91 93920 94201, or email info@jalsax.com, without needing to visit at all. See our locations for the areas covered.

Call or WhatsApp +91 93920 94201, or email info@jalsax.com. The office itself is at Gokul Nagar, FCI Road, Mallapur, Hyderabad, Telangana 500076, but phone is the quicker route if you want pricing in the same conversation, since we do not publish a figure that could turn out not to apply to your school.

Yes. The office is at Gokul Nagar, FCI Road, Mallapur, Hyderabad, Telangana 500076, and it is where Ecole is built and where onboarding is run from. Call or WhatsApp +91 93920 94201 before you come, so we can arrange a time and walk you through Ecole live.

Get in touch and we will show you Ecole rather than describe it. Call or WhatsApp +91 93920 94201, or email info@jalsax.com, and say what your school's fee counter or attendance process looks like today; that is the fastest way for a demo to be useful rather than generic. Pricing comes in the same conversation, too.

Not yet. Ecole today is staff-only: there is no parent or student app, and no WhatsApp or SMS sent to parents, in this version. Parent communication is planned as a paid add-on later, but it is not part of what you are buying now, and we would rather say that plainly than let you assume it.

No, not currently. Ecole does not send WhatsApp or SMS to parents in this version; it is a staff-only tool, used by class teachers, subject teachers, accountants, the front office and the principal. Parent-facing communication is planned later as a paid add-on, not something to expect from the product as it stands today.

Ecole ships presets for CBSE and Telangana State (SSC) exam schemes and grading scales as a starting point, which your school checks and edits before its first report card. Beyond those two, exam types, maximum marks and weightage are all configuration per school per year, so another board's scheme can be set up the same way. See CBSE and Telangana State board.

Each school gets its own address, in the form yourschool.ecole-erp.com, rather than a shared portal where you pick your school from a list. This sits alongside data isolation at the database layer, so your school's address and its records are both kept apart from every other school on the platform.