Most centres already run something. This has to live inside it.

A coaching centre that has spent three years getting its staff to record attendance in one place does not want a second place. So the first question is rarely “does the marking work” — it is “where does the marking live, and who has to log into what.” There are three honest answers, and they cost very different amounts of your time.

One: the marking on its own

A teacher-only tool. Upload the question paper, the sheets come in as photographs or a batch scan, the marks come back and the teacher approves them. Nothing else changes, nobody else gets an account, and no data moves out of whatever you already use for fees and attendance.

This is the right answer more often than people expect, and it is the one that starts this week rather than next month. It is also the one charged purely on pages marked.

Two: the marking inside our platform, under your name

The checking is one part of a larger system — attendance, timetables, tests and DPPs, fees, doubts, batch analytics and the weekly report that goes to parents. Described in full here. Taken this way it runs on your own subdomain with your logo and your colours: students and parents see your institute, not ours.

The work here is configuration rather than engineering — your batches, your subjects, your fee structure, your report format — and it is measured in days.

Three: built into the system you already run

The case this page exists for. A school with an ERP it is not going to replace. A centre whose parent communication already runs somewhere specific. A chain that wants the marks to land in its own dashboards rather than in ours.

Be warned what this is and is not. There is no self-serve API key, no plug-in directory and no one-click Zapier connector, and any vendor in this category telling you otherwise is describing a roadmap. What there is, is a small team that builds the join for you: agreeing what moves in each direction, where the student roster is authoritative, what happens when the two disagree, and then writing it. That is weeks, not days, and it is quoted as a build rather than charged per page.

What usually has to be decided first

• Which system owns the student roster. Two systems both convinced they are authoritative is the failure that turns up in month three, not week one.
• Whether marks flow back. Reading a roster in is easy. Writing marks into someone else's gradebook is where their software's assumptions start mattering.
• Who approves. The teacher approval step is not optional here, so wherever the marking lives, a teacher has to have a screen to approve on.
• Where the data sits. Student data belongs to the institute and almost all of these students are minors. Moving it between two systems is a decision with a privacy answer, not just a technical one.

Common questions

Do you have an API for answer sheet checking?

Not a public, self-serve one, and we would rather say that than imply otherwise. Integrations are built per customer, against what your system actually exposes, which is usually the only way it works anyway — Indian coaching ERPs vary enormously and a generic connector tends to fit none of them properly.

Can the marking write back into our existing gradebook?

Usually, if your system can accept marks from outside — an API, a file drop, even a structured export. The part worth checking early is not whether marks can be written but whether your gradebook can represent what we produce: per-question marks with written feedback, not just a total.

How much does a custom build cost?

It is quoted, not listed, because the range is genuinely wide — reading a roster from a system with a clean API and building a two-way join into one without are different projects by an order of magnitude. Page-based charging covers the marking itself; the build is separate and priced once we have seen what we are joining to.

What if we want to start small and decide later?

That is the usual and the sensible order. Run the marking on its own for a term, find out whether your teachers actually use it, and only then pay anyone to wire it into anything. Nothing about starting at option one makes option three harder later.