What runs at your college
Send the project out. Get the work back.
One action sends a project to a student, a group, or a whole cohort. Students hand in files, drawings, writing, and forms in one place, and the work is locked once it’s in.
What it does
What your college gets
- Assigning takes one action.
- The teacher picks who gets it. The task, the format, the deadline, and the scorecard are already set in the project.
- Students learn the screen in one sitting.
- It’s a list of what’s due and a place to put the work. Nothing else to teach them.
- The work is locked when it’s handed in.
- It stops changing. A score, a teacher’s comment, and a professional’s feedback still point at the same version two years later.
- The work stays on your servers.
- Submitted work, drafts, and marking stay on your own infrastructure. Only a finished, approved record for a student who agreed to it goes to the public page.
On screen
What a student sees
The shape of the work
Files, writing, drawings, and forms
One submission can hold several kinds of work at once, because a drawing, a document, and the reasoning behind them are usually one piece of work.
| Subject | What a student hands in |
|---|---|
| Law | A drafted clause and a note to the client. Documents and writing. |
| Architecture and design | Drawings, boards, and the reasons behind the choices. Several files, plus text. |
| Management | A recommendation with the workings behind it. A document, a spreadsheet, a short form. |
| Journalism | A reported piece, the interview log, the sourcing. Text typed in, with audio and images. |
| Engineering design | A proposal, the calculations, the reasoning. Drawings, documents, and text. |
| Teacher education | A lesson plan, the materials, a reflection. Documents, text, a short form. |
Those are examples of the kind of work, not a list of the subjects we support. Nothing in the software knows what is being taught. One college can run law, journalism, and music on the same installation.
How it works
Five steps, in this order
- 01
The teacher picks who gets it
One student, a group working together, or a whole cohort, in a single action.
- 02
The student opens the brief
It says what to do, what to hand in, and by when.
- 03
The student hands the work in
Several files, text typed straight in, and short forms, all in one submission.
- 04
The work is locked, and marking starts
Submitted work stops changing, so every comment made about it later still refers to the same version.
- 05
The work stays where it was handed in
Submissions, drafts, and marking stay on your infrastructure. Only a finished, approved record for a consenting student reaches the public page.
Next comes a first draft score with comments, ready in minutes. Then your teacher reads it and decides the real mark.
The obvious question
It sits next to Moodle. It doesn’t replace it.
Most colleges that would use this already run a system that collects files. That isn’t the gap. What they don’t have is marking against a shared scorecard, checked by a working professional from industry.
Course delivery is not part of ReadyHo. It runs alongside Moodle and your student records rather than replacing them, and your college decides which system holds the course.
Why would students hand work in twice?
For ordinary coursework, they shouldn’t. This is for the few projects meant to produce a record an employer can check. Our cost model assumes around ten of those per student per year.
What it does not do
What this part does not do
- No course delivery. No lectures, reading lists, schedules, attendance, or discussion. A project brief is the only thing a student reads here.
- No file storage. Work is held because it’s being marked. This is not a document store, and not a portfolio students keep work in.
- No plagiarism checking. Work isn’t compared against other students or against anything on the internet. Neither the score nor the finished record says anything about whether the work is original.
- No other grades. Attendance, exams, internal marks, and course grades stay in your existing systems. Nothing here writes to a transcript.
Everything here is about one project. Any claim wider than that, about a student’s honesty or about a student overall, is outside what the software will say.
Choices your college makes
- How one group submission produces a record for each member of the group.
- Whether a student sees the full scorecard before handing work in.
- Whether late work is refused, marked late, or left to the teacher.
Work that is not text is read less directly
A written clause or a reflection is text a computer can read against a scorecard point. A floor plan or a presentation board is not. Where it reads those less well, the first draft counts for less, and the teacher and the professional count for more.
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.
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.
- First draft scores Every submission comes back scored against your scorecard, with comments. No student ever sees this part.
- 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.