SchoolDeck runs a CBSE school against one student record: admissions and the PEN, period-wise attendance, fee heads and instalments, internal assessment in the CBSE structure, and report cards in your existing format. Data needed for OASIS and the List of Candidates is held in the fields those returns ask for, so filing is an export rather than a retyping exercise.
We do not file returns for you and cannot submit to CBSE portals on your behalf. What we remove is the retyping and the reconciliation before the filing.
The specific pain of a CBSE school is not the teaching. It is that the same student appears in the admission register, the attendance sheet, the fee ledger, the internal assessment sheet and the List of Candidates, and that at some point in the year those five disagree with each other.
They disagree because each was maintained separately. A name gets corrected in one place, a section change happens in another, a candidate is withdrawn in a third. By the time the LOC has to be right, someone is reconciling five sources by hand against a deadline.
A return is painful in proportion to how far its fields sit from where the information is actually known. The mother’s name as it must appear on a certificate is known at admission. The candidate’s subject combination is known when the option is chosen. The practical marks are known by the teacher who ran the practical.
So they are collected there, in the format the return wants, at the moment somebody knows the answer. The alternative — collecting loosely and normalising in February — is where the week of retyping comes from.
CBSE’s internal assessment structure is a set of components with weights. The software’s job is to hold the components, apply the weights, and show the teacher what the composite comes to — not to decide what a child is worth.
We do not compute a predicted board grade, and we do not generate a remark and publish it under a teacher’s name. Both are things software can technically do and should not: a predicted grade gets treated as a fact by parents, and an auto-written remark is a signature on someone else’s sentence.
Nothing here integrates with a CBSE portal, because no such integration is available to vendors. Any product claiming to file OASIS or upload an LOC automatically is describing a person with your credentials doing it manually, and you should ask which person.
What is genuinely automatable is everything up to the file: the data being complete, internally consistent, and formatted the way the portal expects when it is exported.
Phrased the way they arrive, answered so each one stands on its own.
No, and no vendor can — the portal has no integration for third-party software. SchoolDeck holds the candidate data in the fields the LOC asks for and exports it in that shape, so the person filing is checking a file rather than assembling one.
Yes. The report card is reproduced in the format your school already issues rather than a generic template, and each academic year keeps its own version so a reprint of a past year comes out as it was originally issued.
Yes. The board is a property of the enrolment rather than of the school, so two streams coexist with their own assessment structures, their own report card formats and their own calendars, on one student roll.
It sits on the student record alongside the admission number and is captured at admission. It is not a separate register, so a student who leaves or transfers updates in one place.
Checked by the Implementations desk on 7 September 2026. Corrections go in the page, dated, rather than quietly.
Pricing is on the page, in the open, with the counting rule written next to it. Nobody has to book a call to find out what it costs.
See pricingForty minutes with an implementation engineer — your classes, your fee heads, your grading scheme, entered as we go. No slides, no sample school.