NEP-2020 readiness checklist for school IT teams

The National Education Policy 2020 isn't a single specification — it's a framework that touches twelve different operational areas of a school. Most ERPs were architected before NEP existed and have bolted features on. A few were rebuilt around it.

Here are the twelve questions to ask your ERP today.

1. Continuous assessment with multiple kinds

NEP wants you to record more than one kind of assessment per term: term tests, project work, peer review, oral assessment, lab work. Your ERP needs a configurable assessment-kind catalog per class, not a hardcoded "marks out of 100".

Test: Can you add a new assessment kind ("class-wise peer review", weight 10%) from the admin UI in five minutes — without a code change?

2. Holistic Progress Card (HPC)

The CBSE HPC template has 50+ fields covering academics, co-curricular, sports, attendance, behaviour, and self-assessment. Your ERP should print this template natively. If your school does ICSE or a state board, the same engine should print their template — these are configuration, not code.

3. Mother-tongue / multilingual content

Report cards in two languages. Quiz questions translatable. Parent app text in the parent's preferred language. Your AI quiz generator multilingual — Hindi prompts producing Hindi questions, English prompts producing English ones.

4. Multi-disciplinary tracking

A class-9 student doing music alongside science needs both tracked. Cross-subject projects need attributable to multiple subjects. Your ERP's data model must allow a single "learning unit" to belong to multiple subject areas.

5. Skill-based progress

Numerical scores aren't the only measure. NEP wants per-skill tracking — communication, collaboration, critical thinking, creativity. Your ERP should let a teacher tag an assessment with the skills it measures and roll those up into a per-student skill profile.

6. Academic Bank of Credits (ABC) from Class 9

By the time a student joins college, their last 3 years of credits should already be in the ABC database. That means your K-12 ERP needs to:

• Compute credits per subject per term per student
• Store an ABC ID for the student
• Submit the credit-accumulation data to ABC in the prescribed format

This is the one most K-12 ERPs are quietly missing.

7. Vocational subjects from Class 6

NEP brings vocational education into the regular curriculum from Class 6. Your timetable engine needs to handle subjects that are taught in lab settings, in shorter slots, sometimes by external instructors. If your timetable can't model an external instructor with their own availability calendar, you have a problem.

8. Outdoor / activity-based attendance

NEP encourages experiential learning. Attendance for a field trip or sports practice needs to count without ruining your subject-period attendance reports. Your ERP should distinguish "class attendance" from "activity attendance" and report on both separately.

9. Bag-less days

Ten bag-less days per year, per NEP. Your ERP should let you schedule these in the calendar, suppress homework on those days, and not penalise attendance.

10. Anganwadi / pre-primary integration

Foundational stage (3-8 years) is now part of school. If you run pre-primary as well, your ERP needs to handle different curricula, different parents, and the eventual handover to formal Class 1.

11. Parent participation tracking

NEP wants parents in PTA, in school management committees, in their child's learning. Your ERP should track parent engagement — meeting attendance, response to messages, participation in events. Not for surveillance — for follow-up with parents who've fallen off.

12. NEP-aligned assessment reporting to government

State governments are starting to ask for NEP-aligned data dumps. Your ERP should generate the reports your state expects, in the format they expect.

This is the checklist we built School Console against. Every item above is either shipped or in our active build plan. Request a demo if you want to see them on your data.