Show employers the courses and projects your students actually did, not just a branch and a CGPA. Proof of the courses and projects your students actually did.

ReadyHo

What runs at your college

A first draft score, ready in minutes

Your teachers stop marking from a blank page. Every piece of work comes back scored on each part of the scorecard, with a written reason for each score. Your teacher then reads it and decides the real mark.

Why this exists

Your teachers do not have the time

One teacher, three hundred pieces of work, five things to mark on each. That is 1,500 separate judgements in a single semester.

So it does not happen. Students get a number and a line of comment, weeks late. The teacher is not lazy. The time is not there.

The software reads all three hundred first, so your teacher starts from a draft.

What it does

What comes back

Within minutes of a student handing work in, four things land in your teacher's queue.

  • A score for each part of the scorecard. Not one mark for the whole thing.
  • A written reason for every score, pointing at the exact part of the work it came from. A clause number. A paragraph. One sheet in a set of drawings.
  • A note of which system produced it, so the same work can be checked again later.
  • A draft, marked as a draft, waiting for the teacher who set the project.

Nothing else happens. The student is not told. No score goes out. The draft stays on your own servers, and nothing is published without consent.

Draft score · Contract work, section 9 Illustrative
Status Draft. Waiting for the teacher.
2. Developing Sharing of risk
The cap in clause 9.1 protects the supplier and leaves the client exposed.
3. Competent Holds up under Indian law
Clause 9.2 copies wording written for United States contracts. Indian law handles this under section 73 of the Contract Act.
3. Competent Clear obligations
Clause 4 names a payment date, an amount, and what happens if payment is late.
An example. The scorecard here is a law one, and the same thing runs against a scorecard for any subject. Every score shown is a draft the teacher can raise or lower.

The rule that never bends

A machine can write a score. Only a person can give one.

No student ever sees a machine score on its own. Every score is labelled as a draft, on every screen it appears on, until a teacher approves it.

If no teacher reviews a submission, the student gets nothing. No professional is invited. No record is made. There is no setting that turns this off.

How teacher review works

The output

Why a score for each part, not one mark

A single mark is a verdict. A score on each named part is something a person can check and correct.

  • Your teacher can disagree with one line. Five scores, two wrong. Change the two, keep the three.
  • The student learns what to fix. A 58 out of 100 tells them nothing. A score on sharing of risk, next to a description of the level above, shows them what better work looks like.
  • Reasons can be checked in seconds. A score that names clause 9.1 is checked by reading clause 9.1.

Any subject

Any subject you teach

The software does not know or care what subject it is being used for. Your teachers write the scorecard, so they set what is marked and what good looks like.

We publish a few scorecards so you do not start from nothing. Law, architecture and design so far. They are a starting point, not a limit. Use them, change them, or ignore them.

Cost

What it costs to run

70 to 400 rupees per student per year

At around ten submissions each. It moves with document length and the system you choose.

Limits

What it does not do

  • It does not decide the mark. Your teacher does, every time.
  • It does not talk to students. Feedback reaches a student only after a teacher approves it.
  • It does not check who wrote the work. There is no plagiarism checking and no detection of machine written text. We do not claim either.
  • It does not mark anything your scorecard leaves out. Effort, attendance and presentation are not scored unless you put them on the scorecard.
  • It does not run or test the work. Where a test can already tell you whether work is right, such as running code, that tool does the job better. This layer earns its place where there's no single right answer and the judgement is the whole point.

Next step

Get started

ReadyHo is free and open source. It runs across your departments, and a college can start with one course or roll it out widely. You keep everything that comes out of it.

Get started See how the whole loop works

The rest of what runs at your college

  • Set the work Your teacher writes the project and a simple scorecard once, then reuses both every year.
  • Collect the work Send a project to one student, a group, or a whole year. The actual work comes back in one place.
  • Your teacher decides Your teacher sees the work and the draft side by side, changes anything they disagree with, and sets the mark.
  • An industry signature A working professional checks the same work and puts their name and credentials to it.
  • The proof The work, the scorecard, all three opinions, and who gave each one. One page an employer can open.
  • Student control Nothing is published unless the student says so, and they can change their mind at any time.
  • Cost control You hold the account, pick what it uses, and set a spending limit. Nothing is billed through us.
  • Your servers One install on your own machine. Student work, drafts and marks never leave your college.