What a CBSE school ERP should support in 2026

School obligations and ERP buying criteria

A school buying an ERP in 2026 needs to consider academic assessment, student data and well-being together. Start by identifying the school’s responsibilities, then ask which parts the software can support and which remain with staff, counsellors and school policy.

CBSE Circular 02/2026, dated 19 January 2026, amends the counselling provisions of its affiliation bye-laws and distinguishes socio-emotional counselling from career counselling. The Supreme Court’s July 2025 judgment in Sukdeb Saha requires educational institutions to adopt a mental-health policy drawing on UMMEED and related initiatives. Neither document should be presented as a prescription for a particular ERP product.

HPC: follow the evidence into the progress card

PARAKH has developed Holistic Progress Cards for the Foundational, Preparatory, Middle and Secondary stages. They connect progress with competencies and multidisciplinary activity. A useful purchasing test therefore follows a teacher’s evidence through to the learner’s report, using the framework relevant to the school’s stage.

Ask the academic coordinator to bring one classroom activity to the demo. The vendor should show how a teacher selects the relevant competency, records an observation, reviews progress and prepares the report. Check how an incomplete entry or a correction is handled, and whether information must be typed again elsewhere.

Ask during the demo

Show us one learner’s journey from a classroom observation to a reviewed HPC. Then correct the observation and show which records and reports change.

• Stage-appropriate curricular goals, competencies and descriptors.
• Concise evidence entry with the date and responsible teacher.
• Teacher review and correction before publication.
• Learner, peer and parent inputs where the applicable framework calls for them.
• A clear report and a usable export when the school changes systems.

DPDP: buy for a documented readiness plan

As of this guide’s review date, the DPDP framework has phased commencement. G.S.R. 843(E) places core Act duties, including sections 3–17, in the group starting eighteen months after Gazette publication. Rule 1 of the 2025 Rules phases their start too. The procurement implication is to prepare during 2026 and verify each applicable provision’s start, rather than describe every DPDP duty as already enforceable.

The Rules address parental-consent verification and conditional exemptions for children’s data, including defined educational uses. These are purpose-specific provisions, not a blanket exemption for every school or vendor. Record the school’s interpretation for each use and have the appropriate adviser review it.

Ask the vendor to walk through a student’s data lifecycle: admission, use, sharing, correction, retention and exit. The school needs both working controls and a written account of who is responsible when something goes wrong.

Ask during the demo

Export one student’s record, correct a field and show how that correction reaches connected systems. Explain how temporary migration copies and backups are handled at exit.

• A field inventory, purposes and a list of integrations receiving student data.
• Support for the school’s notices and consent or other applicable processing basis.
• Named accounts, appropriate access controls and prompt removal of staff access.
• Evidence of protection in storage and transfer, backups and incident coordination.
• A tested correction, export and deletion process with defined retention exceptions.
• Written processor terms and a dated plan for any missing capability.

UMMEED: support the people responsible for care

UMMEED describes a whole-school approach involving a School Wellness Team, staff capacity, timely response and review. Software can help coordinate the school’s process. Counselling, referral decisions and care require trained people.

For staffing, CBSE’s January 2026 circular states a socio-emotional counsellor ratio of one per 500 enrolled students. Read the separate career-counsellor provision and its qualification conditions too. The Supreme Court’s July 2025 guidelines also address professional support, referrals, staff training and reporting. Have the school assess these overlapping responsibilities rather than use an ERP checklist as a staffing calculation.

In a vendor demo, use a fictional concern and follow it from the reporting teacher to the person responsible for review. Confirm how urgent concerns reach a trained person immediately under the school’s protocol; a software queue must not delay that response.

• Clear referral contacts and named responsibility for each follow-up.
• A factual record of the observation, action and next review date.
• Appropriate communication with the learner and family under school policy.
• Separate coordination for socio-emotional support and career guidance.
• Aggregate review of completed actions without circulating private case narratives.

Counsellor records: demonstrate who can see what

UMMEED calls for securely maintained records, with access limited to the School Wellness Team and concerned people. A broad “staff” permission is a poor buying test for this information. A classroom observation, a referral status and a counsellor’s detailed notes serve different purposes and need different sharing decisions.

The following is a recommended permissions scenario, not a universal legal access rule. Ask your counsellor and safeguarding lead to define the actual boundaries. Then test them in the proposed ERP or a separate secure record system. Check search results, notifications, exports and reports as well as the main screen.

A useful stopping point

If a vendor cannot demonstrate the required separation of access, keep detailed counsellor records in an approved separate system. Decide what limited referral information can safely be coordinated through the ERP.

• Log significant access, edits, sharing and exports without copying private narratives into the log.
• Keep session-note text out of routine dashboards, messages and HPC reports.
• Make any emergency access controlled and reviewable under the school’s policy.
• Agree retention, secure disposal and transfer when a counsellor leaves.

Run a demo with five practical scenarios

Use fictional student data and the same scenarios for each shortlisted vendor. Invite the academic coordinator, administrator, counsellor and person responsible for data governance. Each should test the work they will actually perform.

1. 1. Create and review an HPC

   Record one activity, add evidence, review the descriptor, correct an entry and produce the parent-facing report. Ask how a framework update affects historical records.

2. 2. Trace a student-data request

   Locate a record, correct an error and produce an authorised export. Explain deletion, retention exceptions and responsibility for copies in integrations or backups.

3. 3. Coordinate a support referral

   Record a concern, assign an owner and follow-up date, and show how the right person receives it. Explain the school’s immediate-response route for urgent concerns.

4. 4. Challenge record permissions

   Open the same fictional case as a teacher, counsellor, principal, parent and finance user. Try search, report generation and export. Inspect the relevant activity log.

5. 5. Test a handover and exit

   Remove a staff account, transfer authorised responsibilities and export the school’s data in a usable format. Obtain the exit process, time and cost in writing.

A checklist to compare shortlisted vendors

For each row, record “demonstrated”, “requires another system”, “planned” or “not available”, plus the evidence and owner. A roadmap promise should have a delivery date and contract consequence. Resolve any failed privacy or access test before selecting a system to hold confidential records.

Agree implementation, cost and ownership

Put the agreed workflows, access boundaries and acceptance checks into the implementation scope. If confidential records will sit in a separate service, name who administers it, what the ERP receives and how duplicate copies are avoided. Schools can choose that architecture deliberately rather than force every record into one database.

Compare the full cost of implementation, migration, staff training, hosting, support, integrations and exit. Pilot with a small team and fictional records before moving sensitive information. Make the academic lead responsible for HPC acceptance, the counsellor for the confidentiality workflow and the school’s data owner for governance and vendor terms.