Every Question Schools Ask Before They Decide

Your ERP records what happened. Ocoviz tells you what's about to happen — and what to do about it. Most school ERPs are excellent at storing data: attendance registers, mark sheets, fee records. What they don't do is connect that data, spot patterns, or proactively flag that a student is heading toward a problem before it shows in exam results. Ocoviz is an intelligence layer on top — not a replacement for your ERP.

You don't need to switch — that's the point. Ocoviz integrates with your existing systems rather than replacing them. Your attendance data, mark sheets, and student records don't move; Ocoviz reads them and layers intelligence on top. The onboarding ask is a one-time data import, not a full system migration. Most schools are fully set up within 48 hours.

No. Government portals like UDISE or CBSE's own systems are compliance reporting tools — they're not designed to give you real-time intelligence. Ocoviz sits alongside these, pulling from the same underlying data your school already captures, without duplicating your compliance obligations or interfering with mandatory reporting workflows.

This is the most common concern we hear — and it's the one we've designed against most carefully. Ocoviz reduces the manual work teachers do today: compiling attendance summaries, writing risk assessments, preparing progress notes. Pilot schools reported an average of 12 minutes saved per teacher per day in admin overhead. The Risk Radar doesn't ask teachers to do more — it surfaces what they'd otherwise spend time hunting for themselves.

This is a real concern and one worth addressing directly with your staff. Ocoviz is designed to give teachers a view of their students — not a view of teacher performance. The Risk Radar is framed explicitly as a co-teacher that catches what's easy to miss across 40+ students, not as a monitoring system. That said, how you introduce it to your team matters. We'll walk you through an internal rollout conversation as part of onboarding — because adoption depends on framing as much as features.

Yes — and this was a core design constraint. The interface was built for a teacher managing a full workload with limited screen time, not for someone who wants to configure dashboards. The most-used view (the daily class risk summary) requires exactly three taps from login. Guided onboarding takes under one hour per teacher, and we provide a simple reference card for the first few weeks. If a teacher can navigate WhatsApp, they can use Ocoviz.

Partial adoption reduces the value — but doesn't break it. Ocoviz's risk scoring works on whatever data is flowing in. If some classes are logging attendance and assessments consistently and others aren't, the platform flags the gap so the principal knows which classes to follow up on. Full adoption is the goal, but partial adoption still gives leadership a clearer picture than before.

For a typical school of 500–2000 students: 48 hours from sign-up to live dashboard. Day 1 is data import (student records, class structure, teacher mapping) — our team handles this with you. Day 2 is teacher walkthroughs — one session per department, under an hour each. By Day 3, the Risk Radar is collecting signals and the principal dashboard is live. We don't leave you with a manual and a phone number.

Starting mid-term is actually common — and in some ways better, because you get immediate signal from live data rather than waiting for a new session to begin. The platform needs about 2 weeks of data before risk scores stabilise. If you're in the second half of a term, that's still enough runway to act on early warnings before term-end. The worst time to start is after the problems have already shown up in results.

Typically three people: the principal (to approve the rollout and set role-based access), one admin staff member (to coordinate the data import), and ideally one tech-comfortable teacher to be the internal champion during the first week. You don't need a dedicated IT person or a technical coordinator — our onboarding team handles the heavy lifting.

Most schools we work with are in exactly this situation. Our import process accepts data in common formats (Excel, CSV, even structured PDFs) and our team works through the cleanup with you. It adds a day or two to onboarding but doesn't block it. Going forward, data entry happens directly in Ocoviz — so the messiness is a one-time problem, not an ongoing one.

No. We do not sell, rent, or share student data with advertisers, data brokers, or any unrelated third party. Ocoviz's business model is a school subscription — your data is never the product. This is written into our data processing agreement, not just a policy we cite verbally. See our Trust & Security page for the full breakdown.

All data is stored and processed on servers located within India. No student or school data crosses Indian borders for storage or AI processing. This is a core architectural decision — not an afterthought.

You own your data — always. On request, we provide a complete export of all your school's data in a usable format (CSV/Excel). After offboarding, data is permanently deleted from our systems within an agreed retention window, confirmed in writing. We don't hold your data hostage to prevent switching.

This is an area where Indian education law is still evolving, particularly with the DPDP Act 2023 coming into effect. Our onboarding includes a model parent consent clause you can add to your school's standard admission forms — covering how student data is used within the school's own systems. We actively track regulatory changes and update our guidance accordingly. We'd rather flag this honestly than pretend it's already fully resolved.

Ocoviz is priced in annual tiers based on your school's verified student strength — not self-reported numbers. This means pricing is transparent, predictable, and doesn't change mid-year unless your school's actual enrollment moves to a different band. We'll share exact tier pricing during your demo conversation, since the right tier depends on which modules your school needs and your student count.

We'll give you the tools to make this easy. After your demo, we provide a one-page ROI summary you can share with your trust — showing time savings per teacher, risk reduction outcomes from pilot schools, and a cost comparison against the manual work Ocoviz replaces. We can also schedule a separate 20-minute trustee briefing if that helps move the conversation forward faster.

Yes — we offer a 30-day pilot for qualifying schools, which includes full platform access across your chosen modules, onboarding support, and a results review at the end of the trial period. There's no credit card required to start. If the pilot doesn't show measurable value for your school, you walk away with no obligation. We'd rather earn your subscription than lock you into one.

No — and smaller schools often see faster results. With fewer students, signals are easier to act on and the principal has direct visibility into every flagged case. Our entry tier is designed for schools under 500 students. If anything, a 300-student school with one attentive principal using Ocoviz daily can move faster than a 2,000-student school still figuring out internal processes.

The Risk Radar scores each student across five dimensions: attendance trend (not just today's mark, but the pattern), assessment performance trajectory, engagement signals (participation, submission rates), peer comparison within their class, and teacher-flagged notes. A student doesn't get flagged for one bad day — the model looks for correlated signals across multiple dimensions over time. A student who misses 3 days, drops 15 marks on an assessment, and stops submitting homework in the same two-week window will score high risk. Any one of those alone typically won't.

Yes — false positives happen, especially in the first 2–3 weeks before the model has enough baseline data. This is why Ocoviz is designed to support teacher judgment, not replace it. A flagged student is a prompt for the class teacher to check in — not an automated intervention. Teachers can dismiss a flag with a note, which helps the model calibrate. Think of it as a very attentive colleague tapping you on the shoulder — you still decide whether to act.

The web and mobile apps require an internet connection to sync data and update risk scores. Offline mode (capturing attendance locally and syncing when connected) is on our roadmap for 2026. If your school has reliable connectivity during school hours — even 2G on a mobile hotspot — the core attendance and assessment modules work fine. The AI processing happens server-side, so it doesn't require a fast connection on the teacher's device.

No — and this is intentional. Ocoviz amplifies what a good teacher can already do; it doesn't replace the human judgment, relationship, and care that defines great teaching. The platform's job is to make sure no student falls through the cracks unnoticed. What happens after a flag is raised — the conversation, the intervention, the support — is entirely in the teacher's hands. We're the early warning system; teachers are still the solution.

This is a fair concern to raise with any early-stage EdTech platform. Here's our honest answer: Ocoviz is founder-led, growing, and actively onboarding schools across Punjab — but we're not a decade-old company with a long track record yet. What we can commit to: your data is always exportable in full, you're never locked in, and we'll give you 90 days' notice of any material change to service. The 30-day pilot is specifically designed so you see real value — or you leave — before making a long-term commitment.