NEP 2020 and Your School Software: What Actually Has to Change

Ask a school software vendor whether their product is NEP 2020 compliant and most will say yes. It is not a meaningful answer, because there is no NEP certification for software and no body that issues one. NEP 2020 is education policy. It does not specify a database schema.

What it does do is change what schools have to record, assess and report — and some of that lands squarely on your software. This guide separates the three categories: what genuinely requires a capability your system may not have, what is configuration you can do this afternoon, and what nobody can sell you yet because the government process is still settling.

The parts that genuinely touch your software

1. The holistic progress card

This is the big one, and it is where most report-card engines fall over.

The traditional Indian report card is a marks table: subjects down the side, terms across the top, a total and a rank. NEP’s holistic progress card asks for something structurally different — a record of the child across cognitive, socio-emotional and psychomotor domains, including self-assessment, peer input and teacher observation alongside academic attainment.

Three software capabilities follow from that, and they are worth testing specifically:

• Descriptive and rubric fields alongside numeric marks. Not a "remarks" text box bolted onto the end, but assessable areas with defined levels that a teacher selects and that print properly.
• More than one contributor per student per term. A subject teacher, a class teacher, the student themselves. Most mark-entry screens assume exactly one author per subject.
• A layout engine that is not a marks table. If the report card template is hard-coded, no amount of configuration will produce a holistic card.

The question to ask a vendor: "Show me a report card with a descriptive rubric section and a self-assessment field, printed." Not a slide about it — the actual output. Our examinations page sets out what our grading schemes do and, in the limits section, what they do not.

2. Competency-based assessment

NEP pushes assessment away from content recall and towards competencies and learning outcomes. In practice this means an assessment is tagged to a competency, and you want to be able to report on the competency across a class rather than only on the paper.

Software-wise this needs a layer most systems do not have: a competency framework you can define, and marks that attach to it as well as to a subject. Many products handle this partially — you can name an assessment after a competency, which gets you a label but not the analysis.

Be realistic when evaluating. Ask whether you can produce a report showing how a class performed against a specific learning outcome across two terms. If not, you can still run competency-based assessment; you will just do the analysis outside the system.

3. The 5+3+3+4 structure

Foundational, Preparatory, Middle and Secondary stages replace the older primary/secondary split, and the Foundational stage now formally includes three years of pre-primary.

For most software this is genuinely configuration rather than a rebuild — classes get grouped into stages, and reporting rolls up by stage. Two things do bite:

• Schools that did not previously run pre-primary in the same system now need Nursery, LKG and UKG as real classes with real records, not a separate register.
• Promotion rules differ by stage, and a promotion screen that assumes one rule for the whole school will need per-stage handling. Our student information module treats promotion as a reviewable mapping with per-student exceptions for this reason.

4. Data quality, for APAAR and UDISE+

APAAR — the Automated Permanent Academic Account Registry — gives each student a lifelong academic identity, generated on the back of verified UDISE+ data.

The important thing to understand is that the software requirement here is upstream of APAAR itself. Generation happens on government portals. What your school needs from its own system is data clean enough to survive matching: names spelled consistently with the birth certificate, correct dates of birth, parent details, and Aadhaar where you hold it — all matching what you filed on UDISE+.

That sounds mundane and it is the part that actually causes trouble. Schools that kept student names in three places now discover that "Aarav Sharma", "Aarav Kumar Sharma" and "A. K. Sharma" are one child, and that the UDISE+ filing used a fourth version. A single student record with document verification is the fix, and it is worth doing before you need it. Be sceptical of any vendor claiming end-to-end APAAR automation; the process is still settling.

What is configuration, not capability

Several things people worry about turn out to be settings in any reasonable system:

• Grading bands and boundaries. A1/A2/B1 with your cut-offs, or a nine-point scale, or descriptive grades. If these are values you set, you are fine.
• Term weighting. Periodic assessment at 10%, half-yearly at 30%, finals at 60% — or whatever your school decides.
• Scholastic and co-scholastic separation. Long supported for CBSE and directly reusable for NEP’s broader domains.
• Subject naming and the addition of vocational or skill subjects.

If your current software forces you into one grading model, that is a real limitation — but it is a limitation it had before NEP too.

What nobody can sell you yet

Two areas where a confident vendor answer should make you cautious rather than reassured:

Automated APAAR generation from inside the ERP. The workflow runs through government portals and depends on UDISE+ verification. A vendor promising one-click APAAR for your whole school is describing an aspiration.

A single national holistic progress card format. Implementation varies by state and board, and formats are still being issued and revised. Configurability is what protects you here — not a template that matches one circular from 2024.

A practical sequence for a school

1. Clean the student record first. One authoritative name, verified date of birth, guardian details, documents attached. Everything downstream — APAAR, UDISE+, transfer certificates — depends on it, and it is the least glamorous and most valuable work.
2. Map your classes to the four stages and check that reporting rolls up correctly.
3. Redesign one report card, for one class, for one term. Not the whole school. Find out what your software can and cannot print before you commit the academic calendar to it.
4. Add descriptive and self-assessment fields to that one card and see whether teachers can actually complete them in a reasonable time. If a holistic card takes twenty minutes per child, it will not happen at scale, and that is a process problem rather than a software one.
5. Only then roll it out.

Questions to ask your vendor

1. Show me a printed report card with a descriptive rubric and a self-assessment section.
2. Can two different staff members contribute to the same student’s assessment in the same term?
3. Are grading bands, boundaries and term weights values I set, or values you assumed?
4. Can I map classes to the 5+3+3+4 stages and report by stage?
5. What is your honest position on APAAR — what do you do, and what happens on the government portal?
6. What does this not do for NEP?

That last question again. A vendor who answers "we are fully NEP compliant" has told you nothing checkable; a vendor who says "we do configurable rubrics and stage mapping, we do not do competency-level analytics across terms" has told you something you can act on.

Where to go next

If you are evaluating systems with NEP in mind, the features checklist covers what to look for module by module, and how to choose school management software sets out the demo questions. For the record-keeping foundation that APAAR and UDISE+ both depend on, see student information.

Primary sources

The rules described above come from the regulators and portals themselves. Where this guide and an official source disagree, the official source is right.

• Ministry of Education, Government of India — The department that issued NEP 2020 and publishes the policy text.
• UDISE+ — The reporting portal the policy relies on for school and enrolment data.